Windows 2000 Pro hangs on start up

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I restart, the computer appears to stop responding (hang) and takes an
unexpectedly long time, up to 30 minutes, to start.

I found an article - 312945 - that describes a similar problem cause by
Lexmark software. There is no Lexmark software on this system.

Does anyone know of other software that may cause this?

Thank you,
Shawn
 
A failing hard drive can cause this, as the drive's built-in code
executes thousands of retries while the OS simply waits for a critical
access to complete. This sort of thing leaves no logged "footprints,"
and before the drive totally dies a successful access may occur after
many retries.

I'm sure there are other conditions as well, like an apparently
corrupted system routine, perhaps residing on a patch of oxide that
ought to be marked bad.
 
Thank you for the suggestion.

I ran scandisk. Although there was no report of bad sectors, an interesting
thing happened: It wiped out my system.ini, win.ini, and boot.ini files. It
reported the files as invalid and truncated them. I restored them from
backups.

I have been trying to get a bootlog but it does not create file.

There is a second installation of 2000 on the drive and it boots fine.
 
Scandisk won't detect the kind of error I was talking about. No software
that uses the system API hooks will, including the system itself.
Drive manufacturers provide standalone diskette-booted drive diagnostics
that detect (and sometimes correct) problems. Such diagnostics are free
and downloadable, and usually must be run before tech support will give
you an RMA for a replacement drive.
 
Shawn - I should have pointed out that there is no scandisk in W2k. The
improved software in W2k is called chkdsk. I hope you meant chkdsk!
 
Dear Shawn,

Any change that the the Post SP4 Rollup pack would have been applied to this
computer, either buy you or the automatic update process?

While your at it, what make/model of computer is it?

Svend.
 
Lukesh,

Thanks for your input.

I tried msconfig.exe with no success. the only way to get a quick boot is
"safe mode". Any setting in msconfig results in a delayed boot. I tried with
the system.ini, win.ini, & boot.ini all disabled.

It would not even produce a bootlog when that option was set.

Shawn
 
Svend,

Thank you for the suggestion.

There is a good chance that the Post SP4 Rollup pack was applied. Is there
known problems with it?

The system is a Dell Dimension 4100, 930Mhz CPU, 512M RAM, 40G HD

Shawn
 
Here's what I've tried:
sfc.exe - no errors, no change
msconfig.exe diagnostic boot with nothing starting - same problem
scandisk - reports no errors.
maxtor disk tool - no errors.
installed a 2nd copy of 2000 - it works fine.

I have tried to have Widows create a bootlog but it never does.

Shawn
 
I uninstalled the Rollup - no change.

Shawn

Svend said:
Dear Shawn,

Any change that the the Post SP4 Rollup pack would have been applied to this
computer, either buy you or the automatic update process?

While your at it, what make/model of computer is it?

Svend.
Click to expand...
 
Hi Shawn,
Try detaching the non- on board hardware one by one and see if there is any
difference.

Lukesh
 
Back
Top