Installed Windows 7 x32 (and the Boot Camp drivers) on a MacBook Pro (2.4 GHz T8300 Core2Duo / 2GB / NVIDIA GeForce 8600M GT), and had no problems with the sleep/wake cycle until this morning. I had installed Sonar and the MOTU USB/Firewire audio drivers (the recent release containing WaveRT support). After that, the computer would only partially wake from sleep or hibernate, in the following order:1) System fan starts2) Hard drive begins to access2) Optical drive noise (probably checking for a disc. The drive is empty.)3) Screen backlight turns on, but no cursor or mouse4) Small pop from the speakers, indicating that at least the amplifier has been turned back on.That's it. Nothing on the display.The obvious culprit was all of the software and drivers I installed, so I attempted a system restore to a point before I had installed the items. That didn't work. I've tried a variety of power profile settings, to no avail. I've got a potentially related problem with the display as well. I went to disable the screen saver (as a potential interruptor of the wake cycle), and got a message informing me that I needed a Direct 3D compatible driver. Of course, that's ridiculous considering the hardware, so I re-installed the driver. The message is gone, but the computer still won't wake from sleep.Any thoughts?

Well, Windows completely lost the driver for the apple display, and wouldn't let me reinstall it from the Boot Camp disk. So, I decided to roll back to an even older restore point. Here's a list of what was deleted/restored:Deleted:IcoFX 1.6.4Java(TM) 6 Update 12 6.0.120 Java(TM) 6 Update 7 1.6.0.70Microsoft Visual C++ 2005 Redistributable 8.0.56336 (part of the Sonar 8 installation)MOTU Firewire/USB2 Audio 1.00.0000Native Instruments Guitar Rig 3 (bundled with Sonar 8)Nord Stage Manager v4.00OpenOffice.org 3.0 3.0.9379Sonar 8.0 Producer Edition 17.0WinMount V3.2.0120 3.2.0120Mark of the Unicorn (Media) 12/18/2008 3.6.8.1394MOTU (Media) 12/18/2008 3.6.8.1394MOTU (Media) 12/18/2008 3.6.8.1394MOTU (SYSTEM) 12/18/2008 3.6.8.1394Restored:Adobe Flash Player 9 Plugin 9.0.45.0The restore point I had tried previously had removed the following:Microsoft Visual C++ 2005 Redistributable 8.0.56336 (part of the Sonar 8 installation)MOTU Firewire/USB2 Audio 1.00.0000Native Instruments Guitar Rig 3 (bundled with Sonar 8)Sonar 8.0 Producer Edition 17.0Mark of the Unicorn (Media) 12/18/2008 3.6.8.1394MOTU (Media) 12/18/2008 3.6.8.1394 MOTU (Media) 12/18/2008 3.6.8.1394 MOTU (SYSTEM) 12/18/2008 3.6.8.1394So, that leaves the following as potential causes:IcoFX 1.6.4Java(TM) 6 Update 12 6.0.120 Java(TM) 6 Update 7 1.6.0.70Nord Stage Manager v4.00OpenOffice.org 3.0 3.0.9379WinMount V3.2.0120 3.2.0120Of course, for the day that all of those were installed before I installed Sonar and the MOTU drivers, the computer worked fine.I'm going to look for any correlation between Java updates and sleep/wake issues, but I'd appreciate any enlightenment on why I suddenly had display/monitor issues. I'm assuming that the display problem was the cause of the sleep/wake problem. Thanks in advance.

There has been news of a later Boot Camp version for Win 7. You should check for that.Rating posts helps other users Mark L. Ferguson MS-MVP

I have got a similar problem, but on an EEE 1000H. It seems to be a problem with the battery mode. When I am hibernating in AC mode and try to start in battery mode the display will flicker until it blanks out or stays black. Nevertheless I am able to use the "Fn"-key to send the eee to sleep-mode or increase or decrease the backlight, but the screen stays dark. This problem is also working vice versa, hibernating in battery-mode and starting in AC won't work either. Hibernating and starting in AC is possible. To my surprise the battery-mode did not worked when I tried to boot the pc in the train. This only happend once so far and the eee was not hibernated, so I do not know if this is another problem. Any ideas why this problem occurs without using a Mac and without a bootloader? Thanks, Stefan Found it: http://support.microsoft.com/kb/929909/ It's a problem with the AHCI driver.