Stacker 3.1 for Windows and DOS - Late Breaking News

This document contains information not included in the Stacker 3.1
Supplement or the Stacker for Windows & DOS User's Guide. If you're 
using any unique software with your system, such as Super PC-Kwik
Cache, see the Stacker Setup Help.

To get Stacker help from Windows:

1   Double-click the Stacker Setup icon.
2   Press F1.
3   Click Contents.
4   Click Software Considerations.

To get Stacker help from DOS:

1   Change to the Stacker directory and type SETUP.
2   Press F1.
3   Press ENTER to choose the Index.
4   Press TAB to select Software Considerations and press
      ENTER.

IMPORTANT:  IT IS A GOOD IDEA TO PRINT THIS README.TXT FILE SO YOU
CAN REFER TO IT EASILY.

                    TABLE OF CONTENTS

1.0     Stacker 3.1 and MS-DOS 6 Preloading

2.0     The STACKER.INI File

        2.1     STACKER.INI Structure
        2.2     General Syntax rules
        2.3     Switches
        2.4     Mounting Parameters
        2.5     Editing your STACKER.INI File
        2.6     Example for a Single Stacker Drive
        2.7     Example for Multiple Stacker Drives

3.0     Converting DoubleSpace Disks Outside of Setup

        3.1     DCONVERT Syntax
        3.2     Converting an Unmounted DoubleSpace Drive
                3.2.1  Mounting a Stacker Drive Temporarily
                3.2.2  Mounting a Stacker Drive Permanently
        3.3     Converting a Removable Disk Compressed with DoubleSpace
        3.4     Interrupted Conversion

4.0     File Duplication on Compressed and Uncompressed Drives
        
        4.1     Duplication Required by Stacker 3.1
        4.2     Duplication Not Required after Upgrading from
                Earlier Stacker

5.0     Doubling the Capacity of RAM Drives

6.0     Using Stacker for OS/2 & DOS with Stacker 3.1

7.0     MS-DOS Command Equivalents

8.0     Upgrading Stacker 3.1 on a Startup Disk That is Mounted
        Replaced

9.0     Compatibility Issues

        9.1     Using Anti-Virus Programs
        9.2     Using NetX with Stacker 3.1 (Novell Networks)
        9.3     Using the Adaptec Controller with Stacker 3.1 and DOS 6
        9.4     Using Norton Utilities version 7.00


STACKER 3.1 FOR WINDOWS & DOS  README.TXT

1.0     Stacker 3.1 and MS-DOS 6 Preloading

        Prior to DOS 6, changes to your system configuration were
        were specified in the CONFIG.SYS file. MS-DOS 6 loads
        DBLSPACE.BIN (a device driver) before it processes CONFIG.SYS.
        As supplied with MS-DOS 6, DBLSPACE.BIN configures DoubleSpace
        compression. Stacker 3.1 Setup modifies DBLSPACE.BIN to configure
        Stacker 3.1 compression and serve as a Stacker device driver 
        instead. Then it creates a hidden file named STACKER.INI to 
        provide Stacker configuration information to DBLSPACE.BIN.

        At start up, MS-DOS 6 preloads and processes DBLSPACE.BIN
        before it looks for any other file. DBLSPACE.BIN uses the
        information in the STACKER.INI file to configure your system
        and load the Stacker driver into memory. 

2.0     The STACKER.INI File

        The STACKER.INI file contains configuration information for the
        Stacker device driver. It replaces the Stacker device driver
        statements used in the CONFIG.SYS file in previous Stacker 
        versions. STACKER.INI is a hidden file in the root directory of
        your boot drive. 

        Setup creates STACKER.INI if it doesn't already exist and modifies
        its contents if you create a Stacker drive on any device except a
        floppy disk drive. Several Stacker commands update STACKER.INI
        whenever they change the configuration of your system.

        Here's a sample STACKER.INI file:

           /P=1
           /DIR=C:\STACKER\
           C:\STACVOL.DSK,SW

        The /P switch controls how fast Stacker compresses data
        when it puts it on the disk. The /DIR switch tells DOS where
        to find the Stacker files. The last line loads the Stacker
        drive and assigns a new drive letter. SW exchanges or swaps 
        the drive letters, so the data is still referenced by the 
        original drive letter.

        NOTE: Normally, you won't need to edit this file. Setup takes care
        of the initial configuration and other commands keep STACKER.INI
        up to date.

2.1     STACKER.INI Structure

        Each statement or switch in STACKER.INI appears on a separate
        line. Switches appear at the beginning of the file, while all 
        of the drive specifications appear at the end. The switches can 
        be listed in any order. The order of the drive specifications is
        the order in which drive letters are assigned.

        Section 2.5 explains how to edit your STACKER.INI file.

2.2     General Syntax Rules

        Each line can contain one switch or drive specification. A drive
        specification can be followed by a comma and a mounting parameter
        (RP,SW, or NS). Switches can include spaces and tabs before or 
        after "=", but not after "/". 

        You may want to modify the STACKER.INI file to change switches
        or to cause other effects. 

2.3     Switches

        The following switches may be found in the STACKER.INI file.

        *       Reserves a drive letter. If you convert DoubleSpace
                drives to Stacker drives or use Unstack to decompress
                data on a Stacker drive, Setup uses the * to
                maintain the previous drive letters. You can use *
                to force Stacker to assign specific drive letters
                CD-ROM drives or network drives, if necessary.
               
        /-AUTO  Turns off automounting for all removable
                drives. This saves about 2.7 KB in the driver.

        /BD=x   Specifies the base drive letter (x) from
                which to start Stacker drives. This appears if Stacker
                converted from DoubleSpace drives to maintain the
                DoubleSpace drive letter assignments. For example, if
                the first DoubleSpace drive was assigned to drive
                letter F, the switch /BD=F appears in STACKER.INI and 
                F is assigned to the first Stacker drive.

        /C or /C=n  Specifies the cluster size as the default (/C) or 
                4, 8, 16, or 32 KB. This value is established when the
                Stacker drive is created and must not be changed.
 
        /DIR=<stacker path>  Specifies the path where the
                Stacker software is located. This switch generally
                occurs at the top of the STACKER.INI file.

        /EMS    Indicates that Stacker's disk cache (up to 64 KB) should
                be stored in expanded memory, if any is available.

        /I-     Turns off Stacker's interceptor used with Novell
                networks.

        /LHF-   Turns off Stacker's normal clearing of the cache used
                by SmartDrive under MS-DOS 6 when any application ends.
  
        /M=n  Sets the cache memory size to n KB. Use any
                value between 1 and 64. The amount of driver
                memory required increases by whatever you specify
                up to a maximum of 64 KB for the cache (The /M
                switch has no effect if you use it with /EMS.)

        /P=n    Sets the compression tuning. Use any value between 0 and
                9. 0 turns compression tuning off decreasing memory 
                requirements by 4.4 KB. You'll have to restart your system
                to take advantage of any change in tuning if you change 
                between 0 and any other value. If no /P switch is included,
                Stacker uses /P=1.

                Values 0 and 1 are the fastest, with standard compression.
                9 gets the best compression but takes a bit longer. Setup
                uses level 9 to get the best possible compression while 
                creating the Stacker drive.

        /Q-     Turns off normal quiet startup. This switch causes your
                Stacker drives and their uncompressed drives to be listed
                at Startup, along with other program and copyright 
                information.

        /RP=n   Sets the number of replaceable drives to reserve, in 
                addition to any specific drive specifications. 

        /SW=swap-pairs   Sets up multiple swapping that takes place after
                individual drives are mounted and swapped. If necessary, 
                use /SW to specify swapping to occur after all Stacker
                drives are mounted.

                See the end of Section 2.4  Mounting Parameters for more
                details.
 
        /W-     Disables Windows permanent swap file pointer updating. By
                default, if Stacker detects a Windows permanent swap file
                on a disk that was swapped, Stacker searches through its 
                preset pattern for the Windows directory and places the
                full path of the Windows permanent swap file in SPART.PAR
                in the Windows directory. Once this is done (the first 
                time you restart your system after compressing the disks 
                that contain the permanent swap file), it really doesn't
                have to be done again unless you make drastic changes to
                your system. If you add this switch to the STACKER.INI 
                file, the search won't take place and you'll save a bit
                of time at startup.

                NOTE: Stacker checks for a Windows permanent swap file
                every time you restart your system. You can include the
                /W- switch to shorten startup time even if you don't 
                have Windows.

        /W=<directory>  Names the directory that contains your permanent 
                swap file pointer (SPART.PAR). Use this switch if your
                directory has an unusual name or isn't on the default
                path that Stacker searches. If Windows can't find its 
                permanent swap file after you compress a disk, add this
                switch and restart your system. This switch tells Stacker
                exactly where to find the SPART.PAR file, saving a bit
                of time on startup. Replace it with /W- after Windows 
                finds its swap file.

        /W+<directory>  Names the directory that contains your permanent
                swap file. Use it if your directory has an unusual name
                or isn't on the default path that Stacker searches. It
                causes Stacker to search its regular default path and
                find this one too, just in case you have multiple swap
                files. This switch actually lengthens the search, but 
                ensures that it finds all the files.

2.4     Mounting Parameters

        The following parameters appear after a STACVOL statement that 
        specifies a Stacker drive. These parameters specify the mounting
        method for the Stacker drive. A comma precedes each one.

        RP      Mount replaced. Useful for removable and RAM disks.

        NS      Mount without swapping, using the next available drive
                letter. Used for additional Stacker drives on the same
                original disk.

        SW      Mount swapped, using the next available drive letter.
                Used for the first Stacker drive on a fixed disk.

        To set up swapping to occur after all Stacker drives are mounted,
        use the /SW switch. To set up multiple swapping, use a line like
        this:

           /SW = jk mn xy

        After mounting all drives, Stacker will swap drives in pairs:
        J: with K:, M: with N:, X: with Y:, and so on, up to 26 swaps.
        Most users don't need multiple swapping, because the mounting 
        parameter "sw" on the STACVOL line handles swapping on an 
        individual drive basis. If you use the /SW = switch, put it at
        the TOP of the file along with the other switches. It will be
        processed after all the drives have been mounted.

       
2.5     Editing Your STACKER.INI File

        STACKER.INI is located in the root directory of your
        uncompressed boot drive. To edit it with your usual text editor,
        first change the hidden attribute. Alternatively, Stac provides
        the STACINI editor for you to use.

        1   At the DOS prompt, type STACKER and press ENTER.
        2   Note the drive letter of STACVOL.DSK listed for drive C.
        3   At the DOS prompt, type STACINI drive: where drive: is the 
              letter identified in step 2.
        4   When the lines of the file appear, edit as required (see
               the switches in the following section).
        5   Press Ctrl-Z to save the file.
        6   Restart your computer to put any changes into effect.

2.6     Example for a Single Stacker Drive

        The sample computer has a single hard drive and expanded memory.
        The STACKER.INI file created by Express Setup contains these lines:

         
          /DIR=C:\STACKER\     | Where Stacker files are stored
          /P=1                 | The default compression tuning (fastest
                               |   speed with standard compression)
          /EMS                 | Puts the Stacker cache in expanded memory
          C:\STACVOL.DSK,SW    | The location of the Stacker drive; SW 
                               |   swaps the drive letters

        After this file is processed, drive C holds the compressed data 
        and drive D holds uncompressed data and the STACVOL file.

2.7     Example for Multiple Stacker Drives

        Suppose a computer has two fixed disks. You create these Stacker 
        drives: 

           - One Stacker drive compresses all the data on drive C. 
           - One Stacker drive compresses data on drive D, leaving 
               about 40 MB free space. 
           - One Stacker drive uses the free space left on D.
           - One Stacker drive in floppy drive B
           - A Stacker RAM drive.

        You expect to use drive A with manually mounted Stacker drives.
        The STACKER.INI file might contain these lines:

           /DIR=C:\STACKER\   | Where Stacker files are stored
           /P=5               | Compression tuning (more compression
                              |   and a bit less speed)
           /EMS               | Puts the Stacker cache in expanded memory
           /RP=1              | One removable drive (for A)
           /BD=H              | Starts assigning new letters at H
                              |   (inserted by DoubleSpace conversion)
           B:\STACVOL.DSK,RP  | Specifies automount for drive B, replaced
           C:\STACVOL.DSK,SW  | Stacker drive on C, swapped 
           D:\STACVOL.DSK,SW  | Stacker drive on D, swapped
           D:\STACVOL.000,NS  | Second Stacker drive on D, not swapped
           E:\STACVOL.DSK,RP  | Stacker RAM drive, replaced

        After STACKER.INI is processed, these are the drive letter:

           C   Stacker drive
           D   Stacker drive created first on E (from existing data)
           E   Stacker RAM drive 
           F   DOES NOT EXIST
           G   DOES NOT EXIST
           H   Uncompressed drive containing the STACVOL file for 
                  Stacker drive C
           I   Uncompressed drive containing STACVOL files for Stacker 
                  drives D and E
           J   Stacker drive created second on E (from free space)
        
        Typing STACKER at the DOS prompt gets this result:

          Drive A: was Drive A: at boot time
          Drive B: was Drive B: at boot time [Auto-mounting Stacker drive]
          Drive C: was Drive C: at boot time [H:\STACVOL.DSK = size]
          Drive D: was Drive D: at boot time [I:\STACVOL.DSK = size]
          Drive E: was Drive E: at boot time [E:\STACVOL.DSK = size]
          Drive F: was Drive F: at boot time 
          Drive G: was Drive G: at boot time 
          Drive H: was Drive H: at boot time 
          Drive I: was Drive I: at boot time 
          Drive J: was Drive J: at boot time [I:\STACVOL.000 = size]
      
3.0	Converting DoubleSpace Disks Outside of Setup

	Stacker 3.1 Setup automatically converts any mounted DoubleSpace
	drives to Stacker drives. It does not convert any removable
	disks or any DoubleSpace drives on the fixed disk that are not 
	mounted.

	You can use the DCONVERT command outside of Setup to convert 
	DoubleSpace removable disks or unmounted DoubleSpace
	disks to Stacker drives. The process is the same for both.
        You must run DCONVERT under DOS, rather than under Windows.

        IMPORTANT: IF YOU USE DCONVERT, LET IT RUN TO COMPLETION. DO NOT
        INTERRUPT THE PROCESS.

3.1     DCONVERT Syntax

                DCONVERT /C dblspace-volume-name [/M]
            or
                DCONVERT /G dblspace-volume-name stacker-volume-name [/M]
	
        /C dblspace-volume-name 

                Converts the named DoubleSpace volume to a Stacker drive.
                If you don't include a drive letter in the path, a file of 
                that name on the current drive is converted.

        /G dblspace-volume-name stacker-volume-name

                Generates a new Stacker volume by copying the named 
                DoubleSpace volume to a new Stacker volume. It doesn't
                change the existing DoubleSpace volume. If you omit the 
                drive letter in either volume-name, the current disk is
                used. 

        /M      For use on a monochrome monitor.

        Use /C to convert a DoubleSpace volume into a Stacker volume.
        Run CHKDSK on the uncompressed drive before converting the
        DoubleSpace volume. 
        Use /G to copy a DoubleSpace volume, then convert the copy. 

        DCONVERT needs some working space on a disk to convert it, as much
        as 1 MB depending on the situation. If it runs out of space, you'll
        see a WRITE ERROR. There is no problem. Just use /G instead to make
        a converted copy of the DBLSPACE file on a different disk. Then use
        COPY to transfer the resulting STACVOL file if you want it on a 
        removable disk.

3.2     Converting an Unmounted DoubleSpace Drive

        Suppose DoubleSpace drive D was unmounted when you ran Stacker.
        Setup. Setup won't convert it automatically. Drive D contains the 
        hidden file DBLSPACE.000; use DIR drive: /AH to list hidden files
        on any drive. To convert the drive, type:

                DCONVERT /C D:\DBLSPACE.000

        The file is converted and renamed to STACVOL.DSK. DCONVERT does
        not mount the drive, however. 

3.2.1   Mounting a Stacker Drive Temporarily

        To mount a Stacker drive, type STACKER drive:, where drive is 
        the disk that contains the STACVOL file. When you restart your
        computer, this drive will be unmounted again.

3.2.2   Mounting a Stacker Drive Permanently

        DCONVERT does not modify the STACKER.INI file when it is run 
        outside of Setup. To cause a converted drive to be mounted when
        you restart your system, edit the STACKER.INI file as described
        in section 2.5 and add a drive specification line. For the example
        in 3.2, you would type on a new line:

                D:\STACVOL.DSK,SW 

        When you restart your computer, the drive is mounted along with
        any other drives specified in STACKER.INI.

3.3     Converting a Removable Disk Compressed with DoubleSpace

        Insert the disk into a drive and type DIR drive: /AH to identify 
        the name of the hidden DoubleSpace volume. Then type:

                DCONVERT /C drive:\dblspace-volume-name

        The volume is converted and renamed to STACVOL.xxx. 

3.3.1   Mounting Removable Drives

        The first time you use Stacker Setup to create a Stacker drive 
        in a removable drive, Setup specifies that drive in STACKER.INI
        so that Stacker drives in it are mounted automatically. 

        If you don't intend to create Stacker drives in a removable drive,
        you can use the techniques in 3.2.1 or 3.2.2 to mount your Stacker
        drives.

3.3.2   Allowing for More Removable Drives

        By default, Setup allows for one removable drive, which includes
        RAM drives. If you expect to use more, edit the STACKER.INI file
        (section 2.5) and add /RP=n, where n is the number of removable
        drives you want allowed. 

        If you include a drive specification (such as B:\STACVOL.DSK,RP)
        in the STACKER.INI file, /RP isn't needed for that drive.

3.4     Interrupted Conversion

        Once you start DCONVERT, let it continue until it is finished. 
        If the power is interrupted, here is how to recover your data.

        1.  Restart your computer and mount the disk if necessary.
        2.  Run CHKDSK.
            a.  If there is no problem, use DIR /AH to check the disk's 
                directory. If a STACVOL file exists and is smaller than
                the DBLSPACE file, delete the small STACVOL file and
                run DCONVERT again.
            b.  If there is a cross linkage, CHKDSK can't fix it. Run a 
                disk repair utility to clear it up, which unlinks the 
                STACVOL file. Then delete the STACVOL file and run
                DCONVERT again.
            c.  If there is size mismatch, let CHKDSK fix it. Then delete
                the smaller of STACVOL.DSK or DBLSPACE.DSK. 
                If you deleted STACVOL.DSK, run DCONVERT again. 
                If you deleted DBLSPACE.DSK, the volume was converted.

4.0     Files Duplicated on Both Compressed and Uncompressed Drives

        Stacker requires that certain files be stored in two places,
        for startup and recovery purposes. The requirements are different
        for Stacker 3.1 under MS-DOS 6 than for versions of Stacker that
        don't use preloading.

4.1     Duplication Required by Stacker 3.1
    
        The following files must be stored in the compressed startup drive
        and its uncompressed startup drive. If you remove any of them,
        your system may not be able to start or they won't be available
        if you need technical support.

            MS-DOS 6 Files              Stacker Files
            --------------              ---------------
              MSDOS.SYS  (hidden)         STACKER.COM
              IO.SYS  (hidden)            SYSINFO.EXE
              DBLSPACE.BIN  (hidden)      CONFIG.EXE
              COMMAND.COM                 CHECK.EXE
              ATTRIB.EXE
              CHKDSK.EXE   

4.2     Duplication Not Required After Upgrading From an Earlier Stacker

        Under Stacker 2.0 and Stacker 3.0 for Windows & DOS, all files
        referred to in the CONFIG.SYS and AUTOEXEC.BAT files were stored
        on both the compressed and uncompressed startup drives. Stacker
        kept the files synchronized to make sure they were the same in
        both locations. This ensured that DOS could find the files it 
        needed during startup. 

        Upgrading to Stacker 3.1 and MS-DOS 6 preloading means that any 
        drive letter switching is finished by the time DOS processes the
        CONFIG.SYS and AUTOEXEC.BAT files, so any files can be stored only
        on the compressed drive. If you wish to conserve space on your
        uncompressed startup drive, you can delete those files. Don't 
        remove them from the compressed startup drive (C).

5.0     Doubling the Capacity of RAM Drives

        RAM drives are created in the CONFIG.SYS file. To automatically
        double the capacity of a RAM drive, you can include an SCREATE.SYS
        device statement following the line that creates the RAM drive. 
        This example creates a 4 MB RAM drive and doubles its capacity:

            DEVICE=C:\DOS\RAMDRIVE.SYS 4086 /A
            DEVICE=C:\STACKER\SCREATE.SYS E:

        The SCREATE.SYS driver command must include the drive letter of
        the RAM drive. SCREATE doesn't remain in memory.

        You can mount the RAM drive in any of the usual ways. If your
        RAM drive is H: edit STACKER.INI and add E:\STACVOL.DSK,RP for
        automatic mounting. If you have enough removable drives allocated,
        you can include STACKER E: in the AUTOEXEC.BAT file or type
        STACKER E: at the DOS prompt. 

        NOTE: If the SCREATE line follows the line that loads STACHIGH,
        Stacker can't mount a RAM drive from STACKER.INI. You'll have
        to mount it manually with STACKER drive:. To let STACKER.INI
        mount the RAM drive, edit your CONFIG.SYS file and move the 
        lines that create and double the RAM drive to a position before
        the line that loads STACHIGH.

6.0     Using Stacker for OS/2 & DOS 6.0 and Stacker 3.1

        If you use these two versions of Stacker, you have to be careful
        to use Stacker commands from the appropriate version to 
        perform certain functions. Check the README file for Stacker for 
        OS/2 & DOS for all the details. 

7.0     MS-DOS Command Equivalents

        If you type a compression-related DOS command for a Stacker drive,
        Stacker's command is automatically run. You don't have to remember
        both the DOS and Stacker commands. The equivalent commands are
        listed below.

        DOS Command                     Stacker Equivalent
        -------------                   --------------------- 
        CHKDSK (and all parameters)     CHECK (and same parameters)

        DBLSPACE/CHK                    CHECK

        DBLSPACE/DEF                    SDEFRAG

        DBLSPACE/LIST                   STACKER

        DBLSPACE/MO drive:              STACKER drive:

        DBLSPACE/U drive:               STACKER -drive:

        DIR/C                           SDIR
        DIR/C/P                         SDIR/P
        DIR/C/H                         SDIR/H
        DIR/C/W                         SDIR/W

        DEFRAG                          SDEFRAG
        DEFRAG/F                        SDEFRAG
        DEFRAG/U                        SDEFRAG/Q
        DEFRAG/B                        SDEFRAG
        DEFRAG/SN                       SDEFRAG/SN
        DEFRAG/SE                       SDEFRAG/SE
        DEFRAG/SD                       SDEFRAG/SD
        DEFRAG/SS                       SDEFRAG/SS
        DEFRAG/LCD                      SDEFRAG/M
        DEFRAG/BW                       SDEFRAG/M
        DEFRAG/CO                       SDEFRAG
        DEFRAG/SKIPHIGH                 SDEFRAG

        FORMAT/S                        Copies the Stacker-modified
                                        DBLSPACE.BIN to the formatted disk.

        SYS                             Copies the Stacker-modified
                                        DBLSPACE.BIN to the formatted disk.

8.0     Upgrading Stacker 3.1 on a Startup Disk That is Mounted Replaced
        
        Your startup disk must not be mounted replaced; that is, it
        must have an uncompressed drive that uses a different drive
        letter. The Stacker files cannot be stored on a disk that is
        mounted replaced. If the files are stored on a Stacker drive,
        Stacker Setup assumes that it is not mounted replaced.

        If you try to upgrade Stacker on a startup disk, that is
        mounted replaced, a message lets you know about the problem.
        Press F1 at that point to get full details on correcting the
        problem. 

9.0     Compatibility Issues

        A few hardware and software setups interfere with MS-DOS 6 and
        Stacker functioning.

9.1     Using Anti-Virus Programs

        DURING SETUP

        Many anti-virus programs interfere with Stacker Setup. Before
        you run Stacker Setup, disable or unload any anti-virus programs.
        If you let Setup restart your computer, it disables all TSRs and
        restores them at the end of Setup.

        DURING UNSTACK AND RECOMPRESSING

        You'll also have to disable the anti-virus programs if you
        use UNSTACK or if you use SDEFRAG to recompress all the data
        on a disk. 

        FAILURE TO LOAD
        
        Norton AntiVirus from Norton Desktop for Windows 2.2 fails 
        to load if all the following conditions occur together:
         - 386-MAX version 6.02 is in use (but not 6.01 or 6.03)
         - STACHIGH.SYS is loaded high using 386MAX's 386LOAD.SYS
             program (not using DOS's DEVICEHIGH)
         - NAV&.SYS is loaded after STACHIGH.SYS

        The easiest way to make NAV&.SYS load is to use DEVICEHIGH instead
        of 386LOAD.SYS.    

9.2     Using NetX with Stacker 3.1 (Novell Networks)
        
        As installed, Stacker's redirection of DOS compression
        related commands to their Stacker equivalents is not effective
        when NetX is running. To make it effective, turn off the inter
        ceptor by adding /I- to your STACKER.INI file. Then add Stacker's 
        REDIRECT command (it has no options) to the end of your 
        AUTOEXEC.BAT file. 

        If you prefer not to run REDIRECT, use the Stacker commands
        when needed. For example, use SDEFRAG rather than DEFRAG to 
        optimize a Stacker drive.

9.3     Using the Adaptec SCSI Disk Controller with Stacker 3.1 and DOS 6

        If you are using an Adaptec 154x bus-mastering SCSI disk controller, 
        be sure that Adaptec's ASPI (Advanced SCSI Programming Interface) 
        manager is properly installed on your system.  Install the ASPI
        DOS managers as well to help DOS communicate with the SCSI host
        adapter more effectively and allow additional SCSI devices. You'll
        need the ASPI DOS managers also:

        - To support programs that use virtual memory (such as Microsoft 
            Windows 3.0 and 3.1, QEMM 386 and Qualitas 386MAX)

        - To support programs that write large amounts of data directly to
             video memory (AHA-1540, 1542, and 1640 host adapters only)

        - When more than two hard disk drives are already installed 

        - To install a SCSI drive that is configured at a SCSI ID other
            than 0 or 1

        - To install removable media such as a CD-ROM or tape backup drive

        For example, If you are using a AHA 1542/B, or 1542/C controller, 
        the following lines should be included in your CONFIG.SYS file:

          FILES=40
          BUFFERS=20
          DEVICE=C:\DOS\HIMEM.SYS
          DOS=HIGH,UMB
          DEVICE=C:\DOS\EMM386.EXE NOEMS
          DEVICE=C:\ADAPTEC\ASPI4DOS.SYS

        NOTE: Adaptec does not recommend loading the ASPI4DOS manager high
        with the 154x/B card, but that is possible with the 1542/C model. 
        See your Adaptec Software manual for further details regarding 
        proper installation this and other ASPI  DOS manager software.

        Under certain conditions, use of an Adaptec controller with a
        Stacker drive can make it appear as though your disk contains
        no data even though the root directory is preserved. Your data
        is intact.

        Stacker can work with the Adaptec controller if one of the
        following is true:
          - The /EMS switch is not used in STACKER.INI
          - Double buffering is used
          - ASPI4 DOS 6 is installed

9.4     Using Norton Utilities version 7.00

        In most cases, Stacker drives work well with the Norton
        Utilities. This section details the exceptions.

        To make a startup disk as suggested on page 4 of the
        User's Guide Supplement, start with a Norton Rescue
        disk rather than an MS-DOS 6 startup disk. Follow
        these steps:
        1.  Set up Stacker 3.1.
        2.  Insert your Norton Rescue disk into drive A.
        3.  At the DOS prompt, type SYS A: and press ENTER to
            make the disk Stacker-aware.
        4.  Relabel the disk "Stacker Startup Disk - Norton
            Rescue" and put it away.

        Norton Disk Doctor is compatible with disks compressed
        by Stacker. However, if you have converted a DoubleSpace
        drive and not yet used SDEFRAG to recompress the data,
        using Norton Disk Doctor may result in data loss. It's
        a good idea to recompress your converted drives right 
        away for better compression and to avoid this problem.

        Norton Safe Format, when used from a Stacker boot drive,
        does not create a correct boot sector on the floppy disk
        being formatted, so the disk can't be used for booting.
        If you want to create bootable floppy disk, use the DOS 
        FORMAT command instead.

        Make Disk Bootable utility does not copy DBLSPACE.BIN to the
        floppy disk. If you want to create a bootable floppy disk,
        use the DOS FORMAT or SYS command.

        



