I still don't think it has anything to do w/ APM/ACPI, it may indeed read
the registry to trigger the process, or there may be some flag in the
hiberate file itself (nothing says it has to be a pure copy of memory, it
may in fact be structured), but just thinking about it logically and
observing the behavior, it's hard to imagine WHAT would require APM/ACPI
dependence. Again, I'm not claiming expertise here, merely observing.
Consider what happens, the CPU is (probably) idled, the memory contents
copied to a file, (maybe a flag set), and shutdown. On reboot, the process
is reversed. It's not like other power options that need, for example, to
rely on the BIOS/APM/ACPI to "wake" a PC from sleep, e.g., WOL (Wake On LAN)
network adapter, or switch to Standy. All of these involve true "power
management" directly, the quiescing of various components, and support by
the hardware (mobo, power supply, and OS) to make it possible. I see
NOTHING in the act of hibernation that requires any of these features. It's
just an "image", a snapshot of memory. As far as the system is concerned, a
clean reboot or reboot to a hibernated file appear the same.
Again, I could be wrong, but I just don't see how APM/ACPI are involved.
The clincher for me was when I was able to hibernate W2K on my old VA-503+
motherboard w/ K6-2+ 450 CPU and AT power supply using APM. You can get
much more lowly in the power management arena than that. That convinced me
this was all a function of the OS, nothing more.
Jim