how 2 replace a file

[m4a2t0t]

when i boot up i get this error saying i have a corrupt file and to re-install a copy of it

how do i replace this file?
<windows 2000 root>\system32\ntsokrnl.exe




win2k
NTFS partitions

[Murman]

boot off your 2k cd and repair


http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q124550

[shadrach]

Most often, this error relates to a corrupted or incorrect BOOT.INI file on your system partition.

The ntsokrnl.exe is the first file that the NT loader looks for, so if it can't find the disk LUN, partition, or directory, (or the file) you'll get that message.

[m4a2t0t]

well i just reinstalled and i still get that error so i guess ill rebuild the raid array and repartition the hdd

[m4a2t0t]

so i rebuilt the raid array and ran fdisk and now everytime i run the setup i get a bsod when its copying files.

the first bsod was irql not less or equal and there was a reference to the ntsokrnl.exe

now i get a bsod that says NTFS file system

[shadrach]

Hmm.... something's wrong, or your missing some step...

How much faith do you have in the hardware? Most problems I've ever had with building NT servers and having the setup blowup repeatidly, were hardware related.

Could be bad RAM or CPU oe hard drive.

OR you haven't actually been able to remove the corrupted partition. Can you low level format your drives throught your BIOS?

[m4a2t0t]

well i just replaced the mobo with another one that i have cause i thought it was screwed but it ended up not being bad so it could have something to do with the mobo.

i was planning on writing zeros to the hard drives but thats gonna take a few hours

i can use the cd that came with my seagates to do a low level format.

should i just low level format?

whats the difference between low level formatting and formatting during the 2k setup

[shadrach]

formatting during the Windows setup (and fdisk) simply erase header information, not actual drive data.

On more than one occassion I've seen Windows OS's read that supposedly deleted data and it throws a wrench into the setup process.

In fact I had a similar problem installs Win98 on an older box of my that used to have NT/98 dual boot. The non-dos logical disk in the extened partition can't be deleted by Windows 98 if it is an NTFS volume, so when I tried to remove it through the NT setup routine, it left the partition defined with a bunch of garbage characters of a volume name. WTF? Every tried to delete a partition in FDISK with a f'ed up volume name like "Ìπ☻∩a╦φŽƒ╚|Ç" ???

So I did a low-level with the adapter BIOS and everything was fine from there on out.

[m4a2t0t]

ill try to low level format

[m4a2t0t]

when i try to low level format i get a error in the prog that says there was a failure,so now im trying zero drive fill

[shadrach]

It's starting to sound more and more like a hardware issue.

[m4a2t0t]

if this doesnt work im gonna swap mobos

[shadrach]

My #2 home box gave me a bitch of a time when I (attempted) built it last year.

I had the vendor ship me out a new KT7A and once that was installed, I had it up and running in about 15 minutes, LOL.

Bad hardware pisses me off... :rolleyes:

[m4a2t0t]

well i swapped mobos and installed and everything went fine after it finished setting up and rebooted the error came back