CS> Don't believe everything you hear or read about NTFS - especially when 
CS> it's from Microsoft. 
CS> You need to read the Microsoft Newsgroups regarding NT.  It's not as 
CS> "self repairing" as MS says it is, however, I don't want to get into a 
CS> which is better "NTFS or FAT" so it's best to drop this.
And we don't have to get into which is a better file system debate. There is 
no question which file system is better. 
Take for example a bad experience I had a few months back when I upgraded my 
motherboard. I had two processors, a 100MHZ and a 133MHZ. I mistakenly put 
the 100MHZ processor in and set the machine up for 133MHZ. Thus I had an over 
clocked CPU. My system would randomly crash. For 2-3 days the system would 
crash almost hourly. I run Microsoft Exchange Server 5.5, IIS (FTP and WEB 
server), WINS, DHCP Server, Time Server, Remote Access Server and the various 
BBS and normal applications all running. 
I mention the Servers because several of them have open databases. Exchange 
Server in particular has a lot of open files. The system crashes would be 
everything from a Blue Screen to a reboot of the machine. I did not loose one 
single piece of data. And in fact most times chkdisk was not required. When 
it was required, Windows NT would run it on start up.
Try that on a FAT system.
Dale
--- Msged/NT 4.20 beta 3
---------------