Help me solve a bizarre scheduled tasks conundrum... Please!

Mr. H · 05-22-2006, 07:02 PM

O.K., here's the deal:

I'm running Windows 2000. I schedule a task to open a command window, and in the advanced properties set Windows to wake the computer in order to run the task. Let's call this task "Wake Up".

If I put the computer into hibernation manually by going to Start->Shutdown->Hibernate->O.K., the scheduled task "Wake Up" will successfully awaken the computer.

It is possible to schedule Windows 2000 to enter hibernation by executing the command "C:\WINNT\system32\rundll32.exe PowrProf.dll, SetSuspendState". However, if I do that, the machine hibernates at the correct time, but "Wake Up" will not wake up the computer at the designated time!! (it is possible to manually awaken the computer by pressing the power button, Windows restores just fine)

What's going on?

The only thing I can think of, is that in Scheduled tasks, you can choose which user the tasks should be run as. If I am logged in as "Mr. H", for argument's sake, is it actually the "Mr. H" user that runs the hibernate command if I go to Start->Shutdown->Hibernate->O.K.?

Any other ideas?

Chevy · 05-22-2006, 10:38 PM

Hibernation is not the same as Sleep Mode or Standby.

Hibernation takes a snapshot of RAM, dumps it to a file, and then shuts the computer down. When you power up, it checks the status of that file, and uses it to bring the PC back to the state it was in.

Standby/Sleep are low-power modes where the system is still running - and therefore can be awakened by a system event.

Mr. H · 05-23-2006, 06:11 AM

Thanks for the reply, but, er... I know that suspend and hibernate are different. Trust me, a sheduled task can turn on a hibernated computer, I've done it many, many times whilst trying to solve this issue. But only if the hibernation is initiated manually. That's the weird part.

When a computer is hibernated, the mains is still connected and power is still connected to the motherboard. That's why some PCs can be turned on with the Keyboard or Mouse, or via the LAN, etc.

The command that I quoted ("C:\WINNT\system32\rundll32.exe PowrProf.dll, SetSuspendState") Hibernates the computer.

And so, funnily enough, does going to Start->Shutdown->Hibernate->O.K.

If I use the latter command, a scheduled task does wake up the computer. If I use the former command, a scheduled task does not wake up the computer.

Both ways of initiating hibernation look exactly the same. Windows brings up a dialogue that says "preparing to hibernate" and then the progress bar appears whilst RAM is copied to the HD. Then, the computer shuts off.

This problem, interestingly enough, also occurs if I use suspend instead of hibernate (i.e., scheduled task can wake up from manual suspend, but not from scheduled suspend (which I scheduled using a third-party app))

muleclem11 · 12-10-2007, 11:21 AM

Hello,

I came across this thread while searching for an answer to the exact same problem. I've messed with this issue for days and have the EXACT same problem. Did you ever get an answer as to why a scheduled task will NOT wake up the computer when set to hibernate with the rundll32 powrprof.dll, SetSuspendState?

I can get it to hibernate manually or using a 3rd party solution, or using the shutdown -h command...and then a scheduled batch file WILL wake the computer. However, when running the rundll32 hibernate command (above), the same batch file won't open it. One may be asking, well, why worry? Just go ahead and use one of the other hibernate methods. The reason why I can't is those hibernate methods keep allowing my computer to power on throughout the day.....

Please help...or let me know if you ever figured this out...thanks
vr
Muleclem

05-22-2006, 07:02 PM	#1 (permalink)
Mr. H Registered User Join Date: May 2006 Posts: 2 OS: Windows 2000 and OS X 10.3	Help me solve a bizarre scheduled tasks conundrum... Please! O.K., here's the deal: I'm running Windows 2000. I schedule a task to open a command window, and in the advanced properties set Windows to wake the computer in order to run the task. Let's call this task "Wake Up". If I put the computer into hibernation manually by going to Start->Shutdown->Hibernate->O.K., the scheduled task "Wake Up" will successfully awaken the computer. It is possible to schedule Windows 2000 to enter hibernation by executing the command "C:\WINNT\system32\rundll32.exe PowrProf.dll, SetSuspendState". However, if I do that, the machine hibernates at the correct time, but "Wake Up" will not wake up the computer at the designated time!! (it is possible to manually awaken the computer by pressing the power button, Windows restores just fine) What's going on? The only thing I can think of, is that in Scheduled tasks, you can choose which user the tasks should be run as. If I am logged in as "Mr. H", for argument's sake, is it actually the "Mr. H" user that runs the hibernate command if I go to Start->Shutdown->Hibernate->O.K.? Any other ideas?

05-23-2006, 06:11 AM	#3 (permalink)
Mr. H Registered User Join Date: May 2006 Posts: 2 OS: Windows 2000 and OS X 10.3	Thanks for the reply, but, er... I know that suspend and hibernate are different. Trust me, a sheduled task can turn on a hibernated computer, I've done it many, many times whilst trying to solve this issue. But only if the hibernation is initiated manually. That's the weird part. When a computer is hibernated, the mains is still connected and power is still connected to the motherboard. That's why some PCs can be turned on with the Keyboard or Mouse, or via the LAN, etc. The command that I quoted ("C:\WINNT\system32\rundll32.exe PowrProf.dll, SetSuspendState") Hibernates the computer. And so, funnily enough, does going to Start->Shutdown->Hibernate->O.K. If I use the latter command, a scheduled task does wake up the computer. If I use the former command, a scheduled task does not wake up the computer. Both ways of initiating hibernation look exactly the same. Windows brings up a dialogue that says "preparing to hibernate" and then the progress bar appears whilst RAM is copied to the HD. Then, the computer shuts off. This problem, interestingly enough, also occurs if I use suspend instead of hibernate (i.e., scheduled task can wake up from manual suspend, but not from scheduled suspend (which I scheduled using a third-party app)) Last edited by Mr. H; 05-23-2006 at 06:19 AM.

12-10-2007, 11:21 AM	#4 (permalink)
muleclem11 Registered User Join Date: Dec 2007 Posts: 1 OS: XP Home	Re: Help me solve a bizarre scheduled tasks conundrum... Please! Hello, I came across this thread while searching for an answer to the exact same problem. I've messed with this issue for days and have the EXACT same problem. Did you ever get an answer as to why a scheduled task will NOT wake up the computer when set to hibernate with the rundll32 powrprof.dll, SetSuspendState? I can get it to hibernate manually or using a 3rd party solution, or using the shutdown -h command...and then a scheduled batch file WILL wake the computer. However, when running the rundll32 hibernate command (above), the same batch file won't open it. One may be asking, well, why worry? Just go ahead and use one of the other hibernate methods. The reason why I can't is those hibernate methods keep allowing my computer to power on throughout the day..... Please help...or let me know if you ever figured this out...thanks vr Muleclem

05-22-2006, 10:38 PM	#2 (permalink)
Chevy Retired Join Date: Jul 2003 Location: Notlob Posts: 5,452 OS: Vista Ultimate My System	Hibernation is not the same as Sleep Mode or Standby. Hibernation takes a snapshot of RAM, dumps it to a file, and then shuts the computer down. When you power up, it checks the status of that file, and uses it to bring the PC back to the state it was in. Standby/Sleep are low-power modes where the system is still running - and therefore can be awakened by a system event.