It looks correct.
But now that you tell us you have Linux dual booted, be aware that having GRUB on the same HD with Win7 can corrupt Win7 beyond repair. We had another case last week of sleep not working because of it.
Yet there are many good reports of Dual Booting using EasyBCD 2.02 without complication.
I have used both GRUB and GRUB2 and it has never damaged my Windows 7 partition.
But thank you for the advice.
I have also had no problems in the past with Grub, Grub2, grub4dos or any other variant corrupting a Windows OS.
Windows invariably tries to wipe out any other system on installation, even other Windows installations (sometimes when startup repair is attempted too). Grub is generally much kinder, chainloading existing Windows 7, Vista, & XP installations and even finding and adding bootmenu items for WinRE recovery partitions.
What was the mechanism by which Grub affected the sleep function Gregrocker?
I'd like to be aware if it ever happens to a machine I am dealing with. Perhaps you have already mentioned it in another thread?
We have a steady stream of cases where GRUB makes Win7 irreparable. In fact if Startup Repair cannot start Win7 we invariably find out GRUB was involved. It sometimes happens if a HD is not wiped of GRUB, just formatted.
The best arrangement for Dual Booting (especially with GRUB) is to put the OS's on separate HD's installed while the other is unplugged, then boot preferred first in BIOS Boot order, boot the other one using one-time BIOS Boot Menu key.
Next best is to use EasyBCD 2.0 to Dual Boot Linux on the Add Boot Entry tab.
Were they irreparable because the installed Windows 7 went wrong and the users tried a startup repair without removing the Grub bootloader first?
That I can understand.
But how can Grub stop Windows from sleeping?
Quote