I've just spent hours getting s3 to work right on my new machine, so while it is fresh in my mind, here is all I learned:

I can now sleep with fans and all powered down, I can resume from remote, and my wireless keyboard and mouse DO NOT power up the system!

 

(This is not the only way, but it worked for me)

 Overview:

1. Setup hardware (MB jumpers)

2. Setup Bios

3. Add reg setting

4. Configure devices you want to be able to wake up

5. Windows Changes

6. Troubleshooting

 

1. Hardware setup

For your remote to be able to resume the system, it needs power. This power comes from the MB and must be enabled by a jumper. {My notes are from an ASUS MB, others should have similar} Look up the manual for your MB "USB device wake-up". The jumper needs to be on "+5VSB".

Note:

• You may have multi jumpers for different pairs of USB ports. You only need to turn on the ones for IR receiver. I recommend Keyboard and mouse too (see troubleshooting for reason).
• Make sure you hard power off (switch on the back of power supply or pull the power cable) - these jumpers are live when the system is 'soft' off
• Some new MB are always +5VSB (Asus A8N-SLI deluxe is one)

2. Setup the BIOS

• 2.a If you have any suspend setting, set them to s3 only (or s1 & s3)
• 2.b Turn on ACPI 2.0 support (and any other advance power support options)
• 2.c Turn off Wake on LAN, ps2 keyboard...  basically everything

3. Add Reg Setting

• Add HKLM->SYSTEM -> Current Control Set -> Services ->USB (A Key)
• Add Dword value USBBIOSx=0
• REBOOT

4. Configure Devices for wakeup

In device manager:

• under Keyboards
  • Properties on Microsoft eHome...
    • Power management TAB
      • Make sure 'Allow this device to bring..." is checked
  • Properties on your keyboard
    • Power management TAB (if exists)
      • Change setting based on your preference
• under Mice and other pointing devices
  • Properties on your mouse
    • Power management TAB (if exists)
      • Change setting based on your preference

5. Windows Changes

Apply windows updates that relate to 'ehome' - reboot

To not have a password prompt on resume (optional)

1. Right click on generic background
2. Select properties
3. 'Screen Saver' TAB
4. 'Power' button
5. 'Advanced' TAB
6. Un-check Prompt for password when comeputer resumes from standby

 

6. Troubleshooting

• ftp://ftp.microsoft.com/products/Oemtest/v1.1/WOSTest/Tools/Acpi/dumppo.exe is a handy power test tool.
  • in Dos 'dumppo admin' will show your current power settings
  • 'dumppo admin minsleep=S3' will force windows to go in to s3 when you do start -> Turn off -> Standby

1. Can't get the machine to S3 (only goes in to s1 - fans stay on) - Use the above tool to force an S3 setting "dumppo admin minsleep=s3"
2. When I try s3 Windows gives an error that ehome is blocking power save:
   1. APPLY WINDOWS UPDATES FOR MEDIA CENTER (esp any labeled EHOME)
   2. Make sure you have the IR receive plugged in to a USB port that has +5VSB set
   3. Rumor is if you installed windows with your MB not set to do s3 you are hooped.  If you had to change your MB power save settings you may have to do a re-install. MS apparently checks this on install, and puts a different dll in if no ACPI or s3 is found (I've alwasy had s1 or s3 on, has not been an issue)
   4. If you don't have the power management tab, remove the device (all eHome devices) unplug USB fo rthe IR receiver, Reboot, plug devices back in - this should re-install with power management.
3. Unit goes to sleep and wakes right back up:
   1. Something else is waking up the unit - unplug all USB devices with the unit on (except the IR receiver) and try to power off. If that works, add back other USB devices 1 by 1 (starting Keyboard, then mouse...) till you find the device waking up your machine.
      1. My wireless Keyboard/Mouse was the cause, turning on the +5VSB power solved this.
   2. Remove any extra PCI cards, add back 1 at a time
4. Keyboard or mouse movement wakes up PC - Double check step 4 above
5. Other devices are waking up system - check settings similar to step 4 above
6. On resume the system asks for password - Check screen saver settings make sure 'On Resume, Password Protect' is not checked
7. On resume I have to click on my username - Under Power option (ctrl panel, or display-.screen saver), make sure 'Prompt for password when...' is not checked
8. On resume I get a black screen - I've seen something about a patch for this, I think it was ATI related
9. On resume, my machine blue screens - you've got a bad driver... I had to re-build from scratch
10. On resume, my machien reboots - It's probaly blue screen with auto recover - re-build, add 1 driver at a time. start with Video card.

 

Hope that helps you.

 

If you find any typos, fixes or additions that I should add to this, let me know (direct email, not a reply) and I will edit it to try to keep it a good resource.

 

Special thanks to all on this board (ESP Crazy) for the info that lead to this.

 

 2/4/2005 - Subsequent test I found that a load I did with S3 only set in bios - I could not power save.  My device setting did not have the power tab. I re-loaded with the bios setting at (s1 & s3) and everything worked great (with above procedure)

4/8/2005 - I received a few questions from people on exactly how to edit the reg (at your own risk ;-)

Open Regedit - (start -> Run -> Regedit)

Expand the 'HKEY_Local_machine'

Expand 'System'

Expand 'CurrentControlSet'

right Click on  'Services'  -> 'NEW' -> 'KEY'

Name the KEY 'USB'

right click on your new key 'USB' ->'NEW' - 'DWORD Value'

Name the dword 'USBBIOSx'

Close regedit

 

9/2/2005 - I just rebuilt my machine.  The windows updates seemed to help fix things 

Also made misc clean up / updates to the message.

 

Thanks for posting this, it solved a long standing problem I was having with this. The key piece of info that I was missing was the jumpers on the MB. Didn't know these existed. Went back to my ASUS manual, and there it was, explaining the whole thing.

Sometimes you just have to know where to look...

this is an unbelievably helpful topic.  I think i have the problem nailed with my setup and am just doing final testing.  I will chime back in with my results (and hopefully success) with your above guide.  THANKS!

The steps above worked for me, but I am now having a problem that my machine waking up from S3 suspend during the night for soem reason.  It's also not going back to suspend even though I have my power settings set to go into standby after 20 mins of inactivity.

I have checked and my keyboard and mouse are correctly setup such that they do not wake the computer up from standby. So thsi is definitely a software thing.

Had any experience iwth this one?

I am able to go into S3 standby with the remote.  However, when I press the power button on the remote again, the system fires back up but hangs on a black screen.

I can't find anything here that's helped me to get by this problem.  Suggestions?

Matt

I think I may be having a similar problem that Matt is having... 

My S3 works just fine, except for one very annying bug.  My Radeon 9550 is hooked up to my TV through S-video.  I can go to S3 suspend, then if I power on with the remote, the system turns on, and I get a black screen on my TV.  However!  My computer has successfully woken up, It will record TV shows in this state.

If I send my machine to S3 again, and then turn it back on, it will wake up and successfully display on the TV.

To sumarize:

1.  S3 Suspend -> OK

2.  Remote Wake up -> Black Screen, with functional wake up

3.  S3 Suspend -> OK

4.  Remote Wake up ->  Successful wakeup

5.  S3 suspend -> OK

6.  See Step 2... Rinse and repeat.

There must be a fix for this, since the system is not crashing, only failing to initialize the S-video.  I figure it might have something to do with my display drivers, but there really isnt much to change, or options to use.

Matt, is this the same problem you are having?

Any Ideas are greatly appreciated!

-Caveman

This is worth mentioning from my above post!  It's very important.

This cycle of black screen and successful display ONLY happens when I suspend in the MCE interface.

If I am on the Desktop, it will S3 suspend, and wake up with a display 100% of the time.

This fact my shed some light on my problem.

 

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!

Jusify73:  what video card are you using and what version of the nvidia drivers caused the problem? And which ones fixed them?

I have integrated video on the MB... some NForce stuff.  I'm not at home, so I can't give you specifics.  However, the 6.6.xx versions of the video drivers were the drivers that were causing the video to vanish after coming back on from standby.

I reverted to the 5.X version, and all is well.

If you want specifics on the version numbers and what not, I'll have to wait until I get home to get them for you.

Matt

If you could get the exact numbers, it might help me out. I'm having issues with standby / hiberation that sound similar: When I hibernate, everything looks fine. When I resume, the system boots up to the desktop, but freezes at the desktop. (It was freezing in MCE, but I tried hibernating without MCE active to ensure that wasn't the culprit--it's not.) I'm convinced it's a driver thing, since this system ran beautifully before I erased the disk and "upgraded" to MCE.

Help!

I've got:

Asus A7N8X-E Deluxe

AMD XP 2400+

Geforce FX 5200 (S-Video out to my TV)

EVGA NVTV dual tuner version

 

---

Intel DG31PR mobo, Core 2 Duo E6700, 2GB DDR2 RAM, Asus nVidia 8500 GT, Hauppauge Win-TV-PVR 500MCE, HVR-2250, integrated audio, Antec Fusion 430 case

Remove your Evga Dual Tuner and see if you are able to return from standby without freezing. I've gone through 2 Evga dual tuners and they cause crashes for me.  

I thought it was hardware problem at first, so i RMA's my first card but the second/replacemnet card still has the same issues. I'm convinced it's a bad driver.

I gave up on Evga tuners and bought 2 single tuners based on the new ATI Theater 550 Pro chipset from zipzoomfly.com.

Looks like we've hit the same bug. I disabled the NVTV card in Device Manager and sure enough, it returns from hibernation without locking up. Def. their drivers are causing this. I'll alert eVGA, but in the meantime, you're right, the ATI Theater 550 Pro (TV Wonder ELite) is the way to go. Thanks!!

---

Intel DG31PR mobo, Core 2 Duo E6700, 2GB DDR2 RAM, Asus nVidia 8500 GT, Hauppauge Win-TV-PVR 500MCE, HVR-2250, integrated audio, Antec Fusion 430 case

Don't cheer too soon

I got my ATI TV wonder Elites yesterday and found out that i'm getting the same crashes on return from standby.  Looks like it's actually my motherboard that's causing the problem!  (Asus A8N-SLI).  This motherboard has been plagued with buggy Bios' every since it was released.. I've sent an RMA request to ZipZoomFly.com to get it exchanged for a Gigabyte Nforce4-Ultra board instead.

Good luck! With my Asus A7N8X-E Deluxe mobo, this fixed the crash problem with hibernation. Haven't tried standby yet...hmm. Interesting. The A8N uses the nForce4 SLI chipset, which I bet has the same driver as the nForce2-based A7N8X series. Maybe it's something in that chipset itself, or just that it's so new they haven't finished ironing out the problems, as your BIOS issues would indicate.

---

Intel DG31PR mobo, Core 2 Duo E6700, 2GB DDR2 RAM, Asus nVidia 8500 GT, Hauppauge Win-TV-PVR 500MCE, HVR-2250, integrated audio, Antec Fusion 430 case