enabling ACPI after XP install
Raginfury
standby function doesn't react properly: it will keep the fans running.
When I installed winme for testing(AFTER enabling) it did work properly:
shutting down etc.
so is there a way to enable suspend to ram for windows xp after
installing the OS?
Paul
SDK.
Paul
"Raginfury" <ba...@1000mbit.replacethisbyNL> wrote in message
news:MPG.189563919...@newszilla.xs4all.nl...
Robert Hancock
works to enable S3 suspend (main power off, RAM contents maintained using
the +5VSB power from the power supply) for that session, but it doesn't save
across reboots so you'd have to re-run it each time you rebooted. Hopefully
Microsoft will address this in a future service pack or something..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hanc...@nospamshaw.ca
Home Page: http://www.roberthancock.com/
"Raginfury" <ba...@1000mbit.replacethisbyNL> wrote in message
news:MPG.189563919...@newszilla.xs4all.nl...
Raginfury
don't have the file on my harddisk. What does the file do and do you
know a good place to start looking for it?
thanks.
In article <nt6dnUIjR6f...@comcast.com>,
someone_who_does_not_want_spam@nobodies_business.org says...
Raginfury
1000mbit.replacethisbyNL says...
> Google nor microsoft.com searches show me any downloadable result and I
> don't have the file on my harddisk. What does the file do and do you
> know a good place to start looking for it?
> thanks.
I found the file and think i'll have to add the line
dumppo admin/ ac minsleep=S3
to my registry in the startup part. thanks.
Raginfury
1000mbit.replacethisbyNL says...
like this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"sleeper"="C:\\dumppo.exe admin/ ac minsleep=S3"
Nom
That's it. Worked fine for me too.
Nom
Eh ?
Start > Run > dumppo.exe admin/ ac minsleep=S3
It only needs to be run once - your method will do it on every boot !
Paul Busby
> Start > Run > dumppo.exe admin/ ac minsleep=S3
>
> It only needs to be run once - your method will do it on every boot !
Some people have reported that it doesn't stick & there seems to be some
variation on the commandline switch which will work, ie some don't need the
admin part which may or may not be related to its use with Pro or Home. I'm
using Pro so "dumppo admin /cap" reads back the truncated list of available
capabilities. What's needed is some official MS documentation.
--
:) Feedback doesn't cost much bandwidth :)
Opinions are fine - until they masquerade as facts
Chief Toaster Tester: alt.os.windows-xp
Paul Busby
the chain then typed:
> You can try the dumppo.exe method that some have talked about. For
> me, it works to enable S3 suspend (main power off, RAM contents
> maintained using the +5VSB power from the power supply) for that
> session, but it doesn't save across reboots so you'd have to re-run
> it each time you rebooted. Hopefully Microsoft will address this in a
> future service pack or something..
Nothing to do with MS, it's an issue with Asus' Bios implementation which
most other m/b manufacturers aren't suffering from.
--
:) Feedback doesn't cost much bandwidth :)
"Gentlemen - you cannot fight here, this is the War-room!"
from Dr Strangelove
Certified to have *NOT* been checked by AVG anti-virus system!
http://www.virusbtn.com/vb100/archives/products.xml?table
Chief Toaster Tester: alt.os.windows-xp
Paul
once.
It would be nice if M$ would offer some documentation. If not for this
program, then for where this program makes the changes in the registry.
Paul
"Paul Busby" <m...@privacy.net> wrote in message
news:3e2c407a$0$160$65c6...@mercury.nildram.net...
daytripper
<someone_who_does_not_want_spam@nobodies_business.org> wrote:
>"Paul Busby" <m...@privacy.net> wrote in message
>news:3e2c407a$0$160$65c6...@mercury.nildram.net...
>> Nom (b0gvb...@enews2.newsguy.com) pulled the chain then typed:
>> > Start > Run > dumppo.exe admin/ ac minsleep=S3
>> >
>> > It only needs to be run once - your method will do it on every boot !
>>
>> Some people have reported that it doesn't stick & there seems to be some
>> variation on the commandline switch which will work, ie some don't need the
>> admin part which may or may not be related to its use with Pro or Home. I'm
>> using Pro so "dumppo admin /cap" reads back the truncated list of available
>> capabilities. What's needed is some official MS documentation.
>
>once.
>
>It would be nice if M$ would offer some documentation. If not for this
>program, then for where this program makes the changes in the registry.
You really think it would be wise for MS to encourage the type of user that
buys the "home" version of any os to diddle with the registry?
Ooog....That could get very ugly, very quickly...
Paul
"daytripper" <day_t...@REMOVEyahoo.com> wrote in message
news:tpbp2vctsuqjnqj0r...@4ax.com...
I went back to the Home version as the Pro version's cost was to much to
consider. I personally have been tweaking in the registry of all flavors of
Windoze since NT4.0. When I built my last computer, I went back from W2K to
XP Home. I am not in a domain environment so I don't need all the security
features built into the Pro version. There are only two things that I miss,
1) being able to manually set permissions on any/all files/folders and 2)
having Terminal Services. The latter is more of a "Ooh neato" factor then
anything else. VNC works for me but it interrupts the screen of the person
who is logged in at the time.
Paul
Paul Busby
> I use Home and it sticks with every reboot. I have only run the
> command line once.
>
> It would be nice if M$ would offer some documentation. If not for
> this program, then for where this program makes the changes in the
> registry.
Nope, nothing to do with the registry unfortunately. If it was, you wouldn't
need to mess with dumppo! AFAIK, dumppo writes to the m/b registers via
hal.dll.
--
:) Feedback doesn't cost much bandwidth :)
Nom
> > Start > Run > dumppo.exe admin/ ac minsleep=S3
> >
> > It only needs to be run once - your method will do it on every boot !
>
> Some people have reported that it doesn't stick & there seems to be some
> variation on the commandline switch which will work,
"Sticks" just fine on mine.
I ran "dumppo admin minsleep=S3"
Nom
> Robert Hancock (GxIW9.72957$Yo4.4...@news1.calgary.shaw.ca) pulled
> the chain then typed:
> > You can try the dumppo.exe method that some have talked about. For
> > me, it works to enable S3 suspend (main power off, RAM contents
> > maintained using the +5VSB power from the power supply) for that
> > session, but it doesn't save across reboots so you'd have to re-run
> > it each time you rebooted. Hopefully Microsoft will address this in a
> > future service pack or something..
>
> Nothing to do with MS, it's an issue with Asus' Bios implementation which
> most other m/b manufacturers aren't suffering from.
Er, no.
Assuming you install WinXP SP1 *AFTER* you've enabled STR S3 in the BIOS,
then DUMPPO isn't needed.
If you install WinXP, and STR S3 is disabled in the BIOS, there's no way to
enable it in WinXP, without using DUMPPO.
Paul
> need to mess with dumppo! AFAIK, dumppo writes to the m/b registers via
> hal.dll.
> --
Okay, I'll bite. What registers on the mobo could this NT-only-based program
write to? If I go back and do a 'dumppo cap', I still see that the mobo
supports "S1 S3 S4 S5". If I do a 'dumppo admin' it reports "Admin policy
overrides" as having a min sleep state of S3 like I told it to do. Using some
logic you would have to conclude that it is a OS limitation. In other words,
if S3 is not enabled before XP installation, then you have make the OS aware
S3 is available. Now I might buy your statement if you were to say that
dumppo updates the hal.dll file directly. That makes sense too.
Paul
Raginfury
says...
it doesn't on mine. what os and mobo?
here P4PE, bios 1003b6
WinXP pro SP1.
Dave
If I can jump in here, I'm going to be putting together a P4T533-C for a
friend this coming week using WinXP Home. Is this whole issue about sleeping
or hibernating the computer tied to how I initially set up the BIOS when I
first boot up but BEFORE I install the OS? Can you offer any advice as to
how I should make these settings?
TIA,
Dave
Paul Busby
> If I can jump in here, I'm going to be putting together a P4T533-C
> for a
> friend this coming week using WinXP Home. Is this whole issue about
> sleeping
> or hibernating the computer tied to how I initially set up the BIOS
> when I first boot up but BEFORE I install the OS? Can you offer any
> advice as to
> how I should make these settings?
It's fairly simple. Enter the Bios, Power menu then enable the setting
called something like Suspend to RAM Capability. While you're in the Bios,
search out P&P OS & turn it *OFF*.
Paul Busby
> Okay, I'll bite. What registers on the mobo could this NT-only-based
> program write to? If I go back and do a 'dumppo cap', I still see
> that the mobo supports "S1 S3 S4 S5". If I do a 'dumppo admin' it
> reports "Admin policy overrides" as having a min sleep state of S3
> like I told it to do. Using some logic you would have to conclude
> that it is a OS limitation. In other words, if S3 is not enabled
> before XP installation, then you have make the OS aware S3 is
> available. Now I might buy your statement if you were to say that
> dumppo updates the hal.dll file directly. That makes sense too.
>
> Paul
I'm quoting a plausible explanation from several months ago on this NG. At
first I thought that hal.dll was some sort of configuration file but its
date was well before I installed & I didn't tweak at the time that it was a
dll! This file acts as an interface to the m/b registers. Quite what's going
on, I'm not certain.
When I 1st installed XP, I didn't set the capability in the Bios & searched
for the location in the registry to enable S3 rather than S1. More than one
person told me that it wasn't that simple. I reinstalled XP after a format &
got it all working. A few months later, dumppo was mentioned & appeared to
help some but not all with this problem & others reported that the setting
wouldn't stick, hence it being loaded at startup. Some also reported that a
repair install didn't set S3 but a suitable Restore point did. I've never
run dumppo in anything but diagnostic mode - if it ain't broke...
Paul Busby
>> which most other m/b manufacturers aren't suffering from.
>
> Er, no.
>
> Assuming you install WinXP SP1 *AFTER* you've enabled STR S3 in the
> BIOS, then DUMPPO isn't needed.
>
> If you install WinXP, and STR S3 is disabled in the BIOS, there's no
> way to enable it in WinXP, without using DUMPPO.
OK, I'll put it differently: if it's a fault with XP, it only appears to be
a problem with Asus m/bs! An explanation I heard was Asus try to implement
S1 & S3 whereas most manufacturers just do one or the other.
Paul
> Paul (MuCcnaw8VZ7...@comcast.com) pulled the chain then typed:
> > Okay, I'll bite. What registers on the mobo could this NT-only-based
> > program write to? If I go back and do a 'dumppo cap', I still see
> > that the mobo supports "S1 S3 S4 S5". If I do a 'dumppo admin' it
> > reports "Admin policy overrides" as having a min sleep state of S3
> > like I told it to do. Using some logic you would have to conclude
> > that it is a OS limitation. In other words, if S3 is not enabled
> > before XP installation, then you have make the OS aware S3 is
> > available. Now I might buy your statement if you were to say that
> > dumppo updates the hal.dll file directly. That makes sense too.
> >
> > Paul
>
> I'm quoting a plausible explanation from several months ago on this NG. At
> first I thought that hal.dll was some sort of configuration file but its
> date was well before I installed & I didn't tweak at the time that it was a
> dll! This file acts as an interface to the m/b registers. Quite what's going
> on, I'm not certain.
>
>
The hal.dll is not a configuration file.
As I recall the design of the NT platform, the HAL (or Hardware Abstract
Layer) is at the bottom of the NT Kernel between the rest of the OS and the
hardware itself. Depending on the type of hardware you are running (i.e. an
Alpha, Intel, PowerPC, Multi-CPU, Compaq etc.) a different HAL is installed
during the installation process. I can only assume that as part of the
installation detection process the HAL will get configured according to what
the NT-based OS thinks the hardware will support. This must occur in software
somewhere, maybe in the hal.dll file itself???
Anyway I decided to do a quick search for information on the hal.dll file and
came across this link. It kind of ties back in with the original subject of
this thread so I am including it here:
http://www.dewassoc.com/support/win2000/tshoot_hal.htm
Yeah, I know it is for W2K not XP, but remember they are both based on the NT
technology so some of the troubleshooting can be used across all three
versions.
Paul
Nom
A78NX Deluxe, Windows XP SP1.
If you reformat, and reinstall XP SP1, with STR enabled in the BIOS, it'll
work fine without DUMPPO.
Nom
> Nom (b0ja4...@enews2.newsguy.com) pulled the chain then typed:
> > "Paul Busby" <m...@privacy.net> wrote in message
> >> Nothing to do with MS, it's an issue with Asus' Bios implementation
> >> which most other m/b manufacturers aren't suffering from.
> >
> > Er, no.
> >
> > Assuming you install WinXP SP1 *AFTER* you've enabled STR S3 in the
> > BIOS, then DUMPPO isn't needed.
> >
> > If you install WinXP, and STR S3 is disabled in the BIOS, there's no
> > way to enable it in WinXP, without using DUMPPO.
>
> OK, I'll put it differently: if it's a fault with XP, it only appears to
be
> a problem with Asus m/bs!
?
It's not a "fault" with either XP or ASUS.
You have to enable STR in the BIOS, *BEFORE* you install XP. And then it all
works fine.
The only "problem" occurs when you install XP with STR disabled in the BIOS.
Even if you enable it in the BIOS, there's no way to turn it on in XP,
without DUMPPO.
The same applies to ACPI.
Paul Busby
<Snipped>
> Anyway I decided to do a quick search for information on the hal.dll
> file and came across this link. It kind of ties back in with the
> original subject of this thread so I am including it here:
>
> http://www.dewassoc.com/support/win2000/tshoot_hal.htm
>
> Yeah, I know it is for W2K not XP, but remember they are both based
> on the NT technology so some of the troubleshooting can be used
> across all three versions.
Thanks Paul, I'll digest that page.
Paul Busby
>
> It's not a "fault" with either XP or ASUS.
>
> You have to enable STR in the BIOS, *BEFORE* you install XP. And then
> it all works fine.
>
> The only "problem" occurs when you install XP with STR disabled in
> the BIOS. Even if you enable it in the BIOS, there's no way to turn
> it on in XP, without DUMPPO.
>
> The same applies to ACPI.
I know it works fine without dumppo - I've even stated that I've never run
it in anything but diagnostic mode basically because once I'd encountered
the problem, I re-installed with the correct Bios setting many, many months
ago & have been beating the drum about it on this group ever since. However,
most boards will not have this problem - it's peculiar to Asus (& perhaps
one or two other boards).