(c) Copyright 1997 by Symantec Corporation. All rights reserved.


                    pcANYWHERE for DOS

                       Version 5.04

                        July 1997


Thank you for selecting pcANYWHERE for your remote computing
needs.

If you are new to pcANYWHERE, please read the User's Guide.  The
manual has a great deal of information to help you install and
configure pcANYWHERE to work optimally for you.

If you are upgrading from an earlier version of pcANYWHERE,
please read the sections "What's New in pcANYWHERE 5.0" and "For
Users of Earlier Versions of pcANYWHERE" sections of Chapter 1 of
the User's Guide for changes in this version. This chapter will
direct you to any topics that may be important to you as you
upgrade your installation of pcANYWHERE.

This file has four sections. The first contains information you
should be aware of before you install pcANYWHERE. The second
contains corrections and additions to the printed manual. The
third section contains some compatibility information that you
may need to use pcANYWHERE with some other products. The final
section contains some biref notes on fixes and enhancements that
have been added to pcANYWHERE 5.0 since its initial release.

For technical assistance with pcANYWHERE, you can contact
Symantec Technical Support at (541)465-8430, or through the
Symantec Bulletin Board at (541)484-6669. (There is a default
Online Service configuration for the Symantec BBS in this
package.) If you are a Compuserve subscriber, you can contact
Symantec Technical Support in the Symantec forum (GO SYMANTEC).

              IMPORTANT INSTALLATION INFORMATION
              ----------------------------------

Network Administrator Installation
----------------------------------

After installing over an existing copy of pcANYWHERE 5.0, you
must run AW with the administator user ID ("@@@") immediately
following the installation. This will insure that all
configuration file conversions are performed correctly.


                                        
             CORRECTIONS AND ADDITIONS TO THE MANUAL
             ---------------------------------------


User's Guide -- Chapter 2 -- Installation
-----------------------------------------

Network Workstation Installation

Make certain that a TEMP environment variable is set when running
a workstation installation of pcANYWHERE. If not set, temporary
files will be created in the root directory of the network drive
pcANYWHERE is running from and could result in depletion of
available network space.



User's Guide -- Chapter 7 -- Remote Control Sessions
----------------------------------------------------

Accessing the Remote PC during a Session

When using the 'Go To DOS' feature to access your local machine
do not run any terminate-and-stay-resident (TSR) programs. If a
TSR program remains in memory when you exit the DOS shell,
pcANYWHERE will not be able to reload itself into memory and will
terminate. You will have to reboot your machine.


Creating pcANYWHERE Scripts
---------------------------

RECEIVE STRING command

You must use the SET CANCEL or SET DISCONNECT commands with this
command, or your script will wait for a string without checking
for interruptions from the keyboard or the state of the
communications channel.


MESSAGEBOX and TYPE commands

These commands should not be used in remote control sessions when
the display is in a graphics mode.

SESSION DIAL command

The SESSION DIAL command cannot be used to connect to Norton
Access Server Hosts because they require Login Names which must
be typed in by the user.

Using Automated Procedures
--------------------------

Automated Procedures cannot be used to connect to Norton Access
Server Hosts because they require Login Names which must be typed
in by the user.



                          COMPATIBILITY
                          -------------

Microsoft Windows (TM) and Windows for Workgroups (TM)
------------------------------------------------------

If you will be using pcANYWHERE from within Windows most of the
time, we recommend that you purchase pcANYWHERE for Windows.
pcANYWHERE for Windows is a native Windows application, so it
takes advantage of Windows functionality to improve performance
and reliability in this environment.

If you install Windows AFTER installing pcANYWHERE, you can add
the pcANYWHERE Windows drivers by running the INSTALL program in
the pcANYWHERE directory and selecting 'Special host installation
for Windows'.

The pcANYWHERE Windows Host VGA driver does not support
single-plane 16-color drivers. You must use the standard VGA
(VGA.DRV) or SuperVGA (SUPERVGA.DRV) driver from Windows, or a
similar four-plane 16-color driver.

If you experience video problems when remotely controlling
Windows, you should configure the memory manager on your remote
computer to provide at least 1 MB of available EMS memory.

In order to make Netware IPX connections from a Windows DOS Box
in Windows for Workgroups, you will have to install the Novell
Netware network support ONLY.

To run Windows for Workgroups on a pcANYWHERE Host using Netware
IPX, you will have to remove the NetBEUI network protocol in
Windows for Workgroups, leaving only the Netware IPX/SPX
protocol.

Starting or ending Windows on a Host while a background file
transfer is in progress will cause the file transfer to abort
before completion. Windows makes changes in DOS which cause any
ongoing file operations to fail. Background transfer can be
resumed once Windows has finished initializing or terminating.

If you will be running Windows on a machine you are using as a
pcANYWHERE Gateway, the Gateway must not be loaded into high
memory. Windows changes the memory management as it is
initializing and terminating, which will cause an active Gateway
to end the active session if it is installed in upper memory.

The "Display1=" option in PCAW.INI is no longer supported.


Novell Netware
--------------

There is a problem in the latest version of Netware's VIPX.386
driver for Microsoft Windows (the file is dated 10/11/93). If you
are using Windows on a machine which is a Netware IPX Host, you
may experience problems if you exit Windows between remote
control sessions. Earlier versions of this driver do not exhibit
this problem.


Disk Caches
-----------

If you are using a disk cache that caches disk writes (the
feature may be called delayed writes or write-behind), and you
plan to use the Host drive security feature to prevent callers
from writing to your fixed drives, and your Host will be logging
calls to a fixed drive, you should disable the write caching
feature of your disk cache.

If you are using a version of the disk caching utility 
SMARTDRV.EXE that is dated 3/10/92 or earlier, please upgrade to
a later version, or errors may occur.  


Networks
--------

If you use remote drive mapping to access a remote network drive,
and are using COMMAND.COM as your DOS Shell program, the DIR
command may not work as expected. You may need to use the command
"DIR *.*" to see the list of files on the mapped drive.


Drive Mapping
-------------

To enable drive mapping, your CONFIG.SYS file should contain the 
statement 'LASTDRIVE=Z'.  This will increase the number of 
available drive letters to map to your host's drive.


Novell Netware Connection Services (NASI)
-----------------------------------------

For use with Netware Connect, you should use a NASI driver that
is version 1.00f (dated 3/22/94) or later.


Telebit Access Server (TACS)
----------------------------

The Novell Netware VIPX.386 driver for Windows dated 10/11/93 or
later is required if you will be running Microsoft Windows on a
TACS Host.


Symantec/Fifth Generation Systems DiskLock 2.0
----------------------------------------------

You must use the Special Keyboard Handler when using Disklock 2.0
on a pcANYWHERE Host. Once you are connected to the Host, you
will have to press a key to get the DiskLock login display.



              CHANGES SINCE THE INITIAL RELEASE
              ---------------------------------

- Corrects slow re-connection time when connecting through
  routers.
- Resolves issues caused by consecutively connecting to
  a Novell Connection Services (NASI) port.
- Corrects AWSEND transfer problems with Netware Connect.
- Corrects FONT downloading issues. 
- Allows you to specify from the command line the host you would
  want to connect to through Gateway.  
    Example: aw /o:r /m:d /n:"Gateway 1" /c:"Host PC"
- Corrects login problems to a Lan Server while Drive Mapping is
  enabled. 
- Corrects issues with Shiva setups. 
- Corrects Online Service printing issues. 
- Corrects the issue of incorrectly transferring database-like
  files. 
- Corrects lock-ups seen when using Novell Netware VLMs with
  Drive Mapping enabled.
- $Result/$Error now work correctly when using the Script
  language.
- Corrects the issue of the screen displaying garbled characters
  when connecting to a VT100 Terminal. 
- Corrects the issue of the host not logging dropped connections.
- Works with 3com Net Modem pc Card by utilizing shared IRQ
  support.
  ** To enable you must add the following to the aw.ini file:
        ShareIRQ=1 
- Corrects issue of remote video going blank upon connection with
  some European video cards.
- Fixed cache overrun problem when connecting to pcANYWHERE32 7.5
  via serial connection. 
- Corrects garbled character issue when using remote printing. 
- Added "host_name" command line switch that adds the host name
  to the dial directory specified by a /N command for command-
  line remote control operation.

