Hibernation problem

L

Lorne

Using SP3 with all updates on a desktop, if I resume after hibernation but
do not click my logo on the login screen within a minute or so the computer
shuts down again.

How can I stop it shuting down unless I tell it to?

It is really anoying to get a phone call just after restarting the computer
and then finding that when the call is over the computer is not up and
running unless I remember half way through the conversation to go and click
the startup logo. All my power option are set to never power down uhnless I
click a button to do so.
 
J

Jose

Using SP3 with all updates on a desktop, if I resume after hibernation but
do not click my logo on the login screen within a minute or so the computer
shuts down again.

How can I stop it shuting down unless I tell it to?

It is really anoying to get a phone call just after restarting the computer
and then finding that when the call is over the computer is not up and
running unless I remember half way through the conversation to go and click
the startup logo.  All my power option are set to never power down uhnless I
click a button to do so.

Is it really a minute or so or is it exactly 5 minutes?
 
L

Lorne

Using SP3 with all updates on a desktop, if I resume after hibernation but
do not click my logo on the login screen within a minute or so the
computer
shuts down again.

How can I stop it shuting down unless I tell it to?

It is really anoying to get a phone call just after restarting the
computer
and then finding that when the call is over the computer is not up and
running unless I remember half way through the conversation to go and
click
the startup logo. All my power option are set to never power down uhnless
I
click a button to do so.

Is it really a minute or so or is it exactly 5 minutes?

I don't know because it has always shutdown by the time I get back - if you
think it is exactly 5 minutes that suggests there is a setting somewhere so
how do I access the setting to change it to 30 minutes?
 
J

Jose

Is it really a minute or so or is it exactly 5 minutes?

I don't know because it has always shutdown by the time I get back - if you
think it is exactly 5 minutes that suggests there is a setting somewhere so
how do I access the setting to change it to 30 minutes?

I think you will find it is 5 minutes.

Windows is working as designed, but perhaps not as desired as you can
read here:

http://support.microsoft.com/kb/318355

Windows doesn't seem to know why it came out of hibernation and
nothing seems to be happening and there is no good reason to be awake
so it hibernates again.

With this behavior, XP has your best interest in mind as usual. I
don't know where to change th setting to not do that but one day I
came up with a way to fool it.

When you power up after hibernation, you (or your computer) needs to
do something active. Doing something active means a keystroke or
mouse movement. If you are not there, something needs to do it for
you, but only when you hibernate.

Create a batch file and run it from a desktop shortcut to put your
system in hibernation. After the hibernation command is executed,
there are more commands in the batch file that will be executed when
the system comes out of hibernation. Those commands will manipulate
the mouse cursor and fool XP into thinking the mouse moved by your
hand - which is enough to satisfy XP to not go back into hibernation.

Here is one way I have tested:

Get the nircmd utility from here:

http://www.nirsoft.net/utils/nircmd2.html

Put the nircmd.exe somewhere in your path or in c:\windows\system32 or
refer to it directly.

Crate a batch file that looks similar to this:


c:\windows\system32\rundll32.exe powrprof.dll,SetSuspendState
Hibernate
nircmd.exe movecursor 10 10
nircmd.exe movecursor -10 -10


When you run the batch file, the system will execute the first command
in the batch file and the system will hibernate. Then when you power
up, the rest of the batch file will run simulating mouse movement.
This will convince XP you moved the mouse and the system will think it
something to do when it woke up (it was not some accidental wake up).

After testing the batch file, create a desktop shortcut to it and use
the new shortcut to invoke hibernation (you'll get used to it).

It is sort of dopey (this workaround) and you will have to remember to
use the shortcut to hibernate and not the usual methods if you want
the results.

I don't advocate batch files or workarounds, but that is all that I
have in my notes for this issue. If there is some other/better way, I
would like to know about it.
 
J

Jose

I think you will find it is 5 minutes.

Windows is working as designed, but perhaps not as desired as you can
read here:

http://support.microsoft.com/kb/318355

Windows doesn't seem to know why it came out of hibernation and
nothing seems to be happening and there is no good reason to be awake
so it hibernates again.

With this behavior, XP has your best interest in mind as usual.  I
don't know where to change th setting to not do that but one day I
came up with a way to fool it.

When you power up after hibernation, you (or your computer) needs to
do something active.  Doing something active means a keystroke or
mouse movement.  If you are not there, something needs to do it for
you, but only when you hibernate.

Create a batch file and run it from a desktop shortcut to put your
system in hibernation.  After the hibernation command is executed,
there are more commands in the batch file that will be executed when
the system comes out of hibernation.  Those commands will manipulate
the mouse cursor and fool XP into thinking the mouse moved by your
hand - which is enough to satisfy XP to not go back into hibernation.

Here is one way I have tested:

Get the nircmd utility from here:

http://www.nirsoft.net/utils/nircmd2.html

Put the nircmd.exe somewhere in your path or in c:\windows\system32 or
refer to it directly.

Crate a batch file that looks similar to this:

c:\windows\system32\rundll32.exe powrprof.dll,SetSuspendState
Hibernate
nircmd.exe movecursor 10 10
nircmd.exe movecursor -10 -10

When you run the batch file, the system will execute the first command
in the batch file and the system will hibernate.  Then when you power
up, the rest of the batch file will run simulating mouse movement.
This will convince XP you moved the mouse and the system will think it
something to do when it woke up (it was not some accidental wake up).

After testing the batch file, create a desktop shortcut to it and use
the new shortcut to invoke hibernation (you'll get used to it).

It is sort of dopey (this workaround) and you will have to remember to
use the shortcut to hibernate and not the usual methods if you want
the results.

I don't advocate batch files or workarounds, but that is all that I
have in my notes for this issue.  If there is some other/better way, I
would like to know about it.

The c:\windows\system32\rundll32.exe... command should be entered all
on one line in the batch file.

The batch file contains 3 lines.

You could also add another line in the top of the batch file to not
see the commands execute:

@echo off

FYI: XP likes to think in seconds so 300 seconds = 5 minutes.
 
O

Olórin

Is it really a minute or so or is it exactly 5 minutes?

I don't know because it has always shutdown by the time I get back - if
you
think it is exactly 5 minutes that suggests there is a setting somewhere
so
how do I access the setting to change it to 30 minutes?

I think you will find it is 5 minutes.

Windows is working as designed, but perhaps not as desired as you can
read here:

http://support.microsoft.com/kb/318355

Windows doesn't seem to know why it came out of hibernation and
nothing seems to be happening and there is no good reason to be awake
so it hibernates again.

With this behavior, XP has your best interest in mind as usual. I
don't know where to change th setting to not do that but one day I
came up with a way to fool it.

When you power up after hibernation, you (or your computer) needs to
do something active. Doing something active means a keystroke or
mouse movement. If you are not there, something needs to do it for
you, but only when you hibernate.

Create a batch file and run it from a desktop shortcut to put your
system in hibernation. After the hibernation command is executed,
there are more commands in the batch file that will be executed when
the system comes out of hibernation. Those commands will manipulate
the mouse cursor and fool XP into thinking the mouse moved by your
hand - which is enough to satisfy XP to not go back into hibernation.

Here is one way I have tested:

Get the nircmd utility from here:

http://www.nirsoft.net/utils/nircmd2.html

Put the nircmd.exe somewhere in your path or in c:\windows\system32 or
refer to it directly.

Crate a batch file that looks similar to this:


c:\windows\system32\rundll32.exe powrprof.dll,SetSuspendState
Hibernate
nircmd.exe movecursor 10 10
nircmd.exe movecursor -10 -10


When you run the batch file, the system will execute the first command
in the batch file and the system will hibernate. Then when you power
up, the rest of the batch file will run simulating mouse movement.
This will convince XP you moved the mouse and the system will think it
something to do when it woke up (it was not some accidental wake up).

After testing the batch file, create a desktop shortcut to it and use
the new shortcut to invoke hibernation (you'll get used to it).

It is sort of dopey (this workaround) and you will have to remember to
use the shortcut to hibernate and not the usual methods if you want
the results.

I don't advocate batch files or workarounds, but that is all that I
have in my notes for this issue. If there is some other/better way, I
would like to know about it.
========
Great answer!
 
D

David Spector

Sure, it's a great answer. Except it doesn't work. And it's been copied elsewhere on the Web...

Me: Windows XP Home SP3.

I've also tried using MacroExpress by itself, and in combination with Springtime Software Events.

Windows is very clever. Only a real user can prevent rehibernation. This is very frustrating in sevaral situations, among them:

* Wake-on-LAN (intentional and controlled) or wake on scheduled job, so a computer can be started remotely or started when no operator can be around (3 AM).

* Starting the main computer then leaving, using VNC (desktop sharing) on a remote device.

"Windows doesn't know why it came out of hibernation--it was probably a mistake, so it goes back in." It's amazing that Windows knows what to do better than we do. Was it too hard to put a flag in the Registry to decide what to do? Oh, wait, I forgot, to ask Microsoft a question costs $99, and even then they don't know. Why? Because only the original programmer knows, and they are long gone, working on the latest bell and/or whistle instead of fixing fundamental bugs. Oh, excuse me, I meant features. Microsoft has no bugs. If they did, they'd have an actual bugs database online for us.

Am I flaming? Sorry.

Since computers can do almost enything, there must be a solution, even an arcane one (modify Windows kernel DLLs, inject a DLL into a Windows process, mount a solenoid to push the mouse around).

I'll continue searching the Web and experimenting myself, but I'm not hopeful.

A hearty thanks, Microsoft, for making our lives interesting!

David
 
K

Klaatu Barada Nikto

EggHead HoopleHead Alert!

David Spector said:
Sure, it's a great answer. Except it doesn't work. And it's been copied
elsewhere on the Web...

Me: Windows XP Home SP3.

I've also tried using MacroExpress by itself, and in combination with
Springtime Software Events.

Windows is very clever. Only a real user can prevent rehibernation. This
is very frustrating in sevaral situations, among them:

* Wake-on-LAN (intentional and controlled) or wake on scheduled job, so a
computer can be started remotely or started when no operator can be around
(3 AM).

* Starting the main computer then leaving, using VNC (desktop sharing) on
a remote device.

"Windows doesn't know why it came out of hibernation--it was probably a
mistake, so it goes back in." It's amazing that Windows knows what to do
better than we do. Was it too hard to put a flag in the Registry to decide
what to do? Oh, wait, I forgot, to ask Microsoft a question costs $99, and
even then they don't know. Why? Because only the original programmer
knows, and they are long gone, working on the latest bell and/or whistle
instead of fixing fundamental bugs. Oh, excuse me, I meant features.
Microsoft has no bugs. If they did, they'd have an actual bugs database
online for us.

Am I flaming? Sorry.

Since computers can do almost enything, there must be a solution, even an
arcane one (modify Windows kernel DLLs, inject a DLL into a Windows
process, mount a solenoid to push the mouse around).

I'll continue searching the Web and experimenting myself, but I'm not
hopeful.

A hearty thanks, Microsoft, for making our lives interesting!

David
 
J

Jose

On 2010-09-10 01:34, David Spector wrote:> Sure, it's a great answer. Except it doesn't work. And it's been copied elsewhere on the Web...



Damn! nearly 4 months ago :)

The better response would have been:

"Great answer and I'm sure it works for everyone else, but it doesn't
work for me"
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top