SYMANTEC--PETER NORTON GROUP

README.TXT--March 24, 1995
Copyright 1995 Symantec Corp.  All Rights Reserved.

Release Notes
Norton pcANYWHERE for Windows
Version 2.0
-------------------------------------------------------------------------------
-  The TCP/IP connection type does not support gateways, as the gateway is a
   DOS program and TCP/IP for pcANYWHERE 2.0 only works under windows.

-  The TCP/IP connection type allows users to insert the host's IP address for
   the Host Computer Name.  Updating the host list is not necessary.

-  Users with Novell DOS 7.0 should update their VIPX.386 file with the latest
   version from Novell dated May 19, 1994 or later.

-  Users who have Windows 3.1 with VIPX.386 dated March 10, 1992 should
   upgrade to a newer version.  The old version causes machines to reboot if
   an IPX host is waiting while exiting Windows.

-  When running the DOS Host TSR at over 9600 Baud in Windows you must add
   device=aw_vcd.386 to the [386Enh] section in the SYSTEM.INI replacing
   device=*vcd.

-  For the SessOpr Remote Send and SessOpr Host Send script commands, the
   first string parameter contains the source file name only. If you wish to
   specify the optional destination file name, a second string parameter
   is required.  The script manual states that both file names are to be
   included in a single string parameter.

-  Sessopr Host commands will not work when running with PCAW Host DOS
   TSR. A possible work around would be to run the AWSEND.EXE program
   as the command to execute after connection. This program is available on the
   Symantec BBS.   You should only use AWSEND.EXE if you are running the DOS
   Host TSR.

-  In the scripting language, an  ON ERROR statement should only be followed
   by a GOTO or a GOSUB statement.

-  Printing remotely from a Host DOS Box requires that the Host DOS TSR be
   loaded.

-  Drive mapping when DOS Host TSR is loaded. You may see network drives on
   the available drive list that are already mapped to network drives and are
   not available.

-  When running the DOS TSR, the Command to Execute After Connect function
   will not work unless you are using the -m=w (Wait for a call mode).

-  Remote operation setting: Use Local Fonts, is defaulted to ON.  If  char's
   don't display correctly on the remote or the display refresh is slow, the
   setting should be changed  to OFF.

-  If you are having problems finding the remote drives in your drive windows
   (Microsoft's File Manager, Symantec's Norton Desktop for Windows Drive
   Window or any other type of  drive/directory/file viewer) or are having a
   problem with any type of file operation on the remotely mapped drives try
   one of the following steps to rectify the situation:
   1.  Make the drive window the active window and press F5.  This will cause
        a drive refresh to occur.  This should fix most of the problems.
   2.  If the problems still persist, then select your O/S option for Connect
        Network Drive or Disconnect Network Drive.  Once the dialog box
        appears, select the cancel button.  This will cause a refresh of all
        of the drives.

-  After an administrator install, to avoid possible 'sharing violation'
   warnings, mark AWMODEM.MD6 as sharable.

-  With OLE2 support being improved, the manual setup of OLE2 in section A-21
   is no longer necessary.  Now REGEDIT is automatically updated to run
   pcANYWHERE through OLE.

-  The manual states on page A-22, CallOnlSvc, to use:
       iStatus=winaw.callhost(0, "CompuServe")

   it should state:
       iStatus=winaw.callonlsvc(0, "CompuServe")

-  Between builds 345 and 347 of Windows95, we have noticed an instability
   in NetBIOS connections.


