XP will not "Wake the computer to run this task"

G

Guest

OK, I've been crawling all over the net and can't find a solution to this:

I have a laptop on which I've scheduled a weekly defrag via task scheduler.
I want it to run at 2am.

Task Scheduler is enabled, and all of my scheduled tasks are configured to
run under a local machine account with a non-blank password.

If I'm actively logged on, they all run just fine. If nobody is logged on,
they run just fine, too, you just don't see them pop up. They all run as a
local user account with a valid password.

Here's the problem: once the laptop goes into hibernate mode, none of the
tasks that are scheduled wake the computer up to run.

For the maintenance tasks like disk defragmenting, I tried to have them
start at one o'clock or two o'clock in the morning, but they don't begin to
run until I manually resume from hibernation before I go to work in the
morning.

Laptop is an ACPI compliant Dell; ACPI shows OK under Computer in Device
Manager. Task settings are exactly the same as my work PC, which DOES wake
up from hibernate to run the task.

Only significant O/S difference is Laptop is connected to a wireless LAN via
a built-in wireless NIC, and PC at work is on a wired LAN through a Broadcom
ethernet NIC. Both run XP SP-2 w/ all Microsoft Update patches applied.

Laptop also has Norton AntiVirus / Internet Security with all extra bells
and whistles turned off, while PC workstation runs MacAfee / Network
Associates EPOAgent bundle.

I have read through lots of different descriptions about power management,
and this one appears to be pretty concise:

Description of the Different Advanced Power Management States
http://support.microsoft.com/kb/308535

And here's a TechNet article that definitively states an ACPI-compatible
system can "wake up" from hibernation.

Windows XP Professional Resource Kit
Supporting Mobile Users
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c07621675.mspx

Excerpt:
Enabling Devices to Wake the Computer
On ACPI-compatible systems, Windows XP Professional can enable some devices
to wake the system from hibernation or standby. Windows XP Professional
supports wake events such as modem wakeon-ring, wakeon-LAN, and
wakeon-critical battery. Windows XP Professional also supports wakeon-LAN for
CardBus network adapters. Note that for the wake features to function, they
must be supported by the appropriate computer hardware.
***
So that rules out the popular misconception that "when your system is
hibernating, it's totally off / written to disk / nothing can possibly run".

If I follow the gist of the article, at least three types of wake events are
available: one the modem recognizes (wakeon-ring); one the NIC recognizes
(wakeon-LAN), and one that some battery management / monitoring component (?)
recognizes (wakeon-critical battery).

Given the above, I decided to go into Device Manager on my laptop, and to
look for power management settings on my network cards. Both my wireless NIC
(an Intel PRO/Wireless 2200BG internal PCI card) and the built-in ethernet
card do have some power management settings that you can configure, though
neither of them has a "Power Management" tab on the device properties.
Interestingly, the built-in Conexant modem does have a "Power Management"
tab...

At any rate, the wireless NIC's power management properties consist only of
a slider that goes from low to high; no mention is made in the help about any
"wake up" capability. For all I know, it's possible that the wirless NIC
itself doesn't support wakeon-LAN notification handling. This is the NIC I'm
using on the laptop, and is the reason I mentioned in my original post that
my office PC is using a regular ethernet NIC.

Strangely, though, the Broadcom ethernet card has a "Wake up Capabilities"
property that can be set to "Wake up Frame", "Magic Frame", or "None". I
have no earthly idea what the difference is here, but it's set to "Wake up
Frame". As I mentioned before, there is no Power Management tab with the
"allow this device to bring the computer out of standby" checkbox here,
either.

I had earlier tried enabling the regular NIC on my laptop and seeing if that
worked, but it did not (though I only tested without an actual LAN cable
plugged in.) The author of the article at the following link seems to imply
that Task Scheduler uses the Wake-On-LAN notification mechanism:

XP Pro ACPI, XP task scheduler issues, and a C twist - Printable View
http://www.netadmintools.com/part114.html

I think I read somewhere that there is an API call -- CreateWaitableTimer()
-- that leaves a timer running even when the system is hibernating. What I
don't know is if this is what Task Scheduler uses, and if so, what ACPI
compliant hardware receives the notification when time is up?

I can't figure it out. Can anyone help?


--------------------------------------------
Task settings are as follows:

Main "Task" tab in Task Properties dialog:
-----
Run as: MyLaptop\AnAdminUser

Run only if logged on: Unchecked (no)
Enabled: Checked (yes)


Schedule tab:
-----
Daily, 1am, every 1 day(s)


Settings tab:
-----
Scheduled Task Completed group:
Delete the task if it is not scheduled to run again: Unchecked (no)
Stop the task if it runs for: Unchecked (no max time)

Idle Time group:
Only start the task if the computer has been idle for at least: Unchecked
(no idle requirement)
Stop the task if the computer ceases to be idle: Unchecked (no)

Power Management group:
Don't start the task if the computer is running on batteries: Unchecked (no)
Stop the task if battery mode begins: Unchecked (no)
Wake the computer to run this task: Checked (yes)
 

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