Windows NT 4.0 Workstation Hang on Startup

[gary]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Gets past the OS selection screen, the Checking Hardware
message appears and that's it, the OS doesn't load, no
feedback, no error messages, nothing. I've checked the PC
over and all the hardware seems fine but without feedback
from the OS I'm not sure where to go from here.

This is a corporate machine and if I can't recover the OS I
can re-image it but I would prefer not to since the user
has a lot of extra software installed that we do not put in
our base image.

Any help/feedback would be greatly appreciated!

Thanks
Gary

 

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Boot from the nt cd and pick repair, use erd if you have
it.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

>-----Original Message-----
>Boot from the nt cd and pick repair, use erd if you have
>it.
>.
>

We have ERD bootable CDs, problem is I still don't know
what to repair once I get the ERD command line up and
running. We do not keep NT recovery diskettes for our
systems (which in hindsight seems like a good idea! ;-) so
I cannot initiate a repair in that manner either.

Thank you
Gary

 

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

I'm not sure what an "ERD bootable CD" is. If you boot
off a plain old Windows NT system CD, you get the repair
option.

 

[gary]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

>-----Original Message-----
>I'm not sure what an "ERD bootable CD" is. If you boot
>off a plain old Windows NT system CD, you get the repair
>option.
>.
>

Emergency Repair Disk, it boots you up to a DOS like
command prompt and gives you full access to the system
without the GUI so that you can go in and replace damaged
drivers, sysmte files etc.

As for booting off of the NT system CD and initiating a
repair you need the NT recovery diskettes at that point so
that the registry can be restored and we do not create
those diskettes for our users.

Thanks for your feedback it is very much appreciated!

Gary

 

[Calvin]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Hi DLW,

you have me totally mystified trying to work out what you are talking about.

In NT4.0 there is NO way to boot to a command prompt only. There are third party
products (not free) from suppliers like WinInternals (ERD Commander) that can do
what you describe, or if you have access to a Win2k or later CD it is possible
to use the 'repair console' function provided on them to work with an NT4.0
machine, but they are the only options along the lines you are suggesting.

With creativity, the code provided by Peter here:
http://home.eunet.no/~pnordahl/ntpasswd/ may be able to be used for similar
activities, but I have never personally tried. Does anyone know of any other
options ?

Calvin.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Calvin:
Thank you for taking the time to thoroughly read and
understand my comments in this thread.
DLW.

 

[Calvin]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Hi Gary,

you have me totally mystified trying to work out what you are talking about.

In NT4.0 there is NO way to boot to a command prompt only. There are third party
products (not free) from suppliers like WinInternals (ERD Commander) that can do
what you describe, or if you have access to a Win2k or later CD it is possible
to use the 'repair console' function provided on them to work with an NT4.0
machine, but they are the only options along the lines you are suggesting.

With creativity, the code provided by Peter here:
http://home.eunet.no/~pnordahl/ntpasswd/ may be able to be used for similar
activities, but I have never personally tried. Does anyone know of any other
options ?

Calvin.

 

[Calvin]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Hi DLW,

I think we were actually both 'preaching from the same sermon' actually 🙂

Hopefully the guy who started this strange thread has worked out what is going
on - it sounded very much like he was a bit lost !

I just realised when your reply appeared that I had sent the response to the
wrong part of the thread :-(

I prepared my answer, and then checked to whom it should be addressed, realised
it was supposed to go to Gary, NOT YOU, and fixed it, but obviously wound up
transmitting both replies. The one addressed to you wasn't meant to be sent -
operator finger trouble :-(

Humble apologies,

Calvin.