5 minute startup on new T60 - suggestions?
Posted: Mon Sep 03, 2007 1:07 pm
Guys- I just took delivery of a 2613CTO (T7200 C2D, 100/7200 HDD, 1GB (1DIMM.. for now) 15" IPS SXGA+, Radeon X1400, IBM 802.11 a/b/g w. Bluetooth, no WWAN).
The installed OS was XP Home, but out of the box I removed all the trialware I knew I didn't need and then did an in place upgrade to XP Pro SP2 with Volume media. That went AOK with no problems. Then I put Office 2007 on, and a few other essentials (graphics viewer, Nero, Firefox.)
The system run's great except for this -- at boot the system comes up in normal time, I can logon (using the FP reader) and the desktop comes up pretty quickly. But the HDD stays occupied for at least 5 minutes, and in the mean time the system is unresponsive. The mouse moves, and the keyboard lights (Caps Lock, etc) respond, but until the disk activity stops I can't do anything. Once its settled down, the system is sweet. The event log doesn't show anything abnormal, but I have a feeling something in the stock package is a resource hog.
I did make a pretty big (5GB) Security volume with the Security software, and think maybe de-crypting this is part of the long delay? That's just a wild guess, though.
If anyone has a suggestions for other components to remove or where else to look I'd appreciate it.
In a couple of day's I'll have the extra 1GB stick of RAM and I'll see how that helps.
Other than that, it's a boss machine.
The installed OS was XP Home, but out of the box I removed all the trialware I knew I didn't need and then did an in place upgrade to XP Pro SP2 with Volume media. That went AOK with no problems. Then I put Office 2007 on, and a few other essentials (graphics viewer, Nero, Firefox.)
The system run's great except for this -- at boot the system comes up in normal time, I can logon (using the FP reader) and the desktop comes up pretty quickly. But the HDD stays occupied for at least 5 minutes, and in the mean time the system is unresponsive. The mouse moves, and the keyboard lights (Caps Lock, etc) respond, but until the disk activity stops I can't do anything. Once its settled down, the system is sweet. The event log doesn't show anything abnormal, but I have a feeling something in the stock package is a resource hog.
I did make a pretty big (5GB) Security volume with the Security software, and think maybe de-crypting this is part of the long delay? That's just a wild guess, though.
If anyone has a suggestions for other components to remove or where else to look I'd appreciate it.
In a couple of day's I'll have the extra 1GB stick of RAM and I'll see how that helps.
Other than that, it's a boss machine.