Win2k Running Slow - What to do?

[Citadel535]

I installed Windows 2000 on my system and it takes a long time to start up and shut down. I have a 1200MHz AMD Athlon and 640MB PC133 SDRAM. Tried defragging the hard disk and no good. All that starts up with it is Norton Antivirus and ZoneAlarm.

 

[bjc112]

hmm do u have a network card?... it may havea hard time locating it...

 

[Citadel535]

Yeah an Intel Pro/100+. Why would it redetect each time my system boots?

 

[Razl]

How long is long? W2K is much slower to bootup and shutdown than W98. Also, did you notice your boot time degrading as you added more programs? If so, some of them might be the culprit. You'll need check your registry for applications that REALLY are loading, not just what you see onscreen.

 

[Citadel535]

Since the first boot it was roughly the same speed to the desktop. I was wondering if it has to do with the size of my page file since I am using the recommended size (960-1220). Seemed to run better on my old 233...

Also the programs that load after the desktop is reached is clearly different from boot during the Windows 2000 Built on NT Technology screen.

 

[bjc112]

hm.. my boot time in 2k is faster than 98.. well.. very close..i bet its that card.. could u possibly.. take it out.. or unistall it and try it with out.. ???!

 

[Citadel535]

I think I would hold off on removing it tonight but I will try later and see what happens. Maybe it has to do with how my network connections are set up.

 

[Jittos]

Yes, it could be the network card. It happened to me before on my older computer, while booting, my comp was wating for something. I knoew it was the network card becuse it never happened until I used that card. Is it possible that it was the wake on LAN or some similar feature that caused the problem?
I never fixed the problem, because soon after, I upgraded my computer, and reinstalled everything, and the problem was gone by itself.

 

[mindiris]

You have 2 NICs? If you don't assign a static IP to a NIC, WinNT/2K would spend about a minute just waiting for a DHCP server to respond on startup.

Not sure what could slow the shutdown. One contrived example would be a long, and silent wave file used for the shutdown event, but that's somewhat unlikely. A better idea would be to check what programs are running, and what services are running, and put them on manual or disabled to see what happens.