NTOSKRNL.EXE error even with a new HD

I was receving the Windows could not start because the following file is missing or corrupt: <winnt root>\System32\ Ntoskrnl.exe.

error trying to boot into W2k and did some research and I found mostly it would be the boot sector. I went ahead and bought a new HD and reinstalled W2k and I still ge the same message. What could be the problem? Its a brand new HD on a IBM 600x Thinkpad.
mmbc_voltronAsked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
PAQ'd and 125 points refunded

modulo

Community Support Moderator
Experts Exchange
0
 
Arjun1Commented:
Hi,

I do not know how you are installing Win2k. I assume that you are installing it from Win2K CD-ROM.
Now your old HDD may have been bad. But at the same time it is also possible that your CD-ROM also has given up its ghost.
What I mean to say here is that maybe due to some reason(e.g scratches on the CD ROM) NTOSKERNEL.EXE is not being copied (to the HDD) properly.

You said that you bought a new HDD and I assume that you used the same CD-ROM to try and install Win2K. Is the HDD setup properly and does the computer recognise it ? If everything else is well and still the " NTOSKERNEL.EXE " is not being executed then I would think that maybe the CD - ROM is a goner.

Also remember that any software being  copied is being saved in the RAM before being finally copied to the HDD. May be your RAM is not too good or there isnt enough to execute 'NTOSKERNEL.EXE'  or maybe even slowly going bad.
I would check that also.

I think you can try to figure this put by replacing your RAM with some known good quality RAM and using the old HDD and trying to install Win2K. At least then you will be able to isolate the problem.

Here there are only two variables involved. One is the CD-ROM and the other is the RAM. I say this because you mentioned that you changed the HDd but still got the same problem as you did with the old HDD.

Remember WinK likes to have enough memory. Even 128 MB is a tad towards the lowest amount required. Increasing the memory to a good quantity(in case you have less memory) with known good quality memory should be another aspect that I think would solve your problem.

I hope this helps you.
0
 
Xavier_BERTHIERCommented:
Hello,

Please check the content of c:\boot.ini

You can have this message because of corrupted or misconfigured boot.ini file.

Regards,

Xavier BERTHIER
0
 
mmbc_voltronAuthor Commented:
Thanks arjun1 I will try the memory I did try a different cd and still the same so maybe we are leaning towards the mem.

Xavier I have had no luck getting to the boot.ini
0
 
mmbc_voltronAuthor Commented:
Thanks arjun1 I will try the memory I did try a different cd and still the same so maybe we are leaning towards the mem.

Xavier I have had no luck getting to the boot.ini
0
All Courses

From novice to tech pro — start learning today.