             WAL/Win 5.0 production bewares.txt file (12/19/96)

INTRODUCTION:

This file is the bewares.txt file for the WAL/Win 5.0 production 
release. Various "be aware" items and release notes are listed below.

The WAL/Win 5.0 software is delivered on CD-ROM only, with the ability
to install from diskettes after copying files from the CD.

We support Microsoft Visual C++ v4.1.
==================================================================
UNSUPPORTED ITEMS

The following items are not supported in the production release of
WAL/Win 5.0:

1) 	There is no Uninstall capability on the WinNT 3.5 PCs.

2)      The XNS protocol is not currently supported with Win95 unless 
        the IMS server is at IMS release 3.3.1 or greater.


SETUP:

1)  Windows NT 4.0 requires certain modules of the WAL/Win release to be
    written to the System area.  In order to write into this area,
    the user installing the WAL/Win 5.0 production release is required to
    have System Administrator privileges.

2)  If the WAL/Win 5.0 beta software is already present on the PC where the
    WAL/Win 5.0 production release is being installed: 

    The user should "Uninstall" the 5.0 beta release before installing
    the 5.0 production release software; otherwise, duplicate entries
    for WAL/Win will appear in the Add/Remove panel.

    Users should also open the printers window in the Windows control
    panel and delete the Form Image Printer.  Failure to do this before 
    upgrading to the WAL/Win 5.0 production release could result in a 
    "SEVERE ERROR" message stating that the Form Image Printer 
    is unable to be installed.

3)  During SETUP, the user can select either XNS or TCP. Since
    networking files are installed as part of the Windows 95 or
    Windows NT installation, this option does not change any of the
    networking files. The option's only purpose is to copy the correct
    *.sts module to the f3sts.dll module.  

4)  When the networking section of the LOGON.CFG file is created,
    the entries will appear to be insufficient. However, additional
    information will be added to this section (such as TCP address,
    STS Type, etc.) the first time the PC logs on to a server.

5)  WAL/Win 5.0 is released on CD media only, but can be installed from
    diskette if the files are copied over.  Refer to the README.TXT
    file for instructions on installing from diskette.

6)  Uninstalling WFD with WAL/Win software installed, removes the
    FORM IMAGE PRINTER driver.  The workaround is to do an upgrade 
    of WAL/Win to get the driver re-installed.

7)  Uninstalling WFD and then uninstalling WAL/Win corrupts the
    WAL/Win uninstall file.  The workaround is to manually delete
    the WAL related files.


NETWORKING ISSUES: 

1) The ability to use XNS on a Win95 PC is handled by SETUP.
   The user will be prompted to verify that the server is running
   IMS release 3.3.1 or greater.  If the server is not running
   IMS 3.3.1 or greater, the user cannot use XNS with Win95 and
   must choose TCP.

   If the server is a WinNT server, it must be running IMS 3.3.1
   production level or greater software.  It must also contain a 
   patch from Microsoft (see IMS STR 36335).

Workaround: Install OS patch Q153665.

References: STR 36335


2) If your network protocol is not correct for the PC Windows version,
   the following message will be displayed:

		15,151,0 FileNet SEQ Unknown Error

   To correct this condition, make sure:

   Win95 with XNS is using an IMS 3.3.1 or greater server 
   as default domain and has "UseSTTHeader=1" in the LOGON.CFG
   file.
   
3) For WinNT users: Selecting XNS during SETUP and answering "Yes" 
   when asked whether the server is running IMS 3.3.1 or greater will
   mean the user can only log on to a server running IMS 3.3.1 or
   greater. However, this choice maximizes server efficiency.


ERROR MESSAGES:

1) Error messages will be allowed up to 255 characters.  The error 
   tuple returned will be the database error, instead of a generic 
   error tuple.  Developers should be careful in using the ERM entry
   points, making sure that enough space has been allocated for the 
   returned error string.  Please see STRs 28983 and 34334.
