pcANYWHERE32 for Windows 95 and Windows NT                 Version 7.5
Copyright 1996 Symantec Corp.  All Rights Reserved.            6/11/96

======================================================================
                 Thank you for choosing pcANYWHERE32

If you experience problems with pcANYWHERE32, 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.

======================================================================
COMPETITIVE UPGRADE OVERVIEW
======================================================================

* pcANYWHERE32 Upgrade will perform a competitive upgrade from a 
  variety of competitor remote control products and previous versions 
  of pcANYWHERE.  If a competive product is found on the user's system 
  or you have the original installation disks, then installation will 
  proceed.
	
  Specifically, pcANYWHERE32 Upgrade will trade-up from the following 
  product versions:
	
	* Traveling Software Laplink for Windows v6.0x
	* Traveling Software Laplink for DOS v5
	* pcANYWHERE for Windows v1.0x, v2.0x
	* pcANYWHERE for DOS v4.5, v5.0x 
	* Stac/Ocean Isle ReachOut v4.0x v5.0x
	* Microcom Carbon Copy for Windows v2.0x, v3.0x
	* Microcom Carbon Copy for DOS, v6.x

NOTE:	Installation of pcANYWHERE Upgrade will not trade up the trial 
	version of pcANYWHERE32 (30 Day Version).

======================================================================
INSTALLATION
======================================================================

NETWORK INSTALLATIONS

* Administrators creating a pcANYWHERE32 NT workstation installation 
  from a network drive need to alter the "Add Be A Host" template 
  before workstation users begin to create Host session items. The 
  default template setting "Run as a Service" should be unchecked if 
  Host items files are stored on the network. Host files stored on a
  network drives will not launch if "Run as a Service" is checked.

* In order to access Administrator options, a workstation install must
  be performed on the Administrator's machine. If the /A option is
  invoked without first installing a workstation, you will not be
  prompted for an Administrator password.

* If Host or caller files are located on a network drive, you will not
  have access to the "Launch Host at startup" feature.

WINDOWS NT
----------

* Because Windows NT allows varying access to protected files and
  services, installing and uninstalling pcANYWHERE32 should be
  performed by a user with Administrator privileges.

* Windows NT 3.51 with Service Pack #4

  To properly install pcANYWHERE32, use the following steps:

  1. In the SYSTEM32 sub-folder of your Windows NT folder, rename
     SMSS.EXE to SMSS.OLD.
  2. Copy SMSS.EXE located on "pcANYWHERE32 Disk 1" to the SYSTEM32
     sub-folder.
  3. Restart Windows NT.
  4. Run pcANYWHERE32 Setup program.

  For more information, contact Microsoft Windows NT product support
  or look for article #Q148485 at http://www.Microsoft.com/kb.

======================================================================
COMPATIBILITY
======================================================================

OLDER VERSIONS OF pcANYWHERE
----------------------------

* pcANYWHERE 2.0x TCP/IP Hosts can be made visible to a pcANYWHERE32
  Remote browse list in two different ways:

  1. Specify the Host IP explicitly on the Remote TCP/IP browse list,
     located under Application Options, or

  2. Enhance the older pcANYWHERE 2.0 Host with a file (AWCMTCP.DLL),
     available on the Symantec BBS or Symantec forum on CompuServe.

* Simultaneous File Transfer and Remote Control is only supported
  between pcANYWHERE 7.5 or later Hosts and Remotes.

* If you experience slow performance when connected to a pcANYWHERE 
  7.5 Host with an older version of pcANYWHERE (5.0 for DOS or 2.0 for
  Windows) try turning off the Remote's cache file.

* Executing an AutoXfer(tm) procedure with a previous version of 
  pcANYWHERE will "End session when finished" even when this feature 
  is not enabled.

* pcANYWHERE Access Server

  To perform file transfers when connecting to a pcANYWHERE Access
  Server Host, click "Remote Control" and start the file transfer
  after the connection has been made.

* Configuration Conversion

  When converting pcANYWHERE configuration files under Windows NT,
  please note that all newly created session items with IPX as the
  connection type will be changed to SPX.

  The master password from a previous installation of pcANYWHERE 2.0x
  should be disabled before converting files.

  Data files configured as "Shared" under a previous Administrator
  installation of pcANYWHERE cannot be converted to pcANYWHERE32.

WINDOWS NT
----------

* When connecting to a pcANYWHERE32 Host under NT, the Host user must
  already be logged-in before a successful AutoXfer can take place.

* Owners of previous versions of pcANYWHERE may now take advantage of
  the pcANYWHERE32 feature "Send CTRL-ALT-DEL".  Pressing CTRL-ALT-D
  while connected to a pcANYWHERE32 Host will emulate this feature.

* For optimal performance under Windows NT 3.51, it is recommended
  that pcANYWHERE32 NT Hosts are configured to "Run as a Service".

* Those who see a performance decrease when opening a DOS window on a
  pcANYWHERE32 NT Host can improve the speed by altering NT tasking,
  located under System in the Control Panel. The default setting
  should be changed from "Best Foreground Application Response Time",
  to "Foreground and Background tasks equally responsive".

* If you have problems with your remote keyboard (such as non-ALT keys
  selecting menus) when connected to a pcANYWHERE32 NT Host, try 
  individually pressing the ESC, Shift, ALT, or CTRL keys.


NOVELL NETWARE
--------------

* Multiple sessions using IPX connections are not currently supported
  under Microsoft Windows 95.

* Windows NT

  To enable Remote File Transfer support with NetWare volumes, your
  Novell NetWare password should be the same as your Windows NT
  password.

  pcANYWHERE32 SPX Host lists are supported under Windows NT only if
  Novell Netware client for Windows NT is installed.

  SPX Host objects are currently not supported with the Novell NetWare
  Client32 for Windows NT installed. This also applies to
  pcANYWHERE32 Gateways where SPX is the inbound device type.


MULTIPROCESSOR COMPUTERS
------------------------

pcANYWHERE32 has been tested on the following multiprocessor
computers:

Micron Millennia SMP Power Server (2 processors)
Hewlett Packard Netserver (4 processors)
Hewlett Packard Vectra XU  (2 processors)

If you are planning to use pcANYWHERE on another multiprocessor
computer, Symantec recommends that you test pcANYWHERE on that
computer before using it in a production environment.


CAPI
----

AVM/A1 cards running the North American CAPI drivers (Windows 95) do
not support channel bonding. Checking "Attempt Channel Bonding" in
pcANYWHERE32 may produce unpredictable results.

Contact AVM for information on updated drivers.

If you plan to use channel bonding, make sure "attempt channel bonding" 
is enabled on the pcANYWHERE32 host.


VIDEO ADAPTERS AND GRAPHICS ACCELERATORS
----------------------------------------

If you experience problems with a 3D graphics accelerator video
adapter, you may need to disable some of the adapter's advanced
accelerator features.

Testing with the Matrox Millenium indicates that the PowerGDI
Acceleration option should be disabled when the adapter is used with 
a pcANYWHERE32 Host.


MODEMS
------

* If you experience connection problems using modems under WIN95, try
  lowering the default FIFO buffer settings, or changing the default
  data rate. These options are found in the modem's Connection
  property page, under the headings "Port Settings" and "Maximum
  Speed".

* Some modems and direct-connect serial cables do not permit the DSR
  (Data Set Ready) signal to be set "high". In these cases, it is
  necessary to set a registry entry to ignore the state of the DSR
  signal. The key is:

 HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\pcANYWHERE\CurrentVersion\System

  Create a new DWORD entry named SerialIgnoreDSR and set its value to
  1.


SERIAL PORT HARDWARE
--------------------

Many older and low-end PC's use 8250 UART chips for their serial
ports. These chips do not adequately support large amounts of data at
high data rates. To get the best performance from pcANYWHERE and other
communication applications, you should use a serial I/O card with a
16550A UART or similar chip. These are available at many computer
stores.


TCP/IP HOST NAMES
-----------------

When specifying TCP/IP Host names to connect to, lowercase extended
ASCII characters (e.g. "ö") cannot be used, or the name will not
appear on the list of available Hosts.


WinFAX AND pcANYWHERE HOSTS
---------------------------

In order for WinFax to give control of an incoming telephone call to a
waiting pcANYWHERE32 Host, the WinFax feature "call discrimination"
must be enabled. For more information, consult your WinFax User
Manual.

If you are using Delrina's Wincomm Suite follow the procedure below:

1. In Winfax, click on "Setup" drop down menu and then click on
   "Receive".
2. Enable "Call discrimination"
3. Enable "Automatically answer incoming calls"
4. Click on OK.

If you are using Delrina's Winfax 7.0 standalone, you will need to
modify the Windows Registry. If you do not know how to do this, check
your Windows 95 or Windows NT documentation.

1. Run REGEDIT and edit the key:

     HKEY_CURRENT_USER\Software\Delrina\Commsuite\7.0\Modems\Modem#

2. Set "DataCapable" to 1.
3. Set "CallDiscriminationSupport" to one of the values below:

          Value       Description
            1         FAE...ATO  (recommended value)
            2         FAA...ATO
            3         FAE
            4         FAA
     The following values are NOT supported in the October 31,1995
     release of WinFAX but are in later releases:
            9         FCLASS=1 FAE...ATO
           10         FCLASS=2 FAA...ATO
           11         FCLASS=1 FAE
           12         FCLASS=2 FAA

4. Close REGEDIT.
5. In Winfax, click on "Setup" drop down menu and then click on
    "Receive".
6. Enable "Automatically answer incoming calls".
7. Click on OK.

Check the TELEPHON.INI that is in the WINDOWS directory. Make sure
that the [HandoffPriorities] section is as follows:

        [HandoffPriorities]
        RequestMakeCall=DIALER.EXE
        datamodem=wfxmod32.exe,
        unknown=
        g3fax=wfxmod32.exe,

Run WinFAX or the Commbar utility. Start the pcANYWHERE32 Host. WinFAX
7.0 will answer the call. If it is a FAX call, WinFAX 7.0 will handle
it. If it is a data call, WinFAX 7.0 will hand the call off to
pcANYWHERE32.

======================================================================
CORRECTIONS AND ADDITIONS
======================================================================

CALLER SECURITY OPTIONS
-----------------------

* Under Security Options, the feature "Prompt to confirm connection"
  will only function for those callers that are not SuperUsers (that 
  is, those who have individual caller privileges defined).

SCRIPT LANGUAGE
---------------

* The script command "LOAD CONFIG" is no longer supported. Use the
  commands "LOAD ONLSVCINFO" or "LOAD HOSTINFO" instead.

* Scripts may be executed from the command line by using the following
  syntax:

    AWREM32.EXE <scriptname>

  The <scriptname> must include the path, and the extension ".SCR".

OLE
---

* pcANYWHERE Host objects do not support OLE when they are "Run as a
  service."  Disable this feature when launching Host objects embedded
  within other applications or run from the file manager.

* The OLE service must be installed and activated under Windows NT
  3.51 before installing pcANYWHERE32.


REMOTE NETWORKING
-----------------

After successfully configuring a Remote Networking item, a
pcANYWHERE32 Remote Control item named "RAS" is created in the Remote
Control window. This item is not to be used for your dial-up
networking connections. Click "Remote Networking" and choose the
appropriate item.


DRIVE SECURITY
--------------

* Do not restrict access to the pcANYWHERE installation directory by
  setting callers' security privileges to "No Access". Callers must be
  given read-access to these files.

* Drive Security is not supported by pcANYWHERE32 under Windows NT. If
  you need security, use an NTFS partition and allocate rights to
  users with the Administrative Tools included in NT.


TCP/IP HOST BROWSE LIST
-----------------------

The pcANYWHERE32 TCP/IP driver now supports browsing for Hosts at
connection time. While the default configuration of this feature will
work fine for most users, you may need to make some adjustments on
your system. To do this, you will need to use the Windows Registry
Editor. See your Windows documentation for more information.

The following Registry items affect the ability to browse and connect
to pcANYWHERE32 TCP/IP Hosts:

TCPIPBrowseDelay -

Allows the user to set the delay used when creating the Remote's
browse list. For a RAS connection, start with a setting of 11. If the
complete Host list is not received over a WAN connection, start this
value at 1 and increase until the entire Host list is displayed.

DisplayInHostList -

This item can be altered for pcANYWHERE32 Hosts that do not wish to
appear in a Remote's browse list, when the Remote is scanning the
network. The default for this setting is 1. To keep the Host from
being displayed on a browse list, assign the registry key a value of
zero.

TCPIPConnectIfUnknown -

Use this feature if your Internet service provider filters directed 
packets. Test this by specifying a known pcANYWHERE32 Host
in the TCP/IP Host list. If the status remains "unknown", set the
DWORD to a value other than zero. (Connecting to a Host whose status
is known, but is actually busy, will correctly result in a blank
screen).

To add or modify these Registry entries, use the following steps:

1. Run the Registry Editor (REGEDIT.EXE)
2. Edit the key:

 HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\pcANYWHERE\CurrentVersion\System

3. Create or edit the DWORD value with the TCP/IP browse option name.
4. Assign the desired value to the entry.

TCP/IP FIREWALL SECURITY
------------------------

Network administrators may configure their network security to allow 
TCP/IP connections over the Internet.  pcANYWHERE32 uses two ports, 
5631 and 5632, which must be left open by the system administrator 
to allow connections through the firewall.

SCHEDULING AutoXfer(tm)
-----------------------

An AutoXfer can be scheduled to run whenever is convenient for you.
Follow these steps to create an unattended file transfer:

1. Create an AutoXfer procedure for a Remote Control item. See your
   manual for a complete description of this process. The procedure
   should have the "End session when finished" option selected.

2. Using a scheduling program (for example the Microsoft System Agent
   which is part of the Windows 95 Plus! pack, or the Norton Program
   Scheduler), schedule the Remote Control item you used in step one.
   The item will be a file with the extension .CHF (for example,
   DIRECT.CHF). By default, pcANYWHERE creates items in the DATA
   folder in the folder pcANYWHERE is installed in (e.g.
   C:\Program Files\pcANYWHERE\data).

