----------------------------------------------------------------- STACKER NOTE STACKER NOTE REBOOT DURING SDEFRAG, WRITE PROTECTED (Applies to all versions of Stacker) STAC FAX 31707 (12-07-1993) ----------------------------------------------------------------- BACKGROUND When Stacker mounts a Stacker drive it verifies the STACVOL file containing the compressed data. If the Stacker Optimizer (SDEFRAG) was interrupted during the "Optimizing files..." stage of optimization, Stacker pauses the normal startup of your computer with this message until the problem is corrected: E: = C:STACVOL.DSK Reboot during SDEFRAG detected (Write protected) Press any key to continue... NOTE: The Stacker utility CHECK is referenced throughout this document. If you use a version of Stacker prior to 3.0, use SCHECK instead of CHECK. SOLUTION 1. Type SDEFRAG drive: where drive is the Stacker drive. SDEFRAG repairs the drive and restarts your computer. 2. Run CHECK /F on the Stacker drive before running the Stacker Optimizer again. UNABLE TO REPAIR FATS, #139 / UNABLE TO REPAIR FATS, #86 If SDEFRAG is not able to repair the Stacker drive, you'll get one of these messages. It means that both copies of the File Allocation Table (FAT) have been corrupted. Some data is already lost, but this procedure will save the remaining data on your disk. 1. Switch to the Stacker drive and type CHECK /=A /F and press . 2. When CHECK offers to repair the drive, let it. 3. When CHECK offers to delete files, respond no. 4. Restart you computer and run CHECK /F again. Let it delete any files still reported as damaged. Then use your most recent backup to restore missing files. ----------------------------------------------------------------- Copyright 1993 Stac Electronics