Citizen Bob <spam@uce.gov> wrote

> For those who have been following this tortured saga
> of the Corrupt NTFS Filesystem, I think I finally fixed it.

> I am running Win2K which was built from an InPlace Upgrade
> of a previous installation of Win2K in another computer, which
> was built from a previous installation of NT4 in yet another
> computer. The original NT4 was first installed in the first part
> of 1997, so this current version of Win2K traces back 10 years.

Urk.

> I know, I should reinstall Win2K from scratch. But I refuse to do
> it because 1) I have close to 100 installed applications, many of
> which I do not even recall the customizations. It would take months
> to reinstall all that software to the same configuration I now have;

Fine.

> 2) I refuse to cave in to the absurd demands of Windows having to be
> reinstalled every 6 months just because MS won't spend the money to fix it.

That isnt true of either 2K or XP.

> Maybe I will install Vista from scratch, but not XP or Win2K.

XP has a files and settings transfer wizard
which should bring the config stuff across fine.

> So I have no choice but to work around the many problems that
> a 10 year old installation of Win NT and its spawn have to offer.

That is just plain wrong, you do have a choice.

> This one, the corrupt NTFS filesystem problem,
> has been plaguing me for over a year.

And if you had done your backups properly, you could have
stepped back to the copy you had before the problem showed up.

> If I reboot Win2K and run it normally for over 1 day, when I reboot
> I find either CHKDSK wants to run or once in a while I get a BSOD.
> In every instance but one, I have been able to recover the corrupted
> disk by mounting it as D: and running CHKDSK D: /f on it. All sorts of
> crap fills the screen - stuff about broken files all over the place, mostly
> having to do with security descriptors and empty space in the MFT.

> So I think I may have fixed this fiasco - no more "corrupt NTFS
> filesystem". Do you really want to know how I did it?

> I converted to a FAT32 filesystem, and guess what
> - no more corrupt NTFS filesystem. Pretty cool, eh.

You'll likely find that if you convert it back to NTFS now it will be fine too.