Paul,
Thanks for the simulation. I continue to think look and search for the
solution.
The strings from the link you referenced were the ones I used, with some
modification e.g. adding Standby or Hibernate at the end, to create the two
successful desktop shortcuts I am currently using and hey both work without
a hitch.
Standby: %windir%\System32\rundll32.exe powrprof.dll,SetSuspendState Standby
Hibernate: %windir%\System32\rundll32.exe powrprof.dll,SetSuspendState
Hibernate
This is work-around.
You go to your desktop, right click and create a new shortcut, then
for the location type in or cut and paste one of the above commands, click
next and then give the Shortcut a name in the final screen.
Double click and it does what it was commanded to do depending on which
Shortcut your were using. If you are using the Standby then I unchecked
"Enable Hibernation"
I am still hoping to find a way to restore the functionality to the machine
to the extent it goes into Standby or Hibernation on response to its own
triggers.
Thanks for the help.
I will continue to experiment and monitor this link.
Docster said:
Just wondering!!!
When I create a shortcut using [Standby: %windir%\System32\rundll32.exe
powrprof.dll,SetSuspendState Standby] it works like a charm, which suggest
the machine has the capability to suspend and go into a real Standby mode
with no fans turning and with the response to wake up on mouse movement or
keyboard activity. What I would like to know is how do I get my installed
Windows OS to respond the same way. I don't know what the triggers are
that
signal the computer to go into Standby, was caused it to execute the
string
it used to tuck its self in and go to sleep.
I was wondering if, it was possible to somehow bury this string in the
windows directory and link it to the triggering mechanism. Probably not
real
clear so I will try it another way. If I am currently pointing and using
my
mouse to execute the instructions included in the shortcut I created how
do
I get the computer to execute this or a similar action to go into Standby.
I keep thinking if the computer was incapable of going to Standby noting
would put it in that mode, yet I can manually. How do I get it back into
an
automated state is the question. It has done it in the pass. I think I
might
be close to resolving this, with your help, for myself and many other
people. I think the thinking is correct, if you will, just not concluded.
There are enough WinXP users around, and I suspect will be for some time
to
come, that this might be a worthwhile pursuit.
In the article here, there is a suggestion that the Power control
panel options can have an impact on how the system behaves. But I'm
not sure I like doing this.
http://support.microsoft.com/kb/555569
To put the system in to Stand by :-
1] Make sure that the system is hibernation disabled.
The thing is, where are the commands for doing that stored ?
Are they in the registry ? Are they hard coded in a DLL somewhere ?
Are they a response based on checking a whole bunch of registry
values (like the ACPI hive) ? Who knows ?
A respondent in a thread like this one, claimed there were
somewhere around 200 registry entries for this stuff (ACPI
related). And even with all of that, the important bits of it,
might not even be in the registry.
As an example, if I scan the registry for "powrprof.dll", I don't
find it. Neither do I find "SetSuspendState" (in case the
powrprof.dll was implicit).
I was lucky to find the dumppo info, when I needed it...
Another thing I tried to research in the past, was what actually
shuts off the computer. Is it the OS ? Is it the BIOS ? I think
it's some BIOS code that presses the button, but I've not been
able to confirm that.
Paul