Repeat: Question about NeOS

Since I don’t yet have low-level functions for working with disk (they haven’t brought them to me yet), I decided to work on the NeOS command interpreter.
The essence of Subj is this: Specky’s screen is quite narrow (especially if the driver is 42 or 32 characters in line), and the path (current directory) can be
quite long and not fit in one line, which is not very convenient.
Therefore, there are two ways out of this situation:
1. Abandon the usual MS-DOS type: path:>command, that is,
do not constantly show the path, but show it by a special command.
2. Do not show the path, but introduce a special mode when the path is shown.
I.e. it will look something like this: enter the DISK command (for example) and
NeOS goes into path display mode. Exit via EXT.MODE. Moreover, the path can
be shown according to the MS-DOS principle, or constantly, for example, at the top,
and it will not scroll, since it will not enter the text window.

So I don’t know how to do it. So far, option 2 seems prettier (it’s not always
convenient to call a path on command).

With respect, Roman aka Megus of Brainwave Association.

[Team ZX-Spectrum] [Team Agatha Christie] [Team Metallica] [Team Iron Maiden]

19 Aug 98 Roman Petrov, hoping that everyone will read it, wrote:

RP> 2. Do not show the path, but introduce a special mode when the path
RP> is shown.

This option is suitable imho.

Please, add the latest BIOS information here!

Area: .NETMAIL
From: Alexander Kormishin, 2:4616/11.3
To: Roman Milukov, 2:4616/7.8
Subj: Firmware.
--------------------------------

[skip]

P.S. I was looking at the BIOS help and for some reason I didn’t see any disk errors there (maybe the old help was copied from you).
The errors are described there, but Err sec, No disk, Write protect etc are not there.
I’ll probably give the turboloader to Roman Petrov, and then let him
convert it to the BIOS, everything there is in Russian-English scheduled.

P.P.S. Yesterday I already formatted the disk for 1.44 MSDOS.

[skip]

Well, that's it. Goodbye, Roman.
Sincerely, Sasha.

- --- Posted by LARA v1.50.
* Origin: >>> aim here >>>---------------------------------

All the best.
Roman.

RM> This option is suitable imho.
Okay, I’ll implement it, otherwise for now (due to the lack of disk functions until recently
the first one was implemented.

RM> Please, add the latest BIOS information here!
OK! Today I’ll add information on the drivers, sort the functions in Help
in their numerical order, number them and upload them.

RM> P.S. I was looking at the BIOS help and for some reason I didn’t see any disk errors there
RM> (maybe the old help was copied from you).
That’s right, the old help. At that time it was simply not known what errors
would be required, although the standard three were still known. Now disk
errors are already included in help, since work has begun on disk functions.
RM> I’ll probably give the turboloader to Roman Petrov, and then let him
RM> convert it to the BIOS, everything is written there in Russian-English.
Thank you, share if you can. Actually, they already wrote to me, but it’s just that the driver that they wrote to me does not define read-only and no disk. Yes,
loader (and saver, too, by the way) should be able to load and write a block of
sectors to disk with an arbitrary sector size and number of sectors.
In principle, I can make such changes (number of sectors, size) in the driver, you don’t have to modify it.

C Respectfully, Roman aka Megus of Brainwave Tracks.

[Team ZX-Spectrum] [Team Iron Maiden] [Team Die Krupps] [TeamGuitar]

26 Aug 98 Roman Petrov, hoping that Roman Milukov would read, wrote:

AK> Probably, I’ll give the turboloader to Roman Petrov, and then let him
AK> himself
AK> convert it to the BIOS, everything is written there in Russian-English
AK> is written out.
...
RP> loader (and saver, by the way, too) should be able to load and
RP> write a block of
RP> sectors to a disk with an arbitrary sector size and
RP> number of sectors.

Sasha himself will probably write to you about this...
I saw his procedure, there the number of sectors is specified arbitrary, but the size
I don’t know. But both MS-DOS and TR-DOS can be read/written.

All the best.
Roman.

RP> That's right, then old help. At that time it was simply not known which errors
RP> would be required, although the standard three were still known. Now disk
RP> errors are included in help, since work has begun on disk functions.

Is there an error like 'no drive' there?

IMHO it is necessary.

W!7h Be$7 W!$he$, FK0.

RP>> what errors will be needed, although the standard three are still known.
RP>> Now disk errors are included in help, since work has begun
RP>> on disk functions.
KF> Is there an error like 'no drive' there?
KF> IMHO it is necessary.
What do you mean there is no such device? Hmm, thanks, I somehow forgot about it,
but it would have popped up soon anyway, while writing a function to
determine whether a disk belongs to any system.