Jump to content

Recommended Posts

Posted

I recently installed a sound card on my Windows 2000 box, but something went wrong and I have the above message.

I've checked this file from Windows 200 server (D:) and it's ok, but nevertheless I copied on it another from my iso backup.

Also, I checked boot.ini which is ok, too.

Is there a chance to have drive letters wrong after installation?

My disk installation is C: (old NT partition), G: (This W2k), D: (Windows 2000 server)

I haven't got any rescue diskettes, but I have a system state backup just before the installation.

Can I recover it?

thanks.


Posted

You usually get this message, not because the ntoskrnl.exe is missing but likely one of its dependencies got removed, moved, corrupted or was updated by a third party. In other words, ntoskrnl needs other files to load, but if they are missing or aren't correct, it can't. Then when the next step in Windows load process looks for ntoskrnl and it isn't running, it says that it is missing.

If you are lucky, yes you can replace the ntoskrnl using the one on the Windows CD. You may have to make use of the EXPAND program, and either use NTFSDOS or the Recovery Console. Also, if you happen to be on a network, you may be able to replace the file that way, but only until you change its attributes. I believe those would be -R +A -S -H. But you would have to reverse that after replacing the file, so +R -A +S +H.

Posted
"I recently installed a sound card on my Windows 2000 box"

Have you tried removing the sound card and rebooting?

The error he is getting is software related. Removing the soundcard wouldn't likely fix the issue. If anything, removing the soundcard software or driver package would be more helpful. I don't have the operational experience with Windows 2000 to tell you how to even attempt that, however.

Posted (edited)
"I recently installed a sound card on my Windows 2000 box"

Have you tried removing the sound card and rebooting?

The error he is getting is software related. Removing the soundcard wouldn't likely fix the issue. If anything, removing the soundcard software or driver package would be more helpful. I don't have the operational experience with Windows 2000 to tell you how to even attempt that, however.

Well, my understanding is that if the hardware is removed then NTDETECT.COM will not detect it during the boot sequence therefore the software/driver would not be loaded and, perhaps, the software conflict would not arise. However, I have been wrong before now and I hope to live long enough to be wrong again. :whistle:

Edit: Already proved myself to be wrong, the device should be uninstalled in Device Manager before being removed. This article http://www.windowsnetworking.com/kbase/Win...andDevices.html explains it.

Apologies for jumping in at the deep end...

Edited by Hedonist

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...