Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

wint nt server 4.0 restarting while booting 1

Status
Not open for further replies.

PeriyurParthi

IS-IT--Management
Jul 18, 2001
258
IN
hi all
i have installed a vb application on nt 4.0 with sp 3 which its check hardware lock at lpt port, as soon as installations completed , it asked for restart, when i give yes, it keep on restarting( its restart at whiel blue screen comes) i have a huge number of datas in it, now unable to boot the server, please help if anyone knows.looking lot of replies
thanks
parthi
 
Can you hit the Space Bar (just before the Blue Screen) and take another profile?

There will be a message saying to hit the space bar to select a different hardware profile, after hitting the space bar follow the prompts.
New Zealand, a great place to live.
tokala@orcon.net.nz
 
thanks for your response Darr, even if i select another profile , its keep on restarting.. is there anyother way, its very urgent, help me please
thanks
parthi
 
Not sure about your problem but i'd suggest once you do get it running, upgrading to sp6 might not be a bad idea.
 
See if you can boot it in safe mode. If you can then right click on my computer,left click on properties and then take the check mark out of automatically reboot. The you might want to uninstall what you installed. Install SP6 then try your to reinstall your application.
 
thanks dmas and darr,the thing is i cant able to enter into my computer itself,system is not at all geting into desktop, then how can i install sp6, is there any solution please help me...
thanks
parhti
 
Try boot off your Install floppies (or the NT4 CD). When you get to the menu take the R option (Repair) and follow the prompts.

Another option is to put the hard drive into another NT box (Workstation) as the secondary drive. Boot off the workstations' own hard drive and you will then be able to browser the 'faulty' hard drive. Check the AUTOEXEC.NT, BOOT.INI files etc, to see if you can find the problem entry. New Zealand, a great place to live.
tokala@orcon.net.nz
 
hi darrangal,
yeah the same thing i have done by connecting the in anothere winnt server, i cant able to find the files but i dont know what are all the bootable files and where to modify, if you know the bootable file please help,
thanks
parthi
 
Go with The repair option off the NT boot discs. This will restore any damaged files with their default versions and you should at least be able to boot the machine up. If this doesnt work, I'd probably say go with a OS reinstall......a bit drastic, but effective.
 
create a boot disk by placing ntdetect.com ntldr.exe boot.ini from another server and try to see if it will boot up that way
 
With the 'faulty' drive as the slave in another workstation. Make copies of the NTDETECT.COM, NTLDR and BOOT.INI files. Rename the AUTOEXEC.NT file (if you have one) to AUTOEXEC.OLD. All these file are in the root of the boot partition (the C drive).

If you can't see any of these file you will have to set Windows Explorer to Show all file. Open Windows Explorer click View, Options and click the radio button to Show All Files.

Copy the NTDETECT.COM and NTLDR files above from your workstation hard drive onto the 'faulty' drive (the BOOT.INI file should cause the problem). This is like doing a SYS command on a Win98 box.

Reinstall the drive into your server and try again. If that doesn't work try the Repair from the NT Floppies from my previous post.

New Zealand, a great place to live.
tokala@orcon.net.nz
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top