🚀 go-pugleaf

In article <49299@ut-emx.uucp>, gcoen@emx.utexas.edu (Gary A. Coen) writes:
|> Running Windows 3.0 on an IBM PS2 Model 80 (6Mb RAM, 44.5Mb FD, PCDOS 3.3),
|> when invoking the CHKDSK function with the /F parameter set, I get the fol-
|> lowing behavior:
|> 
|> 	CHKDSK /F
|> 
|> 	Volume is ...
|> 	File A is cross linked on cluster n.
|> 	File B is cross linked on cluster n.
|> 
|> I have not been able to find documentation of this in my DOS manual.  Is it
|> bad?  Does anyone *know* what it means?  Does anyone *know* why it is happen-
|> ing?
|> 
|> --Gary Coen

What it means is that somewhere along the way the file system got
confused and it thinks that a cluster belongs to two different
files. I do remember reading that running chkdsk with the /f
option from within Windows is a distinct no-no. You should
exit Windows and run it again to make sure. Unfortunetly one of
the files thats involved in the cross link is toasted. The solution
is to copy both files involved in the cross link to new files, then
go back and kill the original. But you will always lose some data
when this happens, hopefuilly it was something you have backed up
elsewhere.
--
-----------------------------------------------------------------------
- Scott Berger                               sberger@cpocd3.intel.com -
- Intel Corporation, Chandler, AZ            sberger@ch3.intel.com    -
-----------------------------------------------------------------------