4.0x Serial&LAN ************ BTRIEVE & NETWARE 2.0a **********************
                            ************************
*  When running Novell 2.0a, run btrieve before running anywhere. Type in:
        btrieve /m:20 /p:1536 /b:2 /f:4 /e

*  "File not found AW.TRM" can be caused by load btrieve first with none or
        incorrect parameters. "btrieve /m:20 /p:1536 /b:2 /f:4 /e" is the correct
        settings for us. Or they can take it out of memory with bstop awbtrv.zip
        on BBS.


4 Serial&LAN *************** CUBIX and VGA problems **********************
                            ************************

A patch program was sent to Cubix from development to fix a problem unique to 
certain Cubix boards. This problem did not occur with pcANYWHERE 4.03c. The
problem is that these Cubix cards are not fully emulating certain VGA registers
(DAC registers), causing the remote screen to look grey. Cubix will correct the
problem in its future boards. Future releases of pcANYWHERE will not require this
patch, automatically checking for DAC registers.

Cubix will distribute the patch to their customers who require it. The name
of the patch file is P45-1.ZIP.




4.03xLAN **************** GATEWAY in HIGH MEMORY *************************
                         ************************

            The 4.03c version of awlan.exe dated 5-24-91 does not load
          the gateway high. The Problem is fixed in the new release 4.5.

            4.03 users who do not wish to upgrade can load the gateway
          high from the DOS prompt by entering:

                    "loadhi awlovl3 -i=xxx -p=path".

              * loadhi = the executable for the memory management
                program they are using

              * xxx = the user ID for awlan

              * path = the drive and path where the awlan
                configuration files are stored 



4.xLAN ********************* NASI/NCSI Users *****************************
                            *****************

o   Older version of NASI/NCSI can cause problems.

    Problems such as data loss, inability to connect to a NASI/NCSI port, random
    disconnect, or file transfer abort can usually be solved by installing 
    the latest version of the communication server software. If you are using
    Novell's NACS, please contact Novell for the latest versions of NASI and NACS.
    Even though version 2.09j may fix some earlier problems, you will need a later
    version 3 in order to avoid random disconnect problems.
    
    If you are Network Product Corporation's ACS2 or NMP, please contact Network
    Products for the latest version of NCSI and ACS2 to properly operate with
    pcANYWHERE for LAN.



4.xLAN ******************** NETWARE 386 Users ****************************
                           *******************

    When using the NetWare/IPX device type, you should make your host
    information entries specify the computer name of the host. Leaving
    the host name blank will not display a list of names.

    The fix for this requires you to upgrade to version 3.10 of NetWare 386,
    and install the "SCBFIX.ZIP" patch available from Novell on NetWire on
    Compuserve in Library # 16 Novel new uploads. There is no fix for version
    3.00.  Contact Novell for any additional information on this upgrade and
    patch. You can download tapsys in library #16 this is a menu for getting
    around comnpuserve faster. Novel 3.11 has the patch built in.



4.5LAN ********************** WINDOWS and IPX ****************************
                             *****************

o   The VIPX.386 driver is only for DOS programs using IPX services.
    This driver appears in the "network=" line of your SYSTEM.INI
    file if you specified a Novell network when Windows was
    originally installed.  The "pcANYWHERE Installation for Windows"
    procedure removes the reference to this driver from your
    SYSTEM.INI because current versions of VIPX.386 (including
    version 3.00) cause pcANYWHERE to lock up.  If future versions
    of VIPX.386 work properly and are needed by other applications,
    you may return this reference to your SYSTEM.INI file.

    The original line in the SYSTEM.INI contained something like:
            network=*vnetbios, vnetware.386, vipx.386
    The reference to vipx.386 is removed by the installation program:
            network=*vnetbios, vnetware.386


o   With an IPX connection, when running DOS under Windows, it is
    possible that a key may have to be pressed in order to start the
    DOS session. If you experience this problem, a change to your
    SYSTEM.INI file can help. In the [386Enh] section, add a line to set
    the value for TimerCriticalSection to 100, as follows:

       [386Enh]
       TimerCriticalValue=100

    If the problem persists, increase the value in increments of 100.
    Note that modifying this parameter may affect Windows performance.