I have been trying since Jan 13/06 to get a straight forward answere to this problem of corrupted files. How can any respectful softwarevendor continue to sell this stuff whith verfication problems that go back through 3 to 4 versions. ~Snipped~ off topic comment Please refrain from such comments -Ron This is what TI9 did to my system: SYMPTOMS When you try to delete a file on an NTFS volume, you may receive the following error message: Cannot delete file name: The file or directory is corrupt and unreadable. The System event log in Windows NT 4.0 contains the following message: Event ID: 41 Source: Diskperf Description: The file system structure on disk is corrupt and unreadable. Please run the chkdsk utility on the device with label "Volume_name" The System event log in Windows 2000 contains the following message: Event ID: 55 Source: NTFS Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:" If you run Chkdsk against the volume, Chkdsk may or may not make repairs, but afterwards you still cannot delete the corrupted file. CAUSE This behavior can occur if the NTFS volumes' Master File Table (MFT) is corrupted. The short and long file name pairs that are stored in the directory index record and the file names that are stored in the associated File Record Segment (FRS) contain case-sensitive characters that do not match. NTFS supports case-sensitive (POSIX) file names, but Chkdsk does not check file names in case-sensitive mode. For example, assume that the directory index record has a BADFILe.TXT entry but the FRS has a BADFILE.TXT entry for the file name. NTFS views this as being invalid or corrupted, but Chkdsk compares only the names and ignores the case. It does not make repairs. RESOLUTION To resolve this issue, back up the volume that contains the corrupted file(s) and exclude the corrupted file(s) from the backup job. Reformat the volume, and then restore from the backup.