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. Without IDLEHALT, FDAPM reports ~50% of idle time. With IDLHALT=1, the result is seemingly worse, because FDAPM reports only ~40% of idle time (but this migh be a wrong perception of FDAPM, since it sees the kernel giving away less time exactly because of kernel-issued HLTs...) I'd be curious to know if I am alone with this problem - do you have 'good' idle results on your PC when the system only blinks at a command prompt? The test is as simple as this: FDAPM APMDOS FDAPM ZAPSTATS (here wait for 30s or so) FDAPM STATS I never really payed attention to this, and assumed that's just how things are, but when testing DOSMid I was surprized to see that DOSMid achieves 95% and more of idle time when playing MIDI files, while FreeCOM is apparently doing something 50% of the time, when it should do literally nothing. So now it's cheaper (power-wise) for me to play MIDI files all day long on my PC rather than leave it "idle" at the DOS prompt :) Mateusz ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
