

                  Norton pcANYWHERE 5.0 for DOS

                          March 4, 1994


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 two sections. The first contains corrections and
additions to the printed manual. The second section contains
some compatibility information that you may need to use
pcANYWHERE with some other products.

For technical assistance with pcANYWHERE, you can contact
Symantec Technical Support at (503) 465-8430, or through the
Symantec Bulletin Board at (503) 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).


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



                          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.

When doing file transfers across a network, it is recommended
that you disable the network broadcast function (run the command
"CASTOFF ALL" before starting pcANYWHERE). Pressing CTRL+ENTER
on the Remote will not clear the broadcast message on the Host
machine.



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.



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.



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.


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