Windows Forum

Ask something
Discussion Locked

NT WS 4.0 automatically shuts down.

0 helpful
3 replies

by hotzmiller

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The user came to me, placed a pc onto my desk and asked me to restore the backup of another pc onto this one so it could be used as a spare. The original pc is used in manufacturing production to control equipment. Having no choice, I said I'd try.

I installed WinNT WS 4.0 inot a different directory than it is installed on the original PC. I then restored the backup onto that PC, edited Boot.ini so I could go back to my fresh install, if needed, and rebooted.

Here's the trouble:
1. The workstation is a member of our NT domain. The production PC is onthe network 24 hrs a day.
2. The workstation is configured to automatically log on to a domain account without administrative rights. Because I am keeping the PCoff the LAN, the logon fails and uses cached information. I can't get on the LAN anyway until I change the PC name and ip address. I am considering changing the production PC, but it is in constant use and this is not an emergency.

5. Fifteen seconds after Windows is started, the PC shuts down. I don't know why or how, excpet that it is a "normal" shutdown, apart from the fact I did not implement it.

So, I tried a emergency repair - that caused the cached password for the auto logon to fail. Now I canlogon with an administrative account. It still autoamtically shuts down.

Next I tried an upgrade install into the same directory. That was no help at all.

I can still boot to NT in my first install on the hard drive.

Perhaps I can edit the registry of one while booted to the other? I need to do so, I think. Any suggestions?

3 replies

by bohicam1

The only thing I can come up with is an automated logon script that you backed up with the workstations data that tells it to shutdown if it cannot connect to a domain. Have you checked to see if there is anything on there during boot that suggests that this may be happening? BTW, if you install concurrent installations of winnt, you will be given the option of which version to boot into at bootup, there is no need to edit the boot.ini file. The latest install will be the first one listed.
Good luck!

Mike

by hotzmiller

There is no script. The production PC is running fine. I restored a complete backup of the production PC to the hard drive of the spare PC.

I had to edit boot.ini because the second OS was not "installed", but restored from a backup.

This discussion is closed to new replies.