      -----------------------------------------------------------------
      STACKER NOTE                                         STACKER NOTE
                   STACKER AND WINDOWS FOR WORKGROUPS 3.11
                 (Applies to Stacker 4.0 for Windows & DOS)
      STAC FAX  4201 (11-29-1994)
      -----------------------------------------------------------------
                                      
      BACKGROUND
      
      Stacker 4.0 works with Windows for Workgroups (WFWG) 3.11. WFWG
      3.11 includes a new feature called 32-bit file access (32BFA),
      which uses a 32-bit cache called Vcache that resides between
      Windows and DOS. Multimedia Stacker supports WFWG 3.11's 32BFA.
      Some earlier shipments of Stacker 4.0 did not support 32BFA.
      However, Stac is providing an add-on file that allows 32BFA to be
      enabled on all Stacker 4.0 drives.
      
      SOLUTION
      
         - Determine if you have the updated Stacker driver that
           supports 32BFA
         - Update the driver if necessary
         - Enable 32BFA
         - If  32BFA does not enable on a drive
         - Other issues
           
      Determine if you have the updated Stacker driver that supports
      32BFA
      
       1.  From the DOS prompt, change to the STACKER directory.
       2.  Type: DIR VSTACKER.386 <enter>.
       3.  If the file is present, you may enable 32BFA. If not, obtain
           the add-on file from Stac.
           
      Update the driver if necessary
      
      You may download the add-on file from the on-line services
      Compuserv, America On-Line, or the Stac BBS. The file name is
      S4UP.EXE, which is a self-extracting archive file. After
      downloading the file, simply place it in the STACKER directory
      and run it. Follow the on-screen message to update the files. See
      the brochure "How To Reach Stac" for information on using the on-
      line services. Also, StacFax 4512 provides details on using the
      Stac BBS.
      
      Enable 32BFA
      
       1.  Open WFWG as usual. Open the Main group.
       2.  Open the Control Panel and then open the 386 Enhanced icon.
       3.  Click on the Virtual Memory button. At the next screen click
           on the Change button.
       4.  At the bottom of the dialogue box, check the 32BFA box. A
           cache size will appear in the adjacent window. Accept the
           default setting for now. If you wish to change it later, you
           may do so.
       5.  Click on OK. When asked, click on OK again to accept the
           changes.
       6.  You will be asked whether to restart your system so that the
           changes may take effect. Choose Restart.
       7.  After restart, open WFWG again and use the system like
           normal.
           
      If 32BFA does not enable on a drive
      
      32BFA requires that certain conditions be met. Most of these
      conditions are independent of disk compression. They are outlined
      here, but contact Microsoft for full details.
       1.  When using disk compression like Stacker a "Real Mode
           Mapper" volume must be available. The RMM driver is loaded
           if the following lines are in the [386Enh] section of the
           SYSTEM.INI file:
           device=vfat.386
           device=ios.386
           device=vxdldr.386
           These lines are normally placed in WFWG's SYSTEM.INI file by
           default when enabling 32BFA on a compressed drive.
       2.  The "minfilecache=" entry in the [vcache] section of the
           SYSTEM.INI should be appropriate for the amount of memory in
           the system. For example, a 15MB cache on a system with 16MB
           of RAM is too large.
       3.  If there are open files during the initialization of 32BFA,
           or if you are using a temporary swap file, the process will
           fail. Set up a permanent swap file if you have not already
           done so. Some programs leave files open during Windows
           startup. PCACHE is known to do so, and certain
           fax/communications programs may also. If the DOS SUBST
           command is run before WFWG loads, 32BFA will not initialize.
           Some users create a WINSTART.BAT file that loads programs
           that may leave files open while 32BFA is initializing.
       4.  If you have started the real mode network (NET START FULL or
           NET START BASIC) and then started WFWG, 32BFA won't load.
           
           Other issues
      
       1.  If you install SUPDATE.EXE and Windows hangs during startup,
           open the \WINDOWS\SYSTEM.INI file in an editor. Look for the
           line "NoEMMDriver=On" in the [386Enh] section. Disable it by
           typing ";" at the beginning of the line. (Don't type the
           quotation marks.) Restart Windows.
       2.  If you wish to enable the write delay function of VCACHE,
           you must edit the SYSTEM.INI file. Open the file in an
           editor and go to the [386Enh] section. Add this line:
           ForceLazyOn=xxx
           where xxx is the drive letter of each drive where you wish
           to enable the write delay feature. Please consult your WFWG
           documentation for information on the trade-off between speed
           and safety when write delay is enabled.
       3.  Ensure that you are loading the WFWG IFSHLP program in your
           CONFIG.SYS file. Examine the CONFIG.SYS for a line that
           looks something like this:
           DEVICE=C:\WINDOWS\IFSHLP.SYS
      -----------------------------------------------------------------
      Copyright 1994 Stac Electronics
