NeOS for Scorp Nefurychit.

KF> Click on RESET immediately, Roman!

KF> 17 Apr 99 16:20, Roman Petrov wrote to Dmitry Sharikov:

DS>>> If there was compatibility with IS-DOS restarts, there would be fewer problems
DS>>> it would be possible to drag a soaper with a term from there already
DS>>> there is...
RP>> With is-dos it’s problematic, although the general ideas are similar. The is-good
RP>> source code, IMHO, can be remade without much difficulty, but
RP>> a ready-made program will not work. And I didn’t want to just do is-dos
RP>> sitting in a ROM.

KF> Why do you need a ROM? Let it sit in RAM and EMULATE ISDOS RESTARTS.

You can emulate ISDOS restarts. But the programs will still
not work directly, since most of them use a priori
information about memory allocation.
Or do you think that someone having the source codes of the program under
IS-DOS will take them and _remake_ them for Non-OS. IMHO, it's unlikely.

RP>> PS2All: Yesterday I started writing NeOS Commander. As soon as he learns at least
RP>> to launch files and run through directories, well, some other small
RP>> functions, he will fly here.

KF> And there the command line is not forgotten?
KF> But on the Spectrumthe command line is only in the MOA commander (91
KF> year...)

In the commander, the command line is not required.
If from the commander you can exit back to the command line interpreter
from where the commander was called.
It would be nice to also be able to launch the command line interpreter as an executable file (command.com)
from commander.

2authors_of_NeOS:
Sewing an interpreter into the kernel is a grave mistake.

+-All the best, Kirill!
|I was with you
|Valentin Pimenov aka Valker/Style_Group
+---------------

20 Apr 99 23:16, Valentin Pimenov wrote to Kirill Frolov:

VP> In the commander, the command line is not required.
VP> If you can exit from the commander back to the interpreter
VP> of the command line from where the commander was called.

So I don’t know isdos - With every error, a window pops up and again
run mon.com (mon+.res).

VP> It would also be nice to be able to launch the interpreter
VP> command line as an executable file (command.com)
VP> from the commander.

Sax. IMHO, you need to make the command line the most important part of the system, and
so that errors are written on the screen like MS-DOS.

VP> 2authors_of_NeOS:
VP> Sewing an interpreter into the kernel is a gross mistake.

Well, in isdos it turned out to be a mess.

Kirill Frolov. [ZX]

On Tuesday April 20 1999 Valentin Pimenov wrote to Kirill Frolov:

VP> You can emulate is-dos restarts. But it doesn’t matter directly to the program
And under NeOS there are no problems with this. RST #10 - free, you can hang anything on it.

KF> So I don’t press the isdos - with every error a window falls out and again
KF> run mon.com (mon+.res).
That's it. I completely agree with you here. And the proposal to shove it onto a RAM
Disk does not always work.

RP> Have you ever tried to work with MS-DOS on floppy disks and without a RAM-Disk?
RP> I tried
RP> - I didn’t like it...

I tried it. You have a copy of command.com on each disk and there are no
problems.

You misunderstood me. I am not in favor of always loading it.
I am in favor of the interpreter not becoming attached to the system, like the is-dos shell to the is-dos itself. Here people are suffering, trying to tear one thing away from the other, because they don't need the shell, but the is-dos itself does. So you want the interpreter to be opened as well? Imagine that I wrote my own
interpreter. And how can I make it work in HeOS, if
this is not provided by the authors?
As for reading from disk, it’s hardwired into your kernel anyway, it’s better to spend space in the kernel on something more generally useful, and save the interpreter in the upper memory. Fortunately, now
they will spoil it less.

+ - All the best, Roman!

RP> It may be a mistake if everyone has screws, but not
RP> everyone has them, far
RP> not everyone has them. And it’s not so scary that the interpreter sits in ROM, especially since even so, in theory, you can add new commands to it. This is done
RP> by intercepting
RP> errors No such command.

Yeah, and that module on which the pointer is rearranged is loaded
after exiting any program? It's better, IMHO, not to flash the interpreter!!! Then you will remember me with a kind word.

VP> Ask something easier. For cool programmers, probably. I wrote,
Don’t tell me. The command line can be very useful. It's not all the same with the mouse :)

VP> is called sequentially, passing parameters in the command line, and
VP> the user did not press anything on the keyboard.
No one argues that this is possible.

RP>> RAM-Disk? I tried it and didn't like it...
VP> I tried it. You have a copy of command.com on each disk and no
Good “no problems” - command.com is constantly loaded from disk. Horror,
it’s slow... And inconvenient.

VP> I am for the interpreter not to become attached to the system, like
VP> the is-dos shell to the is-dos itself. Here people are suffering,
You see, the interpreter is not a shell, it is essentially a small part of the system that provides basic contact with the user.

VP> did you tear off the interpreter? Imagine that I wrote my own
VP> interpreter. And how can I make it work in HeOS, if
VP> this is not provided for by the authors?
Why is it not provided for? Write your own interpreter and run it. Everything will
work... Although no, aloneThere is a problem - if the program calls the
interpreter itself, then it will turn to the ROM interpreter, and not to yours.
However, there is a way out of this problem - a system variable with the address of the
interpreter. Then you can freely connect an alternative
interpreter.

RP> You see, the interpreter is not a shell, it is essentially a small
RP> part
RP> of the system that provides basic contact with the user
yes, but this interpreter is just like a shell, only more primitive
for the average user, but also more powerful for a specialist!

VP>> did you open the interpreter? Imagine that I wrote my own
VP>> interpreter. And how can I make it work in NeOS, if
VP>> this is not provided for by the authors?
RP> Why is it not provided for? Write your own interpreter and run it. All
shell from shell? Class! :(

and in general, why don’t you focus on YUNIKH?? There are many years of experience
many people there!
by the way, did you make your own FS? As cool as in Unix? ;)
and the executable file will again be counted by extension?
make a FS where each file will have at least 5 flags: rwxdl (r-read,
w-write, x-execute, d-directory, l-link)

RP> Bye, Valentin! Megus/Brainwave^X-Project. [ZX] [NeOS]

Always yours Eugene