This isn't true, and "maxsleep" isn't what you want to change anyway--"minsleep" is.

The "best" way to go about using STR is to enable "Suspend To RAM" in the BIOS before installing the operating system. Unfortunately, this isn't common knowledge, and no one (i.e. Asus) goes out of their way to TELL you this. I didn't know myself, back in January when I built my A7N8X Deluxe system.

The good news is that DUMPPO.EXE can correct the matter--without having to be run at every boot. Here's how:

1) Download DUMPPO.EXE from Microsoft (to ensure you get the correct file):

ftp://ftp.microsoft.com/products/Oem...cpi/dumppo.exe

2) Go to a command line rooted in the directory DUMPPO.EXE resides in, and enter this command:

DUMPPO.EXE admin

DUMPPO.EXE will list some basic information about the current sleep policies. For example, here is what I had before correcting matters using DUMPPO.EXE:

C:\Downloads>DUMPPO.EXE admin
Admin policy overrides
Min sleep state......: S1
Max sleep state......: S4 - hibernate
Min video timeout....: 0
Max video timeout....: -1
Min spindown timeout.: 0
Max spindown timeout.: -1

The problem here is the "Min sleep state" value. When you tell WinXP to enter standby mode, WinXP uses the "Min sleep state" setting to determine what ACPI standby mode to use. In the case above, WinXP sees and uses S1 (which is normal standby, where all that happens is that the hard drive(s) and monitor(s) power down).

3) Correct the "Min sleep state" value using the following command line:

DUMPPO.EXE admin /ac minsleep=s3

4) Reboot, and when you do, go into the BIOS and ensure that the "Suspend To RAM" value is enabled(!).

5) Back in Windows, issue the DUMPPO.EXE admin command again, exactly as in step (2), and you should see something similar to this:

C:\Downloads>DUMPPO.EXE admin
Admin policy overrides
Min sleep state......: S3
Max sleep state......: S4 - hibernate
Min video timeout....: 0
Max video timeout....: -1
Min spindown timeout.: 0
Max spindown timeout.: -1

The "Min sleep state" value should stay at S3, across reboots, and your system should be able to enter STR mode. (Incidentally, when I ran DUMPPO.EXE, I tried half-heartedly to monitor the registry and file system for the changes it made, but came up with nothing.)

If your system enters STR (i.e. S3) mode properly, but does not restore itself properly (e.g. the monitor stays blank, you get BSOD errors, etc.), the most likely culprit is a buggy or incompatible driver or piece of hardware.

I figured it was worth resurrecting this old thread in order to try to help...

Cool. Finally a M$ expert who could clear us up. Admit that it requires quite some knowhow to operate dumppo properly :D

O, do you have any idea where this minsleep and maxsleep settings are stored? Registry, cmos or somewhere else?

Thx, JockyW

Must be the registry, but as I said, I didn't find any specifics. I will do a bit of digging and see what I come up with.

Hi:

I used a registry logger and saved 2 logfiles. One for "dumppo admin /ac minsleep=S1" and one for "dumppo admin /ac minsleep=S3".

A "diff" compare came to the following:

4c4
< OpenKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE23DB5C0
---
> OpenKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE1AF8440
6,7c6,7
< CloseKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE23DB5C0
< OpenKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE23DB5C0
---
> CloseKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE1AF8440
> OpenKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE1AF8440
9,10c9,10
< CloseKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE23DB5C0
< OpenKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE23DB5C0
---
> CloseKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE1AF8440
> OpenKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE1AF8440
13,14c13,14
< CloseKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE23DB5C0
< OpenKey HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon SUCCESS Key: 0xE23DB5C0
---
> CloseKey HKLM\System\CurrentControlSet\Control\Terminal Server SUCCESS Key: 0xE1AF8440
> OpenKey HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon SUCCESS Key: 0xE1AF8440
16,17c16,17
< CloseKey HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon SUCCESS Key: 0xE23DB5C0
< OpenKey HKLM SUCCESS Key: 0xE23DB5C0
---
> CloseKey HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon SUCCESS Key: 0xE1AF8440
> OpenKey HKLM SUCCESS Key: 0xE1AF8440
20c20
< OpenKey HKLM\Software\Microsoft\Rpc SUCCESS Key: 0xE1AF8440
---
> OpenKey HKLM\Software\Microsoft\Rpc SUCCESS Key: 0xE12B5300
22c22
< CloseKey HKLM\Software\Microsoft\Rpc SUCCESS Key: 0xE1AF8440
---
> CloseKey HKLM\Software\Microsoft\Rpc SUCCESS Key: 0xE12B5300
25c25
< OpenKey HKLM\System\CurrentControlSet\Control\Session Manager SUCCESS Key: 0xE1AF8440
---
> OpenKey HKLM\System\CurrentControlSet\Control\Session Manager SUCCESS Key: 0xE12B5300
27,28c27,28
< CloseKey HKLM\System\CurrentControlSet\Control\Session Manager SUCCESS Key: 0xE1AF8440
< OpenKey HKLM\System\CurrentControlSet\Control\ComputerName SUCCESS Key: 0xE1AF8440
---
> CloseKey HKLM\System\CurrentControlSet\Control\Session Manager SUCCESS Key: 0xE12B5300
> OpenKey HKLM\System\CurrentControlSet\Control\ComputerName SUCCESS Key: 0xE12B5300
32,33c32,33
< CloseKey HKLM\System\CurrentControlSet\Control\ComputerName SUCCESS Key: 0xE1AF8440
< OpenKey HKLM\SYSTEM\CURRENTCONTROLSET SUCCESS Key: 0xE1AF8440
---
> CloseKey HKLM\System\CurrentControlSet\Control\ComputerName SUCCESS Key: 0xE12B5300
> OpenKey HKLM\SYSTEM\CURRENTCONTROLSET SUCCESS Key: 0xE12B5300
35,36c35,36
< CloseKey HKLM\SYSTEM\CURRENTCONTROLSET SUCCESS Key: 0xE1AF8440
< SetValue HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power\PolicyOverrides SUCCESS 02 00 00 00 05 00 00 00 ...
---
> CloseKey HKLM\SYSTEM\CURRENTCONTROLSET SUCCESS Key: 0xE12B5300
> SetValue HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power\PolicyOverrides SUCCESS 04 00 00 00 05 00 00 00 ...
39c39
< CreateKey HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power SUCCESS Key: 0xE1AF8440
---
> CreateKey HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power SUCCESS Key: 0xE12B5300
43c43
< CloseKey HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power SUCCESS Key: 0xE1AF8440
---
> CloseKey HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power SUCCESS Key: 0xE12B5300


So I think it maybe is the following value:

S1
HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power\PolicyOverrides SUCCESS 02 00 00 00 05 00 00 00 ...

---

S3
HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power\PolicyOverrides SUCCESS 04 00 00 00 05 00 00 00 ...

Hope that helps

DSidious

Re: A7N8X standby (S3) issue
 

Having the same problems here, but I'm using Win2kPro instead.
Tried the Dumppo utility and seems to be working, will need to check upon reboot.

In my system, dumppo seems to have created the following register line which did not exist before:

HKLM\SYSTEM\CURRENTCONTROLSET\Control\Session Manager\Power\PolicyOverrides
with the following value: 04 00 00 00 05 00 00 00 - 00 00 00 00 ff ff ff ff - 00 00 00 00 ff ff ff ff

:thumb: to you, nameless and DSidious! Thank you very much!