|
From: Jim H. <jh...@fr...> - 2026-06-11 16:55:33
|
On Thu, Jun 11, 2026 at 11:17 AM Franco Martelli via Freedos-user <fre...@li...> wrote: > > On 11/06/26 at 16:40, Jim Hall via Freedos-user wrote: > > Out of curiosity, did FDAPM not prevent high CPU usage? Typically, you > > would run this in your FDAUTO.BAT > > > > FDAPM /apmdos > > > > > > For example, that's what I use in my FDAUTO.BAT, and FDAPM /STATS > > shows the CPU is idle about half the time: > > Yes, sadly my web search result omitted FDAPM, it seems to work well > here, like DOSidle does and it takes only 1K of RAM despite of DOSidle > that it takes 3K of RAM. > > So, is there any drawback to add that line (FDAPM /apmdos) together the > other lines related to FDAPM that already exist in FDAUTO.BAT? > ... > alias reset=fdisk /reboot > alias reboot=fdapm warmboot > alias halt=fdapm poweroff > ... > > Maybe "FDAPM /apmdos" is not included as default because it can slow > down some application, am I correct? > Actually, FDAPM should be loaded in the :DOSHIGH section of FDAUTO.BAT. I didn't type the "LH" command before it, in my example, but this is what's in the default FDAUTO.BAT file: :DOSHIGH lh fdapm APMDOS lh ctmouse REM lh share if not exist %DOSDIR%\BIN\DOSLFN.COM goto NOLFN lh %DOSDIR%\BIN\DOSLFN.COM REM - Add other stuff here once LFN is loaded.. If you modified your FDAUTO.BAT, you should check that FDAPM is loaded. (Note: the slash in the FDAPM command line option is optional .. that's the same as FDAPM /APMDOS or FDAPM APMDOS) |