Path: utzoo!attcan!uunet!van-bc!ubc-cs!alberta!dvinci!reeves
From: reeves@dvinci.usask.ca (Malcolm Reeves)
Newsgroups: comp.sys.ibm.pc
Subject: Re: cross linked file problems... HELP!
Message-ID: <1990Jun2.013644.21277@dvinci.usask.ca>
Date: 2 Jun 90 01:36:44 GMT
References: <1990Jun1.160056.11952@watdragon.waterloo.edu>
Distribution: na
Organization: University of Saskatchewan
Lines: 33

From article <1990Jun1.160056.11952@watdragon.waterloo.edu>, by sekoppenhoef@rose.uwaterloo.ca (Shawn E. Koppenhoefer):
> When I run CHKDSK /F I get the following report:
> 
> C:\WORDPROC\TEX\PK\432\CMB10.GF
>     Is cross linked on cluster 216
> C:\SHAWN
>     Is cross linked on cluster 216
> C:\WORDPROC\TEX\INPUTS\NULL.TEX
>     Is cross linked on cluster 216
> 
> and then the normal info about disk space, hidden files, directies etc.
> 
> QUESTION: *how do i get rid of these cross links?! I thought /F was supposed
>            to fix the problem?! Anyone I've asked has said they have no idea.
>            No-one seems to know what the trouble is or how to fix it! :-(
> 
> 
>
The problem is that the file allocation table (FAT) for both files contains
an entry for cluster 216 (for reasons too numerous to mention). The fix is
to use a hex editor of a utility like Norton Utilities to patch the two FAT's.
The problem is that one or both files will probably be damaged. For ASCII text
the clean up may be minor - for binary files you should refer to your most
recent backup :-)  If you have a nice fresh clean disk the FAT's may show some
signs of pattern, for an old well-used, fragmented disk you have a problem. 
Good luck.
A
 
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|       _ _       KLEIN BOTTLE for sale...
>         Shawn E. Koppenhoefer |        |        enquire within.
>  ...watmath!rose!sekoppenhoef |	       -		 
> ~~~~~~~~~~~~~~~~~sekoppenhoef@rose.uwaterloo.ca sekoppenhoef@rose.uwaterloo.edu