Reinstalling NT 4.0 over itself.

Printable View

July 22nd, 2003, 01:14 PM
Low_Level_Owl

Reinstalling NT 4.0 over itself.

Will all the apps still work? Will security remain intact? Drivers....

I was installing SP6a on a bunch of machines and this one started popping up messages about corrupted or missing files....after a few hours it's still the same...I want to try an inplace reinstall.

Will it work?!?!?!
July 22nd, 2003, 01:28 PM
silencio

No. The only way to fix an install of NT is to repair it. A reinstall will create new sids.
July 22nd, 2003, 01:34 PM
Low_Level_Owl

I tried a repair. It only made it worse!!!!

:mad:
July 22nd, 2003, 01:52 PM
silencio

Try a parallel install, remove the important data and reinstall clean.

If it's a PDC you have a problem. :p
July 22nd, 2003, 01:59 PM
Low_Level_Owl

If it was a PDC, I would of gone home crying to mommy!!!!

I tried a repair and it worked this time. I've been given the O.K. to wipe it out and install 2000.

Luckly for me he's fairly new so he's only got a few documents and not much else.
August 8th, 2003, 11:39 AM
amyb

reinstalling

I had a similar problem..this was after I ran all the updates via the M$ site(after updating, got a ntoskernl.exe error). After reinstalling (repair made it worse), I now have a blinking cursor..ARGGGGGHHHHH. :flame:
August 8th, 2003, 12:23 PM
PeLiGrOsO

2000 good, nt bad :D
August 8th, 2003, 01:04 PM
amyb

but why???

I have never seen a blinking cursor occur after a supposedly without errors installation..Has anybody? Can't wait until Monday so I can experience the user's wrath.:eek2:
August 8th, 2003, 05:21 PM
silencio

Re: but why???

Quote:

Originally posted by amyb
I have never seen a blinking cursor occur after a supposedly without errors installation..Has anybody? Can't wait until Monday so I can experience the user's wrath.:eek2:

I've seen it in association with the wrong (or corrupt) bootdd.sys or boot.ini reference. Also, a reinstall into an old directory mixes and matches files that simply won't work together. There is a way to lay a service pack onto an install without booting into NT... can't remember how but it's probably on technet or the MS knowledge base.

If you have a blinking curser try making a NT boot floppy (format in NT, copy boot.ini, ntdetect.com, and ntldr to the floppy), edit the boot.ini to match your current disk/os configuration and try booting from the floppy. It's easier than it sounds. Sometimes that doesn't work with the new raid controllers. In that event, change the arc path to SCSI (if it was MULTI before), copy the RAID controller driver to the floppy and rename it bootdd.sys. I've had to do this a couple times..
August 8th, 2003, 05:46 PM
amyb

interesting..

Thanks. I'll try that on Monday. It's just one of those days..ya know..where soap operas would be a welcome alternative..:eek: Just kidding of course..
August 11th, 2003, 08:53 AM
amyb

argh

That didn't work, still have the blinking cursor..:confused:
August 13th, 2003, 06:15 PM
amyb

AHH, forget about it..

We just decided to scrap NT and just update it to W2K then upgrade to XP. Since it was a lab machine we had to make sure that MassLynx would play nice with XP. It will. Very strange though about that cursor though even after trying to do a parallel install..Oh well.:sad: