Thinkpads Forum

Can't figure this one out. TP600X-450, running W2K Pro, most current BIOS, all Windows patches and service packs applied.

Going to standby/sleep mode, whether commanded in software via W2K, or by closing the lid of the machine, results in a normal sleep. But when the machine is woken up, either by nudging the power button or by opening the lid, there is an interval of anywhere up to 4mins (typically about half that) during which the machine wakes up, but with agonizing slowness.

During that time, the fan runs, and the hard drive light occasionally flickers, and the LED on the wireless card illuminates. Eventually, the screen will light up normally with a login prompt.

I've dug around in the archives but have not found the like of this. Any suggestions which might be of help? Thanks!

My bet would be that your 450Mhz machine is running more like 225Mhz (i.e. half speed). I have a 650Mhz 600X running Windows 2000 Professional SP4. In certain cases, the CPU is throttled down to 330Mhz and it's not a SpeedStep issue. Windows 2000 is controlling the front side bus speed and instead of being run at 100Mhz, it's changed to 51Mhz. The appropriate item to check is the Power Option Properties. Change it to Maximum Performance (I'll bet that it isn't already), re-boot and see if your speed picks up.

edit: BTW, you may want to download a copy of CPU-Z in order to measure your bus/processor speeds. You can get it at:

http://www.cpuid.com/cpuz.php

You could also try pulling out your wireless card and seeing if that makes any difference. Sometimes the computer can slow down forever waiting for network connections to be re-established the way it remembers.

If the problem turns out to be your network connection, then there isn't really a solution, but at least you've figured out the source of the delay.

Phil.

Okay, I think I have solved this by pure thumbfingered empiricism.

What I had done previously when waking the machine was to immediately invoke Fn-F2 after opening the lid or pressing the power button. That did not do the job.

But waiting for ten seconds and then invoking Fn-F2 does produce an immediate wake. I can't speculate as to why there is a window of unresponsiveness at the very first.