Link to home
Start Free TrialLog in
Avatar of steva
steva

asked on

W2K Boot Delay

When I boot my Windows 2000 system there's a 90 second delay after I enter Ctrl-Alt-Del and log in before the desktop icons appear. During this time the mouse pointer is alive but the screen is a solid color.  Does anyone have an idea what Windows 2000 is doing during this time, and how I can eliminate the delay?

Thanks

Steva
Avatar of jhance
jhance

Have you installed SP2?  There are a number of issues that can cause this and many are fixed with SP2.
Avatar of dew_associates
There could be many reasons, especially if you have the system networked or you have a high speed connection such as DSL etc.

Dennis
In addition to the above
 Cleanup the startup stuff. In,  NT or win2k,
Download the Startup COP a free pcmag utility from
http://www.zdnet.com/downloads/stories/info/0,,77594,.html
 Run it and it will show you everything that is listed in all the possible startup
                        places, and allow you to disable things one at a time until the problem is eliminated.
 A lot of probelms are caused by excess old baggage - programs that have not been properly  un-installed. Startup Cop will eliminate leftovers and un-wanted programs that you no longer want.
Older Antivirus programs and Norton Utilities have been known to cause problems
try disabling them also !

I hope this helps !
Avatar of steva

ASKER

Hi guys,

Yes, I have SP2 installed.

I do have the system networked, but it's only back-to-back to another W2K machine, and the  "Setting up networking"  message comes and goes long before I log in and  this delay starts.

I downloaded and installed Startup COP, but it doesn'tseem to  do anything.  I see exactly the same delay, with no messages from Startup COP that help me.  I notice in the Readme for Startup COP that it doesn't say it works with  W2K.

Any more ideas?

Steva

ASKER CERTIFIED SOLUTION
Avatar of SysExpert
SysExpert
Flag of Israel image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of steva

ASKER

Problem solved!  The event logs showed that QoS Packet Scheduler service was timing out because Active Directory wasn't configured properly.  I don't care about this service.  It got added in as an oversight when I added Network Monitor.  Uninstalling it solved the problem.

Thanks

Steva