Hi all,

you can now get an updated version of FDAPM from

Short description of the update:

The new FDAPM version no longer hangs during
flush / suspend / poweroff even if you have
broken drivers or BIOS, and it supports more
flexible ACPI handling, making poweroff and
throttling (speed setting) work on more PCs.

Thanks to ldwar lodoss and RayeR for asking
for those extra compatibility additions and
for testing them.

NOTE: If FDAPM SPEED9 (check current speed,
and show ACPI info) and other ACPI related
functions crash for you, then you have to
use the MEMCHECK option for EMM386. If you
do not use EMM386, then you have to use
another version of HIMEM, or none. Problem
is that EMM386 and HIMEM can make access to
ACPI data fail and throw an exception which
FDAPM cannot catch and handle.

Long explanation:

See the HIMEM / EMM386 explanation above if
FDAPM crashes for ACPI related functions...

The update explicitly enables interrupts before
it starts a delay: With broken drivers or BIOSes,
FDAPM would otherwise get stuck in the few second
delay of the FLUSH function. As FLUSH is also run
for the STANDBY / SUSPEND / POWEROFF functions,
those functions got stuck, too.

The second change in the updated FDAPM is that
now more complex ACPI data is supported, in
particular having a Power Management 1b register
set in addition to the basic 1a one, and having
the ACPI table entry point in the extra BIOS
area at e000:...., as opposed to the classic
location at f000:.... or in the EBDA.

The update fixes several issues: The ACPI tables
on some modern HP PC are now found, poweroff /
throttle will work on more chipsets, flush no
longer hangs with RayeR's BIOS, and all people
now get extra ACPI information by running
FDAPM SPEED9 (read current speed) :-). Setting
for example FDAPM SPEED2 is also a good way to
make old games run better on new hardware AND
save energy at the same time - Speed 2 means to
halt the CPU 6/8 of all hardware timeslices :-).

FDAPM is a tool for energy saving and related
functionality in DOS. Most functions are direct
action ones, only APMDOS stays in RAM: Put
in your autoexec to halt the CPU and save energy
whenever DOS is idle - in a safe way, so FDAPM
should never degrade the speed of your DOS, but
might not always give the best energy savings.

Please read the documentation for more details
about the other functions beyond POWEROFF, SPEEDn
and APMDOS :-).

Enjoy the new FDAPM version, and let me know if
your hardware or software still causes problems.


Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
Freedos-user mailing list

Reply via email to