gcoen@emx.utexas.edu (Gary A. Coen) (05/21/91)
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
huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence) (05/22/91)
> 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'm doing this from memory, so if anybody can expand on this please do. My Norton book is at the office. What happened is the File Allocation Table (FAT) is shows that File A and File B are occupying the same cluster (n). It's like parking your car and your wife's in the same stall -- it's pretty difficult to extract them once done (Yugos excluded). When you attempt to use File A or File B, expect some corruption. Hopefully they're .bak or .tmp files -- if so delete them if you're done with 'em and be on your way I've seen this response most often when using Windows. Windows is disk intensive, and sometimes loses track of it's .tmp files. This causes chkdsk to report errors. One possible solution is putting the following in your config.sys: STACKS 0,0 And you might also try this close to the beginning of your autoexec.bat: SET TEMP=C:\WINDOWS\TEMP or the location of your TEMP directory for Windows. Good luck! Steve ----- Steve Huff, student, University of Kansas "Still love that KU basketball!" Microcomputer Consultant, Hill's Pet Products, Topeka, Kansas Internet: HUFF@kuhub.cc.ukans.edu Bitnet: HUFF@UKANVAX GEIS: HUFF@HILLCORP#