Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rutgers!deimos!phobos.cis.ksu.edu!bdn
From: bdn@phobos.cis.ksu.edu (Bryan D. Nehl)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Crosslinked files in MS-DOS
Keywords: crosslinked, FAT
Message-ID: <1990Jan6.204250.1399@deimos.cis.ksu.edu>
Date: 6 Jan 90 20:42:50 GMT
References: <1990Jan4.210414.4085@geac.com>
Sender: @deimos.cis.ksu.edu
Organization: Dept. of Computing and Information Sciences, Kansas State U.
Lines: 32

In article <1990Jan4.210414.4085@geac.com> wdawe@geac.com (Wayne Dawe) writes:

>I have been experiencing a problem with crosslinked files on a Samsung
>clone running MS-DOS. It has had a problem with crosslinked files.

>Wayne Dawe
>wdawe@geac.com
>{uunet!jtsv16,yunexus,utgpu}!geac!wdawe

I have run into a similar problem.  I added a second hard drive to
my DTK 10mhz xt system, WD rll 1002-27x? controller (3:1), with
seagate 238r and rodime 3.5".  I have the rodime set to drive C: and
the seagate set to drive d:.  I know I have everything set correctly
according to western digital.  I am using the hard drive cable with the
twist in the end.  I am using IBM PC dos 3.2.  The problem is that
when the rodime is seeking a certain sector it starts looking at the
seagate to try and find the info!  This has happened using VOPT, Speeddisk
and Spinrite.  Both Spinrite and VOPT marked these two spots bad after
seeking for quite a while.  However, both drive with the exception of
the two places I mentioned seem to check out okay under spinrites deepest
level of testing.  My question is: If I upgrade to ms-dos 4.01 will the
linking problem go away?  Also, is there anything I can do to 
possible rectify this problem?

Thanks for the help,

Bryan.
--
/* ================================================================+
[   Big Bad Bear Beasties Inc.    ][   Bryan Nehl                  ]
[   kodiak@ksuvm.ksu.edu          ][   bdn@phobos.cis.ksu.edu      ]
+___ ...!{rutgers|texbell}!ksuvax1!phobos.cis.ksu.edu!bdn   _____ */