                      Stacker(R) 4.0 for Windows & DOS
                           Late-Breaking News

NOTE: It is a good idea to print this file so you have it
      for future reference.

========================================
==CONTENTS

==Product Support for IBM Stacker Users
==Getting More Information about Stacker
      Always Check Stacker Help
==Compatibility and Other Issues
      Third-party Disk Optimizers
      Norton Disk Doctor 7.0
      QEMM 7.x
      QEMM Stealth Mode and Configurations Without DPMS
      Qualitas 386MAX and DPMS
      PKZIP 2.04
      Stacker(R) for OS/2 & DOS
      Compaq Computers
      Windows for Workgroups 3.11
      Windows for Workgroups 3.11 and Lazy Writes
==Backing Up a Stacker Drive
==Upgrading from Stacker(R) 1.x to Stacker(R) 4.0
==Using the /R=0 Switch in STACKER.INI
==The Stacker Interceptor & STACHIGH.SYS
==Rebuilding the Stacker Configuration Files
==Fixing or Restoring a Stacker-aware DBLSPACE.BIN File
==Repairing a Stacker Drive & Removing Write Protection

========================================
==Product Support for IBM Stacker Users

Portions of the Stacker Help system or the screens refer to contacting
Stac and to the Stac TALK and Stac FAX services. These same types of
services are available from IBM. Please contact IBM Customer Support
with questions about Stacker.

========================================
==GETTING MORE INFORMATION ABOUT STACKER

----------------------------------------
Always Check Stacker Help!
----------------------------------------
Please note that Stacker Setup Help and the Stacker Help system
in Windows contain up-to-date information about using Stacker.
(Stacker Help works with Windows 3.1.)

The easiest way to get detailed information about Stacker is to
double-click the Stacker Help icon in the Stacker program group
under Windows Program Manager and then click the Search button.
Select or type in the name of the Stacker tool or procedure you need
help on and select the topic. Stacker Help contains information on
such topics as:

- DPMS and Stacker in memory
- Stacker AutoSave
- Compressing and AutoMounting floppy disks
- Repairing a damaged STACVOL file

=======================================
==COMPATIBILITY AND OTHER ISSUES

----------------------------------------
Third-party Disk Optimizers
----------------------------------------
Disk optimizers other than the Stacker Optimizer(TM) are not effective on
Stacker drives. Please do not use optimizers such as Norton Speed Disk 7
or PC TOOLS PRO 9.0 for DOS after you've set up Stacker on your system.

----------------------------------------
Norton Disk Doctor 7.0
----------------------------------------
Unfortunately, Norton Disk Doctor 7.0 is not yet compatible with
Stacker 4.0 drives. If you are using NDD 7, please check the option
to "Skip Compression Tests."

----------------------------------------
QEMM 7.x
----------------------------------------
If you are running a version earlier than QEMM 7.03, please consider
upgrading to the latest version. For QEMM 7.01, please add the option
/B=2001 to the DEVICE=DOSDATA.SYS line in your CONFIG.SYS file.
In all, versions of QEMM, at startup, the DOS-UP feature (DOSDATA.SYS)
temporarily disables your monitor and Stacker's password prompt. In your
CONFIG.SYS file, add the option: DEVICE=DOSDATA.SYS /ALTVIDEO-
so the password prompt is visible again.

----------------------------------------
QEMM Stealth Mode and Configurations Without DPMS
----------------------------------------
Stacker automatically uses DPMS when possible. If your system cannot
use DPMS, Stacker's Express Setup automatically uses EMS if the
resulting Stacker drive uses 32K clusters (large drives). In these cases,
insert the option /DBF=2 on the QEMM386 line of your CONFIG.SYS file.

If you do a Custom Setup and can't use DPMS and want to use EMS, add
the /DBF=2 switch on the QEMM386 line of your CONFIG.SYS file.

However, please don't use EMS if you are using QEMM's Stealth mode.
Stealth mode cannot access memory using EMS. During Custom Setup, if you
are given the option to use EMS or not, choose "Don't Use EMS."

----------------------------------------
Qualitas 386MAX and DPMS
----------------------------------------
To run DPMS, you need a '386 processor or higher and more than
1 MB of memory. In addition to these hardware requirements, you need
to run a memory manager that enables VCPI (Virtual Control Program
Interface). When you run a 386MAX and try to use DPMS, you get the
following error message:

           "VCPI services are not available."

The Qualitas 386MAX defaults to turning off VCPI. Check your
Qualitas documentation for information about enabling VCPI.

----------------------------------------
PKZIP 2.04
----------------------------------------
If your computer takes advantage of Stacker's DPMS (386 or higher with
1 MB of RAM), please use the -) option on the command line when using
PKZIP 2.04. This option disables PKZIP's use of DPMI services that interfere
with DPMS. If you want to permanently disable PKZIP's use of DPMI, add the
-) option to your PKZIP.CFG file.

----------------------------------------
Stacker(R) for OS/2 & DOS
----------------------------------------
Please do not install Stacker(R) 4.0 on a system that is using
Stacker for OS/2 & DOS. If you do, you won't be able to see your
compressed DOS drives under OS/2. Stacker for OS/2 & DOS does not yet
take advantage of Stacker SmartPack(TM). If you want to install Stacker 4.0,
you'll have to first remove Stacker for OS/2. First use the UNSTACK
command to decompress your data. Then, remove the OS/2 Stacker driver
STACKER.SYS and its associated files from their directory
(usually C:\STACKER\OS2). Then you can set up Stacker 4.0.

----------------------------------------
Compaq Computers
----------------------------------------
If your system uses PCMCIA cards, you need to make a few adjustments
to your system when you install Stacker.

For example, if you use a docking station or other driver that will change
drive letters around, be aware that the PCMCIA card will be assigned the
next drive letter. Since you can put the cards into different slots, just
entering one drive letter into the STACKER.INI will not necessarily automount
the drive. Use the following steps to ensure that you turn on AutoMount:

1. Add the following lines to the STACKER.INI file and save the changes:
      /RP=2
      /AUTO

2. In the AUTOEXEC.BAT file, add the following lines:
      STACKER x: (where x is the drive letter for the first slot for the
                  given setup)
      STACKER y: (where y is the drive letter for the second slot for the
                  given setup)

Notes: PCMCIA Flash Cards are treated like network drives. Stacker will
       not install on these devices.

       Also, if the PCMCIA driver offers the option to do a "compact format,"
       do NOT do so. This option won't create a boot sector; therefore,
       Stacker won't install. Format your ATA cards without the compact
       option.


----------------------------------------
Windows for Workgroups 3.11 
----------------------------------------
If you want to use Windows for Workgroups 32-bit file access with Stacker
drives, you'll need to disable DPMS. To do this, edit your CONFIG.SYS file.
REM out (or remove) the line DEVICE=C:\STACKER\DPMS.EXE. After editing your
CONFIG.SYS file, restart your computer. It's a good idea to then rerun your
memory manager (such as MemMaker or QEMM Optimize) to account for the removal
of DPMS.

Note: If you are using a non-Stacker DPMS client (which may be the case if
      you're using Novell DOS 7), you should instead add the switch /-DPMS
      to the end of your STACKER.INI file. Use ED /I to quickly open the
      STACKER.INI file.

----------------------------------------
Windows for Workgroups 3.11 and Lazy Writes
----------------------------------------
By default, Windows for Workgroups 3.11 does not perform lazy (deferred)
writes on Stacker drives, unlike other drives. To tell Windows for Workgroups
to perform lazy writes on your Stacker drives, you must insert a line in the
[386Enh] section of the SYSTEM.INI file in your Windows directory (typically
C:\WINDOWS that says ForceLazyOn= followed by the drive letter(s) of your
Stacker drive(s).  Some Microsoft documentation states that the ForceLazyOn
line goes in a different section of SYSTEM.INI, but in fact, it must go under
[386Enh].

For example, if your Stacker drives are C:, D:, and E:, and you want Windows
for Workgroups to perform lazy writes on all three of them, you would insert
a line under [386Enh] in C:\WINDOWS\SYSTEM.INI that says:

      ForceLazyOn=CDE

This will take effect the next time you start Windows for Workgroups.

===========================================
==BACKING UP A STACKER DRIVE

You can perform your standard backup procedure to back up files on the
Stacker drive. If you also want to back up the files on the uncompressed
drive, backup all files EXCEPT the hidden STACVOL file. (The STACVOL
file actually contains your compressed data, which was backed up during
the regular backup procedure.) Type STACKER at the DOS prompt to
determine the location of your STACVOL file. The location of the STACVOL
file will be in [brackets].

For example, on a computer with C as the Stacker drive, the uncompressed
drive is typically D [D:\STACVOL.DSK = size]. You would back up all the
files on drives C and D except the file STACVOL.DSK.

===========================================
==UPGRADING FROM STACKER 1.x TO STACKER 4.0

Note: This procedure applies only if the boot drive has been compressed.

Before you upgrade from Stacker 1.x:

1.  At the DOS prompt, type SWAPMAP and press ENTER to
     determine which drive letter is being swapped with C.
     Write that letter here._____________

2.  Insert Stacker 4.0 floppy disk #2 into its drive.

3.  Type:

     drive:SATTRIB -R C:\AUTOEXEC.BAT

      where drive: is the letter of the floppy drive where you
      inserted floppy disk #2. This removes the read-only attribute
      from the AUTOEXEC.BAT file.

4.  Type:

      COPY drive:\AUTOEXEC.BAT C:\

      where drive: is the drive letter with which C is being swapped
      (determined in step #1).

5.  When the AUTOEXEC.BAT file has been copied, type:

      COPY drive:\CONFIG.SYS C:\

      where drive: is the drive letter with which C is being swapped
      (determined in step #1).

6.  Install Stacker 4.0 starting with Disk 1.

If you are using DOS 5 or an operating system that does not preload
compression, you need to add the /SYNC+ option to your STACKER.INI
file to synchronize configuration files on compressed and uncompressed
drives. (From the Stacker directory, type ED to start the editor. Then,
choose STACKER.INI from the File menu. Add the /SYNC+ on its own line
anywhere in the file.)

===========================================
==USING /R=0 WHEN RUNNING A DISK REPAIR UTILITY

Stacker's driver can modify its read error handling with the setting
of the /R=? switch. When using this switch, set the number at 0.
Placing /R=0 in the STACKER.INI file forces the driver to make
additional error checks during decompression.

Note: Using /R=1 switch causes the driver to disable all error
checking during the decompression phase. Using /R without
the zero is the same as using /R=1. The safest choice is to
use /R=0.

In Chapter 5 (Troubleshooting) in the manual, the procedure to scan the
Stacker drive with another utility tells you to use Stacker's editor, ED, to
add the /R command to the beginning of your STACKER.INI file. If your
STACKER.INI has an /R switch, change it to /R=0.

To verify or change the /R switch in your STACKER.INI file

1. Exit Windows completely and get to a DOS prompt.

2. At the DOS prompt, change to the directory that contains your
Stacker files, usually C:\STACKER.

3. Type ED to open Stacker's editor.

4. Press ALT-F to access the File Menu; then type 3 to open the
STACKER.INI file.

Note: STACKER.INI is a hidden system file. Using ED is the fastest
way to access the file and make changes.

5. Add the /R=0 switch on a separate line at the beginning of
the file. If you already have /R, just add =0 to complete the line.

6. Press ALT-F then X to exit ED and when prompted, type Y
to accept the changes.

7. Restart your computer to put the changes into effect.

8. Run a disk repair utility, such as PC Tools DiskFix, on the Stacker
drive.

9. When you are done running the repair utility, use ED again to
remove the /R=0 command (it's only for diagnostic use). Save the
changes and restart your computer.

===========================================
==THE STACKER INTERCEPTOR & STACHIGH.SYS

In Chapter 5 (Troubleshooting) of the manual, the Stacker Interceptor section
incorrectly states that Stacker adds a REDIRECT.SYS line to your CONFIG.SYS
file during installation. Setup actually inserts:

	DEVICEHIGH=C:\STACKER\STACHIGH.SYS

STACHIGH (not REDIRECT) tells Stacker to intercept many DOS 6
commands typed at the DOS prompt and run the Stacker equivalent
when it performs operations on a Stacker drive.

===========================================
==REBUILDING THE STACKER CONFIGURATION FILES

If you can't access your Stacker drives when you restart your computer,
you may have to rebuild your Stacker configuration files.

To rebuild the Stacker configuration files

1. At the DOS prompt, change to drive C and type:

	\STACKER\CONFIG

and press ENTER.

2. Press Y to let CONFIG make its changes.

3. Restart your computer.

If you still can't get at your data and you are using preloaded data
compression, the DBLSPACE.BIN file may be damaged. See the next
procedure for information about restoring a Stacker-aware DBLSPACE.BIN
file.

===========================================
==FIXING OR RESTORING A STACKER-AWARE DBLSPACE.BIN FILE

If you still can't get at your data and are using DOS with preloaded
compression, the Stacker-aware DBLSPACE.BIN file may be corrupt.
Stacker provides a special program that you can use to build a new
Stacker-aware DBLSPACE.BIN file on your system.

To fix or restore a Stacker-aware DBLSPACE.BIN file:

1. At the DOS prompt, change to the Stacker directory. This is
usually C:\STACKER. If you loaded Stacker into a different
directory, change to that directory.

2. At the DOS prompt, type

	REDBL drive:

where drive is the uncompressed drive letter of the boot drive. If no
Stacker drive is mounted, use drive C.

The REDBL program analyzes your computer and builds or replaces
the file that integrates data compression with MS-DOS 6.

3. Remove any floppy disks, and restart your computer.

The REDBL program assumes the ATTRIB.EXE program is in the
\DOS directory or in the path. It won't work if the file isn't present.

===========================================
==REPAIRING A STACKER DRIVE & REMOVING WRITE PROTECTION

Stacker's AutoProtect feature regularly scans your Stacker drive for
problems. It fixes some problems immediately so you never even know
they existed. However, if AutoProtect finds a more serious problem,
it write-protects the drive to protect it from further damage. Your
data is still safe, but to access it, you will have to repair
the Stacker drive. This could involve several steps:

* Checking the file structures on the disk (cluster & file allocation
table (FAT) integrity)

* Repairing any errors found

* Checking the disk media (surface scan)


To repair Stacker drives using CHECK

1. Exit Windows completely and get to a DOS prompt.

Note: If you can't get to a DOS prompt, start your system using
the Stacker Startup Disk you created after you installed Stacker.
It gets you to a DOS prompt.

2. Change to the directory that contains your Stacker files,
usually C:\STACKER.

3. Type CHECK to evaluate the drive.

4. When CHECK asks if it should make repairs, let it.

5. When CHECK asks if it should do a surface test, let it.

6. When you return to the Stacker DOS Toolbox, press F10 then
ENTER to exit.

CHECK may recommend that you run DOS' CHKDSK or another disk repair
utility to resolve DOS problems. (See the manual for the full CHKDSK
procedure.) If you can, back up damaged files before running CHKDSK.
Take the time to correct any problems identified by either CHECK or
CHKDSK before doing anything else.

Once you have corrected the problems, restart your computer and run
CHECK again. When CHECK determines there are no more problems, it
removes the write protection, and you can access your data.

===========================================

(C) 1994 Stac Electronics. All rights reserved.
One or more U.S. patents: 4701745, 5016009, 5126739, and 5146221, and
other patents pending.

Portions (C) Novell 1994.
