Resume via WOL results in 2 minutes timeout to standby.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

XP Pro SP2, all updates etc. Compaq Deskpro with up to date drivers.

When my PC resumes from standby via key press or mouse it then goes into
standby mode after 20 mins of inactivity as set in control panel/power
options. Fine.

However, when my PC resumes from standby via WOL/PME, it goes into standby
after 2 mins of inactivity, ignoring the 20mins setting in control
panel/power options.

There is no Bios or NIC setting to change this timeout. MS Tech Support not
much help.

Any suggestions please?
 
I'm in the same situation. Apparently, XP doesn't know why the system woke
up, so it just shuts down if it doesn't detect specific activity within 2
minutes. I'm doing RPC to this system, and SOME tasks that I start will reset
the inactivity timer, but others will not. If I knew what windows was looking
for, I'd write a small util to give it a nudge, but the KB article on this
behavior offers no suggestions, it just documents the timeout as a fact of
life (no help there).

I don't want to be so crude as to fake out a keystroke, so I'm looking for
something a bit more elegant. I'd settle for some kind of net keepalive
packet, but I haven't found anything yet.
 
I still haven't found a solution. Yesterday, I used WOL to wake up my system,
then started a remote desktop session. I started streaming video from that
system using uPnP, and I also was pinging it from another system. It still
went to sleep after 2 minutes. I woke it again, then sent a keypress every
minute via remote desktop, and it stayed awake.

Does anyone know where I could find some source or utils that monitor
whatever XP is using for its activity timer? There are some programs that
will keep the system awake, but apparently the uPnP server isn't one of them.
I'd like to write a keepalive that watches for uPnP activity, but what do I
do to keep Windows from nodding off?
 
Back
Top