So I found this article:
http://archimedesden.wordpress.com/2011/11/29/windows-hibernate-where-did-my-bios-options-go/
It explains what I found, which is that if you hibernate Windows, you cannot enter the BIOS setup or boot selection dialog when resuming. The author went on to claim that he was able to circumvent this by pulling the power plug and battery, and then holding the power button down to clear the capacitors. This did not work for me, I tried it, and was still not able to enter the BIOS.
Apparently "Hibernate" does not actually power off the system completely, like many believe. It uses less power than S3 sleep mode, but more power than S5/G2 "soft-off" mode (the power mode that you get when you shut down your computer instead of pulling the power cable, which still supplies a small current to the power switch).
Okay, so I understand the reasoning behind this; one could theoretically screw up the hibernation by changing vital BIOS settings. However, there are many BIOS settings that I could want to change that wouldn't break anything. More importantly, what I often want to do is to hibernate my Windows OS, and then boot up from my Linux OS on a different hard drive, and then reboot and resume my Windows OS. This is not possible with Windows because it prevents my BIOS from letting me use the boot device selection screen.
However, for some reason, it IS possible with linux! If I hibernate my Lubuntu Linux OS, I am able to use the BIOS no problem, and boot to my Windows OS, then reboot and resume the Lubuntu hibernation, without issue! So why is Windows preventing me from doing the same the other way around? And HOW is it doing it? Is there some ACPI flag that Windows sets upon hibernation, that if the BIOS reads, it does not display the "Press DEL to enter setup" message?
Thanks for any help!
http://archimedesden.wordpress.com/2011/11/29/windows-hibernate-where-did-my-bios-options-go/
It explains what I found, which is that if you hibernate Windows, you cannot enter the BIOS setup or boot selection dialog when resuming. The author went on to claim that he was able to circumvent this by pulling the power plug and battery, and then holding the power button down to clear the capacitors. This did not work for me, I tried it, and was still not able to enter the BIOS.
Apparently "Hibernate" does not actually power off the system completely, like many believe. It uses less power than S3 sleep mode, but more power than S5/G2 "soft-off" mode (the power mode that you get when you shut down your computer instead of pulling the power cable, which still supplies a small current to the power switch).
Okay, so I understand the reasoning behind this; one could theoretically screw up the hibernation by changing vital BIOS settings. However, there are many BIOS settings that I could want to change that wouldn't break anything. More importantly, what I often want to do is to hibernate my Windows OS, and then boot up from my Linux OS on a different hard drive, and then reboot and resume my Windows OS. This is not possible with Windows because it prevents my BIOS from letting me use the boot device selection screen.
However, for some reason, it IS possible with linux! If I hibernate my Lubuntu Linux OS, I am able to use the BIOS no problem, and boot to my Windows OS, then reboot and resume the Lubuntu hibernation, without issue! So why is Windows preventing me from doing the same the other way around? And HOW is it doing it? Is there some ACPI flag that Windows sets upon hibernation, that if the BIOS reads, it does not display the "Press DEL to enter setup" message?
Thanks for any help!
Facebook
Twitter
Instagram