                           Late-Breaking News

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

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

==Stacker(R) and Multimedia Cloaking(TM)
      Multimedia Cloaking and DPMS
==Getting More Information about Stacker
      Always Check Stacker Help
      Use STAC FAX(TM) or STAC TALK(TM) for Special Topics
==Using 32-bit File Access with Windows for Workgroups
      Common 32BFA Workarounds
==Compatibility and Other Issues
      Third-party Disk Optimizers
      Norton Disk Doctor 7.0
      QEMM 7.x
      QEMM and Configurations Without DPMS
      Qualitas 386MAX and DPMS
      PKZIP 2.04
      Compaq Computers
==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

========================================
==STACKER AND MULTIMEDIA CLOAKING
========================================
If you purchased Multimedia Stacker, your copy of Stacker 4.0
includes Multimedia Cloaking by Helix Software Company. Please be
sure to install Stacker before installing Multimedia Cloaking.
Follow the instructions in the Multimedia Cloaking User Guide
to install Cloaking.

If you are an advanced user, you might elect to use write 
caching in the Multimedia Cloaking disk cache, CACHECLK.
We strongly recommend you disable the write cache before
running Stacker utilities and flush the cache to disk before
you turn off or reset your computer. Use the following commands
at the DOS prompt to turn the caching off or on and to flush
the cache.

CACHECLK /NOW  To turn off write caching, such as before you run
               Stacker utilities

CACHECLK /W    To turn write caching back on

CACHECLK /F    To flush the cache, especially before shutdown

Note: Rebooting with Ctrl-Alt-Del also flushes CACHECLK's write
cache.

IMPORTANT: If you are not an advanced user or if you think you
might not remember to always flush the cache before you shutdown
or reset and disable the cache before running a Stacker tool, we
recommend you not enable the write caching feature permanently.
If the CACHECLK line in C:\AUTOEXEC.BAT has no /W switch, write
caching is not enabled.


----------------------------------------
Multimedia Cloaking and DPMS
----------------------------------------
If you're using DPMS and then install Multimedia Cloaking,
DPMS.EXE will display the following message:

     "DPMS: Another DPMS server is already active."

This is normal as Multimedia Cloaking's CLOAKING.EXE is also a
DPMS server and is loaded before DPMS.EXE.

Note: If you run Multimedia Cloaking and decide at some point
that you need to disable DPMS, you need to make the following
two edits to the CONFIG.SYS file:

- REM out the DPMS.EXE line
- Put a /NODPMS switch at the end of the CLOAKING.EXE line.


========================================
==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

----------------------------------------
Use STAC FAX(TM) or STAC TALK(TM) for Special Topics
----------------------------------------
If you have an unusual configuration or are interested in specific
advanced Stacker topics, you can order information from our STAC FAX
STAC TALK system. Both services are available in the U.S. and Canada
24 hours a day, 7 days a week. See your product support brochure for
information on how to reach STAC FAX or STAC TALK. For a list of
STAC FAX topics, request STAC FAX # 1000.

Some releases of Stacker include the STACFAXes directly on your
distribution media. Check your distribution media for the directory
\STACKER\STACFAX. Advanced Stacker users may want to scan the files
in this directory for technical bulletins about unique hardware and
software configurations and troubleshooting. For an index of documents,
refer to the file CATALOG.TXT.

========================================
==Using 32-bit File Access with Windows for Workgroups 3.11
========================================

Stacker now works seamlessly with Windows for Workgroups' 32-bit file
access (32BFA). Stacker requires no special options or configurations.
To get the best performance, you do, however, have to:

- Turn on 32BFA. (Refer to your WFW documentation if you don't know how.)

- Enable Lazy Writes in WFW.

To enable lazy writes in WFW

1.  From the Program Manager's File menu, choose Run.

2.  In the Command Line box, type SYSEDIT

3.  Select the window that contains your SYSTEM.INI file and in the [386Enh]
section, type a line that says ForceLazyOn= followed by the drive letter(s) of
your Stacker drive(s). For example, if your Stacker drives are C:, D:, and E:,
you would insert the following line:

                ForceLazyOn=CDE

4. Save the file and exit the editor.

----------------------------------------
Common 32BFA Workarounds
----------------------------------------
If you have trouble initializing 32BFA in Windows for Workgroups, here are
some common workarounds that might help:

* Make sure you are using a permanent swap file. 32BFA will not initialize
  properly with temporary swap files.

* Be sure to close any open files or files (such as printer caches) that
  are open by a line in your Autoexec.bat file.

* After turning on 32BFA, ensure these lines are in the [386Enh] section
  of your SYSTEM.INI file:

	device=vfat.386
	device=ios.386
	device=vxdldr.386

  These lines mean a Real Mode Mapper (RMM) is loaded.

* Make sure the "minfilecache=" entry in the [vcache] section of the
  SYSTEM.INI is appropriate for the amount of memory you have. 

  For example, a 2-MB cache would be appropriate for a system with
  8 MB RAM.

* If the DOS SUBST command is run before Windows for Workgroups loads,
  32-bit file access will not initialize.

* If you started the real mode network (NET START FULL or NET START
  BASIC) and then start Windows for Workgroups, 32-bit file access will
  not initialize.

For information about other system conditions that might interfere with
using 32BFA, check with Microsoft.

=======================================
==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 8 or PC TOOLS PRO 9.0 for DOS after you've set up Stacker on your system.

----------------------------------------
Norton Disk Doctor 7.0 and 8.0
----------------------------------------
Disk repair utilities, such as Symantec's Norton Disk Doctor (NDD),
are not aware of Stacker's new SmartPack(TM) technology. If you run
NDD against a Stacker 4.0 drive, you will receive an error message,
and NDD will recommend that you use the utilities provided with the
compression program. 

However, you can run NDD against your Stacker drive if you skip
compression tests. You can turn off compression tests from the
command line or the NDD menu.
_______
From the command line:

   Type: NDD /NOCOMP drive: <enter>

________
From the NDD menu:

   1. Start the NDD program as usual.
   2. From the main menu select Options.
   3. From the Options menu, select General.
   4. Select Skip Compression Tests, then OK, and OK again to return
      to the main menu.

In either case, once you have turned off Compression Tests, you can
run NDD against any drive, including Stacker drives. NDD will no longer
give you error messages.

Windows users:
If you run NDD from Windows (Norton Utilities, version 8), or
have Norton Destop for Windows version 3, you can use the following
method to skip compression tests:

1. Open NDD.
2. From the menu bar, select Options.
3. From Options, select Preferences.
4. Click the box for Skip Compression Test.
5. Click OK to save the changes.

You can now run NDD without the error messages.


----------------------------------------
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 and 7.02, 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 and Configurations Without DPMS
----------------------------------------
If your system doesn't use DPMS, the Stacker driver can use EMS (Expanded
Memory Specification) memory instead. This requires a /EMS switch in the
STACKER.INI file. When that switch is present and if you are using QEMM,
you should add the /DBF=2 switch to the QEMM386 command line in your
CONFIG.SYS file.

SETUP automatically puts the /EMS switch in the STACKER.INI file if:

- You run Express Setup and it creates creates a Stacker drive that uses 32 KB
  clusters

  OR

- You run Custom Setup and tell it to use EMS.

Run ED /I from a DOS prompt to edit or view your STACKER.INI file and ED /C to
edit your CONFIG.SYS file and add the /DBF=2 switch.

Note:  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
----------------------------------------
DPMS requires a memory manager that enables VCPI (Virtual Control Program
Interface). When you run 386MAX and try to use DPMS, you get the following
error message:

           "VCPI services are not available."

To have 386MAX provide VCPI, reply YES when asked if you would like
to enable EMS services during the 386MAX installation. If you already
have 386MAX installed, run INSTALL/R from the 386MAX directory
and reply YES to enabling EMS services.

----------------------------------------
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.

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

For example, if you use a docking station or other driver that changes drive
letters around, the PCMCIA card is 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 Stacker 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.

========================================
==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, back up 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 D:\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.

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
========================================

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.

The text should say to add /R=0.

During normal computer use, you don't need the /R at all. But, when you
want to use a disk repair utility and check for errors, having the /R=0
command in the STACKER.INI forces the driver to make additional error
checks during decompression. Using /R=0 results in maximum error
detection.

Note: Previous Stacker documentation suggested setting this switch
to /R=1. In Stacker 4.0, this setting causes the driver to disable all
error checking during the compression phase. Please use /R=0 or nothing
at all.

To add /R=0 or change /R to /R=0 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 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 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 a version of DOS with
preloaded compression (MS-DOS 6.x, Novell DOS 7, or PC-DOS 6.1 or higher),
the Stacker-aware DBLSPACE.BIN file, which integrates data compression
with DOS, 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
DBLSPACE.BIN file.

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

========================================
==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 and file allocation
  table (FAT) integrity)

* Repairing any errors found

* Checking the disk media (surface scan)

To repair Stacker drives using CHECK /F

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 /F 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.
Other patents pending.

All Stac product names are trademarks or registered trademarks
of Stac Electronics. Other product names are trademarks of their
respective holders.

Portions (C) Novell 1994.

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