OS: CP/M, NeOS & etc

AI> this shine! :) ms-dos it turns out to be no ms-dos, but just
AI> just
AI> a cool CPU...

Isn’t it? It seems that Uncle Bill bought it for further modernization.. ;)

AI> this question is not for me, but for the author. but as I understand it, no one is going to parallelize
AI> processes
AI> there. the principle of
AI> pseudo-multitasking will simply be implemented, and even then not immediately, but “later”.

By the way, it’s really possible to parallelize processes, of course
it will be slower, But this would be very, very useful! Moreover, you can
introduce some flags that can be used to specify whether a given
program is intended to be executed in the background or not (almost like in Mazda, but not
exactly like that).
And the processor time quanta for each task can be made quite
large - 1 frame. A lot of problems disappear immediately, because... a small kernel that provides multitasking will sit on the interrupt and change the task with each call according to the specified priority and allocated resources for the task. In this case, the code for multitask tasks will of course need to be stored in pages. For
each frame you will only needsave the registers, and everything will be a bunch. All
work with hardware, in this case, should be carried out _only_ through the system,
otherwise there will be glitches ;) You really need to decide what to do with the screen.... ;)

With best regards, Yuri Voynalovich.
[Powered by Z80] [intel outside] [AMMY] [ъ]

AI>> no one is going to parallelize processes there. the principle of pseudo-multitasking will simply
AI>> be implemented, and even then not immediately, but
AI>> “later”.
YV> By the way, it’s really possible to parallelize processes,
YV> of course - it will be slower,

and even slower!

YV> But this would be very, very useful!

depending on what to parallelize. IMHO, printing to a printer can be done in the background
but there is no need to work with a flopper..

YV> Moreover, you can introduce some flags that can
YV> set whether a given program is intended to be executed in the background
YV> mode or not (almost like in Mazda, but not quite like that). And the quanta
YV> of processor time for each task can be made quite
YV> large - 1 frame. A lot of problems disappear immediately, because... a small kernel
YV> providing multitasking will sit on the interrupt and each
YV> call will change the task according to the given priority and allocated
YV> resources for the task. In this case, the code for multitask tasks will need
YV>, of course, to be stored in pages. For each frame you will only need to
YV> save the registers, and everything will be a bundle. All work with hardware, in this
YV> case, should be carried out _only_ through the system, otherwise you won't get glitches
YV> ;) It really is necessarydecide what to do with the screen.... ;)

the game won't burn out, IMHO.

Best wishes, Artur. [ZX]