Hang or "Read Fault" Accessing Bad Cluster on Compressed DriveLast reviewed: January 26, 1996Article ID: Q128354 |
The information in this article applies to:
SYMPTOMSWhen you are using a real-mode driver (DRVSPACE.BIN or DBLSPACE.BIN) and you try to access a file on a DriveSpace or DoubleSpace compressed drive, the computer stops responding (hangs). If you are using a protected-mode driver (DRVSPACX.VXD), you receive the error message "Read Fault." To determine whether you are using a real-mode or protected-mode driver, run DRVSPACE.EXE and click About DriveSpace on the Help menu.
CAUSEThe file that you are trying to access is stored in one or more bad clusters. A bad cluster on a compressed drive is a cluster that cannot be read successfully. Note that an unreadable cluster on a compressed drive does not always indicate a media defect on the physical surface of the disk.
RESOLUTIONWith the protected-mode DriveSpace driver loaded, run ScanDisk for Windows and click the Thorough option button in the Type Of Test box. Test both the system and data areas on the compressed drive, as well as on the host drive. To run ScanDisk and perform a thorough test, follow these steps:
MORE INFORMATIONBad cluster markings due to physical media defects should appear only on uncompressed drives. If ScanDisk is unable to read a cluster on a DriveSpace compressed drive, ScanDisk erases the Microsoft DriveSpace FAT (MDFAT) entry for that cluster and changes the portion of the file that was using the cluster to 0 bytes in length. The physical sectors previously used by the unreadable cluster are marked as free and can be used again.
|
KBCategory: kbtool kberrmsg
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |