      -----------------------------------------------------------------
      STACKER NOTE                                         STACKER NOTE
                       WRITE-PROTECTED STACKER DRIVES
                      (Applies to Stacker Versions 2.x, 3.x, 4.0)
      STAC FAX  4708 (05-10-1994)
      -----------------------------------------------------------------
                                      
      BACKGROUND
      
      Problems with compressed data can result from errors in the DOS
      file system or defects in the hard disk media itself.  Stacker
      pauses the normal startup of your computer when it detects a
      problem that warrants your immediate attention:
      
           D: = C:STACVOL.DSK UPDATING STACKER ALLOCATION MAP...error
           (run   CHECK /F)  (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
      
         - Observe the write-protect error at start up
         - Run CHECK /F
         - Dealing with damaged files
           
      OBSERVE THE WRITE-PROTECT ERROR AT START UP
      
      If Stacker tells you to run CHECK /F, then skip to the next
      section for details.  Otherwise, check the table below for other
      types of write-protect situations.
      
       WRITE-PROTECT MESSAGE 			   SOLUTION
       Size mismatch - Write protected
       (existing installation)          	StacFax  # 4702 
       Reboot during SDEFRAG detected
       - write protected                 	StacFax  # 4704 
      
      RUN CHECK /F
      
       1.  Press any key to clear the write-protect message and to
           continue booting.  CHECK should start up automatically from
           the AUTOEXEC.BAT file.
       2.  If CHECK does not start automatically, then exit any
           programs that do start automatically such as Windows or a
           menu program.  Then, to fix Stacker drive C for example,
           from a DOS prompt, type:
              CHECK C: /F  <Enter>
       3.  When CHECK prompts you to repair the drive, type yes and
           press <Enter>.
           NOTE:  If CHECK reports IOCTL ACCESS DENIED ERROR #27, see
           StacFax #4706.

           
      DEALING WITH DAMAGED FILES
      
      If CHECK reports damaged files, it will prompt you to "delete the
      damaged files listed above so that all the errors may be
      corrected?"  Read through both options before you decide whether
      to respond yes or no.
      
      "YES" -- ALLOWING CHECK TO DELETE DAMAGED FILES
      If you already have a backup of the damaged files, or if the
      damaged files are unimportant, type yes and press <Enter>.  CHECK
      will then delete the damaged files and remove the write
      protection.
      
      If CHECK reports errors "which should be repaired with CHKDSK or
      a disk repair utility," then run a multipurpose disk repair
      utility such as Norton Disk Doctor or PC Tools DiskFix on the
      Stacker drive.  If you have no disk repair utility, run CHKDSK
      instead.  After cleaning up the errors, you can restore backup
      copies of the damaged files if necessary.
      
      "NO" -- RECOVERING DAMAGED FILES MANUALLY
      Depending on the type and extent of the corruption, some damaged
      files can be partially or completely recovered manually.  To
      attempt manual recovery, type no and press <Enter>.  CHECK will
      correct other errors while leaving the damaged files intact.  It
      will then remove the write protection and tell you to copy the
      files with errors to another disk.
      
      Copy the damaged files to a different drive.  If a file is
      damaged beyond repair, you will get the error:  "Read fault error
      reading drive; Abort, Retry, Ignore, Fail?"  Abort out of any
      read faults - you will have to recreate such files or restore
      backup copies.
      
      If you get the message "1 file(s) copied," it indicates that DOS
      was able to copy something of the original file.  After
      attempting to recover the files you need, repeat the instructions
      for running CHECK /F and allow it to delete the damaged files.
           
      -----------------------------------------------------------------
      Copyright 1994 Stac Electronics
