Vista won't wake properly

[Hiawatha Bray]

I'm running Vista Ultimate. It's set to the balanced power plan, which
means that it puts the computer to sleep after one hour of inactivity. Just
one little problem. It won't wake up. When I touch the mouse, I see the
login screen, but I can't type anything in it. Eventually, a screen saver
starts to run, But the computer will not resume what it was doing, and I'm
locked out of it and must reboot. Anybody got any idea why this happens?
It's certainly gotten me thinking that the sleep mode is utterly broken...

 

[Rick Rogers]

Sounds like the keyboard driver doesn't support the sleep function. Check
for an updated one from the manufacturer, and if none is available you may
need to disable sleep mode.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org

 

[John Barnes]

If you run powercfg -a from the command prompt you may get helpful
information. If not powercfg /? will give you a litany of items which may
help.

 

[Hiawatha Bray]

Fascinating. I never heard of that.

I have some el cheapo no-name keyboard. Not sure how to get a driver for
it. But I'll check it out. Thanks.

 

[Hiawatha Bray]

Did a quick check. This is a generic keyboard using the Microsoft keyboard
driver. That ought to work, yes? So why doesn't it? Or could there be a
different problem?

Thanks.

 

[Hiawatha Bray]

Did a quick check. This is a generic keyboard using the Microsoft keyboard
driver. That ought to work, yes? So why doesn't it? Or could there be a
different problem?

Thanks.

 

[Hiawatha Bray]

Fascinating. I never heard of that.

I have some el cheapo no-name keyboard. Not sure how to get a driver for
it. But I'll check it out. Thanks.

 

[Hiawatha Bray]

Okay, here's what I got:


C:\Users\Hiawatha>powercfg -a
The following sleep states are available on this system: Standby ( S1 S3 )
Hiber
nate Hybrid Sleep
The following sleep states are not available on this system:
Standby (S2)
The system firmware does not support this standby state.

 

[Rick Rogers]

Hi,

A generic driver provides basic function (IE: it works in normal operation),
they don't always support advanced features like power saving features.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org

 

[Hiawatha Bray]

OK, but it's the standard Microsoft driver. Why wouldn't it support power
saving? That makes no sense.

You saying I need to buy a different keyboard to use the sleep function?
That sounds downright nuts.

 

[Rick Rogers]

Hi,

No, I'm saying you need a better driver for the keyboard to support the
sleep function. The drivers Microsoft provides for hardware as part of the
OS are often just to provide basic funtion. To get full function, say like
multimedia keys on a keyboard, you need a driver set from the manufacturer.

Microsoft isn't in the driver business, it just supplies those that are
supplied to it. In the case of your keyboard, there is none from the
manufacturer, so the OS assigns one that at least allows you to type in the
basic key commands.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org

 

[NC11]

did this work in XP? is it a new mobo? did you try and change the power
options through the bios?

 

[Hiawatha Bray]

Change through BIOS? Why? What's that got to do with Vista?

 

[Hiawatha Bray]

Sounds like you're saying I need to buy a keyboard...

 

[John Barnes]

Two things are necessary for proper functioning of sleep/hibernation.
Proper settings in the BIOS and drivers for all hardware. Most often if the
BIOS is set properly, you have a driver that causes resume from sleep to
hang. Also the cause for most systems that can't get into sleep mode. I
personally, usually, have to unplug and replug in my network connection when
I resume from sleep or reboot.

 

[Guest]

How hard do you think IBM will laugh at me for asking for "Keyboard" drivers
??? For a 4-5 Year Old Keyboard, that worked with XP, and Linux, and Now in
Vista Decides to be tempramentfull ??

How about you enable the standard MS driver not to send the KB into
hibernate ?