Open boeckmann opened 3 months ago
not sure runtime control is that much useful. a config.sys setting would be nice enough IMO. Esp. if it's named IDLEHALT, so we could use the same config.sys for EDR and the FD kernel :)
Yes, I would make this an IDLEHALT config.sys command to be compatible. But it would neverthless be nice if this could be disabled / re-enabled at runtime if the user notices some specific slowdowns for an application.
the user notices some specific slowdowns for an application.
in my case it was the opposite - when trying out freedos in qemu (kvm), i noticed that my host cpu went to 100% while i had freedos' edit.exe open. since that also means the fans kick in, it's really annoying. either that edit program has a non-blocking input polling loop, or the freedos version i installed doesnt properly support sleep-states...
the user notices some specific slowdowns for an application.
in my case it was the opposite - when trying out freedos in qemu (kvm), i noticed that my host cpu went to 100% while i had freedos' edit.exe open. since that also means the fans kick in, it's really annoying. either that edit program has a non-blocking input polling loop, or the freedos version i installed doesnt properly support sleep-states...
There is something fishy about the FreeDOS edit in general. My mouse cursor flashes constantly, even if the cursor is not moving. This does not seem to be system specific. So at least with a mouse driver loaded there seems to be some polling input loop running.
the user notices some specific slowdowns for an application.
in my case it was the opposite - when trying out freedos in qemu (kvm), i noticed that my host cpu went to 100% while i had freedos' edit.exe open. since that also means the fans kick in, it's really annoying. either that edit program has a non-blocking input polling loop, or the freedos version i installed doesnt properly support sleep-states...
There is something fishy about the FreeDOS edit in general. My mouse cursor flashes constantly, even if the cursor is not moving. This does not seem to be system specific. So at least with a mouse driver loaded there seems to be some non-blocking polling input loop running.
Currently the EDR-DOS kernel delegates power saving to an external driver internally called
$IDLE$
. This driver is not available in source. It would be nice to have an IDLEHALT feature like FreeDOS has right in the kernel and in addition an IDLE command to alter the behaviour at runtime.