Hmm I am sorry for late reply!!
I will check it out~
--
View this message in context:
http://freedos.10956.n7.nabble.com/FreeDOS-1-2-package-compilation-tp22618p22903.html
Sent from the FreeDOS - Dev mailing list archive at Nabble.com.
-
I personally think it is great!
--
View this message in context:
http://freedos.10956.n7.nabble.com/FreeDOS-1-2-package-compilation-tp22618p22904.html
Sent from the FreeDOS - Dev mailing list archive at Nabble.com.
--
On 22/06/2015 18:50, Rugxulo wrote:
> Really naive suggestion: did you try IDLEHALT (in FDCONFIG.SYS)?:-)
Yes, I did, although my understanding is that IDLEHALT is a HLT
implementation inside the kernel, so it's probably (?) redundant with
what FDAPM achieves, when the latter is loaded.
Wi
Hi,
Really naive suggestion: did you try IDLEHALT (in FDCONFIG.SYS)?:-)
http://help.fdos.org/en/hhstndrd/cnfigsys/idlehalt.htm
On Mon, Jun 22, 2015 at 3:39 AM, Mateusz Viste wrote:
>
> I noticed that FreeCOM is using much CPU on my PII machine according to
> FDAPM. When FreeCOM runs in an
Hi there,
I noticed that FreeCOM is using much CPU on my PII machine according to
FDAPM. When FreeCOM runs in an empty shell, FDAPM (APMDOS) reports about
~50% of CPU idleness, while if I run a power-efficient application that
call INT28 from time to time (besides doing its real job), FDAPM rep
