How to Fix Cross-linked Files

Article translations Article translations
Article ID: 83140 - View products that this article applies to.
This article was previously published under Q83140
Expand all | Collapse all

On This Page

SUMMARY

When two (or more) files are cross-linked on the same cluster, do the following:

NOTE: If you are running MS-DOS 6.2 or later, run ScanDisk, instead of using the following procedure.

  1. Verify the error is accurate.

    Not all versions and dialects of MS-DOS access disks in the same manner. If you booted from a floppy, the problem may be that the MS-DOS on the floppy isn't understanding the disk layout properly.

    If Windows and another multitasker is active, all disk updates may not be complete. Exit from all other programs and from Windows before running CHKDSK.
  2. Make copies of the cross-linked files on another drive or subdirectory.
  3. Delete all crosslinked files. This is what actually fixes the File Allocation Table (FAT).

    NOTE: If you are using Undelete and the Delete Sentry method of protection, remove the memory-resident portion of Undelete by typing UNDELETE /UNLOAD at any MS-DOS command prompt before you delete any cross-linked files.
  4. Run CHKDSK to verify all is now well.
  5. Manage the copies of the cross-linked files. If two files are cross-linked on the same cluster, one of them is good and the other is damaged. This can usually be determined in some way.

    -or-

    Reinstall or restore backups of the files that were cross-linked.

MORE INFORMATION

What Are Cross-linked Files?

MS-DOS organizes the disk's data area into sections called clusters or allocation units. Each file has its own directory entry, which includes the file name, size, attribute information, date, time, and the cluster where the start of the file is stored.

The file allocation table (FAT) includes an entry for each cluster. Each cluster's entry includes either a code specifying that it is the last cluster in the file, or the number of the next cluster used by the file. Clusters can also be marked unusable, which CHKDSK reports as bad sectors.

Cross-linked files occur when two or more files are both marked as "owning" the same cluster. Usually, the last file updated is correct; the other is correct except for the cluster's worth that is part of the other file.

For example, suppose you have two files, each 512 bytes in size. Each file requires one cluster. If both files are marked as being located in cluster 5, then cluster 5 probably contains the file with the later date. You can confirm this by looking at it (if it's a data file) or running it (if it's a program).

How Are Cross-linked Files Fixed?

The only way to fix the FAT in this case is to delete BOTH files. When you delete the file, each cluster assigned to that file is marked "free to be used." If only one file is deleted, the cluster on which the cross-link occurred is marked unused, but the file system still shows that cluster as belonging to the "good" file. This causes another error (for example, CHKDSK may report a file allocation error, size adjusted or file allocation error, or file truncated). You also lose access to the file from the part that was stored in the beginning of the cross-linked cluster to the end of the file.

MS-DOS should be able to make a copy of both files (although one will probably be corrupt). If you don't want to delete both files, copy them to a floppy disk or another subdirectory before deleting them.

Properties

Article ID: 83140 - Last Review: May 10, 2003 - Revision: 2.0
APPLIES TO
  • Microsoft MS-DOS 3.1
  • Microsoft MS-DOS 3.2 Standard Edition
  • Microsoft MS-DOS 3.21 Standard Edition
  • Microsoft MS-DOS 3.3 Standard Edition
  • Microsoft MS-DOS 3.3a
  • Microsoft MS-DOS 4.0 Standard Edition
  • Microsoft MS-DOS 4.01 Standard Edition
  • Microsoft MS-DOS 5.0 Standard Edition
  • Microsoft MS-DOS 5.0a
  • Microsoft MS-DOS 6.0 Standard Edition
  • Microsoft MS-DOS 6.2 Standard Edition
  • Microsoft MS-DOS 6.21 Standard Edition
  • Microsoft MS-DOS 6.22 Standard Edition
Keywords: 
KB83140
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com