                           Late-Breaking News

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

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

==Stacker 4.1 and Windows 95
      Stacker Anywhere(TM)
      Windows Swap Files
      Dealing with Long Filenames
      Long Filename Troubleshooting
      Dual Booting Windows 95 and DOS
==Stacker 4.1 and Stacker for OS/2 & DOS

==Getting More Information about Stacker
      Always Check Stacker Help
      Stac's Online Services
==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.5 and Conserving Memory
      QEMM 7.x
      QEMM and Configurations Without DPMS
      Qualitas 386MAX and DPMS
      PKZIP 2.04
      Compaq Computers
==Backing Up a Stacker Drive
==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 4.1 AND WINDOWS 95


If you haven't yet upgraded to at least 16 MB of memory,
you might want to consider doing so before installing
Windows 95. Even though Windows 95 will run with its
minimum memory requirements, it is a complex multitasking
operating system. To get the full benefit of Windows 95 and
all programs that run with it, you really need more memory.
Windows 95, Stacker 4.1, and all your other software will run
faster with a full complement of memory.

----------------------------------------
Stacker Anywhere(TM)
----------------------------------------

Stacker Anywhere lets a computer on which Stacker is
not installed use removable media compressed by Stacker.
If you compress a floppy disk on your computer, other
computers can use the extra space and data even if they
do not have Stacker.

A computer running Windows 95 must make the Stacker
compressed disk available in MS-DOS mode before it can
access data on it from within Windows 95.

To use a Stacker compressed removable disk under Windows 95:
1. Restart your computer in MS-DOS mode.
2. Insert the disk into a drive.
3. Type drive:STACKER and then press ENTER.
   For example, if you insert a floppy disk into drive A,
      type   A:STACKER.
4. Type WIN to return to Windows 95.


----------------------------------------
Windows Swap Files
----------------------------------------
Windows 95 manages virtual memory and swap files itself. If you
find it necessary to change your swap file settings, use
Windows 95 methods for doing so. Right-click the My Computer
icon, select Properties, click the Performance tab,
then click the Virtual Memory button.

If you use Stacker's Virtual Memory icon in the Control
Panel, you'll see a message instructing you to use Windows 95's
own virtual memory management techniques.

----------------------------------------
Dealing with Long Filenames
----------------------------------------

Even if you don't create long filenames yourself, keep in mind
that Windows 95 does. For example, "Start Menu" is the long
filename of a folder in the Windows directory. Windows 95 also
maintains a DOS-style (8 characters with an extension of up to
3 characters) name as an alias for each file. The DOS-style
name for the Start Menu folder is usually "StartM~1".

Stacker 4.1 provides a special utility named SaveLFN to save and
restore long filenames. You will probably never use this program,
but other Stacker utilities will. If you have occasion to backup
and remove or restore long filenames manually, you might want to
use SaveLFN.

SaveLFN can run in either of two modes:
   Backup  -- saves long filenames in a data file and
              removes them from the Windows 95 disk
   Restore -- replaces the long filenames from a data file
              to the Windows 95 disk

SaveLFN can also Preview the results.
   Preview a Backup  -- the data file with long filenames is
                        created, but no long filenames are removed
                        from the Windows 95 disk.
   Preview a Restore -- SaveLFN checks all the filenames in the
                        data file and sees where they would go,
                        but the filenames are not written to the
                        Windows 95 disk.

>> To back up long filenames and remove them from a Stacker drive

1. Restart your computer in MS-DOS mode. When starting, you'll
   see the message "Restarting Windows 95." Press F8 when you
   see the message, then press the appropriate number to choose
   "Command prompt only."
2. Type SAVELFN and press ENTER.
   Use the menus to supply information. As the Mode, choose Backup
   long filenames. Choose the disk to operate on. SaveLFN prompts
   you if you omit required information.  SaveLFN includes
   complete online help.


>> To restore long filenames

1. Start your computer in MS-DOS mode.
2. Type SAVELFN and press ENTER.
   Use the menus to supply information. SaveLFN prompts you for
   required information if you don't supply it.

If you prefer, you can specify options at the MS-DOS command
line in the SaveLFN command.

For example, SAVELFN C: /B C:\STACKER\LONGNAME.DAT backs up
(/B) the long filenames on drive C in a file named LONGNAME.DAT
in the Stacker directory and removes them from the Windows 95
structure. SAVELFN C: /R C:\STACKER\LONGNAME.DAT restores
(/R) the long filenames in a file named LONGNAME.DAT in the
Stacker directory to the specified disk.

Use SAVELFN /? for the syntax and complete list of options.

----------------------------------------
Long Filename Troubleshooting
----------------------------------------

If SaveLFN is interrupted while it is backing up long
filenames, you may see an error message from SaveLFN
or you may restart Windows 95 and find an empty Start menu.
You may be able to resolve any problems with a few
simple steps.

1. Immediately run SaveLFN to restore any filenames already
   removed. You'll have to specify the disk and choose
   Restore.
2. Run SCANDISK and CHKDSK to make sure the disk is in good
   shape.
3. Run SaveLFN with the Preview option to make sure the long
   filenames can be backed up and removed safely.

If the SaveLFN backup process had been interrupted while being
run by another Stacker utility, you can now run the Stacker
utility again.

----------------------------------------
If Your Computer Restarts into Windows 95 but Your
Start Menu is Empty

Several Stacker utilities automatically back up and restore long
filenames in the process of running. If your Start menu is empty
when your computer restarts following some drastic interruption
to a Stacker utility, the Windows 95 long filenames may need to
be restored.

>> To recover:
1. Restart your computer into DOS and change to your
   Windows directory if necessary.
2. Type DIR STA* to identify the Start menu names.
3. Type DELTREE C:\WINDOWS\STARTM~2 (or whatever is the
   highest numbered directory that indicates a Start menu.)
4. Type SAVELFN to restore the long filenames.
5. Press ENTER to choose Run Program Now.
6. When prompted, choose the drive letter.
7. When prompted, choose Restore long filenames.
8. When the program is finished, start Windows 95.

----------------------------------------
Backing up Long Filenames for Other Uses

SaveLFN backs up long filenames independently of Stacker. This
feature can come in handy, for example, if you use a DOS backup
program on your system. Some older DOS utilities can't handle
long filenames, which can result in removing them, scrambling
them, or otherwise corrupting the Windows 95 structure.

If you want to use such DOS utilities with Windows 95, you can
run SaveLFN either to only back up long filenames (use the
Preview option) or to back them up and remove them from the disk.

To restore using that backup, use SaveLFN again to restore the
long filenames before starting Windows 95 again.

You can use SaveLFN's Preview option at any time to try out
SaveLFN without making any changes to the long filenames on
your disk. However, you MUST REMOVE the long filenames (with
Backup mode or /B) if the your DOS backup program or other
utility cannot handle the long filenames.

NOTE: You can only use SaveLFN as part of an image backup and
restore of your hard disk, because you must back up or restore
ALL the long filenames. You can't select individual long filenames
for backup and restore.

----------------------------------------
Dual Booting Windows 95 and DOS
----------------------------------------

IMPORTANT! Stacker utilities keep the system files on your
current boot drive up to date. However, if you are set up to
dual boot Windows 95 or another operating system, Stacker will
not keep both systems up to date. You'll have to modify the
non-current system manually if you make any changes to your
system after installing Windows 95.

========================================
==Stacker 4.1 and Stacker for OS/2 & DOS

If you have Stacker 4.0 for OS/2 & DOS installed on your
computer and expect to install Windows 95, you will want
to get additional information first. Details about
using these two Stacker versions together are documented
in Stac TechNote 4901. You can get it through all
Stac's support locations, including StacFax, the Stac BBS,
CompuServe, America Online, and on the internet at the
Stac Web Site (http://www.stac.com).


========================================
==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 95 and 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 search for 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's Online Services for Special Topics
----------------------------------------
If you have an unusual configuration or are interested in
specific advanced Stacker topics, you can access our online
services and get information immediately. Or you can order
information from our StacFax system. See your product
support brochure for information on how to reach the Stac
support services. For a list of StacFax topics, request
StacFax # 1000.


========================================
==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 for Windows for Workgroups
----------------------------------------
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 opened 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 Stacker.

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 complain about being run on a compressed drive.

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

----------------------------------------
QEMM 7.5 and Conserving Memory
----------------------------------------
If you use DOS 6 or later and have QEMM 7.5 installed,
Stacker can run in as little as 13 KB. You'll have to
modify one of Stacker's configuration files after you
finish setting up Stacker.

1. If you are in Windows, exit it completely and
   get to a DOS prompt.
2. Type ED /I and press ENTER.
3. Press ENTER to insert a new line.
4. Type /QD on the new line.
5. Press the ALT key, followed by F,
   then press X to exit the editor.
6. When asked if you want to save the changes, press Y.
7. Restart your system to put the change into
   effect.

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

Stacker's Setup program 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 allow Stacker to 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 compress 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 compress the
       drive. If you have an ATA card, format it 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 Host 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, its
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.


========================================
==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 Stacker
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 decompression 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 /I to open Stacker's editor for editing STACKER.INI.

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

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

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

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

7. Run the desired disk utility, such as PC Tools DiskFix, on the
   Stacker drive.

8. 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.x 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 remove the
write protection, 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)

Start by repairing the Stacker drive 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.

CHECK may recommend that you run CHKDSK or another disk repair
utility to resolve DOS problems. (See the Stacker User's Guide
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) 1995 Stac Electronics. All rights reserved.
One or more U.S. patents: 4701745, 5016009, 5126739, 5146221,
and 5414850. 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.

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