Hi there,

          I wonder if anyone's got any ideas on this one.  I've enabled s3 standby and with the remote it comes in and out fine  I've also just enabled wake on lan to see if I can wake it up to access files and remote desktop it. 

The problem is if I put the computer in standby with the remote, then try and run a remote desktop session with the computer, I can hear and see from the led's that the computer's woken up, but there's just a black screen.  I'm guessing thescreen isn't refreshing or something. 

Is there any way I can fix this as it's not really making the remote desktop facility much use.

Cheers, Matt

OK guys, i appreciate that there is a vast amount of information in this thread and I've done my best to assimilate it, but I still can't get S3 to work. From the MCE keyboard, it will go into standby no problem, but it always reboots on wake up. Sometimes cleanly, sometimes messily with blue screens, XP dumps, disk checks etc.

The story so far...

I had a fully built, fully functional (inc s3!) machine which worked fine, but had a bit of a change around, which basically involved making one of my older boxes my MCE device.

So, I'm building MCE on a Gigabyte GA-SINXP1394 mboard with a p4 1.7, Saphire 9800 card, no tuner, standard AC97 audio.Following the instructions in this thread....

Check the board, no USB jumpers, manual says USB standby is supported.

Update the BIOS to latest version (non beta)

No BIOS settings for USB standby, but switch off settings for keyboard, mouse etc.

Re-install MCE, using standard USB keboard and mouse, not the MCE ehome unit.

Install various mboard drivers,, including one for a "USB s3 fix". No drivers for audio of video loaded.

apply the registry fix, run dumppo changing minsleep from S1 to S3

Run windows update, taking everything except audio drivers

check the power management setiings

apply all the ehome fixes I can find

swap keyboard  and mouse for ehome, restart and.....

STILL THE SAME PROBLEM

Then had a very interesting session when it seemed to work for a while. MCE was OK, although it would not show pictures, but the box would go in and out of S3 OK. However, when I tried to exit MCE back into XP, the nmachine froze. Fullpower off restart and then back into the cycle of S3 off being ok and always rebooting on wake up. But at least MCE will now show pictures.

I since installed the latest ATI drivera dn the aidio drivers , but still the same problem. Sometimes it starts up with a blue screen, but i can't catch the error, somethjing about a "bad pool"

I'm at my wits end.

Any ideas?

You can disable the auto-reboot on blue screen.  also it makes a minilog on c:\minidump.log (by default) assuming it can still use the drives on crashing.

however: run dumppo changing minsleep from S1 to S3 I think is a dangerous thing to use.  I've found that usually if its reporting s1, something in your machine can't do s3.  Your probably a great canidate to use s4 (hibernate) in this case.  I started using it recently and I like it a lot better.

oshogg:

Hi,

Thanks for this very informative article. I have found it very useful so far. I am using ATI's Remote Wonder remote control and am trying to make it possible to resume from S3 using this remote control.

So far, I did the following. 1. Changed the Jumper settings on the motherboard to enable power on USB during S3. 2. Added the USBBIOSx entry in the registry. 3. For each of the device that had "Power Management" tab in the Device Manager, I turned on "Allow this device to resume". Now, the System goes to S3 fine (CPU fans are off). And, I can resume fine by pressing the power button or by the PS/2 mouse that is connected by wire. However, I can not resume by pressing any button on ATI's Remote Wonder. I see that the little red light on ATI Remote Wonder's receiver is turned on when the system is in S3. The little red light was not on before I made the changes mentioned above. So, I am pretty sure that the receiver is getting power now. Also, The device "ATI Remote Wonder" in Device Manager does not have the "Power Management" tab which other entries have. So, any idea what could be wrong? Any help would be greatly appreciated. thanks, Osho

Make sure to check the USB Root Hubs in the device manager, there under "Universal Serial Bus Controllers" check to make sure that "Allow this device to turn off power" is not checked.  You will be able to see what hub you remote wonder is usinig by checking the under the power tab.  That sounds like your problem though.

Hey your problem seems not so far from mine: when using one Nova-t pci, S3 is working correctly but if I put the second one, computer go in S3 and wake-up immediately!

Not related to AMD core Duo in my case (XP2800).

I will write to Hauppauge to get their feeling on my problem.

Regards;

BSOD:

oshogg:

Hi,

Thanks for this very informative article. I have found it very useful so far. I am using ATI's Remote Wonder remote control and am trying to make it possible to resume from S3 using this remote control.

So far, I did the following. 1. Changed the Jumper settings on the motherboard to enable power on USB during S3. 2. Added the USBBIOSx entry in the registry. 3. For each of the device that had "Power Management" tab in the Device Manager, I turned on "Allow this device to resume". Now, the System goes to S3 fine (CPU fans are off). And, I can resume fine by pressing the power button or by the PS/2 mouse that is connected by wire. However, I can not resume by pressing any button on ATI's Remote Wonder. I see that the little red light on ATI Remote Wonder's receiver is turned on when the system is in S3. The little red light was not on before I made the changes mentioned above. So, I am pretty sure that the receiver is getting power now. Also, The device "ATI Remote Wonder" in Device Manager does not have the "Power Management" tab which other entries have. So, any idea what could be wrong? Any help would be greatly appreciated. thanks, Osho

Make sure to check the USB Root Hubs in the device manager, there under "Universal Serial Bus Controllers" check to make sure that "Allow this device to turn off power" is not checked.  You will be able to see what hub you remote wonder is usinig by checking the under the power tab.  That sounds like your problem though.

Yup...I've got a similar problem....on my usb controllers the tick box for "Allow this device to bring the computer out of standby" is grayed out... this is a massive pain!! as I can't get it to work...I ve tried all the tricks and tips and still can't resume from the mce remote....  does anyone have any experience in getting this tick box enabled as I would put an end to my countless hours of searching the web for answer.... 

Any other tips would be gladly appreciates

Ps I also cannot get the power mangement tab in device manager for the ehome receiver...any ideas on how to fix it...I have tried to reinstall,,,,but no luck.

Thanks

Ernie

I was dreading reloading the OS> I used dumppo admin and set from s1 to s3. I have an asus P4PE and there are no bios settings for s1 and s3. Just enable or disabled standby. Interesting that its supported just kinda hidden i suppose.

Remote turns on and off, no issues at all. This is perfect. Im not a green button user though. I use meedio and mediaportal for the time being. Looking forward to vista ult media center but I need to rebuild this pc. Its currently a 2.8 oc to 3Ghz p4 northwood single core, I have thought about swapping the 6600gt upstairs with the 9200 in the HTPC, but its such a pain to pull it out of the rack.

This thread helped a lot though. i was hoping for bigger things from mediaportal due to its close ties with xbox media center. I dont think its ready for primetime just yet. Im sure it will get there.

Im sure ill post some more soon.

Asus P4PE deluxe = S3 = Yes!

Justify73:

Fixed the problem!

Found on another board that my "updated" NVIDIA video drivers were the cause of my screen not refreshing when I returned from standby.

I removed the suspect drivers, and voila!  Standby works like a charm now.  Thanks for the advice, everyone!

This may have been posted already, I haven't gotten through the whole thread, but I found a better way around this.

My system is XP/MCE on an MSI K8NGM2-FID, which is an nForce 430 (I think) board, with nVidia GeForce 6150 integrated video, which I am using, with nVidia drivers 6.14.10.9371.  CPU is Athlon X2 3800+.

Didn't really set up standby until last night, fortunately I already had the reg entry and had +5VSB set for my VFD and remote to work.  So just did the BIOS and windows settings and everything was great - unil I tried to resume, and got a blank screen. 

Went poking around in the BIOS, and found a setting "Re-call VGA BIOS from S3".  This was enabld before, I disabled it, and bam!  I now come out of S3 beautifully, no driver rollback necessary.

Now if only I could tell Windows not to let my VFD software (iMon) keep the PC awake...

Ed