Hi Andreas,
>>> The new version makes use of the hlt instruction.
>>
>> Not good either. You should rather issue a proper 'idle' int and let the
>> task scheduler or power manager do its job.
>
> "task scheduler"? "power manager"? There must be a misunderstanding
> somewhere. I am talking only about the DOS version.
Mateusz' comment was about TSR such as FDAPM in FreeDOS
or POWER in MS DOS: They coordinate information about
when DOS is "bored" and forward that to BIOS functions
(or simply HLT) to save energy. Doing HLTs yourself in
ROW4 has the disadvantage that other drivers might not
expect "raw" HLT: For example EMM386 may "filter" it.
Using the "DOS is bored" interfaces also helps when you
run ROW4 inside environments which run DOS next to some
other things: For example Windows, Dosbox, Dosemu. For
simulation of complete computers (Bochs, Qemu, etc.) it
is probably sufficient to use HLT, but you could equally
well use the interface to tell FDAPM / POWER that your
software does not need the CPU at a specific moment :-)
> The hlt instruction is only used when you compile the DOS program
> with bcc ("row4t.com"). The ports to other systems use other
> system-specific APIs for the user interface.
This is where FDAPM / POWER is useful: It gathers info
from specified APIs and then uses autodetected actions
such as BIOS calls or HLT. So your DOS program itself
does not have to involve compiler specific variations.
Regards, Eric
> You should rather issue a proper 'idle' int and let the
> task scheduler or power manager do its job.
>
> INT 28 http://www.ctyme.com/intr/rb-4122.htm
> INT 2F,1680h http://www.ctyme.com/intr/rb-4530.htm
>
> Mateusz
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
