
                   Norton pcANYWHERE Access Server
                             Version 1.0

                           November 2, 1994

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

Thank you for choosing the Norton pcANYWHERE Access Server.  

If you have trouble with the Access Server, please check the manual 
and this file for any information that may pertain to your problem.  
If this information does not help, you can call Symantec Technical 
Support at (503) 465-8430.  We also provide a support Bulletin Board 
at (503) 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 trouble-shooting and compatibility 
information.  Please read this information before using the Access 
Server.  

====================================================================== 
                        IMPORTANT INFORMATION
====================================================================== 

It is highly recommended that you use this product on a dedicated 
computer.  This will allow the system to be configured and optimized 
for the Access Server without affecting other users, and vice versa.  

                            -------------

If you are running OS/2 Version 2.11, you may need the OS/2 Fix Pack 
XR0A058.  This patch is required on Pentium computers and many 486 
systems.  The patch is available from Symantec and from IBM.  To order 
it from Symantec, call (800) 441-7234.  Refer to your OS/2 
documentation if you want to contact IBM for the Fix Pack.  

Please refer to Appendix B in the pcANYWHERE Access Server manual for 
more information.  

====================================================================== 
                         SYSTEM REQUIREMENTS
====================================================================== 

The Norton pcANYWHERE Access Server requires OS/2 version 2.11 or OS/2 
Warp version 3.0 or later.  If you are using OS/2 Warp, and you will 
be running Windows applications on the Access Server, you will need a 
copy of Windows or Windows for Workgroups (version 3.1 or later).  

A 486 or Pentium computer is recommended.  The Access Server requires 
2MB of disk space, in addition to the space required by OS/2, 
Microsoft Windows, and your applications.  

The performance of the system is directly affected by the available 
memory.  Our minimum requirement is 8MB per active session plus 8MB 
for OS/2.  So for 2 active sessions, 2*8MB + 8MB = 24MB.  For 8 active
sessions, we recommend at least 64MB.  

If you will be accessing Novell NetWare networks from Access Server 
sessions, the Novell NetWare Client for OS/2 version 2.1 or later is 
required.  

If you will be accessing OS/2 LAN Server networks from Access Server 
sessions, the OS/2 LAN Server DOS LAN Requester version 3.0 or later 
is required.  

====================================================================== 
               ADDITIONS AND CORRECTIONS TO THE MANUAL
====================================================================== 

HOST PERFORMANCE SETTINGS -------------------------------------------- 

The Idle Seconds and Idle Sensitivity settings can have a significant 
effect on session performance.  In particular, the settings that work 
well for DOS programs may be different for Microsoft Windows sessions.  
If you experience performance problems, try experimenting with these 
settings.  

Recommended settings for DOS or Microsoft Windows programs are:  

                  DOS      Microsoft Windows
                  ---      -----------------
Idle Seconds:       0            10
Idle Sensitivity:  75            10


CHANGING USER PASSWORDS -- CHANGEPW ---------------------------------- 

CHANGEPW is a DOS utility program included with the Access Server 
which allows users to change their Access Server passwords when they 
are in an Access Server session.  To run the program, type "CHANGEPW" 
at the DOS prompt (while in session).  The program will prompt for the 
current password, a new password, and will ask you to confirm the new 
password.  

If you are using the NetWare login feature (see the manual, and the 
NetWare section below), the Access Server will keep the user's 
password synchronized, so the CHANGEPW function is not required.  


MAXIMIZED SESSION WINDOWS -------------------------------------------- 

If you use the Open Session command to view a Microsoft Windows 
session and then maximize the session window, the session window will 
fill the screen, with none of the window controls available.  To 
restore or close the window, use the following procedure:  

1) Press Ctrl+Esc to display the Task List.  
2) Select pcANYWHERE Access Server from the Task List.  
3) When the Access Server is displayed, highlight the session.  
4) Select the Sessions menu from the menu bar, and the Open command.
5) The session will return to a the normal window size.  Click the
   minimize button to hide the session.


REMOTE PRINTING ------------------------------------------------------

To print from an Access Server session to a printer on the remote 
computer, you must configure the program running on the Access Server 
(including Microsoft Windows) to use the driver for the printer 
attached to the remote computer.  If you want to print to both the 
Host and the Remote, you must have the same kind of printer (for 
example, a PostScript printer) attached to each computer.  

Printer output is intercepted on the Host by watching for accesses to 
the printer devices LPT1, etc.  In Microsoft Windows, this 
interception only works if Microsoft Windows is configured to use 
printer ports named "LPT1.DOS" or "LPT1.OS2", not the default "LPT1:".  
The Host will intercept calls to any printer port (LPT1, LPT2, LPT3).  

Even if you plan to use only remote printing (printing on the remote
computer, not the Host), you must have a printer attached to the
Access Server, or have the Access Server attached to a network with
printer output redirected to a network printer.


FULL-SCREEN DOS AND MICROSOFT WINDOWS SESSIONS ----------------------

You should avoid using full-screen DOS/Microsoft Windows sessions on 
the host while the Access Server is running.  OS/2's priority
management gives a priority boost the foreground task.  Normally, the
foreground task is the Presentation Manager.  A full-screen
DOS/Microsoft Windows session (not an Access Server session) will
change the priority of any running Access Server sessions, and may
cause them to terminate.  


SUPPORTED MODEMS ----------------------------------------------------- 

There are some modems in the Access Server modem list which are not 
supported by Symantec technical support.  These modems are indicated 
by an asterisk (*) at the end of their names.  


DELETING SECURITY GROUPS ---------------------------------------------

Page 2-29: The Note is not correct. Security groups can be deleted
while sessions are active. Note that any changes to security will not
affect any callers currently attached to the Access Server. The
changes will take effect the next time the caller logs in.


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

pcANYWHERE REMOTES --------------------------------------------------- 

The Access Server is compatible with pcANYWHERE for DOS version 4.5 
and later, and pcANYWHERE for Windows version 1.0 and later. Some 
Access Server features are supported in the latest versions 
(pcANYWHERE for DOS version 5.0 and pcANYWHERE for Windows version 
2.0).  


OS/2 VIDEO ----------------------------------------------------------- 

OS/2 virtual video drivers do not support super-VGA modes in 
background or windowed DOS sessions -- the sessions are frozen until 
they are switched to full-screen in the foreground.  Since the Access 
Server runs several DOS/Microsoft Windows sessions in the background, 
it is restricted to standard VGA modes (up to 640x480 with 16 colors).  

If you are installing OS/2, you should select standard VGA support for 
your primary display in the option selection screen.  If you have 
already installed OS/2 with super-VGA support, you can use the 
Selective Install (found in the System Setup folder in the OS/2 System 
folder) to install standard VGA support.  For more information see 
your OS/2 documentation.  


OS/2 DOS AND MICROSOFT WINDOWS ---------------------------------------

The pcANYWHERE Access Server uses OS/2 to provide multiple DOS and 
Microsoft Windows remote control sessions.  This means that while 
these sessions appear to the remote user to be true DOS/Microsoft 
Windows machines, they are restricted to OS/2's support for these 
operating environments.  These restrictions include:  

- Graphic video modes (Microsoft Windows or DOS) are restricted to the 
  standard VGA modes (up to 640x480 with 16 colors).

- Microsoft Windows applications that require Microsoft Windows 
  virtual drivers (VxD's, usually .386 files) cannot run under OS/2.

- Microsoft Windows DOS boxes (windowed or full-screen) are not 
  supported.

- DOS and Microsoft Windows programs cannot access files using long 
  file names.  DOS limits file paths to 64 characters.

- Any memory-resident utilities, including DOS commands like ASSIGN 
  and APPEND, should be loaded in AUTOEXEC.BAT.

- OS/2 does not support OLE 2.0 applications.

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

On Novell NetWare networks, the NetWare Client should be installed 
with PRIVATE NetWare resources.  This is an installation option for 
the NetWare Client.  If you already have NetWare installed on the 
system, the following line should appear in your CONFIG.SYS file:

DEVICE= ...  VSHELL.SYS PRIVATE 

Be sure that NETX.EXE is added to the default AUTOEXEC.BAT file.  

If your NetWare network has more than one server, be sure your users 
always attach to your "main" server by either:  

- including the "PREFERRED SERVER" option under the "NETWARE
  REQUESTER" section in the NetWare configuration, or

- adding the /ps option on the NETX.EXE line in the default
  AUTOEXEC.BAT.

To avoid problems with file transfer, you should turn off broadcast
messages before starting AWSEND. The NetWare command "CASTOFF ALL" 
will disable all broadcast messages for the session.

The auto-login feature does not support the NetWare encrypted 
passwords feature. It also requires that any servers attached in a 
user's login script do not generate addtional password prompts.


NETBIOS AND LAN SERVER -----------------------------------------------

The pcANYWHERE Access Server can be installed on an OS/2 LAN Server 
workstation or on the LAN Server itself.  If you are experiencing 
difficulty running sessions, be sure that LAPS was installed and 
configured correctly, paying particular attention to the network 
adapter address and frame type entries.  

If your NetBIOS sessions on the pcANYWHERE Access Server are not 
starting, you may need to adjust three settings in the PROTOCOL.INI 
file in the IBMCOM directory.  The settings are:  SESSIONS, NCBS, 
NAMES.  Please consult your OS/2 LAN Server documentation on how to 
adjust these settings.  Try increasing them to the maximum allowed on 
your system.  

If you need to log onto a LAN Server network in an Access Server 
session, you will need to start the Access Server sessions using a 
bootable DOS image. This procedure is described in the file
LANSERVR.TXT.


QUATECH MULTIPLE SERIAL PORT BOARDS ---------------------------------- 

Be sure to read Appendix A in the pcANYWHERE Access Server manual for 
important information.  Be sure you have no I/O address or IRQ 
conflicts in your system.  The Access Server supports IRQ 2-7 only. 
The QUATECH board must be configured to use one of these IRQ lines.

Since the Quatech serial cables only use six wires, the DTR signal is 
not available on the connector.  Most modems will require an additional 
modem string ("AT&D0" on AT-command modems -- this causes the modem to 
ignore the DTR signal) to work with the QUATECH boards.

Some modems may need further special handling.  

USRobotics Modems 
- Enable the hardware switch on the modem which forces DTR always on. 
  See the USRobotics manual for the changing the setting.  
- Use the "USRobotics (no DTR)" modem selection when configuring the
  Access Server session.

Fastcomm Modems 
- Enable the hardware switch on the modem to force DTR always on. 
  See the Fastcomm manual for changing the setting.  
- Use the "Fastcomm (no DTR)" modem selection when configuring the
  Access Server session.

For direct connections (no modem), the "Started By" and "Ended By" 
must both be set to "Always Connected" on the remote side.

On Pentium and many 486 systems using OS/2 2.11, you will need the Fix
Pack mentioned at the top of this file.

If you are using OS/2 Warp or OS/2 2.11 with the Fix Pack, you should 
include the command "VME=NO" at the top of your CONFIG.SYS file.


