      -----------------------------------------------------------------
      STACKER NOTE                                         STACKER NOTE
                        CANNOT CREATE DOS ENVIRONMENT
                  (Applies to Stacker for OS/2 & DOS ver 4)
      STAC FAX  64207 (1/95)
      -----------------------------------------------------------------
                                      
      BACKGROUND
      
      The error message "Cannot Create DOS Environment" during startup
      is normally followed by other errors, until the message "SYS1200,
      the system is stopped" is received. These errors mean that there
      is either Extended Attribute (EA) corruption on the drive, or the
      Stacker lines are missing from the CONFIG.SYS of the uncompressed
      OS/2 boot drive. You must either restore the Stacker lines, or
      repair the EA corruption. If the problem is corrupt EA's, and
      repairing them does not restore your system, you must reinstall
      OS/2.
      
      SOLUTION
      
         - Restore the Stacker lines to the CONFIG.SYS if necessary.
         - Run CHKDSK /F to repair EA's.
         - Reinstall OS/2 if necessary.
           
      Restore the Stacker lines to the CONFIG.SYS if necessary
      
      If you see the error message "Cannot create DOS environment"
      without seeing any Stacker messages during startup, the problem
      is probably missing Stacker lines in the CONFIG.SYS of the
      uncompressed boot drive.
      
       1.  Restart your system with Stacker Disk # 1.
       2.  Type: SWAPMAP <enter> to see the Stacker drive map. Note
           which drive swaps with your OS/2 drive. This is your OS/2
           boot drive. If your Stacker drives are not mounted you will
           receive a message that Stacker is not installed. In this
           case the OS/2 boot drive is the drive letter where you
           originally installed OS/2.
       3.  Type: ED d:\CONFIG.SYS <enter> where d: is your OS/2 boot
           drive.
       4.  Note the beginning of the file. It should have four or more
           Stacker lines. (You will find a detailed discussion of the
           Stacker lines in your Stacker for OS/2 & DOS User's Guide.)
           If the lines are present, then missing Stacker lines is
           not the problem. Proceed to the next section concerning
           CHKDSK.
       5.  Press CTRL-Z to exit the file. Type: CONFIG d: <enter> where
           d: is the OS/2 boot drive. Answer (Y)es to accept changes to
           the files.
       6.  Restart your system. If this procedure does not correct the
           problem, go on to the next section.
      
      Run CHKDSK /F to repair EA's
      
      In order to run CHKDSK /F against your Stacker drive, you must
      start your system with the Stacker-aware boot disks you made when
      you installed Stacker. Then run CHKDSK /F against the Stacker
      drive and the uncompressed boot drive. There may be errors on
      both drives. For details on making Stacker-aware boot disks and
      running CHKDSK, see document # 64005.
      
      After making all possible repairs to the compressed and the
      uncompressed drive, restart your system from the hard drive. If
      the same error message occurs, proceed to the section below.
      
      Reinstall OS/2 if necessary
      
      See the Stacker for OS/2 & DOS User's Guide, Appendix C, for
      instructions on reinstalling OS/2 on a Stacker drive.
      -----------------------------------------------------------------
      Copyright 1995 Stac Electronics
