home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Mce remote hibernate?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="dr.lector" data-source="post: 43066" data-attributes="member: 14972"><p>Okay so here is the deal:</p><p></p><p>After Googlin some time i've found this:</p><p>(btw: It's working great, so we should put this few lines on the tips& tricks site, im sure im not the only one who struggled with this!)</p><p><u></u></p><p><u><em>8351 » How can I enable the S3 system power state for standby when USB devices are armed for wake?</em></u></p><p></p><p>Windows XP and Windows Server 2003 enter the S1 system power state for standby, and only enter the deeper, power saving, S3 system power state if no USB device is armed for wake.</p><p></p><p>This behavior occurs because too many computer BIOS report that they support the S3 system power state for their on-board USB host controller, when they really don't provide proper support. When these systems attempt to wake from the S3 system power state, you can experience loss of power, false device removal/arrival notification, reset of attached USB devices, failure to resume, and other undesirable effects.</p><p></p><p>If you know your computer supports the S3 system power state for standby when USB devices are armed for wake, you can arm the device by checking the Allow this device to bring the computer out of standby on the Power Management property dialog in Device Manager.</p><p></p><p>To enable your computer to enter the S3 system power state when USB devices are armed for wake:</p><p></p><p>1. Open a CMD.EXE window.</p><p></p><p>2. Type the following command and press Enter.</p><p></p><p>reg ADD HKLM\SYSTEM\CurrentControlSet\Services\usb /v USBBIOSx /t REG_DWORD /d 00000000 /f</p><p></p><p>NOTE: Installing a 3rd party USB host controller when the USBBIOSx Value Name exists may cause problems waking the computer through the 3rd party controller.</p><p></p><p>NOTE: Microsoft does NOT recommend adding this key and Value Name. this:</p><p>8351 » How can I enable the S3 system power state for standby when USB devices are armed for wake? 11-Aug-04</p><p></p><p>Windows XP and Windows Server 2003 enter the S1 system power state for standby, and only enter the deeper, power saving, S3 system power state if no USB device is armed for wake.</p><p></p><p>This behavior occurs because too many computer BIOS report that they support the S3 system power state for their on-board USB host controller, when they really don't provide proper support. When these systems attempt to wake from the S3 system power state, you can experience loss of power, false device removal/arrival notification, reset of attached USB devices, failure to resume, and other undesirable effects.</p><p></p><p>If you know your computer supports the S3 system power state for standby when USB devices are armed for wake, you can arm the device by checking the Allow this device to bring the computer out of standby on the Power Management property dialog in Device Manager.</p><p></p><p>To enable your computer to enter the S3 system power state when USB devices are armed for wake:</p><p></p><p><strong>1. Open a CMD.EXE window.</strong></p><p><strong></strong></p><p><strong>2. Type the following command and press Enter.</strong></p><p><strong></strong></p><p><strong>reg ADD HKLM\SYSTEM\CurrentControlSet\Services\usb /v USBBIOSx /t REG_DWORD /d 00000000 /f</strong></p><p></p><p>NOTE: Installing a 3rd party USB host controller when the USBBIOSx Value Name exists may cause problems waking the computer through the 3rd party controller.</p><p></p><p>NOTE: Microsoft does NOT recommend adding this key and Value Name.</p></blockquote><p></p>
[QUOTE="dr.lector, post: 43066, member: 14972"] Okay so here is the deal: After Googlin some time i've found this: (btw: It's working great, so we should put this few lines on the tips& tricks site, im sure im not the only one who struggled with this!) [u] [i]8351 » How can I enable the S3 system power state for standby when USB devices are armed for wake?[/i][/u] Windows XP and Windows Server 2003 enter the S1 system power state for standby, and only enter the deeper, power saving, S3 system power state if no USB device is armed for wake. This behavior occurs because too many computer BIOS report that they support the S3 system power state for their on-board USB host controller, when they really don't provide proper support. When these systems attempt to wake from the S3 system power state, you can experience loss of power, false device removal/arrival notification, reset of attached USB devices, failure to resume, and other undesirable effects. If you know your computer supports the S3 system power state for standby when USB devices are armed for wake, you can arm the device by checking the Allow this device to bring the computer out of standby on the Power Management property dialog in Device Manager. To enable your computer to enter the S3 system power state when USB devices are armed for wake: 1. Open a CMD.EXE window. 2. Type the following command and press Enter. reg ADD HKLM\SYSTEM\CurrentControlSet\Services\usb /v USBBIOSx /t REG_DWORD /d 00000000 /f NOTE: Installing a 3rd party USB host controller when the USBBIOSx Value Name exists may cause problems waking the computer through the 3rd party controller. NOTE: Microsoft does NOT recommend adding this key and Value Name. this: 8351 » How can I enable the S3 system power state for standby when USB devices are armed for wake? 11-Aug-04 Windows XP and Windows Server 2003 enter the S1 system power state for standby, and only enter the deeper, power saving, S3 system power state if no USB device is armed for wake. This behavior occurs because too many computer BIOS report that they support the S3 system power state for their on-board USB host controller, when they really don't provide proper support. When these systems attempt to wake from the S3 system power state, you can experience loss of power, false device removal/arrival notification, reset of attached USB devices, failure to resume, and other undesirable effects. If you know your computer supports the S3 system power state for standby when USB devices are armed for wake, you can arm the device by checking the Allow this device to bring the computer out of standby on the Power Management property dialog in Device Manager. To enable your computer to enter the S3 system power state when USB devices are armed for wake: [b]1. Open a CMD.EXE window. 2. Type the following command and press Enter. reg ADD HKLM\SYSTEM\CurrentControlSet\Services\usb /v USBBIOSx /t REG_DWORD /d 00000000 /f[/b] NOTE: Installing a 3rd party USB host controller when the USBBIOSx Value Name exists may cause problems waking the computer through the 3rd party controller. NOTE: Microsoft does NOT recommend adding this key and Value Name. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Mce remote hibernate?
Contact us
RSS
Top
Bottom
