PCA WIN 1.0 FAQ

PCA WIN 1.0 FAQ. Last Update 11/01/94

I)    Introducing pcAnywhere
      1.1: What is pcAnywhere?
      1.2: What kind of computer do I need to install pcAnywhere?

II)   Installation Problems
      2.1: How do I install PCA?
      2.2: After installing pcAnywhere for DOS, Windows won't start.
      2.3: What kind of changes does PCA make to my System.ini files?
      2.4: How do I uninstall PCA?
      2.5: Can I convert my configuration files from a previous version into
           5.0?
      2.6: Windows for Workgroups

III)  Booting the System Clean
      3.1: What do you mean by booting clean?

IV)   Making the Connection
      4.1: Symantec test Host
      4.2: My modem works with other communication software, why not PCA?
      4.3: I can't connect / I get disconnected
      4.4: Can I connect to a different version of PCA?
      4.5: Can I connect to a PCA Host using another program like ProComm or
           Qmodem?
      4.6: Can I connect to another program like Procomm or Qmodem using PCA as
           the remote?
      4.7: Can I connect to a PCA Host from a Macintosh?

V)    PCA Compatibility: Modems/Video/Software/Terminals
      5.1: What if my modem is not on the modem list?
      5.2: Can PCA and my Fax software share the modem?
      5.3: Can I run PCA and other Comm software at the same time?
      5.4: Can I run PCA on an OS/2 system?
      5.5: Can I run PCA under Windows NT?
      5.6: How do I setup PCA to work with my Terminal Emulation?
      5.7: What are Keyboard Handlers?
      5.8: Resolving display problems
      5.9: Resolving font Problems
      5.10: COMPAQ Video Drivers

VI)   Networks and PCA
      6.1: What networks are supported by PCA?
      6.2: How do I set up PCA 5.0 to work with Netware Connect?
      6.3: Can I run PCA with Novell Version 4.X?

VII)  Scripting
      7.1: Why won't my script work?

VIII) Speed and Performance Issues
      8.1: How can I speed up PCA?
      8.2: What is High (or Upper) Memory?
      8.3: How do I load the Host into High (or Upper) memory?

IX)   PCA 5.0 Command Line Reference
      9.1: AW.EXE Parameters
      9.2: AW_HOST.EXE Parameters
      9.3: AW_GATE.EXE Parameters
      9.4: AWLOGOFF & AWSEND Parameters

X)    Symantec Support Services
      10.1: PCA Telephone Support
      10.2: Online Support
      10.3: User to User Forum
      10.4: Faxback Service

________________________________________________________________


I) Introducing pcAnywhere....
===============================


[1.1: What is pcAnywhere?]
PcAnywhere, or PCA for short, is a remote computing software.  It allows you to
connect to one machine (the Host) from another (the Remote) and control it as if
actually sitting in front of it.

This connection is achieved through either a network, or via modem and phone
lines. You can call your home computer from anywhere in the world, or use PCA to
connect to Bulletin Board Services or CompuServe

................................

[1.2: What kind of computer do I need to install pcAnywhere?]
IBM PC, PS/2 or 100% compatible
2 MB of RAM (3 MB or More recommended)
5 MB free space
DOS 3.1 or Higher
Microsoft or compatible mouse recommended
Windows 3.0 or 3.1

_________________________________________________________


II) Installation Problems
============================

[2.1: How do I install PCA?]
As with the installation of any software, it is highly recommended that you
install to a clean system, clean refers to a computer loading only the TSRs and
device drivers necessary to run Windows. See Section III.

Standalone Installation:
Type A:\INSTALL or B:\INSTALL to start a standalone installation.
During this installation, pcANYWHERE will copy your SYSTEM.INI, WIN.INI and
AUTOEXEC.BAT to the pcANYWHERE for Windows directory as SYSTEM.IN_, WIN.IN_ and
AUTOEXEC.BA_.  These are copies of your original files, do not delete them. 
Depending on how many times you re-install pcANYWHERE for Windows, the file
extension numbers will increment by one. You will need these files for
uninstalling pcANYWHERE for Windows.
Make sure display.drv=, keyboard.drv= and mouse.drv= do not contain paths to the
device's drivers.  All device drivers Windows uses should be located in the
Windows SYSTEM directory.  If you have installed other Windows communication
packages, like Carbon Copy for Windows, please restore your SYSTEM.INI to the
way it was before Carbon Copy for Windows was installed.

Network Installation:
Type A:\INSTALL /A or B:\INSTALL /A to start a network installation.  This
installation will not require you to reboot your computer at the end of the
installation.  This installation only copies the necessary files to your network
drive. Users should then run INSTALL.EXE from the pcANYWHERE for Windows network
directory.

Workstation Installation:
Type netpath\INSTALL to start the workstation installation from the pcANYWHERE
for Windows network directory.  The program will start installing the necessary
program files to your Windows SYSTEM directory.  At the end of the installation
you can either Exit to DOS, Restart Windows, or Reboot.  If you have instructed
your computer to be a Host, it is best you reboot your computer.

................................

[2.2: After I install PCA, Windows wont start]
You probably have a TSR loading that corrupted the install of
pcAnywhere.

First of all, uninstall PCA. You can do this at the DOS prompt by changing to
the WINAW directory and typing Uninstall /U. After that you should be able to
enter Windows again.

Then boot your system CLEAN (See section III).

................................

[2.3: What kind of changes does PCA make to my System.ini files?]
This details what the Norton pcANYWHERE Installation adds to your SYSTEM.INI,
WIN.INI and AUTOEXEC.BAT.  This also includes special information about the
pcANYWHERE Information File, PCAW.INI, and installations.  It is highly
recommended that you review the Norton pcANYWHERE for Windows manual, Chapter 1
"Installation" and the README.TXT file found in the pcANYWHERE directory you
have installed to.

WIN.INI:
[windows]
load=path\winhost.exe   This line is added if the Auto Start Host option is
checked in the Configure Host Operation screen.

NOTES:
pcANYWHERE for Windows will append this to the end of your load line.  It is
best that you move this to the beginning of your load line before other
applications start.
Replace path with the complete path to the pcANYWHERE for Windows program files.

SYSTEM.INI:

[boot]
mouse.drv=original.drv      Your original driver is replaced with aw5mouse.drv.
keyboard.drv=original.drv   Your original driver is replaced with aw5kbd.drv,
                            aw5kbdhp.drv or aw5kbdol.drv. See KEYBOARD NOTES.
display.drv=original.drv    Your original driver is replaced with aw5ega.drv, 
                            aw5vgabw.drv, aw5vga.drv or aw5xga.drv. See DISPLAY 
                            NOTES.

[386Enh]
network=vipx.386          This device must be removed if you are using Windows
                          3.0. See NOVELL NOTES.
device=vpcaw5.386         This device is added to the [386enh] section.
device=vcd.386            This device driver is replaced with aw5vcd.386. See
                          VCD NOTES.
TimerCriticalSection=500  This option is added to the [386enh] section.

KEYBOARD NOTES:
The aw5kbdhp.drv is used for Hewlett Packard keyboard drivers.  If your computer
uses a Hewlett Packard keyboard driver, please use this driver for pcANYWHERE.
The aw5kbdol.drv is used for the Olivetti keyboard drivers.  If your computer
uses an Olivetti keyboard driver, please use this driver for pcANYWHERE.  The
aw5kbd.drv is used for all other keyboard drivers.

DISPLAY NOTES:
The aw5ega.drv is used for EGA resolutions only.  If you are using EGA, please
use this driver.
The aw5vgabw.drv is used for 640x480, 800x600 and 1024x768 resolutions in black
and white only.  If you are using a black and white driver in any of these three
video modes, please use this driver.
The aw5vga.drv is used for 640x480, 800x600 and 1024x768 resolutions with 16
colors only.  If you are using a 16 color driver in any of these three video
modes, please use this driver.
The aw5xga.drv is used for 640x480, 800x600 and 1024x768 resolutions with 256
colors only.  If you are using a 256 color driver in any of these three video
modes, please use this driver.

VCD NOTES:
In some cases you may have a different vcd.386 driver installed.

NOVELL NOTES:
If you are using Windows 3.0 and a Novell Network and you have configured
Windows to be used with a network, you will need to edit your SYSTEM.INI and
either remove the vipx.386 driver from the network line or replace it with the
vipx.386 driver that comes with Windows 3.1.  Normally the network line appears
as follows:

[386Enh]
network=*vnetbios,vnetware.386 ,vipx.386


PCAW.INI:

[pcANYWHERE]
mouse=aworgmse.drv      See MOUSE NOTES.
keyboard=original.drv   Your original driver from the SYSTEM.INI is placed here 
                        in the PCAW.INI file.
display=original.drv    Your original driver from the SYSTEM.INI is placed here 
                        in the PCAW.INI file.
UserID=

[font]
logicalfonts=0  Please see README.TXT in your pcANYWHERE for Windows directory.

[uninstall]
mouse.drv=original.drv  Your original driver is placed here in the PCAW.INI file
                        for use when uninstalling pcANYWHERE.
device=vcd.386          Your original device is placed here in the PCAW.INI file
                        for use when uninstalling pcANYWHERE.

[winsize]   These default settings for the size of your pcANYWHERE for Windows   
            Application.
left=151
top=243
width=520
height=417

MOUSE NOTES:
If your original mouse driver is mouse.drv, the pcANYWHERE installation will
copy your mouse.drv to aworgmse.drv.  The PCAW.INI file then references this
driver instead.  The reason for this is that the Windows environment does not
allow for the mouse.drv driver to be located in an INI other than the
SYSTEM.INI.  If your mouse driver is named anything else, it will be used for
the mouse= line under the [pcANYWHERE] section of the PCAW.INI.

AUTOEXEC.BAT:
path\aw5host -p=config_path -w=win_path -m=r    This line is added to your
                                                AUTOEXEC.BAT. See NOTES.

NOTES:
This is only added to your AUTOEXEC.BAT file if you checked the Allow remote
users to run full screen DOS applications during the installation.  If you are
using pcANYWHERE for Windows from the Network, please execute this command after
your network drivers have loaded.
Replace path with the complete path to your pcANYWHERE for Windows program
files.  This is only needed if you do not have the pcANYWHERE path specified in
your PATH statement.
Replace config_path with the complete path to your pcANYWHERE for Windows
configuration files.
Replace win_path with the complete path to your Windows program directory.

Editing the Configuration Files
Editing your WIN.INI, SYSTEM.INI, CONFIG.SYS and AUTOEXEC.BAT files can be done
easily from within the Windows environment.

To edit your DOS and Windows configuration files from Program Manager or Norton
Desktop for Windows:
1) Select Run from the File menu. The Run dialog box appears.
2) Type SYSEDIT.EXE in the Command Line field.
3) Press Enter. The System Configuration Editor will appear with your WIN.INI,
   SYSTEM.INI, CONFIG.SYS and AUTOEXEC.BAT file showing.
4) View or Edit your configuration files.

To exit the System Configuration Editor:
1) Double Click on the Control box in the upper left hand corner of the editor
   Window or select Exit from the File menu. The editor will automatically close 
   if no files were changed. If a file was changed, it will prompt you to save 
   or cancel the changes.

To edit your pcANYWHERE for Windows information file from Program Manager or
Norton Desktop for Windows:
1) Select Run from the File menu. The Run dialog box appears.
2) Type NOTEPAD win_path\PCAW.INI in the Command Line field.
   Replace win_path with the path to your Windows directory.
3) Press Enter. The Notepad application will appear with the PCAW.INI file
   showing.
4) View or Edit the pcANYWHERE for Windows information file.

To exit the Notepad application:
1) Double Click on the Control box in the upper left hand corner of the editor 
   Window or select Exit from the File menu. The application will automatically 
   close if the file was not changed. If the file was changed, it will prompt 
   you to save or cancel the changes.

................................

[2.4: How do I uninstall PCA?]
Type path\INSTALL /U to uninstall a pcANYWHERE installation.
When pcANYWHERE was installed, it stored your SYSTEM.INI, WIN.INI and
AUTOEXEC.BAT in the pcANYWHERE for Windows directory as SYSTEM.IN_, WIN.IN_ and
AUTOEXEC.BA_.  Depending on how many times you re-install pcANYWHERE for
Windows, the file extension numbers will increment by one. These files are used
by the pcANYWHERE for Windows uninstall program to restore your current
SYSTEM.INI, WIN.INI and AUTOEXEC.BAT.  The uninstall program will read each line
the installation program changed and replace the pcANYWHERE drivers with the
originals.

................................

[2.5: Can I convert my configuration files from a previous version into 1.0?]
Yes, see below.

IF YOU ARE RUNNING pcANYWHERE FOR WINDOWS RIGHT NOW, PLEASE QUIT OUT OF THE
PROGRAM, YOU MUST DO THIS BEFORE CONVERTING THE FILES.

1)  The first thing to do is to rename the configuration files in the pcANYWHERE 
for Windows subdirectory.

A typical command for this would be " REN C:\WINAW\AW*.??5    C:\WINAW\AW*.??9",
where WINAW is the subdirectory for pcANYWHERE for Windows.

The file specification for these files is AW*.??5.

2)  The next step is to copy all the pcANYWHERE for DOS configuration files to
the pcANYWHERE for Windows subdirectory.

A typical command for this would be " COPY C:\AW\AW*.??1  C:\WINAW ", where \AW
is the pcANYWHERE for DOS subdirectory, and \WINAW is the pcANYWHERE for Windows
subdirectory.

3)  After this, run pcANYWHERE for Windows and then the program will say
"Converting 4.5 Files".

You are done!

................................

[2.6: Windows for Workgroups
PCA for Windows should run fine with WFWG, but it is useful to know the
following:

You will need the latest version of SERIAL.386 from Microsoft, particularly if
you're running a pentium. The original SERIAL.386 file handles COM ports
incorrectly.

A recurring cause of problems with WFWG is a conflict with the video display
driver. Try using 8514 driver provided with WFW 3.11. You
should also download NEWVID.EXE from the PCAW library, copy it to your
windows\system directory and execute it. That contains the newest display
drivers for PCA WIN. If all else fails, use Windows 3.1 standard VGA drivers. 16
color.


____________________________________________________________


III) Booting the System Clean
===========================

[3.1: What do you mean by booting clean?]
As with the installation of any software, it is highly recommended that you
install to a clean system, clean refers to a computer loading only the TSRs and
device drivers necessary to run Windows. For example, your AUTOEXEC.BAT and
CONFIG.SYS may appear as follows:

CONFIG.SYS
device=himem.sys    This is required for Windows to start in Standard or 
                    Enhanced mode.
files=50            This is required for the Windows environment.
buffers=10          This is required for the Windows environment.
stacks=9,256        This is required for the Windows environment.

AUTOEXEC.BAT
path=c:\windows;c:\dos;
set temp=c:\temp    This is required for the Windows environment. See TEMP 
                    NOTES.

TEMP NOTES:
Please make sure not to set the TEMP directory variable to a RAM Drive or a
Network directory.  During the pcANYWHERE for Windows installation, we copy
several files to the TEMP directory, exit Windows and then restart Windows.  If
during this process the TEMP directory path is not maintained the pcANYWHERE for
Windows installation may fail.  Please set the TEMP directory to a
non-compressed drive, with more than 5 megabytes of space.
*Compressed drives include SuperStor, Stacker and Doublespace.

________________________________________________________________


IV) Making the Connection
=========================

pcANYWHERE works well with a variety of hardware and software.  However, some
combinations of memory resident software and/or hardware can hinder or impair
functionality.  The following is a list of common software and configurations
that are known to interfere with the operation of The Norton pcANYWHERE. For
testing purposes, please remove all TSR programs (see Section III) and check all
cable connections.

................................

[4.1: Symantec Test Host: A test Host is available at Symantec to test your
modem. ]
PCA DOS: 503-334-7315
PCA WIN: 503-334-7314

................................

[4.2: My modem works with other communication software, why not PCA?]
PCA is interrupt driven, most other communication software is not. See HARDWARE
CONFLICTS below.

................................

[4.3: I Can't Connect / I get disconnected!]
When I call the host machine it gives me three plus signs +++.
When I call the host machine the host gets an error 20 or an error 27.
When I call the host machine it disconnects after a few minutes or seconds.
When I call the host machine all I get is the pcANYWHERE Terminal bar on the
bottom of the screen.
My modem won't initialize.

These are all common problems and in 99% of the cases can be attributed to one
of the following:

-HARDWARE CONFLICTS:
pcANYWHERE is an interrupt driven program. This allows for greater speed but can
cause a problem if you are utilizing other equipment that is using the same
interrupt (IRQ). Standard communication ports are configured as follows:

COM1        Port address 3F8    IRQ=4
COM2        Port address 2F8    IRQ=3
COM3        Port address 3E8    IRQ=4
COM4        Port address 2E8    IRQ=3
IBM PS/2 uses  different port address for COM3 and COM4

Note:   COM1 & COM3 share an IRQ, as do COM2 & COM4

As you can see, there are only 2 interrupt levels for 4 COM ports. So, for
example, if you have your  internal modem on COM3: and a mouse on COM1:, they
will both be on the same interrupt and will cause  problems. Examples include
the modem not initializing, disconnects, or a black screen with the pcANYWHERE
Terminal bar on the bottom. If you are experiencing any of these problems,
please check your system's interrupts. Network interface cards (NIC), backup
devices, and sound cards can also pose potential hardware conflicts. A good
measure would be to remove as much hardware as possible prior to running
pcANYWHERE. Once you are confident that pcANYWHERE works, add additional
hardware until the conflict is duplicated.  A diagnostic utility package may
help in determining which interrupts are being used.  MSD (Microsoft
Diagnostics) which ships with DOS 6.X or with Windows may be of some help in
determining interrupts in your system. Type "MSD" at a DOS prompt, then choose Q
for IRQ status.

To set up a custom COM port in pcANYWHERE:
Use the Windows control panel to set the IRQ and Port Address. More information
on configuring custom com ports in Windows may be obtained in Faxback document
5508 (See section X).

pcANYWHERE for Windows will not work with any IRQ conflicts in Host mode.
It may be possible to disable a built in COM port to free up an IRQ and Port
address.
The IRQ and Port Address must be set on both the modem and in the Software.
Sound cards often use IRQ 5 or 7.
Network Cards often use IRQ  2, 3, 4, 5, 7, 10, 11, 12 or 15.
IRQ 5 and IRQ 7 are sometimes available, or can be made available.

Windows attempts to gain control of all your systems resources. It does this by
enabling the drivers and configuring system information found in your SYSTEM.INI
file. There are some specific commands that need to be removed or remarked out
of your SYSTEM.INI file. These commands are as follows:

COM#Irq=
COM#Base=
COM#AUTOASSIGN=

# is in reference to COM PORT settings that match that of what your modem is set
to. Either remove these lines or place a semicolon (;) in front of these lines.
Removing these will not harm your Windows applications.


-POSSIBLE SOFTWARE CONFLICTS:
Menu Utilities, Memory Managers, Screen Savers, Virus Detectors, Keyboard
Utilities, Disk Cache, FAX software, Share....

Note:   Any menu program that stays resident in memory while other programs are
running should be removed.  pcANYWHERE host should not be run from a TSR menu
program.
Note:   Any Disk Cache with Delayed write disk caches may cause a conflict.
Note:   Any FAX software set to automatically receive a FAX.

Common Host Error messages 
(These errors are generally related to the modems not communicating correctly.)
Error 20  =     No Connection
Error 27  =     No response from remote


-BAUD RATE OR DATA RATE:
If the Data Rate is set to above 9600, the serial port may not be able to handle
that rate.  To use speeds above 9600 you will need a 16550 UART (see MSD report:
UART chip used)

The maximum data rate for INT-14 communications is 9600.


-MODEM CABLES:
For regular connections to external modems, check to make sure the cable
supports pins 1-8 and 20, a total of 9 pins (DB25 to DB25) or Pins 1 through 9
(DB9 to DB9)  or Pins 1-9 (DB9) to Pins 1-8 and 20 (DB25).  A full 25 pin RS232
(standard serial cable) cable will work fine.  Avoid the use of  9 to 25 pin
converters.  A 9 to 25 pin modem cable is preferable.

A symptom of a cable problem is seeing "+++" and immediately disconnecting after
making a connection.

The proper wiring diagrams can be found in Appendix A  Modems & Cables found in
the back of the pcANYWHERE user's manual.


-FLOW CONTROL:
One symptom of a flow control problem is when pressing the letter R causes the
connection to freeze.  The Modem and pcANYWHERE must be set to use RTS/CTS flow
control and XON/XOFF flow control must be disabled.  There are usually two
different commands that control these features.
Consult your modem documentation for the proper commands.

Samples from the Cardinal Manual
&K3     -- Enable RTS/CTS flow control
\G0     -- Disable XON/XOFF flow control

Samples from the Motorola UDS Manual
\Q3     -- Enable bilateral CTS/RTS flow control
\G      -- Disable XON/XOFF flow control

If the hardware and the flow control are configured correctly:
Try disabling Error correction on the modem and attempt a connection. 
Try disabling Data compression on the modem and attempt a connection.
Try setting the data rate to 9600 and attempt a connection.
Please refer to your modem documentation for the proper commands.

NOTE: Flow Control in the Windows control panel should be set to HARDWARE.


-PARITY:
The Parity should be None when connecting to a pcANYWHERE host and the correct
type when connecting to an on-line service.  A wrong setting will display
strange characters on the screen when you attempt to connect.

The setting for pcANYWHERE parity will give the following data formats
None    -   8 Data bits,    No parity,      1 stop bit
Even    -   7 Data bits,    Even parity,    1 stop bit
Odd     -   7 Data bits,    Odd parity,     1 stop bit
Space   -   7 Data bits,    Space parity,   1 stop bit
Mark    -   7 Data bits,    Mark parity,    1 stop bit


-PHONE LINES:
The telephone line can cause many modem communication problems.  Most modems
require an analog phone line.  Answering machines, FAX machines, etc. can cause
problems with modem communications.

Call Waiting will disrupt a modem call.  Call waiting can be disabled for
outgoing calls only.  Adding *70, to the beginning of a phone number works in
many areas.  Check with your local phone company for the proper dial string. 
There is currently no way to disable call waiting for an incoming call.

Test the modems phone line with a regular telephone.  The line should be clear
of static.

Test the modem on a different phone line.

Avoid the use of telephone switching devices.


-TERMINAL TYPE:
In pcANYWHERE 1.x you should use "Call a Host" to connect to a pcANYWHERE Host.

When connecting to a non-pcANYWHERE host, you will use "Call an Online Service".

A wrong setting will display strange characters on the screen when you attempt
to connect.


-CARRIER DETECT SIGNAL:
The Carrier Detect Signal should be set to: DCD active during CONNECT.
The common Hayes compatible command is &C1
Consult your modem documentation for the proper command.
If  Carrier Detect is High or Yes,  the factory default is incompatible with
pcANYWHERE and the command must be sent to the modem.  (see Checking Signal
Status)


-THE SIGNAL STATUS OF THE MODEM:

With pcANYWHERE for Windows type:  "MSD"  at a DOS prompt.  Press "C" for COM
ports.

 COM Ports
                            COM1:      COM2:      COM3:     COM4:
                            -----      -----      -----     -----
 Port Address               03F8H      02F8H      02E8H       N/A
 Baud Rate                   2400       2400      57600
 Parity                      None       None       None
 Data Bits                      8          7          8
 Stop Bits                      1          1          1
 Carrier Detect (CD)           No         No         No
 Ring Indicator (RI)           No         No         No
 Data Set Ready (DSR)          No         No        Yes
 Clear To Send (CTS)           No         No        Yes

MSD reports the COM ports in consecutive order of detection (3F8,2F8,3E8,2E8).

In this example the modem is on COM4(2E8), but since the modem is the third port
detected, MSD lists it under COM3.

CD may be YES on some modems.

If CTS & DSR are both NO the system may lock when a call is attempted.  This is
typically due to a hardware problem with the modem/Cable/COM port.  To resolve
these problems, it may be necessary to contact your computer or modem
manufacturer.

Note: DCR may be NO on some Modems


-DIRECT CONNECTS VIA NULL MODEM CABLE

Click on Be A Host PC and then choose Your Hardware Setup Name: to be Direct
Connect.   Then Edit... the Hardware Configuration.  Choose the proper Device:
(Com Port) and then click on No Modem (Direct Connect).  Set Data Rate: at 9600,
Flow Control: at RTS/CTS, and Parity: at <None>.   Then click on Advanced... and
make sure that Started by: is set to Receive 2 <CR>'s, that Ended by: is set to
Always Connected, and DTR: and RTS: are both Always On.  Choose O.K. a few times
until you return to the Main Menu, then select Wait for Call.

SETUP FOR THE REMOTE

Click on Call A Host PC and then Edit... the Host PC Directory entry that you
will be using for the direct connection.  Your Hardware Setup Name: should be
Direct Connect. (If you have used the LAN installation described on page 1-13 of
the User Guide, you may have to create a New Hardware Configuration, Direct
Connect - Remote). Then Edit... the Hardware Configuration.  Choose the proper
Device: and then click on No modem (Direct Connect).  Set Data Rate: at 9600,
Flow Control: at RTS/CTS, and Parity: at <None>.  Then click on Advanced... and
make sure that Started by: and Ended by: are both set to Always Connected.  Both
DTR: and RTS: should be Always On.  Choose O.K. a few times until you return to
the Main Menu, then choose Call.

When you see the pcANYWHERE terminal screen, hit the return key twice and you
should see the host's screen.  If you are successful, you may return to the
setup for the Host and Remote, and increase the data rate on each.  We suggest
you double the data rate after each success, keeping the same rate at both host
and remote.  If you are not  successful, try setting up the Call Host PC at the
HOST computer, exactly the same as at the remote computer.  Then make the two
(remotes) call each other.  You should see terminal screens at each end.  If you
can type words at one side (such as, "Can you see this?") and see them at the
other side, a setup problem is indicated.  If you cannot see the words you type
at the other side, this indicates a problem with the cable or a Com Port.  To
verify, try a new cable which connects to a different Com Port.  There also is a
very slight possibility that some other program (loaded by your AUTOEXEC.BAT) is
conflicting with the data transmission.

................................

[4.4: Can I connect to a different version of PCA?]
pcANYWHERE for Windows version 1.0 is compatible with pcANYWHERE version 4.5 and
5.0. The normal "Connect to Host PC" selection is used.

Mouse and Windows support are enabled when controlling version 4.5 and 5.0.

To control pcANYWHERE version III, first the ANYWHERE host module of version III
must be configured to accept a VT-100 terminal.  The "Call Online Service"
selection of version 1.0 is used to connect with version III.

4.5 or 5.0 of pcANYWHERE can remotely control a pcANYWHERE for Windows host PC.
Windows must be using standard VGA resolution on the host computer. 

File Transfers between Versions
To transfer files between the Windows version 1.0 and versions 4.5 or 5, version
1.0 must be the remote and must run the file transfer program AWSEND, which is
located in the host's pcANYWHERE subdirectory (usually called C:\AW).  Files can
be transferred in either direction using this method.  File transfers between
pcANYWHERE for Windows and pcANYWHERE III is not supported.

................................

[4.5: Can I connect to a PCA WIN Host using another program like ProComm or
Qmodem?]
No.

................................

[4.6: Can I connect to another program like Procomm or Qmodem using PCA as the
remote?]
Yes, by selecting CALL AN ONLINE SERVICE. The Terminal Emulation setting much
match that of the terminal you're connecting to.

................................

[4.7: Can I connect to a PCA Host from a Macintosh?]
Yes, you can call into a host from a Mac machine. There is a program available
from Argosy Software (303-444-2100) called RunPC which allows the user to call a
PCA host running version 4.x or 5.x. Some users have also reported success
running PCA on the Mac using a PC emulator program.

___________________________________________________________________


V) PCA Compatibility: Modems/Comm Software/Terminals
=========================================================

[5.1: What if my Modem is not on the modem list?]
The Norton pcANYWHERE has an extensive list of pre-configured modem drivers for
many popular modems. Although this list is updated regularly on the Symantec
BBS, CompuServe, and America Online, it is possible that the modem you are using
is not supported within the Norton pcANYWHERE. It is also possible that if the
modem has an older version (or in rare cases, a newer version) of firmware, the
driver in the Norton pcANYWHERE may not work properly. In either case, as long
as the modem is compatible with the Hayes AT command set, it should be possible
to configure the modem for use with the Norton pcANYWHERE.

To access the updated modem list files by modem
Symantec BBS    503-484-6669 (9600) or 503-484-6699 (2400)
CompuServe      GO SYMUTIL
American Online KEYWORD SYMANTEC

The updated modem list files are:
NEWMOD.EXE  for pcANYWHERE 4.5  contains aw.msg, awh.msg, awr.msg
WINMOD.EXE  for pcANYWHERE 1.0  contains awmodem.dat
MOD50.EXE   for pcANYWHERE 5.0  contains awmodem.md6

These are self-extracting archives that contain the updated modem list.  Execute
the file and copy the new modem list to the pcANYWHERE directory.  Then select
the appropriate modem from the updated list within pcANYWHERE.

Creating Your own Modem Initialization String
In most cases, the Hayes Compatible modem selection is a good starting point for
configuring the modem. When the Hayes Compatible selection is used, the
following initialization codes are sent to the modem:

ATZ
AT E0 V1 X1
AT &C1
AT &D2
AT S0=0 S7={Seconds to wait after dial} S10=20 S12=25

If the modem returns an ERROR message while initializing as Hayes Compatible,
then try selecting Hayes Smartmodem 1200. This selection is similar to the Hayes
Compatible selection, but doesn't send any extended commands (those starting
with an "&"). When using these settings, the data rate is adjusted to 2400 bps
for the Hayes Compatible setting and 1200 bps for the Hayes Smartmodem 1200. If
your modem operates at speeds faster than 2400 bps or 1200 bps, feel free to
change the data rate to the fastest speed your modem is capable of.

Additional considerations
While most modems will operate fine with the Hayes Compatible or Hayes
Smartmodem 1200 setting, the modem may require additional parameters in order to
operate properly with the Norton pcANYWHERE. Consult your modem documentation,
and make sure that your modem adheres to the following requirements:

Modem does not implement Xon/Xoff flow control
Modem is set for RTS/CTS flow control (if applicable)
Modem is set to automatically adjust the baud rate
Modem is set to automatically enable data compression (if applicable)
Modem is set to automatically enable error correction (if applicable)
Modem is set to automatically fall back to lesser protocols (if applicable)

If the modem requires additional parameters in order to work properly with the
Norton pcANYWHERE, place those parameters on the Additional Modem Initialization
String field located at the bottom of the Hardware Configuration screen (4.x and
5.x) or on the Advanced Hardware Configuration Screen (1.x).  Also, if the modem
has "DIP" switches which control some of its operating parameters, make sure
that they are set to the factory default settings.

Note:   In pcANYWHERE for Windows version 1.0, to send a % (percent sign), two
(%%) must be sent in the additional modem string.

Tips for writing a modem initialization string
A good starting point for writing a custom modem initialization string is: 
AT&F&C1&D2
Many of the factory default settings will be correct for pcANYWHERE.  This can
make initialization strings much shorter than sending out every command that is
necessary to make the modem operate correctly.

If the hardware and the flow control are configured correctly
Try disabling Error correction on the modem and attempt a connection. 
Try disabling Data compression on the modem and attempt a connection.
Try setting the data rate to 9600 and attempt a connection.

................................

[5.2: Can PCA and my FAX Software share the modem?]
Presently, the only tested software that will allow simultaneous use of the
modem by Fax and PCA is Intel's SatisFAXtion software. It can be set up to allow
the Fax and PCA to answer on different rings. A program called KingCom is also
available, which will allow you to share the COM port. However, Symantec has not
yet tested PCA with that product.

................................

[5.3: Can I run PCA and other Comm software at the same time?]
No. PCA cannot share the modem with any other software (See 5.2 for exception).

................................

[5.4: Can I run PCA on an OS/2 system?]
PCA was written to be run under a DOS/Windows operating system.  Some users have
had success running PCA under OS/2, but it is not recommended or supported by
Symantec.

................................

[5.5: Can I run PCA on an Windows NT system?]
PCA was written to be run under a DOS/Windows operating system, running under
Windows NT is not recommended or supported by Symantec.

................................

[5.6: How do I set up PCA to work with my Terminal Emulation? ]
A common use of The Norton pcANYWHERE is the remote access of a 5250, 3270 or
other type of terminal emulation package. Many emulation programs make extensive
use of keyboard remapping, or employ unconventional memory handling techniques
which make it difficult for other programs in memory to function. What follows
outlines the settings commonly used to operate pcANYWHERE in conjunction with a
terminal emulator.

Setup:

1) Load the Host program into memory before loading the emulation program, if
   the emulation program doesn't have a hot key to toggle back and forth.
2) If the emulation program has a hot key, try loading it first. Then hot key
   back to DOS and start pcANYWHERE in host mode.
3) Verify that the emulation board is not using the same interrupt (IRQ) that
   pcANYWHERE's communication device is using.
4) If a memory manager is being used on the Host, such as Quarterdeck's QEMM, or
   MS-DOS'S EMM386.EXE, avoid any options that may adversely effect pcANYWHERE's
   Special Keyboard Handler.  Try loading your memory manager without any
   additional features such as Stealth Mode (QEMM with ST:M or ST:F), HIGHSCAN
   or AUTO (EMM386).  In addition, also remove any include (i=) statements.

Due to the keyboard remapping used by most emulators, it is necessary to use
pcANYWHERE's Special Keyboard Handler. See below.

................................

[5.7: What are Keyboard Handlers?]
Keyboard handlers allow the remote user to operate the host PC effectively while
executing host applications that handle keyboard input in a non-standard
fashion. The exact setting varies depending upon which emulation program is
being used, and other parameters of the Host system. Generally speaking the
correct setting must be found by trial and error. To set the Special Keyboard
Handler:

1) From the Configure menu, Host Operation/DOS TSR.
2) Select Special keyboard handler type, and set it to Type 1. If this setting
   does not work, try Type 2.
3) Another option frequently required by emulation programs is the Allow
   scanning while host busy. This option should be set to Yes.
4) From the Configure menu, select Remote Operation.
5) Set the Special keyboard handler to Level 1. (If this setting does not work,
   try Levels 2 and 3. We often find level 3 works best).

If these settings do not work, it could be that the emulation program is trying
to use the memory where pcANYWHERE is located. Try the following:

1) Remove any unnecessary memory resident programs from CONFIG.SYS and
   AUTOEXEC.BAT. Load only what is needed to access the emulator.
2) Try loading pcANYWHERE before all other memory resident programs.
3) Try loading The Norton pcANYWHERE into upper memory. This will require at 
   least a 386 based machine, and a memory manager, such as Quarterdeck's QEMM,
   EMM386 (DOS 5 or later), or Qualitas' 386MAX.  For more information on
   loading the Host into upper memory, please refer to document 5019 on the Fax
   Retrieval Service.

................................

[5.8: Resolving display problems]
Icons showing up as black boxes, GPF's in WordPerfect or Access, and the "Black
Screen of Death" are all attributed to possible display problems.

1) Download NEWVID.EXE from the File Library and execute it in the 
   Windows\System directory. This file contains the latest video drivers for PCA
   and will solve most display problems.

2) Use the standard Windows 3.1 video drivers. Many third party drivers/video
   cards are not compatible with PCA WIN.

................................

[5.9: Resolving font problems]
If you experience garbled FONTS on the Remote computer, edit a file called
PCAW.INI located in the Windows directory on the remote computer.  Look for the
section [Fonts], then change the Logical Fonts parameter as follows:

[Fonts]
LogicalFonts=1

After making changes, exit pcANYWHERE, then start pcANYWHERE again.
To increase the DOS Font size add the following to the PCAW.INI in the [Fonts]
section:

DOSFontSize=XX,  (where XX indicates the font size; 18 through 22 is
recommended)

We recommend starting at 20.
To change the DOS Font type, add the following to the PCAW.INI  (the default
FONT is TERMINAL):

[Font]
DOSFont=  (the name of the Font, i.e., COURIER, MODERN, SYSTEM)

Exit pcANYWHERE, then re-start pcANYWHERE to implement the changes.

................................

[5.10: COMPAQ Video Drivers]

COMPAQ drivers: Some COMPAQ's use a proprietary video card that uses and *.EXE
file for it's display driver. The System.ini file will need to be manually
edited to show the PCA display driver instead (see section 2.3). The PCAW.ini
may also need to be edited.

COMPAQ PROLINEA: With the host TSR loaded, the display paints very slowly in
block mode when starting Windows. Contact Compaq support at 800-345-1518.

COMPAQ QVISION Drivers: Version 7.24 works correctly with PCA. For others, add
the following to the COMPAQ.INI located in the Windows subdirectory:

Find the section [Display]
Add the line:    DeviceBitmap=off
in the section: [Config]
Add the line:   DeviceBitmap=off

Exit Windows, then restart Windows.  If you receive an error that says "Invalid
Setting - DeviceBitmap" then remove the DeviceBitmap=off from the [Display]
section in the COMPAQ.INI.


______________________________________________________


VI) Networks and PCA
===================

[6.1: What networks are supported by PCA?]
PCA will work with IPX, NetBIOS, and Banyan Vines. For Novell systems you will
need Netware 3.1+, version 3.10 or greater IPX, and 3.26 or greater NETX.
IPXODI 1.2+ with LSL 1.21, 2.11 if using LSL2.10, 2.12 if using LSL 2.05)
VLM's with 3.11 and 3.12, VLM's with 4.01 using Bindery Emulation.

................................

[6.2: How do I set up PCA 1.0 to work with Netware Connect?]
Novell has introduced an asynchronous communication server package (NetWare
Connect) that is very popular.  It supports Dial-in and/or Dial-out services and
both configurations can share access to the same modems.  This way users can
have pcANYWHERE loaded in Host mode on workstations and also call out with the
Remote mode without reconfiguring.  This flexibility is perfect for pcANYWHERE. 
Other telecommunication services can also share access to the modems with
pcANYWHERE.

NetWare Connect provides three services: AppleTalk Remote Access Service (ARAS),
NASI Connection Service (NCS), and Remote Node Service (RNS).  pcANYWHERE uses
the NCS service.  NASI (NetWare Asynchronous Services Interface) is the DOS
client that acts as an interface between our application and NCS on the server. 
Setting up NetWare Connect should be fairly straight forward using this
document.

Configuring NetWare Connect:

- Creating valid Port Groups:

At the NetWare console prompt (:), load nwccon, then choose from the menus.
Select "Configure NetWare Connect", "Configure Ports", "Configure Communication
Ports", and then "Configure Ports".  Make sure there are ports shown as
available.  If any of the listed ports are not available, select the port from
the list and at "Modem Type:" select none - delete the entry to choose none. 
Select the proper modem type and parameters for each port.

Press "ESC" to  back out of "Configure Ports", then select "Configure Port
Groups".  Create a new Port Group and assign all of the ports that you want for
this group (these ports must be usable and available).  You must create two new
Port Groups if you wish to have both a Dial-in service and a Dial-out service. 
You can assign the same ports to more than one group.

Now return back to the "NetWare Connect Options" menu and select "Generate
Configuration Report".  Choose "Print to Screen" and verify all port settings.

- Creating the NCS service:

From the "NetWare Connect Options" menu select "Configure NetWare Connect",
"Configure Service", "NCS", and then "Configure NCS".  Make sure the "Command
Interpreter Prompt:" is set to "NASI".  Select the list from "General Name List:
<see list>" and add the new Port Group(s).  Add all of the Port Groups you plan
on using for NCS, including the Dial-in and Dial-out Port Groups.   Remove
"ANYPORT" from the list if it is there.  If you plan on having pcANYWHERE set up
for dial-in then you need to select a Port Group in "Dial-in Group:".    The
Port Group used in the "Dial-in Group:" will cause a "General Network Error" if
it is also selected in the "Modem-Independent Group:".

Now exit the "NWCCON" console and execute "NWCSTOP" and then "NWCSTART" to
reload the configurations.

The NASI Setup and Diagnostics.

Execute NASI.EXE with a User's name, password, and a unique Session name on the
same workstation that is running pcANYWHERE.  The command  line for NASI is
"NASI  /N=<username> /P=<userpassword>  /S=<unique session name>".  Execute
"NASIDIAG.EXE" and select "List Available NCS Ports".  The Server is listed
under the "NCS" heading, Service is listed under the "General" heading, and
Physical ports and/or Logical ports are listed under the "Specific" heading.  A
Logical port is a name created by NetWare Connect for the Dial-in Group.  The
name will be a combination of the Server name & "DIALIN".  The Server name will
be truncated to eight characters if it is too long or underscores will be added
to expand the name to eight characters if too short.  If a physical port name(s)
appears under "Specific" for the Dial-in Group then "NCS" was not configured
properly.  The physical port names will be listed for all other groups under
Specific.  Exit NASIDIAG.

Settings for pcANYWHERE.
Execute pcANYWHERE and drop down the "Configure" menu.  Select "System Hardware"
from the menu and select the "NEW" button.  Enter a valid name for the service
type (Dial-in or Dial-out).  Change "Device:" to "NASI/NCSI" and Select
"Settings...".  Place a check in the Server box and select "Browse".  Now choose
the Server you will be using.  Repeat the last two steps for the Service, and
the Port.  Remember that logical port names are for Dial-in services and
physical port names are for Dial-out services.  Now set the modem selection for
the proper modems that are connected to the NCS server.  The data rate for
pcANYWHERE must match the data rate set for the NCS Ports.  Select "OK" to save
the settings.
pcANYWHERE is now properly configured to access the NetWare Connect service. 
pcANYWHERE will not own any physical ports for Dial-in services and users will
be able to use the NCS service as both Dial-in and/or Dial-out service.
Note:    Two different pcANYWHERE hardware configurations will be required if
you are going to use both Dial-in and Dial-out services.
The "pcANYWHERE DOS HOST TSR" (AW5HOST) does not support NASI and therefore
cannot be used to connect through NetWare Connect.  The DOS TSR's command line
may be located in your AUTOEXEC.BAT and looks similar to, "F:\WINAW\AW5HOST 
-P=F:\WINAW  -W=C:\WINDOWS  -M=R".  Type "REM" at the beginning of this line to
disable it. Disabling AW5HOST will only preclude you from exiting Windows during
a session or running a DOS application in full screen mode.  You will still be
able to run most DOS applications from a Windows' DOS window.

................................

[6.3: Can I run PCA with Novell Version 4.X?]
Yes, but you must be running Bindery Emulation.

____________________________________________________________________

VII) Scripting
=============================

[7.1: Why won't my script work?]
Symantec does not support the creation or writing of scripts. Symantec does
however, have many useful samples and documents available on our BBS and
CompuServe to assist you in the process. Faxback documents 5025 & 5028 are
recommended (see Symantec Support Services in Section X).

In the event that you require the assistance of a consultant, Symantec provides
consultant services at the rate of $100/hr. You can call PCA Tech Support at
503-465-8430 to request a consultant call you and give you an estimate.

___________________________________________________________________


VIII) Speed and Performance Issues
=============================

[8.1: How can I speed up PCA?]

Background Information
The Norton pcANYWHERE provides a simple yet powerful way to remotely control a
PC.  pcANYWHERE incorporates data compression technology to make remote screen
updates as quickly as possible, there are additional steps to further enhance
performance.

If you are experiencing slow screen updates you can configure your pcANYWHERE
for Windows for more efficient operation.  Here are some items to check to
increase the speed of the video (screen) transmission.

special hardware/software considerations
The speed of transmission will directly depend on the hardware of your system
and the Windows setup on your system.  Slow modems and slow PCs will directly
effect your transmission (throughput) speed.  Also, large amounts of graphical
data will slow down performance.

Resolution
Hardware Portion.
The first item to look at is the hardware on the system.  If you can get a 14.4
V.42, V.42bis modem this is best.  The next best is a 9600 V.42, V.42bis modem,
then finally a 2400 V.42, V.42bis modem.  If you do have a fast modem and can
get a reliable connection (V.42, V.42bis), the highest data rate for a 14.4 is
57,600, for a 9600 is 38,400, and for a 2400 is 9600.

If the modem is external than we must make one other consideration.  The modem
relies on the PC's hardware (serial port) for communications.  There are several
serial port controller chips out on the market; and the one that is currently
the best is the 16550AFN chip.  This chip performs and controls the PC's
communications, and is called a UART (Universal Asynchronous Receiver and
Transmitter).  You can get one of these chips on a serial I/O Card from a
computer hardware store and replace the one that is currently in your system.

Software Portion.
It may not look as good, but if you remove all Wallpapers and Bitmaps, Windows
calls them Patterns and Wallpapers and set your Windows colors to utilize a
BLACK Desktop, for example: Fluorescent, Black Leather Jacket, LCD Reversed -
Dark, or Plasma Power Saver, these will speed up the video transmission
immensely.  You can select any colors you wish, but these listed have BLACK for
a Desktop color and BLACK is not transmitted.  This can be changed by going into
Windows' Control Panel  then Color then Color Palette >>  then select BLACK for
the Desktop color.  The Patterns and Wallpapers can be changed by going into
Control Panel then Desktop set them both to
(NONE).
If you can use standard VGA this will also enhance throughput.
In windows you can also set  the "Minimize on Use" feature.  Click on Options
then click on Minimize on Use.  If you are using Norton Desktop for Windows_ 
then click on Configure then click on Quick Access then click on  Minimize on
Use.


Also make sure that all your windows are minimized or closed before the
connection starts.

Also if you start Windows after making a connection make sure you start it with
WIN :

................................

[8.2: What is high (or upper) memory?]
It is possible for the Host portion of pcANYWHERE be loaded in into upper
memory, thereby freeing more conventional memory for applications.  Unlike
extended or conventional memory, upper memory is not automatically present when
you turn on your machine. Upper memory is created by a memory manager, such as
EMM386.EXE that is included with DOS or Windows.  You must have at least a 386
machine to have upper memory available.

Upper memory is the area of memory between 640k (the base, or conventional
memory), and 1024k (one megabyte). Even if your machine has several megabytes of
memory, it is still this upper memory area where TSRs and device drivers may be
loaded.  Part of this area is occupied by the system ROM and video ROM, but
there is usually free space available in this area to load TSRs. To create upper
memory on your system, you must be loading EMM386.EXE in your config.sys.
(EMM386 should load after HIMEM.SYS), and you need the line DOS=HIGH, UMB in
your config.sys.

The CONFIG.SYS might look something like this:
    DEVICE=C:\DOS\HIMEM.SYS
    DEVICE=C:\DOS\EMM386.EXE
    DOS=HIGH,UMB

Use the DOS MEM command to find out how much upper memory is available on your
machine.  Type MEM /C /P (for DOS 6.x), or MEM /C ÝMORE (for DOS 5). Look for a
line referencing upper memory.  If a block of upper memory is available that is
large enough, the Host can be loaded high. Should there not be enough upper
memory available, pcANYWHERE will load a portion of the Host high, and the
remainder will load in conventional memory.

................................

[8.3: How do I load the Host into high (or upper) memory?]
In order to load the Host high, you will need to make sure the Load Host into
High Memory option is set to yes.  To verify how this option is set, go into
Configure/Host Operation/DOS TSR.  The amount of memory required by the host
varies depending on the options selected:

Host, with all features set to no:  63K
Maximize Display Speed adds:    46K

If you still need to free more upper memory area, check to see if the  NOEMS 
parameter is on the EMM386.EXE line in config.sys (example:
DEVICE=C:\DOS\EMM386.EXE NOEMS). Use of this line will provide expanded memory
services only for the upper memory area.  If you had been using EMM386 with the
RAM parameter instead, the NOEMS option will give you an additional 64k (The
area that would have been used for the page frame).  Note that with this option,
expanded memory will not be available for some applications that may want to use
expanded memory.  Keep in mind you can use EITHER the RAM or the NOEMS
parameter, but not both at the same time.

Tips for Advanced Users:
WARNING:  Before proceeding further, please be sure you have a working boot disk
available!  If you do not have a boot disk, stop and make one at this time.  To
make a bootable floppy diskette, place a blank diskette in your A drive, and
type format a: /s.  Place this diskette in a safe place.

Depending on your machine, there may be other areas of the upper memory area
that could be included with the I= parameter on the EMM386.EXE line. Care must
be used when using I= inclusions in this manner. A diagnostic utility that can
analyze the upper memory area can be helpful when dealing with inclusions (such
as Quarterdecks Manifest).  Refer to your DOS manual for more information about
using  inclusion statements.  If your machine does not boot normally, reboot
with the boot diskette.

Special Notes for 386MAX:
1) Include the command line parameter: aw5host -m=a (or -m=w, or -m=h) in the 
   autoexec.bat file.
2) Run MAXIMIZE, the automatic system configuration utility.
3) In phase I of maximize you will be asked to specify Full or Quick maximize. 
   Choose Full.
4) In phase II of full maximize specify the command line for pcANYWHERE in the 
   autoexec.bat as one of the programs to be considered for loading into the
   high memory area.
5) 386LOAD will then specify the region size required for loading the resident
   program, then it will use the command line FLEXFRAME to borrow the EMS page
   frame area while loading a program.
6) After optimization simply remark this line from your autoexec.bat file and
   include that in a host batch file.

______________________________________________________________


IX) PCA 1.0 Command Line Reference
===============================

BACKGROUND INFORMATION
When the Norton pcANYWHERE for Windows manual was created, information about
command lines were not available. Instead, they were added to the pcANYWHERE
README.TXT file located in your pcANYWHERE for Windows directory. For
convenience, this document was created to show you all the available command
lines and options.

................................

[9.1: WINAW.EXE Parameters]

Norton pcANYWHERE Windows Application (WINAW.EXE):
The following commands are to be used from the DOS command line as WIN WINAW
including the commands below or from within Windows using the Run command from
the File menu as WINAW including the commands below. Please remember that names
are case sensitive.

-o=h -n=phone_number    Call a remote with specific number.

-o=h -m=w               Waits for a call. Check Host Operations to see if PC is
                        to be locked waiting for a connection.

-o=h -m=v               Voice first connect. Instructs you to press enter to
                        begin data mode.

-o=r -m=w -n=host_directory_name    Waits for a call from a specific Host in the
                                    Host PC Directory. Replace
                                    host_directory_name with the Host PC name as
                                    it appears in the Host PC Directory.

-o=r -m=d -n=host_directory_name    Calls a specific Host in the Host PC
                                    Directory. Replace host_directory_name with
                                    the Host PC name as it appears in the Host
                                    PC Directory.

-o=r -m=v -n=host_directory_name    Voice first connect with a specific Host in
                                    the Host PC Directory. Replace
                                    host_directory_name with the Host PC name as
                                    it appears in the Host PC Directory.

-o=r -m=d -s=onl_svc_directory_name     Calls a specific Online Service in the
                                        Online Service Directory. Replace
                                        onl_svc_directory_name with the Online
                                        Service name as it appears in the Online
                                        Service Directory.

-o=r -m=s -n=script_file_name   Instructs the Remote to execute a script.
                                Replace script_file_name with the name of the
                                script file.

-c=configuration_name     Special hardware configuration option for Host
                          Operations Only. This allows you to specify what
                          hardware configuration to use when specifying any of
                          the above options. Replace configuration_name with the
                          name of the hardware configuration name as it appears
                          in the Hardware Setup List.

-i=user_id     This parameter identifies the configuration files for network
               installations. Replace user_id with the six character ID used to
               start pcANYWHERE.

EXAMPLE #1:

From DOS:C:\>WIN WINAW -o=r -m=d -n=Work Computer

This will start Windows, start pcANYWHERE for Windows and dial the Host PC
specified above as "Work Computer".

EXAMPLE #2: From Windows:Select File.Select Run.
Enter path_name\WINAW -o=r -m=d -n=Work Computer.

This will start pcANYWHERE for Windows and dial the Host PC specified above as
"Work Computer".

................................

[9.2: AW_HOST.EXE Parameters]

-w=win_path        Lets the Host DOS TSR know were Windows is located. This is
                   not required if the i=user_id is used. Replace win_path with
                   the path to your Windows directory.

-p=configuration_path    Lets the DOS TSR know were your pcANYWHERE
                         configuration files are located. Replace
                         configuration_path with the path to your pcANYWHERE
                         configuration files. This is not required if you are
                         using the "AW=" environment variable.

-m=r    Loads the Host DOS TSR resident in memory as Hot-Key to activate. Press
        ALT and the RIGHT-SHIFT key to recall Host DOS TSR menu.

-m=a    Loads the Host DOS TSR resident in memory as Accept Calls at any time.
        Press ALT and the RIGHT-SHIFT key to recall Host DOS TSR menu.

-m=w    Loads the Host DOS TSR resident in memory Waiting for a Call. Press ALT
        and the RIGHT-SHIFT key to recall Host DOS TSR menu.

-i=user_id     his parameter identifies the configuratio n files for network
               installations. Replace user_id with the six character ID used to
               start pcANYWHERE.

-c     This parameter will unload the AW5HOST TSR from memory if it was the last
       TSR loaded.

EXAMPLE #1:
From an AUTOEXEC.BAT file:
PATH C:\DOS;C:\WINDOWS;
IPX.COM
NETX.COM
AW5HOST -m=a -w=c:\windows -p=f:\login\winaw
F:LOGIN

This will load the Host DOS TSR allowing calls anytime. It is looking for the
pcANYWHERE for Windows configuration files in the F:\LOGIN\WINAW directory.

Example #2:
Unloading the Host TSR from the command line:
AW5HOST -C

................................

[9.3: AW_GATE.EXE Parameters]

-p=configuration_path       Lets the DOS TSR know were your pcANYWHERE
                            configuration files are located. Replace
                            configuration_path with the path to your pcANYWHERE
                            configuration files. This is not required if you are
                            using the "AW=" environment variable.

-i=user_id     This parameter identifies the configuration files for network
               installations. Replace user_id with the six character ID used to
               start pcANYWHERE.

EXAMPLE #1:
From an AUTOEXEC.BAT file:
PATH C:\DOS;C:\WINDOWS;
IPX.COM
NETX.COM
AW5GATE -p=f:\login\winaw
This will load the Gateway DOS TSR allowing users to share the modem on this
network workstation. It is looking for the pcANYWHERE for Windows configuration
files in the F:\LOGIN\WINAW directory set by the AW5GATE command line.

EXAMPLE #2: From an AUTOEXEC.BAT file:
PATH C:\DOS;C:\WINDOWS;
SET AW=F:\LOGIN\WINAW
IPX.COM
NETX.COM
AW5GATE

This will load the Gateway DOS TSR allowing users to share the modem on this
network workstation. It is looking for the pcANYWHERE for Windows configuration
files in the F:\LOGIN\WINAW directory set by the "AW=" environment variable.

Example #3:
Unloading the Gateway TSR from the command line:
AW5GATE -C


X) Symantec Support Services
===============================

[10.1: PCA Telephone Support]
503-465-8430    90 Day Complimentary Support
800-927-4012    Priority Support: $25.00/question (less than 1 minute hold time)
900-646-0006    Priority Support: $2.00/minute charged to phone
    (less than 1 minute hold time/1st minute free)

Subscription Service $149.00/year, unlimited calls on 800 line.

................................

[10.2: Online Support]
CompuServe:  GO SYMUTIL
American Online:  Keyword SYMANTEC

................................

[10.3: User to User Forum]
Symantec BBS:   503-484-6669 (9600 baud)
                503-484-6699 (2400 baud)

................................

[10.4: Faxback Service]
If you have a FAX machine you can call 503-984-2490 with a touch tone phone and
request a document . When you hang up the document will be sent to your fax
machine. Most technical documents are available under menu option 2.  Document
5500 contains a listing of all available PCA WIN fax documents.