pcANYWHERE for Windows 3.1 Windows 3.11                    Version 2.0
Copyright 1997 Symantec Corp.  All Rights Reserved.           7/14/97

======================================================================
		 Thank you for choosing pcANYWHERE

If you experience problems with pcANYWHERE, please check the manual
and this document for any information that may pertain to your problem.
If this information does not help, you can call Symantec Technical
Support at (541) 465-8430. We also provide a support Bulletin Board at
(541) 484-6669. CompuServe subscribers can contact Symantec Technical
Support in the Symantec forum (GO SYMANTEC).

======================================================================

This file includes additions and changes to the printed manual. It
also includes important upgrade, trouble-shooting and compatibility
information.

Please read this information before using pcANYWHERE.
======================================================================

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

Novell Netware

   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.

Windows 95

   To improve performance in Microsoft Windows 95, you can disable the
   exploding window affect by following these steps:

     Run REGEDIT.EXE;

     Choose HKEY_CURRENT_USER/CONTROL PANEL/DESKTOP/WINDOWMETRICS;

     Add a string for "MinAnimate", and give it a value of 0;

     Restart the machine. 


   When using pcANYWHERE under Windows 95, you may see an error message:

	"SYMEVNT1.DLL and SYMEVNT.386 DO NOT MATCH." 
	
   To correct this problem, copy the files, SYMEVNT1.DLL, SYMEVNT.386, 
   and S32EVNT1.DLL from your Windows\System directory, to your 
   Program Files\Symantec directory. (Choose "YES" to replace existing 
   files when prompted.)


   The pcANYWHERE Gateway is not supported on Windows 95.

ADDITIONS & CORRECTIONS TO THE MANUAL
-------------------------------------

Gateways

   SPX and TCP/IP connection types are not supported by the pcANYWHERE 
   Gateway. 


TCP/IP Addresses

   The Host's TCP/IP address may be used as the Host Computer Name when
   connecting over TCP/IP.

Scripts

   The manual gives the wrong syntax for the SessOpr Host Send and 
   SessOpr Remote Send commands. The commands take up to two string
   parameters, not one as the manual indicates. The first parameter is 
   the name of the file to be sent, and the optional second parameter
   is the name of the destination file.

       SessOpr Host Send <file to send> [filename at destination]


   To use the Sessopr Host commands when the Host is in DOS (using the 
   Host DOS TSR), you must specify AWSEND.EXE as the Command to Execute 
   After Connect (in Caller Information). AWSEND.EXE is part of 
   pcANYWHERE for DOS, and is available on the Symantec BBS.

   The ON ERROR script command, should only use the GOTO command or 
   GOSUB command. ex: On Error GoSub @errmsg

DOS Host TSR

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

OLE
   The manual setup of OLE 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")

Gateway

   Gateway parity configuration is configured on the Remote side, not 
   the Host side.

Confirmations

   To disable the "Cancel pcANYWHERE?" message box, add the following
   entry to the [pcANYWHERE] section of the PCAW.INI file.

	NoConfirmExit=1       

TROUBLESHOOTING
---------------

DOS Host TSR

   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.

Remote Printing

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

Drive Mapping

   When using Drive Mapping with the DOS Host TSR loaded, you may see 
   network drives in the list of Available Drives (that is, drives that 
   are already mapped to network drives, are are NOT available). 

   If you are having problems finding the remote drives in your drive 
   windows (for example, Microsoft's File Manager),  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. You may just need to refresh the drive window display. In File 
      Manager, press F5 to refresh the drive window.

   2. If the problem persists, 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.

Use Local Fonts

   To maximize performance, Use Local Fonts defaults to ON. If characters
   are not displaying properly on your remote, or the display refresh is
   slow, change the setting to OFF.

   Turning off Use Local Fonts will also correct font problems with 
   international versions of Windows.

Network Installations

   After an administrator install, to avoid possible 'sharing violation'
   warnings, mark MODEMS.AW8 as sharable.


   If you experience problems connecting to a pcANYWHERE 2.0 Host on a 
   network installation of Windows 3.1 using Novell NetWare, where the 
   Remote only displays the icons and the background image is all black, 
   you must do the following:
   
   In the "[Boot]" section of the System.ini file on the Host side, look 
   for a line which says "DISPLAY.DRV=xxxxx" ("xxxxx" value will be 
   "VGA.DRV" or any valid video driver.) Edit this line so it now reads 
   "DISPLAY.DRV=AWDSP.DRV". Below this line add an extra line which says 
   "DISPLA2.DRV=xxxxx", where xxxxx is what was in the original 
   "DISPLAY.DRV=" line.
   
   In your local Windows directory, copy AWDSP.DLL to AWDSP.DRV. (Note: 
   Normally awdsp.dll is installed in the \windows\system directory, but 
   on a network install of Windows 3.1 on a Novell client it will be 
   installed in just the \windows directory.)
	
Video Cards

   If you have a #9GXE video card make sure you have 
  
     TimerCriticalSection=10000

   in the [386Enh] section in the SYSTEM.INI.


   If you are using 16-bit color mode and are seeing problems with remote
   colors, add the following line to the PCAW.INI file.

	ColorFormat=555      ;This goes in the [pcANYWHERE] section


   If you are seeing color problems on remote PC, add the following in the
   [pcAnywhere] section of the PCAW.INI file.

	VIDEO1=256           ;This value can be set in the range of 
			     ;16 thru 512.

International

   Under Windows 95, if "Require Login Names for Callers" is set and then 
   later switched to "Not required", all passwords which have double-byte 
   characters must be re-entered without double-byte characters.

   The Remote's IME is not currently disabled when in session, therefore 
   there will be two IME's visible on the Remote's display.  It is 
   recommended that the Remote's IME remain in Roman Character mode and 
   any switching of modes be directed to the Host's IME.









