SYMANTEC--PETER NORTON GROUP

README.TXT--August 1, 1995
Copyright 1995 Symantec Corp.  All Rights Reserved.

Release Notes
Norton pcANYWHERE for Windows
Version 2.0 pcANYWHERE Fixes
-----------------------------------------------------------------------------
For Windows95 users: Start your machine and press the F8 key.  Then go into
Command Prompt only (DOS) mode.  You may then continue with the following 
instructions.  Restart your computer when you are through.

Execute 20UP_B.EXE to view files required to upgrade pcANYWHERE 2.0.

ADMINISTRATOR INSTALL
Copy all files into your pcANYWHERE 2.0 directory on your network.
          

WORKSTATION INSTALL
The following files need to be copied to the \windows\system directory: 
        AWDSP.DLL
        SYMEVNT.386
        SYMEVNT1.DLL
        VPCAW.386

STANDARD INSTALL
Copy all files into your pcANYWHERE 2.0 directory, except for the
following files which must be copied to your \windows\system directory:

        AWDSP.DLL
        SYMEVNT.386
        SYMEVNT1.DLL
        VPCAW.386

WINDOWS WORKSTATION
If you are running under a shared network Windows installation,  
copy all files into your pcANYWHERE 2.0 directory, except for 
the following files which must be copied to the shared network Windows 
directory:

        AWDSP.DLL
        SYMEVNT.386
        SYMEVNT1.DLL
        VPCAW.386

-------------------------------------------------------------------------------
The following fixes were contained in 20UP_A.EXE

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

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


-------------------------------------------------------------------------------
The following fixes are new to 20UP_B.EXE

- If the host not re-booting if 'Reboot After Session' is set to Yes- and you
  end your session by closing Windows instead of using the online menu.

- PrinterFlushTimeout is not staying at a value of 30, causing remote printing
  to be slow.
 
- File transfer problems when using NASI have been fixed

- A message is displayed to a new remote user trying to logon after a previous
  session had failed, while the host has not checked "Allow any password on
  reconnect." 

- pcANYWHERE will automatically set a default value of 30 when printing remotely
  without having to change the AW.INI file.

- We now allow the host name to be the network name of the remote user when 
  using Banyan Vines or any other network.

  The following parameter and/or section must be added to the PCAW.INI file:
        [HOST]
        HostComputerNameSelection=1
  If this .INI entry is set to 0, the naming procedure will not be modified.

- Fixed problems of connecting in terminal mode where the high ascii 
  characters do not display correctly on the title bar.  

- Fixed the issue of terminating a session by double clicking the terminal menu
  instead of the online menu.
 
- Fixes intermittent hangs during network connections not only related to file 
  transfers.

- Will now display Server, Service, and Port when choosing the "Select When 
  Connecting" option under the NASI/NCSI device type.

- Fixes to the following scripting issues:
  1) using the dial session command without having a waiting host to complete 
     the connection whereupon the script ends.
  2) disconnecting during file transfer causing the script to end.
  3) corrects problems when using ON ERROR




