Here's what happened to me and what I did to fix it. Windows 2000. Dell Optiplex GX-280. SATA HD.
First, Why did I get this problem. I moved to a new pod at work and ignored the little voice in my head that said to make an image of the machine's hard drive before moving

. I set up in the new pod and plugged my computer in and halfway through the boot process the power (on the surge protected) outlet went out. So power interruption was my culprit. I got the dreaded ntoskrnl.exe is missing or corrupt (boy was it ever) error.
I tried the recovery console and ran CHKDSK /P /R. A few interesting things happened. (1) I was not prompted for which installation I wanted to log on to, (2) not prompted for an admin password. The reason being (looking back now) was that my WINNT folder was toast, along with the system32 folder and everything in it.
When the CHKDSK finished (I have had good luck with this tool before) it said that it had found and fixed several problems. Good I thought, I am back to normal, I rebooted and Whamo! same error. I tried every post on this discussion (well at least up until page 9!) and none of them worked except for one. I will now make this long story short

!
When CHKDSK found and repaired the directories it did NOT rename them the same thing. My WINNT directory was named "Found.001". There were four subdirectories within the "Found.001" folder including the "System32, i386 and two others" labeled something like "Found.001,.002,.003,etc.).
I was lucky enough to have another machine that I could stick my hard drive in and compare files to determine which folder was which. After renaming them and copying them back to the root of C: I was able to successfully start my computer. WooHoo! I still had some errors so I ran system file checker (Goto Run, type "CMD" to open a DOS window, then type "sfc /scannow, and follow the windows prompts). With time and patience I have fixed them. I had to find out what each "Found" folder was named originally and rename it and put it back in it's right place. So if you run the Recovery Console and it finds and fixes the errors and you still have this problem, run Recovery Console again and run the DIR command and look for Directories named "Found.XX". This may help you find what's missing and what has to be renamed. Also I am going to follow my advice and make an image (Ghost) of my machine's hard drive.
Thanks to whoever put that post about CHKDSK renaming folders "Found.xx". That has fixed my problem, a problem that I had previously been unable to solve on other computers. This was not the first time I have battled the "ntoskrnl.ex" error. But this is the first time I have beaten it.
Moderator, could you put a post near the first few pages encouraging people to keep reading all the posts on this topic because there are solutions for some people. Thanks.