Again, I'll recap what happened to mine, because it may help you recover your data, at the very least.
My original OS that came with the computer was XP Pro. I had no problems with it and quite honestly liked it to an extent, but it had too many quirky conflicts with my Novell network at work so I chose to install 2000 Pro overtop of it. No problems there. Win2K pro installed just fine and I showed up as D Drive and my original XP showed up as C Drive (That was a little odd, but I sorta did that on purpose.
Anyway, I wanted to reinstall the XP Pro as a dual boot and installed System Commander (A multi-boot proggie, to do this). The XP install went off without a hitch, but like everyone else in this thread, when I went to boot Win2K Pro I had this dreaded ntoskrnl file problem just like everyone else. I think as noted earlier, at least my theory is, that the 2000 and XP NTFS are different versions. When XP is installed it looks for other NTFS partitions and attempts to rewrite them to it's own version. The workaround is to "hide" all other NTFS partitions. This way they don't get "rewritten". By default, SYstem Commander hides the NTFS partitions when using the OS wizard, but when I rebooted to start the install, I think I screwed up and as a result the 200 partition became "unhidden". Hence the "corruption".
After careful study of the solutions offered and the same attempts many have made to solve it, I tried a different approach. I created a fourth partition and did a clean install of Win2K being especially careful this time to "hide" the other NTFS partitions.
In theory this worked. It's a bit of a pain, but the end result is I can boot to both of the latter versions of Win2K and XP partitions. When I boot to Win2K (the new version) it is my C Drive and my old "corrupted" Win2K partition became my D Drive. Hence I was able to access all the files from there, but I could not see either XP partition.
However, when I boot to the new version of XP, My new XP partition is my C Drive and the old XP partition is my D Drive.
Bottom line is I was able to recover all files on the computer and not have to format it and start from scratch.
I'm not sure that's within the range of what most are willing to do, but I am living proof that it can be done. If you'd like to take a look at System Commander here's the link:
http://www.v-com.com/
It's not free (but not expensive either), but I like it even better than Partition Magic.
Hope that helps the many who have been having this problem.
"There's no place like 127.0.0.1 except for ::1."
Alexandria Networks. Leader in IT consulting for associations/non-profits, and small to medium sized businesses around the northern Virginia and Washington D.C. metro area.