XP Standby Mode PSU fan still running
Steve Mowbray
installed XP on and I have identical trouble with Standby mode where the PSU
fan remains running. The power LED remains full on rather than blinking,
otherwise the system appears to be in standby okay and comes out of stanby
normally without problems
Since the problem is common to both systems, I am assuming I have done
something wrong in either the connection of the PSU's, BIOS setup or XP
power management.
Any help would be appreciated as I am stumped
Cheers
Steve
Ian A.
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:X9Bp9.341$E25.2...@news-text.cableinet.net...
First check in the bios to see if they are set to go into S3 standby not S1.
If you are set to go into S3 standby and it still doesn't work you may have
some luck by running a utility called dumppo.
I can't remember where to get it from, try a search on google.
Copy dummpo.exe to windows\system32 and from a command prompt enter this
command:
dumppo ac maxsleep=s3
If you can't find dummpo post back and I'll see if I can't find it for you.
Ian
Jahesh
Also verify that it's not set to boot from LAN. That'll have the same
effect.
Steve Mowbray
ftp://ftp.microsoft.com/products/Oemtest/v1.1/WOSTest/Tools/Acpi/
Will experiment with BIOS/dumppo.
I am unsure as to how S3 state in BIOS relates to the BIOS power management
setup fields, can you point me in the right direction
Thanks for the help so far
Cheers
Steve
"Jahesh" <jah...@lycos.com> wrote in message
news:3DA6F178...@lycos.com...
Steve Mowbray
without success. I found the following page on the web:
http://www.shahine.com/omar/categories/technology/
which discusses the same problem but without enough information to resolve
my problem.
~ It seems that I have to set BIOS to S3 mode to enable correct PSU ACPI
standby function, however I cannot find out how this is done as S1/S3 is not
mentioned in my BIOS setup instructions.
~ It also seems that if XP is installed with BIOS in S1 mode it will never
revert to full S3 operation unless reinstalled. My understanding is dumppo
can be used to override this but must be reapplied after every restart.
Anybody have any ideas or links to information I can follow.
Cheers
Steve
"Ian A." <ian_ag...@hotmail.com> wrote in message
news:PDBp9.4139$Sk6.3...@news1.telusplanet.net...
Bill Halvorsen
to get dumppo.exe from a French website on advice from a newsgroup message
back in August. Worked right away. However, I've installed the service
pack for Windows XP (home) and SP2 for Office XP. Somewhere in there, my
ability to shut down, sleep, everything, went away. Well, I can still
hibernate - thought the screen freezes and the fans remain on.
My system now seems to anxious to sleep, if the flashing "green" indicator
is any indication. If I try to STR, the fans and monitor remain on. If I
try to shut down, same thing - there is no real shutting down. Tried all
workarounds, nada. Even dumppo fails me now, evidently another wonderful
thing that MS mas MeSSed up.
I have to wonder where Asus and its wonderfully ambiguous BIOS settings fall
into this. I'm on the P4T-E motherboard. I'm afraid to try the latest bios
as the online description (click on P4T-E) is wrong (says P4T-E is an SDRAM
MB and, er, really, it's RDRAM). Scary. Now I'm back to being able to shut
down by just accepting BIOS default settings on the power page, however, I
have to awaken with the power button, the keyboard, no matter where the BIOS
is set (PS2) isn't seen. If I coax the machine to hibernate, the keyboard
and mouse ARE seen as wakeup devices (but of course the screen and fans are
already on, just the HDD's spin up).
If anyone has good settings for XP and the BIOS please let me know, this is
really frustrating (and I could be wrong about the SP installation, but had
things working so well before - and yes, I even did a reinstall. Something
messed it up again - will probably never know what. When dumppo worked, by
the way, no, it didn't have to be reapplied after every restart.
Bill Halvorsen
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:INEp9.670$%16.50...@news-text.cableinet.net...
Antonio Amengual MS-MVP
to stop all fans while suspend mode ALL must have 3 wires, but PS fan remains always On because Board needs to be on standby state consuming small power
a few days ago i flashed bios to last version 1007, no need to repair XP, all start in a normal mode
--
Associate Expert Zone
Expert Zone - http://www.microsoft.com/windowsxp/expertzone
XP Pro-2600-limpia+SP1
por favor
respuestas al grupo; asi nos beneficiamos todos
no se responde personalmente
saludos
Antonio
ms mvp dts
"Bill Halvorsen" <bil...@comcast.net> wrote in message news:OQudnfhfOYS...@News.GigaNews.Com...
Jim Banks
>news:eQAE4QWcCHA.1692@tkmsftngp09...
>Hi i'm using Asus P4T-E with 2 GB Rdram from Kingston
>to stop all fans while suspend mode ALL must have 3 wires, but PS fan
remains >always On because Board needs to be on standby state consuming
small power
This may be true for a P4T-E, but it is definitely not a generally true
statement. I have an A7V133 that has 2-wire case fans and they shut down
quite nicely in STR mode, as well as the PS fan shutting down. And, yes,
this is S3 mode, not hibernate.
Jim
Paul Busby
Jim Banks <banks_j...@hotmail.com> pulled the chain then typed:
> This may be true for a P4T-E, but it is definitely not a generally
> true statement. I have an A7V133 that has 2-wire case fans and they
> shut down quite nicely in STR mode, as well as the PS fan shutting
> down. And, yes, this is S3 mode, not hibernate.
to optionally power USB, keyboards etc. Some come unstuck when resetting
their Bios prior to updating them. On most, if not all Asus m/bs, S3,
Suspend to RAM is default off. I had this very problem back in Feb which got
sorted by re-formatting then re-installing WinXP. Dumppo was unknown to me
then. It sometimes needs "administrator" as a switch. I've only run it in
diagnostic mode which returns the S states.
Steve Mowbray
exe is not useful and I cant find a guide for it). Can you describe the
syntax options for dumppo that you are aware of.
It is my belief that the PSU should be commanded into the low power mode by
the motherboard when standby is invoked (there is a wire on the main ATX
connector to the PSU which should signal this). All being well the PSU fan
and all the peripheral fans and other components should be powered down with
only the 5vSB remaining active to maintain the RAM image and wake up
components (USB/PS2 etc).
What I get (and others it seems) is a system in standby with PSU in full
power mode. PSU/Case fans still running and CDROM etc devices still up. The
remainder of the system CPU/MB/HDD is in standby. It would appear to me that
the appropriate signal from the motherboard to the PSU (through the ATX
connector) is not operating properly - however I cant for the life of me
work out if this is a BIOS problem or XP. A BIOS problem would make more
sense but there is so much conflicting and abscure information about that it
is difficult to be sure.
I am surprised that such a relatively basic function should be shrouded in
such mystery by Microsoft, Asus and Award.
Any further views will be much appreciated
Thanks
Steve
"Paul Busby" <xbu...@tele2.co.uk> wrote in message
news:uqfpkin...@corp.supernews.com...
Steve Mowbray
"Jim Banks" <banks_j...@hotmail.com> wrote in message
news:ao7fgu$k07oo$1...@ID-124897.news.dfncis.de...
> >"Antonio Amengual MS-MVP" <amengu...@ono.com> wrote in message
> >news:eQAE4QWcCHA.1692@tkmsftngp09...
> >Hi i'm using Asus P4T-E with 2 GB Rdram from Kingston
> >to stop all fans while suspend mode ALL must have 3 wires, but PS fan
> remains >always On because Board needs to be on standby state consuming
> small power
>
> This may be true for a P4T-E, but it is definitely not a generally true
> statement. I have an A7V133 that has 2-wire case fans and they shut down
> quite nicely in STR mode, as well as the PS fan shutting down. And, yes,
> this is S3 mode, not hibernate.
This is my belief of how correct Standby mode should operate. As I
understand it the ATX connector has a signal line back to the PSU which can
control PSU mode (off/low power/full power). However it does not seem to be
fully operational despite trying lots of different settings in BIOS and
numerous XP reinstalls.
Is there something that I and others are missing here.
Cheers
Steve
Paul Busby
Steve Mowbray <steve_...@hotmail.com> pulled the chain then typed:
> The dumppo administrator switch is new to me (the command line help
> for the exe is not useful and I cant find a guide for it). Can you
> describe the syntax options for dumppo that you are aware of.
>
This took a bit of digging out:
dumppo admin /ac minsleep=s3
dumppo admin /cap returns they S states. Dumppo won't work without the admin
switch for me under XP Pro - nothing happens. test with the /cap switch to
check for correct syntax.
HTH
Steve Mowbray
settings and allows minsleep and maxsleep override. However.... the Standby
mode has the same problems in that the PSU stays in full power mode with
fans active.
I suspect that it may be a motherboard/BIOS fault since standby was
operational (with PSU fans running) straight after install and none of the
BIOS and XP messing around that I have done has helped.
One thing I have noticed is that the power tab in the hardware device
manager is not available for devices I would have expected it for such as
mouse (allow this device to bring the system out of standby etc)
Thanks again
Steve
"Paul Busby" <xbu...@tele2.co.uk> wrote in message
news:uqgn0rc...@corp.supernews.com...
Paul Busby
> report settings and allows minsleep and maxsleep override.
> However.... the Standby mode has the same problems in that the PSU
> stays in full power mode with fans active.
>
> I suspect that it may be a motherboard/BIOS fault since standby was
> operational (with PSU fans running) straight after install and none
> of the BIOS and XP messing around that I have done has helped.
>
> One thing I have noticed is that the power tab in the hardware device
> manager is not available for devices I would have expected it for
> such as mouse (allow this device to bring the system out of standby
> etc)
There is a crucial setting in the Bios that seems to be set to default *off*
under "Power" in the Bios, peculiar to Asus. On my A7V266-E it's called
"Suspend to RAM Capability". It may be called something like "Fans off in
Standby" etc, etc. Unless this is set, no S3, only S1. Only then will dumppo
work to enable S3. Some people have "lost" their S3 mode - usually caused by
the Bios being reset for whatever reason. Under these circumstances I've
been told XP's Restore will re-enable it if available. The A7V333 had to be
set to Jumper mode to gain access to this S3 switch, not sure if a later
Bios fixed that.
There are settings in DM but for cards like NICs rather than mice. All other
PM functions work from Power Options in the Control Panel. MS also recommend
that P&P OS is set to OFF in the Bios as well.
Steve Mowbray
Update to previous post - dumppo fixed P4T533 system, still working on the
P2L97S board, perhaps is too old to support XP properly even with the latest
BIOS purchased from unicore.
I am concerned that there is no mention of S3 or S1 anywhere in the BIOS,
just a lot of power management options that can be enabled or disabled.
I did not realise that MS recomended that P&P OS should be disabled, its a
bit counter intuitive.
Anyway thanks, I have one out of two machines fixed using the additional
dumppo syntax you provided.
Cheers
Steve
"Paul Busby" <xbu...@tele2.co.uk> wrote in message
news:uqgpuoe...@corp.supernews.com...
Nitrof
has to be enabled before Windows Xp is installed for it to work properly.
Is that the case ?
"Paul Busby" <xbu...@tele2.co.uk> a écrit dans le message de news:
uqgpuoe...@corp.supernews.com...
John
Asus A7V 133 rev. 1.05
AMD Athlon 1200, 266FSB
512 MB Spectek ram
IDE 0: WD 100GB 2MB 7200rpm master; IBM 45GB 75GXP slave
IDE 1: Toshiba SDM 1502 16X DVD ROM master; LiteOn 16X 10X 32X slave
Promise PDC 20265: RAID 0 with 2 IBM 60 GB 60GXP
3dfx Voodoo 5
2 D-Link 530 tx nic
SB 16 PCI
OS is on IDE 0
Hello everyone. I have tried dumppo with the following syntax:
dumppo admin /ac minsleep=s3
and the system goes to s3 allright, but stays there. Nothing will wake it
up. I can push the power button and that starts the fans and hdd and power
lights. The monitor stays off and the keyboard does nothing. After the
initial hdd glowing for about 5 secs, nothing more from it. I ran dumpo
again, this time with the following syntax:
dumppo admin /ac minsleep=s1
and everything is back to the way it was, which is to say that the
three-wire fans connected to the mainboard shut off on standby, but the
extra fans on the case stay on.
Any one have any info on how to make this s3 stuff work? How can I
diagnose? Dumppo /cap says I have up to s4-hibernation, which works, BTW.
Paul Busby
Nitrof <nit...@nowhere.com> pulled the chain then typed:
> I have read somewhere in these groups that "Suspend to RAM Capability"
> has to be enabled before Windows Xp is installed for it to work
> properly. Is that the case ?
>
Paul Busby
John <Jo...@Yadayada.com> pulled the chain then typed:
> System Config: Windows XP Pro SP1
>
> Asus A7V 133 rev. 1.05
>
> dumppo admin /ac minsleep=s3
>
> and the system goes to s3 allright, but stays there. Nothing will
> wake it up. I can push the power button and that starts the fans and
> hdd and power lights. The monitor stays off and the keyboard does
> nothing. After the initial hdd glowing for about 5 secs, nothing
> more from it. I ran dumpo again, this time with the following syntax:
>
>
> dumppo admin /ac minsleep=s1
>
> and everything is back to the way it was, which is to say that the
> three-wire fans connected to the mainboard shut off on standby, but
> the extra fans on the case stay on.
>
> Any one have any info on how to make this s3 stuff work? How can I
> diagnose? Dumppo /cap says I have up to s4-hibernation, which works,
> BTW.
Have you made sure that Suspend to RAM Capability is set in the Bios, if
indeed this m/b supports it? Asus' www is down so can't check.
Robert Carr
whatever else do not power down after entering Standby. Thought I would give
my experimental test results.
For the record, I am running WinXP Pro (SP1) on an ASUS P4S333 MB.
I downloaded dumppo.exe from the website given earlier. Copied it to the
C/Windows/System32 folder.
Ran the following at the command prompt
dumppo admin/ cap
It said I had the following sleep capabilities: S1, S4 and S5
I restarted, entered the BIOS setup and in the Power Menu, enabled ACPI
Suspend to RAM.
Rebooted and tried the Standby mode. Results were the same, fans still
running.
Ran the following at the command prompt
dumppo admin/ cap
It said I had the following sleep capabilities: S1, S3, S4 and S5
(note the addition of S3)
I then ran the following at the command prompt
dumppo admin/ ac minsleep=3
It reported back that my minimum sleep mode was S3
I tried Standby again. What do you know, it worked. No fans running, No CD
unit power. It also returned to normal operation, exiting the Standby mode.
I have no idea what prompted this problem. I know positively that it worked
before, although I don't use Standby very much. The only recent changes to
my system were SP1 and a Photo Processing program. I know that I never had
to enable ACPI Suspend to RAM before.
That's it
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:T7Yp9.2092$i32.13...@news-text.cableinet.net...
Steve Mowbray
Good news, I have got to the same place as you with my P4T533 system,
however I am still trying to get the PSU to enter low power mode in Standby
with my P2L97S system.
Could be that the system is too old for that, but its hard to work out for
sure since there is so little information and it seems a little muddled as
to what is in control (BIOS/XP).
Still surprised that such a simple function is shrouded in such mystery, it
cannot be that hard can it?
Cheers
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:k95q9.23537$r83.1...@news1.west.cox.net...
PfcJs
was only after reinstalling XP from scratch with suspend to ram turned
on in the bios.
The only problem now is that I have to be very careful with driver
updates. The new NVidia version 4 Detonator drivers make my resumes
from S3 less reliable. It will sometimes hang during the resume
process either getting to the sign on screen or after I sign back on
my session. At this point, I must shut down. Hitting reset will not
restart XP.
For those of you still trying, keep going. It's worth it being able
to suspend and resume quickly.
My system specs:
P4 1.6A @ 2.2
Asus P4T533C Motherboard Bios rev 1007c
512 MB PC800 RDram
LeadTek Ti4200 Vidcard @ 300/335
Soundblaster Live OEM
Windows XP SP1
NVidia Detonator Driver 30.82
Good luck all.
PfcJs
Robert Carr
After I posted my results, I went to my other computer running Win2K on an
ASUS CUSL2 MB. It had the same problems in Standby. I went through the exact
same process, posted earlier, and it corrected the problems. That MB is
about 2.5 years old. I read something recently that sort of indicated boards
older than about 1999, may not support all sleep modes.
I'll give you my take on this mystery. I believe that the MB/Bios provides
it's sleep mode capabilities to the OS. The OS implements the one it
chooses. If the Bios only reports S1 capability, then the OS implements S1.
If the Bios reports S3, then it will implement S3. I don't think current
OS's are implementing S4 or S5. S4 is basically Hibernate, but I believe
that Hibernate is largely a separate issue from Standby. What I mean by that
is the OS saves RAM to the disk and then shuts down the computer. It doesn't
require any special MB or Power Supply functions, as I see it. Standby on
the other hand, particularly S3 mode, requires the MB to somehow inform the
Power Supply to shutdown everything except RAM. In this case I assume that
the OS tells the MB to go to sleep mode S3 and the MB does just that. If the
OS tells the MB to go to sleep mode S1, it will do that also. However, S1 is
not as low power as S3, so that is why the fans continue to run. Here again
the Power Supply takes it's directions from the MB, which takes it's
direction from the OS.
What concerns me here is what changed relatively recently. Both my
computers(WinXP Pro and Win2k) used to operate properly for S3 sleep
mode(Standby). In both cases something changed, relatively recently. I'm
beginning to believe that it may have been SP1 for WinXP Pro and SP3 for
Win2K. It seems to me that a change was made to the ACPI function of the
OS's and quite possibly a change for the good. However, there seems to be a
problem in the OS updating it's sleep mode capability, based on a change in
MB/Bios mode capability. In this case, it becomes necessary to use this
Dumppo utility, to get the OS back on track. I wish someone that new about
this issue would comment.
Hope all of that makes some sense
Bob
"Robert Carr" <rac...@cox.net> wrote in message
news:k95q9.23537$r83.1...@news1.west.cox.net...
Steve Mowbray
good to have the other one sorted. You may be right that the older
motherboards are beyond fixing.
I am disappointed that BIOS and XP power management does not make this
functionality a little less obscure and the fact that neither
Microsoft/Asus/Award have any (easily) identifiable information relating to
it.
Cheers
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:sbhq9.27510$r83.2...@news1.west.cox.net...
Robert Carr
the S3 Standby state has reverted to S1(Fans keep running, etc.). My BIOS
still has ACPI Suspend to RAM enabled and Dumppo still reports that I have
S1, S3, S4 and S5 capabilities. Looks to me like the OS forgot what I told
it to do yesterday. Oh Well.
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:kRjq9.3758$Wu3.37...@news-text.cableinet.net...
RKelly
Running Win98SE on a Asus TUSL2-C (Intel815EP) chipset.
STR(suspend to RAM) enabled in BIOS.
Power off = "suspend", not "soft off" in BIOS.
In OS power management settings, power button press = standby, not shutdown.
While in windows or DOS prompt pressing power button will suspend machine,
only blinking power LED and no fans spinning. PERFECT! Wakes up correctly
too.
While in windows, choose START, SHUTDOWN, STANDBY, same as above, wakes up
perfect everytime. Am NOT using dumppo.
Here's where it doesn't work, if computer is left unattended for longer than
the settings in power management, thus inducing system standby state, system
will NOT completely go into standby. SAME AS YOU GUYS!!!!! Monitor shuts
off, hard drives turn off but fans still spin!!
As Jahesh says at the very beginning of this thread make sure STR is ENABLED
and "boot from LAN" or "wake up on LAN" are DISABLED
STR was enabled but it was set to "wake on LAN". I changed it to disable in
BIOS and now PERFECT!
System goes into standby perfectly, all 3 fans connected to brd including
CPU, PSU, front chassis fan turn off. Video card fan too.
PSU fan shuts down because I have an Enermax PSU that has a 3 wire plug for
its fan power and monitoring which is connected to the m/brd connector.
Hope this helps!!
RK
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:X9Bp9.341$E25.2...@news-text.cableinet.net...
John
>
> Have you made sure that Suspend to RAM Capability is set in the Bios, if
> indeed this m/b supports it? Asus' www is down so can't check.
>
Yes, I set the Suspend to ram capability for AUTO. The choice is Disabled
or Auto. If I set it to Auto, The system won't wake, as described earlier.
If I set it to Disabled, It does wake up, but no STR.
Steve Mowbray
button and manual standby mode was fully operational, why was the auto
standby any different.
Also why should Wake on LAN disable S3 mode down to S1 mode, cant the LAN
card operate on the 5VSB power.
The PSU fan still spinning is just my mistaken way of saying that the PSU
remains in full power mode. You can check this by opening and closing a CD
drive bay - they are still powered even though the system is in standby
Cheers
Steve
"RKelly" <rjk...@nospam.nb.sympatico.ca> wrote in message
news:pSlq9.1804$UV3.2...@ursa-nb00s0.nbnet.nb.ca...
Steve Mowbray
Cheers
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:w3kq9.28249$r83.2...@news1.west.cox.net...
RKelly
card fully ACPI compliant?? I don't know. Previewing the setting in Windows,
it appears to have all the options associated with power management though.
It has the WOL cable too.
Without disabling "wake on LAN" in bios, the system would not fully shut
down the PCI buses. Even the GF3 vid card fan would still spin!!
When "wake on LAN" is disabled in BIOS the entire system goes into standby.
I guess when you press the power button or tell the system to go into
standby(thru start menu), you're bypassing settings, telling the system not
to wait for any timers, just go to sleep???
Beats me??
RK
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:ILyq9.290$wT6.3...@news-text.cableinet.net...
Robert Carr
Yes I agree. However, some more information.
I was searching around yesterday and found some type of forum site that was
discussing the same basic problem that we are. Unfortunately, like a dummy,
I didn't write my search path down and so can't find it anymore. But, I
remembered one very curious statement made by one individual. He described
his Standby problem as only going to S1, just like us. He then said that he
logged off his normal user account and logged on to the computer
administrator account. While on the administrator account he tried Standby
and it worked perfectly, using S3. I thought, oh sure, tell me another one.
Well, I decided to try this and what do you know, it worked. I did power
offs, restarts, hibernates and any time I tried Standby it worked correctly
for S3. What do you think about that?
I then added a new user account and tried that with Standby. S3 worked
flawlessly. I then went back to my usual(normal) user account and Standby
will not do S3, only S1. Retry the news user account and S3 works correctly.
I have to conclude that my normal user account is contaminated in some way.
I have verified this behavior on both my WinXP Pro and Win2K machines. As
long as I stay off of my old user account, it works correctly.
I then tried one more thing. I disabled the "Suspend to RAM" in my Bios. I
then tried Standby with my new user account. It only did a an S1 sleep mode.
I then re-enabled the "Suspend to RAM" in the Bios, tried Standby on the new
user account and it did S3 beautifully. Seems like it's working the way it
should, but not with my old user account.
So I guess I am going to complete the changeover to my new account, unless
someone can tell me how to fix the existing account.
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:ZMyq9.295$AS6.3...@news-text.cableinet.net...
Steve Mowbray
Thanks for letting me know, I will give this a try and report back.
Cheers
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:BcDq9.8$Pa....@news1.west.cox.net...
Steve Mowbray
I created a new user (with administrator group membership). Same problem
standby problem.
I am close to giving up on this - its a bit stupid as windows 98 did standby
okay on the same machine (as far as I remember)
Cheers
Steve
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:aEQq9.1599$iN2.11...@news-text.cableinet.net...
Paul Busby
Steve Mowbray <steve_...@hotmail.com> pulled the chain then typed:
> I created a new user (with administrator group membership). Same
> problem standby problem.
I would be hugely surprised if this made a difference - it's totally
unrelated. Usually accounted for by different a/cs have different Power
policies.
> I am close to giving up on this - its a bit stupid as windows 98 did
> standby okay on the same machine (as far as I remember)
Not so stupid as it sounds. The PM requirements for Win2k/XP were tightened
up compared to W98 - some m/bs couldn't overcome the problem. Sounds like
your m/b is incompatible with ACPI PM. One out of two ain't bad!
Steve Mowbray
Yep, a cheap (but newer) motherboard is probably my next step
Thanks for all your help in this thread
Steve
Robert Carr
When you said: "I would be hugely surprised if this made a difference - it's
totally unrelated.". What did you mean? I wasn't trying to say that what I
discovered would necessarily fix Steve's problem, but it did fix mine, and
thought I should at least relate my findings.
Do you have any insight as to why a particular user account would inhibit
going to S3 Standby ? I certainly don't understand it, but it is fact. I
verified it again, just before this message was sent.
Bob
"Paul Busby" <xbu...@tele2.co.uk> wrote in message
news:uqnree4...@corp.supernews.com...
Paul Busby
Robert Carr <rac...@cox.net> pulled the chain then typed:
> Paul
>
> When you said: "I would be hugely surprised if this made a difference
> - it's totally unrelated.". What did you mean? I wasn't trying to
> say that what I discovered would necessarily fix Steve's problem, but
> it did fix mine, and thought I should at least relate my findings.
>
> Do you have any insight as to why a particular user account would
> inhibit going to S3 Standby ? I certainly don't understand it, but
> it is fact. I verified it again, just before this message was sent.
If PM works in one profile as expected then the Bios, motherboard & OS are
basically compatible. This leaves either PM settings or a corrupted registry
for that profile. Scrapping a profile is inconvenient rather than a disaster
in most cases or if adventurous, edit the user profile in the registry, thus
keeping folder permissions etc if set.
Robert Carr
I now understand what you were saying, Thanks
I did some further testing and evaluation, to attempt some clarification of
the user account issue I observed. I believe my results are, at least,
interesting. The comments in parenthesis are, in my opinion, key points to
note.
I chose to test this issue on my Win2K machine, since I had no OS installed
on it's second hard drive/partition. I did a new install of Win2K. I added
no service packs or other programs, except the video card driver. The video
card driver was necessary to allow for the extended power modes of Standby
and Hibernation.
I also set my motherboard BIOS STR (Suspend to RAM) to the Disable state,
prior to the install, which is what it had been on all prior installs. I
didn't know, back then, that it needed to be enabled to support S3 Standby.
When the install of Win2K was completed I was logged on to the Computer
Administrator account. I tried Standby. It did an S1 standby. I then
restarted, entered the Bios Setup and changed STR to Enable. I then, still
on the Computer Administrator account, tried Standby. It still only did an
S1 Standby.
(The Computer Administrator account will only allow S1 Standby, regardless
of system capability)
I then restarted, entered the Bios Setup and changed STR back to Disable.
Booted backup, created a new user account (Acct1), logged off the Computer
Administrator Account and logged in on Acct1. I then tried Standby. It did
an S1 Standby. I then restarted, entered the Bios Setup and changed STR to
Enable. I then, still on Acct1, tried Standby. It again only did an S1
Standby.
( This new account only allows S1 Standby, like the Computer Administrator
account)
I then created another new user account (Acct2), logged off Acct1, and
logged on to Acct2. (Remember that the BIOS still has the STR set to
Enable.) I then tried Standby. It did an S3 Standby. I then restarted,
entered the Bios Setup and changed STR to Disable. I then, still on Acct2,
tried Standby. It did an S1 Standby. I restarted again, entered the Bios
Setup and Changed STR back to Enable. I once more tried Standby. It did an
S3 Standby.
(This account will allow either S1 or S3 Standby, depending on the system
capability)
One final test. I logged off Acct2 and logged back on to Acct1. (Remember
that the BIOS still has STR set to Enable) Tried Standby. It still only did
an S1 Standby.
(This account is forever stuck on S1 standby)
My Conclusion:
A user account will, at the first attempt of Standby, limit the Standby mode
according to the maximum system capability at that time. This limit will be
"forever". If the systems capability is S1 at the first attempt, it will be
S1 forever. If the systems capability is S3, it will place the limit at S3
and but also still allow the lower mode of S1.
Although my testing only involved the Win2K OS, I strongly suspect that
WinXP is virtually the same, regarding this user account issue.
I don't know, at the present time, where this limit exists. I suspect it
resides in the registry. I have been unable, so far, to find the appropriate
entry.
Bob
"Paul Busby" <xbu...@tele2.co.uk> wrote in message
news:uqoi826...@corp.supernews.com...
Steve Mowbray
solutions.
Does dumppo.exe fix any of the accounts which were created with the S1
limit.
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:rZZq9.13319$Pa.3...@news1.west.cox.net...
Robert Carr
In searching around the web for some info on this whole issue, it appears
that many people have had Standby problems and for a multitude of reasons.
What I, based on a posting comment by someone else, discovered fixed my
problem. However, it may very well apply to some others.
No, dumppo.exe will not fix any of the accounts. For what it's worth, in my
opinion, the dumppo utility doesn't fix anything. It appears to be an
evaluation tool only. In other words, it allows a person to evaluate a
system by forcing specific sleep states. As soon as the system is re-started
or powered off the minsleep setting provided by Dumppo is lost. At least,
that has been my personal experience.
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:L4_q9.2395$ET4.16...@news-text.cableinet.net...
Derrick
However, after disabling the Hibernation mode from Power Options, the S3
setting was retained after a reboot.
As with all things Windows based, your results may vary.
--
Derrick ( 'gd' UNDERSCORE 'brock' @hotmail.com" )
"Robert Carr" <rac...@cox.net> wrote in message
news:Vh_q9.13328$Pa.3...@news1.west.cox.net...
Bill Halvorsen
enjoyed sleep mode and it worked VERY well, very fast restarts. I could
also hibernate, but that just takes too long. Not sure what happened, but I
start to think that a later iteration of ZoneAlarm, in combination with, or
having nothing to do with, the addition of SP1 to Windows XP home, spelled
the end of any type of stable power management. I'm just grateful to get
the @#$^% thing to shut down gracefully, which it does, though Norton
Antivirus 2003 (which won't work anyway) even killed that.
Dumppo still reads what's available, but I agree, it doesn't stick. It DID,
though, for quite a while - who is the culprit, though, s/w installed,
service pack, BIOS limitations, lousy Windows implentation of power
management, I dunno. I had really good luck with this m/b (P4T-E) with ME
and power management. XP was almost as good but couldn't sleep w/o fans.
Dumppo fixed that for months... but here I am again spending hours
reinstalling, rebooting hundreds of times to get power management to work,
and just can't seem to get sleep mode back. Now I have good "off" and good
"hibernate." Standby - nope. Worse, if I fool around, the computer "jumps"
into sleep mode leaving the monitor on and keyboard dead.
If someone has a good combo of Award BIOS settings for XP and power
management I'd be most grateful!
Bill
"Robert Carr" <rac...@cox.net> wrote in message
news:Vh_q9.13328$Pa.3...@news1.west.cox.net...
Steve Mowbray
I agree but from what I gather this _good_ combination seems to be very
elusive. My guess is if it were a solveable problem somebody
(award/asus/microsoft) would have posted a fix but there is nothing
identifiable on any of the likely manufacturers site (software or hardware).
I only got to understand the problem from snippets gleaned from lots of
different contributions in newsgroups.
Thanks to some of the helpful posts in this thread I have one of my two XP
upgraded systems working with normal power management (my third PC is an HP
which worked fine out of the box - someone in HP had enough inside
information from MS and the BIOS provider to be able to sort it out). It
would be nice if the missing information could be shared out for the rest of
us though.
I find it difficult to accept that a function that worked without problems
in win98 (for me at least) should be lost in a supposedly improved operating
system (which is is in many ways if you exclude the power management).
Cheers
Steve
Robert Carr
I'm just curious. If you run " Dumppo admin/ cap " on your older MB(the one
that won't do S3 Standby), does it report back that you have S3 capability ?
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:Ub2r9.2887$XM5.18...@news-text.cableinet.net...
Steve Mowbray
output from dumppo admin /cap
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
Only I get S1 rather than S3
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:0Zgr9.41633$Pa.5...@news1.west.cox.net...
Robert Carr
Maybe I am nitpicking here, but my output seems to be giving different
information. Are we each doing something different? Here is an exact typed
version of my output at the command prompt.
C:\>dumppo admin/ cap
power capabilities
System power capabilities
Power Button Present........: TRUE
Sleep Button Present.........: TRUE
Lid Present.......................: FALSE
System states supported....: S1 S3 S4 S5
Hiber file reserved..............: TRUE
Thermal control.................: FALSE
CPU Throttle control.........: TRUE
Processor min throttle........: 37
Processor trottle scale........: 100 <1%>
Some disk will spindown...: TRUE
System batteries present.....: FALSE
System batteries scale.........: <G:0 C:0> <G:0 V:0> <G:0 V:0>
Ac on line wake ability........: Unspecified
Lid wake ability..................: Unspecified
RTC wake ability................: S4 - hibernate
Min device wake.................: Unspecified
Default low latency wake.....: Unspecified
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:a8jr9.3853$st1.25...@news-text.cableinet.net...
Paul Busby
> information. Are we each doing something different? Here is an exact
> typed version of my output at the command prompt.
>
> C:\>dumppo admin/ cap
> power capabilities
> System power capabilities
> Power Button Present........: TRUE
> Sleep Button Present.........: TRUE
> Lid Present.......................: FALSE
> System states supported....: S1 S3 S4 S5
> Hiber file reserved..............: TRUE
> Thermal control.................: FALSE
> CPU Throttle control.........: TRUE
> Processor min throttle........: 37
> Processor trottle scale........: 100 <1%>
> Some disk will spindown...: TRUE
> System batteries present.....: FALSE
> System batteries scale.........: <G:0 C:0> <G:0 V:0> <G:0 V:0>
> Ac on line wake ability........: Unspecified
> Lid wake ability..................: Unspecified
> RTC wake ability................: S4 - hibernate
> Min device wake.................: Unspecified
> Default low latency wake.....: Unspecified
sleep = S1. You're getting a lot more info, probably being read from your
Bios by hal.dll.
Robert Carr
The only time I get mention of the min and max sleep states, specifically,
is when I do a
Dumppo admin/ ac
The output then looks like this:
Sleep button................: Hibernate<QueryApps :UIAllowed>
Lid close.....................: Disabled Sleep<QueryApps>
Lid open wake.............: Working
Idle..............................: None
Settings........................: Timeout=0, Sensitivity=50
Min sleep state..............: S1
Max sleep state..............: S3
Reduced latency.sleep...: S1
WinLogon Flags............: 0
Doze S4 timeout...........: 0
Battery broadcast res.....: 3
Battery discharge 0.......: No Battery, but enable is set
Battery discharge 1.......: No battery, but enable is set
Battery discharge 2.......: Disabled
Battery disvharge 3.......: Disabled
Video timeout.................: 900
Hard disk timeout............: 0
Optimize for power..........: TRUE
Fan throttle toler...............: 100
Forced throttle.................: 100% <off>
Min throttle......................: 37%
Over throttle act...............: none
When I was describing my user account issue, much earlier in this thread, it
was this printout that would have both the min and max sleep states set to
S1. On a user account that would properly do an S3 Standby, this printout
was as shown above. This particular printout seemed to reflect what was
going to happen, regardless of the "CAP" printout (system
capabilities)listed in the prior post.
I suppose these printouts may be very MB/BIOS dependent.
Bob
"Paul Busby" <xbu...@tele2.co.uk> wrote in message
news:uqrofeh...@corp.supernews.com...
Robert Carr
It was my understanding from a search result on Dumppo, that the "/ cap
"command provided a listing of the system capability(what it was capable
of), while the "/ ac "command provided a listing of the implemented power
policy(what it would do). The results listed in the power policy, I assumed,
was what Windows implemented. Maybe I'm incorrect on these points.
Bob
"Robert Carr" <rac...@cox.net> wrote in message
news:DVlr9.47453$Pa.6...@news1.west.cox.net...
Bob
Pro. Everything was working fine (all fans shut down) until I upgraded the
BIOS and it not longer worked.
I found a tip in this newsgroup six months ago to simply go to the XP
control panel and change the computer type to a laptop and it has been very
reliable since. Simple tip but it works,
Bob
Steve Mowbray
We have a syntax inconsistency in your placement of the frontslash which is
use as a command line switch prefix. Your placement at the end of the admin
switch seems to be invalidating this switch which is obviously then ignored.
See the syntax test results below:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
-- test 1 : bobs
syntax ---------------------------------------------------------------------
C:\Documents and Settings\Administrator>dumppo admin/ cap
power capabilities
System power capabilities
Power Button Present....: TRUE
Sleep Button Present....: FALSE
Lid Present.............: FALSE
System states supported.: S1 S4 S5
Hiber file reserved.....: TRUE
Thermal control.........: FALSE
CPU Throttle control....: TRUE
Processor min throttle..: 50
Processor trottle scale.: 100 (1%)
Some disk will spindown.: TRUE
System batteries present: FALSE
System batteries scale..: (G:0 C:0) (G:0 C:0) (G:0 C:0)
Ac on line wake ability.: Unspecified
Lid wake ability........: Unspecified
RTC wake ability........: S4 - hibernate
Min device wake.........: Unspecified
Default low latency wake: Unspecified
-- test 2 : no admin switch, same result as bobs
yntax ---------------------------------------------------------------------
C:\Documents and Settings\Administrator>dumppo cap
power capabilities
System power capabilities
Power Button Present....: TRUE
Sleep Button Present....: FALSE
Lid Present.............: FALSE
System states supported.: S1 S4 S5
Hiber file reserved.....: TRUE
Thermal control.........: FALSE
CPU Throttle control....: TRUE
Processor min throttle..: 50
Processor trottle scale.: 100 (1%)
Some disk will spindown.: TRUE
System batteries present: FALSE
System batteries scale..: (G:0 C:0) (G:0 C:0) (G:0 C:0)
Ac on line wake ability.: Unspecified
Lid wake ability........: Unspecified
RTC wake ability........: S4 - hibernate
Min device wake.........: Unspecified
Default low latency wake: Unspecified
-- test 3 : no frontslash prefix to cap switch - gives extra
info ---------------------------------------------------------------------
C:\Documents and Settings\Administrator>dumppo admin cap
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
power capabilities
System power capabilities
Power Button Present....: TRUE
Sleep Button Present....: FALSE
Lid Present.............: FALSE
System states supported.: S1 S4 S5
Hiber file reserved.....: TRUE
Thermal control.........: FALSE
CPU Throttle control....: TRUE
Processor min throttle..: 50
Processor trottle scale.: 100 (1%)
Some disk will spindown.: TRUE
System batteries present: FALSE
System batteries scale..: (G:0 C:0) (G:0 C:0) (G:0 C:0)
Ac on line wake ability.: Unspecified
Lid wake ability........: Unspecified
RTC wake ability........: S4 - hibernate
Min device wake.........: Unspecified
Default low latency wake: Unspecified
-- test 3 : with frontslash prefix to cap switch - gives extra info
only ---------------------------------------------------------------------
C:\Documents and Settings\Administrator>dumppo admin /cap
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
C:\Documents and Settings\Administrator>
----------------------------------------------------------------------------
-------------------------
Sorry about the lenght of this post but dumppo command line syntax seems to
be a bit _loose_. It would help if we could find a command line options
guide to dummppo.
Cheers
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:N8mr9.47484$Pa.6...@news1.west.cox.net...
Robert Carr
Good find on the syntax issue. I just went through the process and it agrees
with your findings. Of course you have now added another inconsistency to
this entire inconsistent Standby process. <G>
Bob
"Steve Mowbray" <steve_...@hotmail.com> wrote in message
news:Zayr9.4778$Rh4.30...@news-text.cableinet.net...
Robert Carr
The same syntax issue also exists for the Ac Power Policy command. I had
been using :
dumppo admin/ ac
dumppo ac gives the same results
dumppo admin ac provides the additional admin overrides
dumppo admin /ac provides just the admin overrides
Bob
snipped older stuff
Steve Mowbray
I am assuming you mean the control-panel->power options->power schemes
setting of "portable/laptop". If not please advise.
Cheers
Steve
"Bob" <B...@hotmail.com> wrote in message
news:xTpr9.546378$Ag2.20...@news2.calgary.shaw.ca...
Steve Mowbray
information to draw any conclusions I suspect.
Thanks for perservering - if you find any further leads, please post them.
Steve
"Robert Carr" <rac...@cox.net> wrote in message
news:S9Cr9.72796$Pa.8...@news1.west.cox.net...
Robert Geite
I got similar problems after installing some more RAM and new harddrive
after which my Dell Dimension 8100 would not enter S3 standby state.
Looking for info I found this nice thread and got help from the dumppo.exe
utility.
Trying to add my little bit to it I located the only thing changed (when
changing min sleep) in the registry to the key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Power]
"PolicyOverrides"
This key consists of lots of hex values of which the first is changed when I
change min sleep through dumppo.
I'm not sure if this helps anyone, but it suggests that different users
would not have different settings as I'm pretty sure that all users share
the control sets.
I have rebooted a few times and to me the setting has stuck so my standby is
now working as I want it to.
Cheers,
Robert
"Robert Carr" <rac...@cox.net> wrote in message
news:rZZq9.13319$Pa.3...@news1.west.cox.net...
Paul Busby
Robert Geite <raw...@hotmail.com> pulled the chain then typed:
> Hi all!
>
> I got similar problems after installing some more RAM and new
> harddrive after which my Dell Dimension 8100 would not enter S3
> standby state. Looking for info I found this nice thread and got help
> from the dumppo.exe utility.
>
> Trying to add my little bit to it I located the only thing changed
> (when changing min sleep) in the registry to the key:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
> Manager\Power]
> "PolicyOverrides"
>
> This key consists of lots of hex values of which the first is changed
> when I change min sleep through dumppo.
>
> I'm not sure if this helps anyone, but it suggests that different
> users would not have different settings as I'm pretty sure that all
> users share the control sets.
>
> I have rebooted a few times and to me the setting has stuck so my
> standby is now working as I want it to.
Info filed away. No such override exists on my system probably because I
never needed to change the min state from S1. By the time I heard about
dumppo, I'd long since fresh installed XP.
It will be interesting to see how long S3 sticks on your system as many have
complained that it didn't - though surviving a few reboots is a good start.