
NetRemote for Windows


Copyright 1994 by McAfee, Inc. All rights reserved.


==============================
Part Three: Reference Material   
==============================
   
24.0  Error Messages   
   
This appendix lists all of NetRemote's error messages and their explanations.   
   
  
24.1 Windows Error Messages   
   
Access Denied, Listener has access turned off.   
	Caller cannot access the listener until listener has access enabled.   
   
Access Denied, Your call was not accepted by the remote user.   
	Listener did not accept the call.   
   
Access Fails!   
	Caller cannot access the listener.   
   
Access Denied, the password you supplied does not match the PC you are   
attempting to call.   
	You may try again by pressing the Retry button.   
   
Bad Listen Response.   
	The response from the listener is unknown.   
   
Bad Initialization Response.   
	The initialization process between caller and listener did not   
	initialize properly.   
   
Call Failed.   
	The connection has been terminated.   
   
ERROR: NRCALL requires NET3.COM Version 2.0 or later.   
	User needs to update the NETX.COM.   
   
ERROR: Bad serial number.   
	The NetRemote serial number is incorrect.   
   
ERROR: Initialization Error.   
	NetRemote initialization process has failed. User should exit   
	Windows and then re-start Windows.   
   
ERROR: Server has bad NetRemote installation data.   
	User needs to clean up the server and re-install NetRemote.   
   
ERROR: checking if NetRemote is installed on server.   
	User needs to install NetRemote on server before attempting to run   
	NetRemote.   
   
ERROR: trying to determine group rights for server.   
	Bad response from server while trying to determine group rights.   
   
Incorrect or missing NetWare DLLs. You must have the NetWare DLLs version   
1.21 or higher in your search path.   
	NetRemote cannot find the NetWare DLLs required by NetRemote.   
   
Listening-PC has disconnected.   
	Listener closed the current connection.   
   
Listener rejects Caller's access because the password Caller supplied does   
not match Listener's password.   
	Listener can try to enter a new password by choosing the Retry button.   
   
Please make sure you are attached to a NetWare server and run the program   
again.   
	NetRemote cannot locate attached NetWare servers.   
   
Reboot Denied!   
	Listener has reboot function turned off.   
   
The DOS Application is in Background now. Please Use Window Option for   
DOS Applications.   
	NetRemote for Windows is not compatible with full screen DOS in this   
	version. Please change DOS to be a Windowed application.   
   
The DOS application is minimized by NetRemote.   
	User needs to choose Window mode from Display Options for DOS settings.   
   
This demo version has expired. Further execution is not possible.   
	The 30-day demo period has expired.   
   
This program requires Windows 386 Enhanced mode!   
	The current version of NetRemote works only in Windows 386 enhanced   
	mode.   
   
User is not a member of the NetRemote NRCALLERS group on server.   
	User has no privileges as a NetRemote Caller; user can be a   
	NetRemote Listener.   
   
You must either hang up the call or stop listening before you can perform   
this action.   
	NetRemote is in a mode that does not allow user to close the   
	NetRemote window or to exit Windows.   
   
  
24.2 Windows File Transfer Errors   
 
The following errors could occur during the file transfer process:   
   
Access Denied.   
	The Listening-PC does not have file transfer enabled. Enable this   
	option in the Listener Options dialog box.   
   
Cannot Collect Directory Information.   
	The Listening-PC could have lost its network connection, or the   
	floppy drive door is not closed.   
   
Connection Terminated.   
	The Listening-PC has hung up or something caused the call to be   
	canceled. Verify the Listening-PC's status and retry the file   
	transfer.   
   
Create Dialog Error.   
	NetRemote was unable to create the Transfer File dialog box. Check   
	the available memory, and then restart Windows.   
   
General File Error.   
	A problem has occurred with the file. It may be corrupt, or you may   
	not have the necessary rights to read the file.   
   
Initialize Communication Error.   
	There may be a problem with your drivers. Check your version of IPX   
	or check the network cable.   
   
Input File Name Error.   
	Verify that the proper file was selected to transfer. The file name   
	must be a valid name.   
   
Memory Error.   
	There is not enough memory to perform this file transfer.   
   
No Response from Partner.   
	Verify that the Listening-PC is ready to receive a call or that no   
	one else is controlling that PC remotely.   
   
Read File Error.   
	A problem has occurred with the file. It may be corrupt, or you may   
	not have the necessary rights.   
   
Receive Unknown Response.   
	There is a possible problem with the driver. Close the dialog box   
	and retry file transfer.   
   
The File Transfer is still in progress. Please cancel the File Transfer   
process first.   
	You cannot exit NetRemote while a file transfer is taking place.   
	Please cancel the file transfer process before exiting.   
   
The File Transfer is still in progress. Please exit the program later.   
	You cannot exit NetRemote while a file transfer is taking place.   
	Please wait until the transfer is complete and then exit.   
   
Write File Error.   
	A problem has occurred with the file. It may be corrupt, or you may   
	not have the necessary rights to write to the file.   
   
  
The following lists possible error messages that could appear in the File   
Transfer Error Report.   
   
All or part of the path is invalid.   
	Check the path of the file being transferred or the path to which   
	the files are being transferred.   
   
An unspecified error occurred.   
	There is a problem with your rights and attributes. You must have   
	read, write and file scan rights; the file must be flagged read/write.   
   
Open file error.   
	There is a problem with your rights and attributes. You must have   
	read, write and file scan rights; the file must be flagged read/write.   
   
Read file error.   
	There is a problem with your rights and attributes. You must have   
	read, write and file scan rights; the file must be flagged read/write.   
   
Share.exe was not loaded, or share region was locked.   
	Make sure this file is in CONFIG.SYS. If it is not, add it and reboot. 
	Then retry the file transfer process.   
   
The drive is full.   
	There was not enough space to transfer the files. Free up some space   
	or change destination for files. Then retry the file transfer.   
   
The file already exists. Upload doesn't allow overwriting.   
	You cannot overwrite files when transferring files from the   
	Calling-PC to the Listening-PC. Delete the file and retry the file   
	transfer.   
   
The file could not be accessed.   
	Verify that you have the proper rights and that the files are   
	flagged as read/write.   
   
The file could not be located.   
	The wrong path was specified in the transfer file dialog box or the   
	file does not exist. Check the location and retry the file transfer.   
   
The permitted open files was exceeded.   
	Change the file handles in CONFIG.SYS to be greater and reboot.   
	Then retry the file transfer.   
   
There was a hardware error.   
	Check your system and the Listening-PC's network cable.   
  
Write file error.   
	There is a problem with your rights and attributes. You must have   
	read, write and file scan rights; the file must be flagged read/write.   
   
You selected not to overwrite the existing files.   
	The file already exists and you chose not to overwrite the file.   
	Either rename or delete the file or choose to overwrite it.   
   
   
24.3 NRLISTEN Error Messages   
   
ERROR 1: IPX.COM V2.1 or greater not found.   
	The IPX version found is less than 2.1. Please upgrade to version   
	2.1 or later.   
   
ERROR 2: Bad product info.   
	Executable is corrupt. Reload product using original distribution   
	diskette. If this does not correct the problem, contact McAfee   
	Technical Support.   
   
ERROR 3: Argument unknown.   
	The argument you used is unknown to NetRemote. Check documentation   
	for correct usage.   
   
ERROR 4: Bad command line syntax.   
	The syntax you have specified is incorrect; check your documentation   
	for correct usage.   
   
ERROR 5: NRLISTEN already loaded.   
	NRLISTEN is already loaded into memory.   
   
ERROR 7: Bad INIT, code xx.   
	NRLISTEN is having difficulty initializing the network. Check your   
	network for errors and reload program.   
   
ERROR 8: Bad install function, code xx.   
	Executable is corrupt. Reload software from original distribution   
	diskette. If you still encounter this error, contact McAfee   
	Technical Support.   
   
ERROR 10: Could not TSR, code xx.   
	Executable is corrupt. Reload software from the original distribution   
	diskette. If you still encounter this error, contact McAfee   
	Technical Support.   
   
ERROR 11: Incompatible version of NRLISTEN loaded.   
	You have loaded a version of NRLISTEN that is incompatible; load a   
	newer version.   
   
ERROR 12: NRLISTEN not loaded. No connection to hangup.   
	You have issued the NRLISTEN/HANGUP command and there is no   
	connection to hangup.   
   
ERROR 13: NRLISTEN not busy. No connection to hangup.   
	You have issued the /HANGUP command and there is no connection to   
	hangup.   
   
ERROR 14: NRLISTEN not loaded. Nothing to unload.   
	You have issued the NRLISTEN/UNLOAD command, but NRLISTEN is not   
	loaded.   
   
ERROR 15: NRLISTEN not idle. Can't unload.   
	You have issued the NRLISTEN/UNLOAD command, but NRLISTEN is in use;   
	therefore, you cannot unload the TSR.   
   
ERROR 16: Can't attach to file server.   
	NRLISTEN was unable to login to the file server. Check that the file   
	server is on-line and available.   
   
ERROR 18: NRLISTEN not last program in memory. Can't unload.   
	You have issued the NRLISTEN/UNLOAD command, but since NRLISTEN was   
	not the last TSR installed in memory, it cannot be unloaded.   
   
ERROR 19: NRLISTEN already loaded. Can't use /HERC option.   
	You have already loaded NRLISTEN. Unload NRLISTEN and reload   
	NRLISTEN with the /HERC option.   
   
ERROR 20: Error retrieving PC Machine information.   
	NRLISTEN was unable to get configuration information about this   
	machine. This error generally occurs on machines with non-standard   
	BIOS or CMOS configuration and should not affect normal operation of   
	NetRemote.  Callers will not have access to the unretrievable   
	information.   
   
  
24.4 NRCALL Error Messages   
	  
ERROR: Bad command line syntax.   
	The syntax you have specified is incorrect or incomplete. Check your   
	documentation for the correct usage.   
   
ERROR: Bad product type.   
	The serialization information in NRCALL is corrupt. Reload the   
	product from the original distribution diskettes.   
   
ERROR: Bad serial number.   
	The serial number for NRCALL is corrupt. Reload the product from the   
	original distribution diskettes.   
   
ERROR: Can't locate current server.   
	The current server has apparently disappeared. Check its availability.   
   
ERROR: Checking if NetRemote is installed on server xxx.   
	NRCALL was unable to check if NetRemote had been installed on   
	server xxx. If NetRemote was previously installed on this server,   
	remove it and re-install it.   
   
ERROR: File NRCALL.PID not found. PC type not available.   
	NRCALL could not find the NRCALL.PID file.  The NRCALL.PID file   
	contains information about different types of PCs and must be   
	available in your search path.   
   
ERROR: Invalid netid type.   
	The ID provided is invalid. Check the various options available   
	with network IDs.   
   
ERROR: NRCALL requires NET3.COM Version 2.0 or later.   
	NRCALL requires NET3.COM V2.0 or later to communicate over the   
	network. You must load a correct version of this software before   
	running any NetRemote programs.   
   
ERROR: Remote PC not responding. Check connection if retry fails.   
	The remote PC is unable to respond within normal time-out values.   
	This can be caused by network overload.   
   
ERROR: Server xx has bad NetRemote installation data. Run UNINSTALL to clean   
up the server.   
	This error can occur if bindery information is corrupt. Use COUT to   
	remove NetRemote, and then use CIN to re-install it.   
   
ERROR: The LISTENING-PC isn't allowing reboot right now.   
	You have tried to reboot the Listening-PC, but the user has   
	the /REBOOT option set to OFF.   
   
ERROR: There is only one server on this network.   
	This error occurs if you only have one server on your network and   
	you request to view other servers. You must install another server   
	to use this option.   
   
ERROR: Trying to determine group rights for server xxx.   
	NetRemote was unable to access information concerning the NRCALLERS   
	group on server xxx. Use SYSCON to determine if the group exists and   
	if the appropriate users are members.   
   
ERROR: Unable to contact local server. Check availability.   
	Your server has probably gone down or is unavailable for some reason. 
	Check its status.   
   
ERROR: Unknown argument id.   
	The argument you used is unknown to NetRemote. Check the   
	documentation for correct usage.   
   
ERROR: Unknown argument processing xx.   
	The argument you used is unknown to NetRemote. Check the   
	documentation for correct usage.   
   
ERROR: /xx is not a valid argument.   
	The argument specified was invalid. Check the documentation for   
	correct usage.   
   
   
   
25.0  Using CONFIG   
   
This appendix explains how to use the CONFIG.EXE program to permanently   
change the options of the NRCALL and NRLISTEN programs.   
   
  
25.1 NRCALL Parameters   
   
The syntax for using the CONFIG.EXE program with NRCALL is:   
   
	CONFIG NRCALL.EXE PARAM VALUE   
   
The table below summarizes the options and values for using CONFIG in   
conjunction with NRCALL.   
   
The lowercase characters indicate user-specified values.   
   
NOTE: Refer to Chapter 5 for detailed explanations of each option.   
  
OPTION   
LPASSWORD=pass   
LKEYBOARD=on/off   
LKEYSTUFF=xxxx   
LOGNAME=name   
LOGPASSWORD=pswd   
ELSFLAG=yes/no   
DISPLAY=xxxx   
MENUKEY=xxxx   
HIGHLIGHT=xxxx   
DIAGS=yes/no   
MAX_CONNS=xxx   
PP_TIMEOUT=x   
CKEYGET=xxxxx   
SILENTEXIT=yes, no   
ALLOBJS=yes/no   
  
  
25.2 NRLISTEN Parameters   
   
The following table lists the NRLISTEN program options.   
   
Lowercase characters in the table indicate user-specified values.   
   
The table also indicates which options can be set via the command line and   
which options can be changed via the CONFIG program.   
   
NOTE: Refer to Chapter 5 for detailed explanations of each option.   
  
OPTION   
LPASSWORD=pass   
TONE=xxxx   
ACCESS=on/off   
REBOOT=on/off   
HERC=on/off   
AUTOBOOT   
MEMORY=xxx   
RING=x   
SUSP_DUR   
PROC_DUR   
HIWATER   
LOWWATER   
   
   
  
26.0  CO/Session Utilities   
   
This appendix explains CO/Session's advanced utilities.   
   
				 
26.1 Removing CO/Session from Memory   
   
Run SUNLOAD locally to unload CO/Session from memory on your PC and return   
the memory to DOS. If the Windows driver RWIN.EXE is in memory, it is also   
unloaded.   
   
NOTE: You should run all utilities from the CO/Session install directory   
(usually C:\REMOTE or C:\HOST). If the CO/Session data files (SESSION.CFG,   
SESSION.MDM, etc.) are in a different directory than the CO/Session install   
directory, then you may have to use the Directory Options command line   
arguments (refer to Chapter 27).   
   
You can also run SUNLOAD remotely during a CO/Session connection to unload   
the Host software from the Host PC's memory.   
   
26.1.1 Unloading CO/Session Remotely   
   
To unload and disable CO/Session on the Host PC from a Remote PC, run   
SUNLOAD remotely on the Host PC. When you do this, CO/Session will   
disconnect and unload from memory on the Host computer.   
   
   
26.2 Unloading Windows Driver Only (Remote Only)   
   
If you have loaded the RWIN driver into memory, then you can use RWUNLOAD   
to unload RWIN without unloading REMOTE.   
   
  
26.3 DOS Level Security (Host Only)   
   
SafeGuard provides dial-in security that lets a Host User restrict DOS   
access on their PC. SafeGuard uses the Directory Access Restriction from the   
Host's Options for all calling Remote users (refer to Chapter 23). If a   
calling user has a Login/Password pair that matches a Login/Password   
pair in a Host Phone Book entry, then Safeguard also applies any Directory   
Access defined in that Host Phone Book entry (refer to Chapter 11).   
   
IMPORTANT: DO NOT prevent access to the directory where CO/Session Host is   
installed (for example, C:\Host); doing so disrupts CO/Session's operation.   
   
SafeGuard is designed primarily to restrict DOS access only when an active   
CO/Session connection is in progress. With SafeGuard, a Remote user may not   
access any drive or directory (either from DOS or from within application   
programs on the Host PC) that is not permitted by the Directory Access   
specifications. Without SafeGuard, Directory Access Restriction only   
restricts file and directory access through the CO/Session File menu.   
		     
SafeGuard also supports a command-line option -a that always restricts DOS   
access, even when there is no active CO/Session connection. The -a option   
still requires CO/Session to be loaded, and furthermore, the default   
CO/Session directory must be permitted as specified in the Directory Access   
Restriction.   
   
SafeGuard requires about 3.7K of RAM and is not unloaded from memory by   
re-booting.   
   
NOTE: You must load SafeGuard before loading CO/Session.   
   
To load SafeGuard on the Host for use only when a CO/Session connection is   
active, enter the following at the DOS prompt:   
  
	SAFEGUARD   
   
To load SafeGuard on the Host for use always, even when a CO/Session   
connection is not active, type the following command at the DOS prompt:   
   
	SAFEGUARD -A   
   
   
   
27.0  Advanced Topics   
   
This appendix describes how you can adapt CO/Session to meet your specific   
needs. It also describes shortcut operations.   
  
   
27.1  Introduction   
   
CO/Session can be used in a variety of environments with a range of   
applications. This appendix describes some ways to adapt CO/Session to   
varying needs. It also describes advanced features that, to simplify   
instructions, were not discussed elsewhere. Topics include:   
   
o  Power Use Features   
	- Command Line Options   
	- Keyboard Shortcuts   
	- Automatic Batch Execution   
o  Compatibility Issues   
	- Remote Mouse Operation   
	- 43/50 Line Text Modes   
	- 3270/5250 Emulation Software   
	- DESQview Multiuser Support   
o  Other Useful Information   
	- Host Memory Use and Expanded Memory Operation   
	- Extended Memory Operation   
   
NOTE: The Host and Remote software work cooperatively to provide remote   
control. Thus, to use some CO/Session features, you may need to understand   
procedures for either the Host PC or Remote PC (or both). This appendix,   
therefore, discusses topics for both Host and Remote programs. If a topic   
applies to only certain programs, the relevant programs are noted.   
   
   
27.2 Command Line Options   
   
CO/Session's operation can be modified in many ways by adding optional   
arguments to the command line. These arguments, unlike the setup Options   
you choose through the Options menu, are effective only for the session   
being started.   
   
This section describes the available command line arguments.   
   
USER TIP: For ease of use, the command line arguments can be placed in a   
batch file.   
   
27.2.1 Directory Options (Host and Remote Use)   
   
CO/Session can be installed in different environments. This section describes   
some of the options, including network installation.   
   
CO/Session can be installed on any drive and in any directory. Furthermore,   
the CO/Session data files can be stored in a different directory than the   
CO/Session install directory.   
   
IMPORTANT: The CO/Session data files consist of: Phone Book (SESSION.RMP),   
Options (SESSION.CFG), Terminal Options (SESSION.100 and SESSION.102) and   
Modem configuration files (SESSION.MDM). If you move any of the data files   
to a different directory, then you must move all of the data files.   
   
If you want to either load CO/Session from a directory that is not the   
install directory or use SESSION.xxx data files in a different directory,   
then the following options must be used:   
   
-ed:path  where d: specifies the drive where CO/Session is installed, and   
path specifies the directory where CO/Session is installed. (This is not   
required for Host Utilities.)   
   
-dd:  where d: specifies the drive where the data files (SESSION.xxx) are   
installed.   
   
-ppath  where path specifies the path where the data files (SESSION.xxx) are   
installed.   
   
For example, the command:   
   
	REMOTE  -eF:\COS  -dF:  -p\COSJONES   
   
loads Remote from drive F: and directory \COS, and uses the CO/Session data   
files from F:\COSJONES.   
   
Likewise, the command:   
   
	HOST  -dC:  -p\MYPHONES -cSALESNYC   
   
loads Host from the current directory on drive C: and makes a call (because   
of the -c argument) using the SALESNYC Phone Book entry from the Phone Book   
in C:\MYPHONES.   
   
IMPORTANT: If CO/Session data files are moved to a different directory than   
the install directory, the directory option arguments must also be used with   
the PHONE, OPTIONS, PRINTO, and TCONFIG utilities. For instance, assuming the   
environment used in the previous example, you would access the Phone menu   
utility with the command:   
   
	PHONE  -dF:  -p\COSJONES.   
   
NOTE: For convenience, put the command lines with appropriate directory   
arguments into batch files. However, note that if a batch file is in the   
same directory as the program it executes, then the batch file must have a   
different root name than the program. For example, you cannot have a batch   
file named HOST.BAT in the same directory with HOST.EXE.   
   
27.2.2 Networks   
   
CO/Session Host and/or Remote can be easily installed on a LAN file server.   
However, if individualized data files (Phone Books, Options, etc.) are   
needed, each user will need a separate CO/Session data directory. This will   
require using the options described earlier for specifying the disk drive   
and directory.   
   
27.2.3 Floppy Drive  
   
CO/Session can be installed and executed from a floppy drive. For example,   
the command below loads Remote from the root directory of the diskette in   
drive A:   
   
	REMOTE  -eA:\  -dA:  -p\   
   
27.2.4 Automatic Access to Call Menu (REMOTE or HOSTMENU)   
   
When disconnected, most of your activity is in the Call menu. If you invoke   
REMOTE or HOSTMENU with the -k option, the Call menu displays when you press   
the hot keys (instead of the Main Menu). This reduces the number of   
keystrokes required to initiate a Call, Wait for a Call, or edit the   
Phone Book.   
   
Examples:   
   
To load Remote menu system:   
   
	REMOTE  -k        
   
To load Host menu system:   
   
	HOSTMENU  -k   
   
After a connection is established, press the hot keys to display the Main   
Menu.   
   
27.2.5 Special Operation Options   
   
You can modify some operations of the Host and Remote programs at load time   
by using the -oN command-line option, where different N values cause   
different effects. The following describes these effects:   
   
NOTE: You can add the N values together for a combination of options. For   
example, -o10  if you want option 2 and 8. Also, some options do not work   
with both Host and Remote programs, but, in some cases, using options when   
loading the Host software can affect Remote operation while connected.   
   
o  N=1 - If you do NOT want CO/Session to cycle back to auto-answer mode   
after every call, use this option. Normally, CO/Session cycles back to   
auto-answer after every connection if it was originally put in auto-answer   
mode.   
   
o  N=2 - (Host only) If you want CO/Session to always take over the printing   
BIOS vector when the remote printing option is selected, even when not   
connected, use this option. Normally CO/Session takes over the printing BIOS   
vector for remote printing only when there is an actual connection.   
Typically, this option is required with network print spool utilities that   
are loaded after CO/Session.   
   
o  N=8 - (Host only) If you do NOT use a Hercules compatible graphics card   
and CO/Session beeps when you try to hot key to menus or totally garbles the   
remote PC screen, use this option.   
   
o  N=16 - If your PC locks up when loading CO/Session. Some PC clones with   
certain BIOS types do not support the clock initialization CO/Session attempts   
when loading, use this option (it inhibits this clock initialization).   
  
o  N=32 - (Host only) If you have a Hercules compatible video card and the   
remote screen displays improperly when in Hercules graphic mode, use this   
option.   
   
o  N=64 - (Remote only) If, when you are using REMOTE.EXE and you are   
currently connected, your PC locks up when you enter the CO/Session menus,   
use this option. This problem has been found to occur on Tandy1400 laptops.   
   
o  N=128 - (Host only) This causes CO/Session to get the current cursor   
position via BIOS rather than directly via hardware. If, when you remotely   
execute a particular application, the REMOTE.EXE screen does not get updated,   
try this option.   
   
o  N=256 - (Host only) This causes CO/Session to adjust its timing handling   
to assume one timer interrupt every 5 milliseconds versus every 55   
milliseconds. This assumes an increase of about 12 to 1; you would use this   
option with an Alloy NTNX system.   
   
o  N=512 - To toggle the OUT1 bit in the UART Modem Control Register when   
initializing the port. This is used by some internal modems as a hardware   
reset.   
   
o  N=1024 - If using a mouse driver on HOST and, when connecting, you want   
the REMOTE mouse driver to be initialized to the HOST mouse driver state.   
HOST and REMOTE mouse drivers may need to be the same version; this is   
useful if connecting to a mouse driven application already active on the HOST.   
   
o  N=2048 - To inhibit a disconnect if a time-out occurs on the "other end OK"   
message exchange. By default, if CO/Session does not receive an "other end OK"   
message at least once per minute it will assume a problem and disconnect.   
   
o  N=4096 - (Host only) If Host is AT&T 6300 series or compatible and/or the   
Remote, when connected, scrolls improperly and displays to use a 43-line   
display mode, then use this option with the Host application.   
   
o  N=8192 - (Host only) If the Remote PC, when connected, scrolls improperly,   
and changing the Host Hardware Option Special Console Driver (available   
through OPTIONS) has no effect (after restarting the connection), then use   
this option with the Host application.   
   
o  N=16384 - (Remote only) Prevents Remote PC from issuing a Mode command   
from the Host if the Mode is already the same. This is useful when loading   
alternate fonts manually to the Remote to match fonts used on the Host; a   
Mode command would clear the font.   
   
CO/Session supports six other special operation options:   
   
o  -f - causes flow control to stop receiving data prior to any file   
transfer disk I/O. If you experience transmit or receive errors during file   
transfers, particularly at speeds greater than 2400BPS and/or on LANs when   
doing I/O to the file server, try loading with the "-f" option.   
   
o  -h - (Host only) causes HOST to swap to its own Program Segment Prefix   
(PSP) before making any DOS calls. This may resolve problems encountered   
when the foreground application uses up all available file handles leaving   
none free for HOST.   
   
o  -lxxx - (Remote only) enables logging, where xxx is an optional operator   
ID.   
   
o  -n - (Host only) use with EMSHOST.EXE on the Host if you are not sharing   
the expanded memory page with any application. This allows EMSHOST to avoid   
having to constantly save and restore the EMS map whenever it processes   
an interrupt.   
   
o  -q - (Remote only) used in conjunction with REMOTE -C, inhibits any   
display of menu screen during call attempt (i.e., is a "quiet" mode).   
Syntax: REMOTE -C -Q   
  
o  -s - (Host only) use this option with the Genius 66-line display mode.   
   
27.2.6 Auto-Dial and Foreground Operation Option (REMOTE Only)   
   
REMOTE.EXE can be invoked with the command-line option -c (for Call), which   
causes a dial-out without having to go into the menus. It also loads REMOTE   
in a foreground mode.   
   
IMPORTANT: CO/Session cannot already be loaded as a TSR to use this option.   
   
You may optionally specify a Phone Book name. For example:   
   
	REMOTE  -cHEADQTRS   
   
This will cause REMOTE.EXE to load and dial out based on the parameters in   
the Phone Book entry "HEADQTRS."   
   
If no entry is specified, then the "DEFAULT" entry is used.   
   
As mentioned, REMOTE.EXE in this mode acts as a foreground program. After   
disconnecting from a successful call or if the connect attempt fails for any   
reason, REMOTE.EXE exits back to DOS. It does NOT become a TSR.   
   
During a connection, you may still hot key to the Main Menu to perform any   
of the CO/Session Remote functions except Suspend.   
   
NOTE: The HOST and EMSHOST programs also have a -c call argument, but this   
only causes the programs to call the indicated Phone Entry; it does not cause   
Host foreground operation. Refer to the Host User Guide for details.   
   
  
27.3 Shortcut Keys (REMOTE Only)   
   
During a CO/Session connection, a Remote user can control some CO/Session   
features by pressing "shortcut keys," instead of invoking the CO/Session   
menus. The shortcut key combinations are:   
   
<CTRL><ALT> or <CTRL><Left Shift> plus:   
   
o  <F>  Full Speed mode - The Host program runs at full speed. The Remote   
screen is not fully updated until the Host screen stops changing. This can   
speed up operation, especially if quickly keying through menus or screens,   
but it can also slow interactive keystroke response.   
   
o  <H> Hangup - Used on Remote, causes Host disconnect/hangup.   
   
o  <M> Video Mode Synchronize - This shortcut key is useful in two situations:   
	- It switches the video mode to the number specified in Option -   
	Video Mode Synchronize. AutoCad is the only known program that   
	requires this. Use this shortcut key when AutoCad displays a graphic   
	screen.   
	- If using a Hercules compatible graphics card, this command switches   
	between graphics pages 0 and 1. CO/Session can't always determine   
	which graphic page is active with Hercules compatible cards. If you   
	are running a program remotely and the screen stops changing or goes   
	blank, try this shortcut key.   
   
o  <R>Redraw screen - This options redisplays the screen contents.   
   
o  <S> Synchronized mode - The Host and Remote screens remain synchronized.   
Everything displayed on the Host displays on the Remote (opposite of <F>   
above).   
   
o  <T> Fast graphics - When running CGA graphics, every other screen line   
displays. For EGA/VGA graphics, this causes the single bit plane specified   
in the Fast Graphics Option to display. Pressing this key combination   
again will return the display to normal.   
   
o  <U> Mouse control - Toggle between Remote only and Remote and Host mouse   
control. By default the Remote has control of the mouse. If MOUSE.COM is   
loaded on the Host, then this key combination gives the Host mouse control.   
To return control to Remote only, press this key combination again.   
   
  
27.4 Remote Mouse Operation   
   
CO/Session allows the use of a mouse on a Remote PC to operate a mouse-driven   
program on a Host. CO/Session mouse support is compatible with the Microsoft   
Mouse Driver interface and Windows Version 3.x.   
   
If the Remote user wants to use a mouse to control a Host PC program, he or   
she must set Remote Mouse Operation to YES using the Remote Options Menu.   
The user must also have MOUSE.COM loaded on the Remote PC.   
   
Loading MOUSE.COM on the Host PC is optional. If both the Remote and Host   
users need mouse control, however, then MOUSE.COM must be loaded on both the   
Remote and Host PCs.   
  
By default, the Remote PC has control of the mouse. To give mouse control to   
both the Remote and the Host user, the Remote user must press <CTRL><ALT><U>.   
(For the Host user to use a mouse, MOUSE.COM must be installed on the   
Host PC.)   
   
NOTE: CO/Session's mouse support only operates with applications that use a   
mouse via Interrupt 33h calls, which is the Microsoft MOUSE.COM standard.   
This includes most DOS applications that allow mouse operation.   
   
   
27.5  Host Program Versions and Available Memory   
   
The Host software includes three versions of the Host program:   
   
o  HOSTMENU.EXE is a full-menu version of CO/Session. It is described in   
detail in the "HOSTMENU Main Menu Reference" chapter of the Host User Guide.   
It uses 123K of memory.   
   
o  HOST.EXE is a command line version which has no menus. It can use as   
little as 61K of memory to execute. When used in conjunction with the   
utilities described in Chapter 26, it has nearly all the functionality of   
HOSTMENU. It is described in detail in the "Using CO/Session Host" chapter   
of the Host User Guide.   
   
o  EMSHOST.EXE is a command line version like HOST.EXE, but it runs in   
Expanded Memory, using only 5K of conventional memory. It is described later   
in this appendix.   
   
If the Host user has loaded HOSTMENU and a program cannot be run remotely   
due to insufficient memory, then try rebooting the Host and loading HOST   
instead (which leaves more memory available). If you have an especially   
memory-hungry application and there is still insufficient memory, you have   
three options:   
   
o  Check for other memory resident programs or drivers that are being loaded   
by the Host's AUTOEXEC.BAT or CONFIG.SYS. After making a backup, edit either   
(or both) of these files to remove any statements that load programs or   
drivers that are not required. Then, reboot the system and try to load HOST   
again.   
  
o  If the Host is a 386 computer with DOS 5.0, QEMM, or 386MAX, load HOST   
into high memory with the LOADHI command.   
   
o  If the Host system has LIM 4.0 Expanded Memory or is a 386 computer using   
a memory manager like QEMM, and the application does not require CGA   
graphics or data compression on transfers, then use EMSHOST as described   
in the section called "Host Expanded Memory Version - EMSHOST (Host Only)."   
   
  
27.6 Using Extended Memory (HOST and HOSTMENU)   
   
If you have a 386 or 486 based PC, then you may be able to use a LOADHI type   
command (provided by DOS 5.0, QEMM, 386MAX, etc.) to load HOST or HOSTMENU   
into Extended Memory above 640K. This conserves standard memory below 640K   
for other applications. To use a LOADHI command in this way, you need enough   
available Extended Memory to hold the HOST program (50-65K) or HOSTMENU   
program (105K). Refer to the manual for your operating system or memory   
manager for details on using its LOADHI type command to load TSR programs   
into Extended Memory.   
   
  
27.7 Host Expanded Memory Version - EMSHOST (HOST Only)   
   
EMSHOST is functionally equivalent to HOST, but runs in LIM 4.0 compatible   
Expanded (EMS) Memory. When you load EMSHOST, it puts itself into the 640K   
conventional base memory, where it only uses 5K and it automatically loads   
HOST.EXE into Expanded Memory.   
   
27.7.1 Limitations   
   
Unfortunately, the LIM 4.0 Expanded Memory specification imposes constraints   
on memory use that impact EMSHOST. Specifically, when loading EMSHOST, you   
can use all HOST command line arguments, but the only memory argument you   
can use is -m0. This means EMSHOST does not provide remote control support   
for CGA graphics applications, and data compression is not provided on file   
transfers.   
   
27.7.2 Requirements   
   
EMSHOST.EXE requires a LIM 4.0 Expanded Memory Manager (EMM) compatible   
driver software, and for XT and AT PCs and compatibles, it requires Expanded   
Memory compatible hardware. On 386 PCs, LIM 4.0 EMM drivers are available   
from Quarterdeck (QEMM), Qualitas (386 MAX), Microsoft, and others. For XT   
and AT PCs, AST (RamPage), Intel (AboveBoard), and others provide Expanded   
Memory compatible hardware.   
   
One limitation with sharing the Expanded Memory "mappable page frame" with   
an application is that the application may not have any disk I/O to or from   
the page frame. This currently prevents using EMSHOST with WordPerfect or   
Btrieve.   
   
27.7.3  Operation   
   
Except for the limitations described above, you can use EMSHOST just as you   
would HOST (with the -m0 argument). The command to load EMSHOST is:   
   
	EMSHOST argument_list   
   
where argument_list can be any valid Host arguments except -m1, -m2, or -m3.   
Refer to the "Using CO/Session Host" chapter and the "Command Line Options"   
topic at the beginning of this chapter for more details.   
   
NOTE: After EMSHOST is loaded into memory, pressing <ALT><Left Shift> will   
open the Keyboard Chat window (just as it does with HOST).   
   
   
27.8 Automatic Batch Execution (Host Only)   
   
CO/Session can run a batch file on the Host automatically upon connection.   
Specifically, HOST.EXE, EMSHOST.EXE, and HOSTMENU.EXE support a feature that   
automatically executes a named batch file upon a connection. If password   
protection is disabled, CO/Session looks for the file CONNECTE.BAT; if   
password protection is enabled, CO/Session looks for the BAT file named with   
the phone book entry for the matched Login ID and Password.   
   
The limitations are as follows:   
   
o  Batch files must be in the same directory as the other CO/Session files;   
this directory should be part of your PATH command unless the PC will always   
be in the CO/Session directory when connecting.   
   
o  When the connection occurs, CO/Session executes the batch file without   
"knowing" whether the PC is currently at the DOS prompt; if the PC is not at   
the DOS prompt, results are unpredictable.   
   
o  Only alpha or numeric characters from the phone book name, maximum of 8,   
are used. For example, if phone book entry name HQ_CENTRAL contains the   
matched Login ID and Password, then CO/Session will attempt to execute   
HQCENTRA.BAT.   
   
  
27.9 43/50 Line Extended Text Modes   
   
CO/Session supports the extended 43 line text mode on EGA monitors and the   
extended 50 line text mode on VGA monitors. CO/Session detects these modes   
automatically. No special options are required.   
   
  
27.10 3270/5250 Terminal Emulation Software   
   
CO/Session works with most terminal emulation packages for remote access to   
mainframes and minicomputers, as long as the Special Keyboard Handling   
Option is enabled on the Host. If a Remote user needs to run a 3270 product   
remotely, such as DCA IRMA 3270, IDEA Associates 3270, or Attachmate 3270,   
or a 5250 product like DCA SmartAlec or AST 5250, then the Special Keyboard   
Handling Option must be set to YES on the Host.   
   
   
27.11 DESQview Multiuser Support   
   
DESQview from Quarterdeck Office Systems provides a multitasking environment   
for running multiple programs at the same time. CO/Session can operate with   
DESQview in any of the following ways:   
   
o  Load CO/Session REMOTE or HOST before DESQview for remote access outside   
the DESQview environment. If in Host mode, this will allow a Remote user to   
dial in and control the entire DESQview environment. The Remote user will   
have normal remote access capabilities.   
  
o  Load CO/Session REMOTE in a DESQview window for remote access from a   
DESQview window. The Remote user is able to switch control between   
CO/Session and other applications running in DESQview.   
   
o  Set up multiuser dial-in access by loading copies of HOST.EXE in multiple   
DESQview windows. Each HOST must have a unique COM port. For each Remote user   
dialing in, it will look like they have complete control of the computer   
with full screen support.   
   
See the READ-ME file for details on setting up DESQview PIF files and   
operating with Quarterdeck's memory management utility QEMM.   
   
  
27.12  COM Port Addresses   
   
The following table lists the COM port addresses.   
  
COM PORT        INTERRUPT       ADDRESS   
COM1            IRQ4            3F8   
COM2            IRQ3            2F8   
COM3            IRQ4            8E8   
COM4*           IRQ3            2E8   
   
* These are default values, but COM4 can be customized to any IRQ and   
Address (by selecting COM4 in the Port Number field of a Phone Book Entry).   
   
   
   
28.0  Modems and Cables   
   
Many technical support calls concern modems which are not installed properly   
or port parameters which are not specified correctly. Therefore, before you   
call, please read this section.   
   
  
28.1  Cabling Pin Arrangements (Modem & Direct)   
   
25 PIN                                          Modem   
   
XMIT    2 -----------------------------    2    XMIT   
RCV     3 -----------------------------    3    RCV   
RTS     4 -----------------------------    4    RTS    
CTS     5 -----------------------------    5    CTS    
DSR     6 -----------------------------    6    DSR    
GND     7 -----------------------------    7    GND    
DCD     8 -----------------------------    8    DCD    
DTR     20 -----------------------------  20    DTR   
   
   
9 PIN                                           Modem   
   
DCD     1 -----------------------------    8    DCD   
RCV     2 -----------------------------    3    RCV   
XMIT    3 -----------------------------    2    XMIT   
DTR     4 -----------------------------    20   DTR   
GND     5 -----------------------------    7    GND   
DSR     6 -----------------------------    6    DSR   
RTS     7 -----------------------------    4    RTS   
CTS     8 -----------------------------    5    CTS   
RI      9 -----------------------------    22   RI    
   
Direct Connect Cables (Null Modem)   
   
25 PIN                                          25 PIN   
   
XMIT    2 -----------------------------    3    RCV   
RCV     3 -----------------------------    2    XMIT   
RTS     4 -----------------------------    5    CTS    
CTS     5 -----------------------------    4    RTS    
DSR     6 -----------------------------    20   DTR   
GND     7 -----------------------------    7    GND    
DTR     20 -----------------------------   6    DSR    
   
9 PIN                                           9 PIN   
   
RCV     2 -----------------------------    3    XMIT   
XMIT    3 -----------------------------    2    RCV   
DTR     4 -----------------------------    6    DSR    
GND     5 -----------------------------    5    GND   
DSR     6 -----------------------------    4    DTR   
RTS     7 -----------------------------    8    CTS    
CTS     8 -----------------------------    7    RTS    
   
9 PIN                                           25PIN   
   
RCV     2 -----------------------------    2    XMIT   
XMIT    3 -----------------------------    3    RCV   
DTR     4 -----------------------------    6    DSR    
GND     5 -----------------------------    7    GND   
DSR     6 -----------------------------    20   DTR   
RTS     7 -----------------------------    5    CTS    
CTS     8 -----------------------------    4    RTS    
   
  
28.2 Modem Selection   
   
If the modem you are using is on the CO/Session modem list, then choose it   
as described in the instructions for the Phone Book Menu in Chapter 11. If   
the modem you are using is not listed, do the following:   
   
1.  If you are using a modem that does not use DIP switches to define DTR   
    (Data Terminal Ready) and DCD (Carrier Detect) handling, then choose   
    Hayes Extended as your modem type.   
   
    Set the baud rate to match the highest speed of your modem (e.g., 1200,   
    2400).   
   
2.  If you are using a modem with DIP switches for DTR and DCD, then check   
    the switch settings as described below and choose Hayes Basic as your   
    modem type.   
   
    Also, read the following sections to make sure your modem is installed   
    and configured correctly.   
   
  
28.3  Customized Modem Control Strings   
   
CO/Session provides a long list of predefined modems. Each modem definition   
is composed of a series of modem strings and a series of YES/NO switches   
that define how characters are sent and received from the modem, and how   
certain modem operations are invoked. You can customize each of the modem   
types to control any asynchronous modem as well as to "script" connections   
through PBXs, modem pools, or X.25 public PADs, over leased lines, or   
literally to any device that requires a text "handshake." The strings of any   
of the modems can be edited, including having their name changed.   
   
CO/Session provides eight modem types called Custom1 through Custom8 that   
are blank. It is suggested that Custom1 through Custom8 be used to add   
modems or scripts that are not otherwise provided by CO/Session. Look at the   
predefined modem strings for detailed examples. All of the modem strings are   
stored in the file SESSION.MDM.   
  
Use the following procedure to edit existing strings or define custom strings.   
   
1.  Choose the Phone Book Add or Change function.   
   
2.  Choose the modem parameter.   
   
3.  Use the arrow keys or the mouse to highlight the modem selection you   
    want to edit.   
   
4.  Press <F1> to view or change the modem string.   
   
5.  Use arrow keys to change fields.   
   
     Within each field, the default mode is overtype. If you want to insert   
     characters,  press <INSERT>. Press <INSERT> again to end insert mode.   
     <DEL> will delete characters.   
   
6.  When you are finished, press <F10> to exit and save your changes. Press   
    <ESC> to exit without saving your changes.   
   
28.3.1 Special Characters  
   
When defining the modem strings, several characters have a special meaning.   
These are as follows:   
  
~       : 1/2 second delay   
,       : 2 second delay   
\       : carriage return   
|       : line feed   
@       : send a break signal   
^       : control  (e.g., ^A = <CTRL> A)   
]       : end-of-string (terminates the string)   
;       : wait for response delimiter   
#xxx    : wait for xxx seconds for defined response, 1-999 are valid values   
?       : insert ring count, example, S0=?; the ring count is set with   
	  Option - Answer on Ring Count.   
   
To have any of the special characters above treated normally, precede the   
character with the slash character "/" (e.g., /@). To have "/" treated   
normally, specify it as //.   
  
28.3.2  String Descriptions   
   
The strings that can be defined are as follows:   
   
o  MODEM NAME - this is the name displayed in the modem window and the Phone   
Book entry modem field.   
  
o  INITIALIZE - this string is used first on a Call, on a Wait For Call, and   
on "voice first" Voice connection when switching to data mode.   
  
o  DIAL PREFIX - this string is used on a Call after the INITIALIZE string   
and before the string in the phone number field of the current phone book   
entry.   
  
o  DIAL SUFFIX - this string is used on a Call after the string in the phone   
number field of the current phone book entry.   
  
o  AUTO-ANSWER - this string is used on a Wait For Call after the INITIALIZE   
string.   
  
o  DISCONNECT - this string is used on a Hangup and after the user has   
picked up the telephone handset on a Voice Switch.   
  
o  VOICE SWITCH - this string is used on a Voice Switch before the user is   
asked to pick up the telephone handset.   
  
o  DATA SWITCH-ORIG - this string is used on a Voice Switch when switching   
to data mode and after the INITIALIZE string on a "voice first." It is used   
for the originating side of the connection.   
  
o  DATA SWITCH-ANSW - this string is used on a Voice Switch when switching   
to data mode and after the INITIALIZE string on a "voice first." It is used   
for the answer side of the connection.   
  
o  CONNECT RESPONSE - this string defines the minimum time expected in the   
connect response message receive on a Call, Wait For Call, and Voice Switch   
when switching to data mode.   
  
o  INTER-CHAR DELAY - this is a YES/NO field which defines whether characters   
sent to the COM port are to be spaced at 200 millisecond intervals or sent as   
fast as they can be by CO/Session. This option is necessary for some modems   
that are sensitive to the speed at which characters are sent.   
  
o  FIX BAUD RATE - this is a YES/NO field which defines whether CO/Session   
should change its baud rate based on the connection speed of the modem. Some   
modems with compression can have an effective throughput of greater than 9600   
baud even though the connection between the modems is at 9600 baud. To   
achieve this increase in speed, the characters must be sent from CO/Session   
to the modem at the higher baud rate--19,200 baud in many cases. The modem   
then compresses the data and transmits it at 9600 baud. The effective   
throughput is greater than 9600 baud because of the compression the modem   
achieves.   
   
o  H/W FLOW CONTROL - this is a YES/NO field which defines whether the modem   
uses RTS/CTS hardware flow control. Most modems do not use RTS/CTS flow   
control; MNP error correcting modems and many multiplexers do. If you are   
using an MNP modem or a multiplexer, you should set this field to YES.   
   
  
28.4 Debugging Modem Strings   
   
There are two ways to debug modem strings:   
   
o  Use CO/Session's COM Port Window function to manually enter modem strings   
to be sure they work.   
   
o  Turn the COM Port Monitor Option ON. Then, when you choose CALL or WAIT   
FOR CALL, you can watch commands sent and data received from the modem.   
   
  
28.5 Modem Switch Settings   
   
CO/Session needs to control and know the condition of your modem and phone   
line. This requires switches on your modem to be set properly. If your modem   
has switches, check the following:   
   
o  DTR - Data Terminal Ready - must be controlled by CO/Session and NOT set   
to be always true or ignored. CO/Session uses DTR to tell the modem it is   
ready to connect. If your modem has a switch to force DTR to always be true   
or for the modem to ignore DTR, it must be disabled.   
   
o  DCD - Data Carrier Detect (or CD) - CO/Session uses this to sense complete   
connections. Modem must be set to recognize the actual line state and NOT   
force CD to be true or ignored.   
   
The following is a list of some specific modem switch settings:   
   
o  Hayes 1200 - Switches 3 & 8 down, all other switches up.   
o  Hayes 1200B internal - Switch 3 down, all others up.   
o  Hayes 2400 - no switches.   
o  U.S. Robotics Courier HST/DUAL/V.32 - Switches 1, 2, 4, 6, 7, 10 up, all   
others down.   
o  U.S. Robotics Sportster,2400E - Switch 1 & 6 off, all others on.   
o  U.S. Robotics Sportster MNP - All switches up.   
o  Microcom AX - Front switches 2 & 8 down, rear switches 6 & 7 down, all   
others up.   
o  Microcom QX - Front switches 2, 3 & 8 down, rear switches 2, 3, 6, 7 & 8   
down, all others up.   
o  Multitech 224E - Bottom switch 1 up. Inside switch 1 down. RTS jumper set   
to Normal.   
   
  
28.6 Verifying that Your Modem is Installed Correctly   
   
If you cannot get CO/Session to dial or to answer and you have tried all the   
suggestions in this section, then do the following:   
   
1.  From the Main Menu (HOSTMENU or REMOTE), choose Call Menu.   
   
2.  Highlight the Phone Entry you have been using.   
   
3.  Choose Open COM Window.   
   
4.  Type ATZ and press <ENTER>.   
   
    The modem should respond with OK. If ATZ does not appear when you type it,    
    press <F7>.   
   
5.  Type ATDT followed by the phone number and press <ENTER>.   
   
    The modem should dial the phone number.   
   
    If steps 4 and 5 succeed, then your modem functions properly and is   
    connected to the computer correctly. Call technical support.   
   
If either step 4 or 5 fails, then either something is wrong with your modem,    
cable, or port parameters you have defined in the Phone Entry, or you may   
have a port conflict.   
   
   
   
29.0  Troubleshooting   
   
If you encounter problems using CO/Session, this appendix should help you   
isolate the problem and resolve it. Many special situations can be addressed   
through command line arguments, which are described in detail in this   
appendix.   
   
If these efforts do not resolve your problem, please call technical support   
for assistance.   
   
  
29.1 Keyboard Problems   
   
Many technical support questions concern the keyboard and not having   
keystrokes on the Remote recognized on the Host. In other words, a Remote   
user can see what is happening on the Host but cannot control it. Below are   
some typical problems and solutions.   
   
PROBLEM: My keyboard does not work. I'm working on the Remote and my   
keystrokes are ignored.   
	EXPLANATION: The Host is running a program that has taken control of   
	the keyboard and, therefore, CO/Session is not seeing the keystrokes   
	you type. On the Host set the configuration Option - Special Keyboard   
	Handling to YES. DESQVIEW and almost all emulation hardware and   
	software products, such as 3270 and 5250 products, require this   
	option.   
   
PROBLEM: When I type on a Remote PC, my keystrokes are displayed slowly.   
	 EXPLANATION: First, understand that when communicating between   
	 computers the keystrokes are slower because of the speed of the   
	 modem. With some high-speed modems, the keystrokes may appear in   
	 bursts. This is due to the modem buffering data as it is received   
	 and sending it out in "packets." For best keystroke response, you   
	 should run in SYNC mode, not FULL SPEED mode. The SPECIAL KEYBOARD   
	 HANDLING option will also slow down the display of keystrokes and   
	 should be turned OFF when using an application that does not   
	 require it.   
   
  
29.2 Modem Problems   
   
If you suspect modem problems, you should review these problems and cures.   
If you do not find your problem, refer to Chapter 28 for further information.   
You may find the COM Port Monitor function is also very useful for   
troubleshooting modem problems.   
   
PROBLEM: When I press <F6> to disconnect, my line does not hang-up and my   
modem does not reset.   
	EXPLANATION: The DTR switch on your modem is set incorrectly. Your   
	modem is ignoring the DTR signal from CO/Session. Check your modem   
	manual to change the DTR switch. If your modem has no switches, then   
	use the Hayes Extended modem setting in your Call ID.   
   
PROBLEM: My modem will not dial.   
	EXPLANATION: This may be a DTR problem. See the previous explanation.   
   
PROBLEM: When the other computer disconnects, my modem does not disconnect   
the line.   
	EXPLANATION: The DCD or CD switch on your modem is set incorrectly.   
	Your modem is assuming that CD is always true and does not recognize   
	that the line has disconnected. Use your modem manual to change the   
	DCD or CD switch. If your modem has no switches, then use the   
	Hayes Extended modem selection in your Phone Entry.   
  
PROBLEM: When I try to CALL or WAIT FOR CALL, CO/Session immediately fails.   
	EXPLANATION: An immediate failure indicates CO/Session is not able   
	to make contact with the modem. This is probably due to a port   
	conflict, which occurs when two or more cards in the computer have   
	the same port address or when CO/Session is directed to the wrong   
	port. Many add-on cards and internal modems have switches to define   
	COM port assignments. The COM port can be 1, 2, 3 or 4 and no two   
	cards can have the same assignment. You should verify that this is   
	the case.   
   
	Another possibility is that you have the wrong port number in the   
	Phone Entry you are using. Make sure the Port number in the Phone   
	Entry matches the port number to which the modem is connected.   
   
PROBLEM: My computer does not answer incoming calls or the other computer   
does not answer my call.   
	EXPLANATION: First verify the phone number. Next, verify that each   
	modem is connected properly to its PC and phone line. For CO/Session   
	to answer a call it must be in WAIT DIAL- IN mode. If this fails you   
	may have an incorrect port, modem type, or baud rate specified. If   
	using the Call Menu, be sure you are highlighting the right Phone   
	Entry before selecting Wait For Call. If you set CO/Session to   
	automatically Auto Answer then be sure the DEFAULT Phone Book Entry   
	has the correct Port Parameters.   
   
   
PROBLEM: I dial out at 2400 Baud and the connection is made at 1200 Baud.   
	EXPLANATION: The remote modem may be a 1200 Baud modem or, if the   
	remote computer is set for automatic Auto Answer, then the DEFAULT   
	Phone Book Entry may not be set for 2400 Baud.   
   
  
29.3 Problems With Direct Connect   
   
If you are unable to make a connection with a direct cable, then check the   
following:   
  
1.  The Phone Book Entry used on both computers must be set for the same   
    baud rate.   
   
    Each entry must also be set for the proper port and a modem type of   
    Direct Connect.   
   
2.  One machine must be in a Wait for Call Mode.   
   
3.  The Cable being used must be a null-modem cable as defined in Chapter 28.   
   
    To verify that items 1 and 3 are correct, the COM Window can be opened   
    on both machines (using the Call Menu). Any keystrokes typed on one   
    machine should appear on the other.   
   
IMPORTANT: If CO/Session is set to Auto Answer automatically, it uses the   
DEFAULT Phone Entry, which must have the correct port and baud rate and a   
modem type of Direct Connect.   
   
   
29.4 Slow Scrolling and Slow Screen Updates   
   
PROBLEM: Whenever the display on the Host scrolls, the entire screen on the   
Remote is redrawn or is very slow in updating.   
	EXPLANATION: CO/Session should scroll the display on the Remote   
	quickly. If this is not occurring, the Host is probably using a   
	console device driver like ANSI.SYS. Check the Host PC's CONFIG.SYS   
	file for a command line like device = ANSI.SYS. If such a line exists,   
	and the Host is using DOS 4.01 or earlier, then on the Host, set   
	Option - Special Device Driver to YES or AUTO. If Special Device   
	Driver is set to YES and the display is slow, try setting it to NO.   
	(For DOS 5.0 or later this should always be set to NO.)   
   
	If this does not solve the problem, then use the -o8192 special   
	option (i.e., start the Host program using either HOST -08192 or   
	HOSTMENU -o8192).   
   
PROBLEM: The Remote screen is updating slowly in Full Speed mode.   
	EXPLANATION: There is probably something constantly changing on the   
	screen like a clock. The Remote user should switch to Synchronous   
	mode by pressing <Ctrl><ALT><S>.   
   
  
29.5 File Transfers   
   
In general, you get the best file transfer performance with CO/Session if   
you use CO/Session's data compression to transfer uncompressed files. File   
transfer speed is adversely effected if you let CO/Session use file   
compression during the transmission of files that are already compressed   
(e.g., "arc'ed" or "zipped" files).   
   
Before transferring an arc'ed file, the Remote user should press <ALT><O> at   
the File Transfer main screen and change the File Compression option to OFF.   
   
CO/Session's compression works fine with the MNP level 5, V.32bis, and   
V.42bis compression found in many modems.   
   
   
   
30.0  Post Connect Scripting   
   
30.1 Introduction   
   
On all call origination attempts, after the modem connection has been made,   
CO/Session looks for a job file with a .CXL extension. This job file will   
contain commands to provide any necessary post connect "handshaking"; such   
"handshaking" may be required before CO/Session can begin its login   
handshake with a called CO/Session PC (or other computer type in terminal   
emulation mode).   
   
CO/Session takes the called Phone Book name, appends ".CXL" to it, and then   
looks in your CO/Session directory for a file of that name.   
   
Only the alpha or numeric characters from the Phone Book name (maximum of 8)   
are used. For example, if Phone Book Entry name HQ_CENTRAL is used for the   
call attempt, then CO/Session will look for the file HQCENTRA.CXL for the   
post connect command job file.   
   
NOTE: If the modem name identified in the selected Phone Book Entry is   
DIRECTxxxx (where xxxx is any character string), then CO/Session will not   
use a CXL file.   
  
30.1.1 CXL Job Files   
   
A CXL job file is a text file, created with any text editor, which contains   
a list of CXL commands, comments, or labels. Each line in the file contains   
one command, comment, or label, and each line can consist of a maximum of   
64 characters.   
   
30.1.2 Command Summary   
   
The CXL commands (and special ON_ESC: label) are listed below. Details are   
provided later in this appendix.   
   
o  DISCONNECT - Disconnect call   
o  ENDIF  - Terminate true condition for IF statement   
o  EXIT - Must terminate JOBFILE for successful connect   
o  GOTO- Go to label   
o  IF [NOT] -  Conditional command   
o  ON_ESC: - Label branched to automatically if <ESC> pressed   
o  PAUSE- Pause for seconds or minutes   
o  SBREAK - Send 300 ms line break signal   
o  SEND  - Output characters to remote   
o  WAITFOR  - Wait for timeout or character sequence   
   
30.1.3 Comments   
   
Comments can be added to a CXL script file by preceding the comment line   
with a semi-colon (i.e., ";"). The semi-colon must be in the first column of   
the line.   
  
30.1.4  Labels   
   
Labels are used to mark a line in a CXL script file that can be branched to   
with a GOTO statement. They must appear on a line with no other command and   
must be followed with a colon (i.e., ":"). Labels are uniquely identified by   
the first six characters and are case sensitive. Currently, a maximum   
of 16 labels may be defined.   
   
30.1.5 Variables   
   
CXL supports the use of variables. Variables can be assigned text string   
values. All variables begin with the percent sign character (i.e., "%"). The   
next six characters uniquely define the variable and are case sensitive. Any   
characters after this are ignored. Currently, a maximum of 16 variables may   
be defined.   
   
  
30.2 Command Descriptions   
   
30.2.1  DISCONNECT   
   
Disconnects a connection.   
   
Format: DISCONNECT   
   
DISCONNECT terminates the CXL jobfile and a connection. Modems are reset   
and the phone line is disconnected.   
   
30.2.2 ENDIF   
   
Terminates True condition for IF statement.   
   
Format: ENDIF   
   
An ENDIF command concludes the "TRUE" condition execution for IF command   
processing. For the "FALSE" condition on the IF command, execution resumes   
at the command line immediately following the ENDIF command.   
   
Example: (see IF )   
   
30.2.3 EXIT   
   
Terminates CXL jobfile for a successful connect.   
   
Format: EXIT   
   
The EXIT command successfully terminates the CO/Session CXL script and   
establishes a successful connection.   
  
30.2.4 GOTO   
   
Go to a label.   
   
Format: GOTO  <label>   
   
<label> defines the line to which the GOTO command directs command execution.   
Labels are internally defined as a series of six alphanumeric characters and   
are case sensitive.   
   
Example:   
IF   WAITFOR = "ABCD"   
	GOTO good1   
ENDIF   
...   
...   
;  If ABCD is received,execution resumes here   
good1:   
SEND "received ABCD"        
...   
   
30.2.5 IF [NOT]   
   
Conditional command.   
   
Format: IF   [NOT]  waitfor  [ = <string >]   
       {statements}   
       ENDIF   
   
where, NOT - optional; may be used to reverse value of the expression.   
<string> - can be a variable such as %STR or an explicit string in quotes   
such as "ABCD."   
   
To determine the result of the IF statement, <string> is compared to the   
result of the last WAITFOR command executed. If <string> is not defined,   
then the IF command processing will use the last WAITFOR command true/false   
evaluation for IF command processing.   
   
Subsequent statements are executed if the IF statement is evaluated as being   
true.  Otherwise, if the IF statement is evaluated as being false, statements   
are skipped until the ENDIF command is encountered at which time execution of   
CXL commands is resumed with the command line immediately following the   
ENDIF command.   
   
Examples:   
; This example waits for the string "ABCD" or ;ten   
seconds,   
;  whichever occurs first. If  "ABCD" arrives ;before   
ten seconds   
; then the IF statement is true, otherwise it ;is false.   
   
WAITFOR  s10 | "ABCD"   
IF WAITFOR   
	SEND "good result"   
ENDIF   
   
; This example waits for any string to arrive ;for ten   
seconds. If a string   
; arrives and is "ABCD" then IF statement is ;true. If   
no string arrives or   
;  a string other than "ABCD" arrives then IF   
;statement is false.      
   
WAITFOR  s10 | *   
IF WAITFOR = "ABCD"   
	SEND "good result"   
   
ENDIF   
   
30.2.6  ON_ESC:   
   
This is a special label that is automatically branched to if <ESC> is    
pressed.   
   
30.2.7 PAUSE   
   
Pause for seconds or minutes.   
   
Format: PAUSE  [s]<time>   
   
The PAUSE command will suspend CXL jobfile execution for the specified   
number of seconds/minutes, where:   
s - Optional and denotes time as expressed in seconds. If s is not included,   
then minutes are assumed.   
<time> - Integer that defines how long CXL processing pauses.   
   
Examples:   
   
; Pause 10 seconds   
PAUSE s10         
; Pause for 2 minutes   
PAUSE 2   
   
30.2.8  SBREAK   
   
Sends a 300 millisecond line break signal.   
   
Format: SBREAK   
   
30.2.9  SEND   
   
Outputs characters.   
   
Format: SEND  <string>   
   
The SEND command will output characters in <string> where <string> is   
specified either as: a string in quotes such as "ABCD," or a string variable   
previously defined such as %STR.   
  
Example:   
   
; In this example the same string is sent ;twice, once   
defined explicitly and once ;defined as a variable.   
%STR1 = "ABCD"   
SEND    "ABCD"   
SEND    %STR1   
   
Custom string special characters can be imbedded in the string definition   
and sent to the remote. They are defined as follows:   
   
\          sends carriage return   
|          sends line feed   
^         control for sending control characters   
   
To have the special characters defined above treated normally (as their   
ASCII equivalents), precede the character with the slash character   
(i.e., "/"). To have the slash character treated normally, specify it as "//".   
   
Examples:   
   
; Sends  abcd followed by a carriage return ;line feed to   
remote   
   
SEND    "abcd\|"   
   
; Sends \ abcd to remote   
   
SEND    "/\abcd"     
   
30.2.10  WAITFOR   
   
Wait for a string or a timeout.   
   
Format: WAITFOR  [s]<time> | <string>   
   
[s]<time> - Specifies time to wait for expression to be received from the   
remote. If "s" is specified the time value is in seconds, otherwise time is   
expressed as minutes.   
   
<string> -  Specifies a string to wait for. <String> can be a character   
string in quotes, a variable or an asterisk (i.e., "*") to specify a "do not   
care" condition.   
   
The WAITFOR command continues executing until either:   
a)      The specified timeout in seconds/minutes expires   OR   
b)      Successful reception of the specified string from the remote.   
   
Examples:   
; Wait for ten seconds or for any string, then ;compare the string   
; received to "ABCD".   
   
WAITFOR  s10 | *    
IF WAITFOR = "ABCD"    
   
	...   
   
ENDIF   
   
; Wait for ten seconds or for the string ;"ABCD". The   
IF   
; statement is true if "ABCD" arrives before 10   
;seconds.   
   
WAITFOR  s10 | "ABCD"   
IF WAITFOR   
   
	...   
   
ENDIF   
   
  
30.3 Debugging CXL Scripts   
   
To debug a CXL script, turn the COM Port Monitor Option ON. This will allow   
you to watch commands sent to and data received from the COM Port.   
   
  
   
31.0  Miscellaneous Reference Information   
   
This final appendix covers the CO/Session data files and video mode   
compatibility.   
   
	   
31.1 CO/Session Data Files   
   
CO/Session creates a number of data files:   
   
31.1.1 Host and Remote   
   
o  SESSION.RMP - contains all the Phone Entries.   
o  SESSION.CFG - contains all the Option settings and path information.   
o  SESSION.MDM - contains defined modem strings.   
o  SESSION.100 - contains options for VT100 emulation.   
o  SESSION.102 - contains options for VT102 emulation.   
o  SESSION.KM0 - contains the VT100 keyboard map.   
o  SESSION.KM1 - contains the VT102 keyboard map.   
  
31.1.2 Remote Only   
   
o  SESSION.LOG - contains Billing Log data.   
o  SVSESION.xxx - default session recording file(s).   
o  SVSCREEN.xxx - default screen save files(s).   
o  SESSION.PRN - default print spool file.   
   
By default, all files are created in the CO/Session install directory.   
They can be moved to and maintained in another directory, but this requires   
the use of Directory Option command line arguments (which are described in   
Chapter 27).   
   
   
31.2 Video Mode Compatibility   
   
To control Graphics mode applications remotely using CO/Session, the Host PC   
and Remote PC should have compatible video display adapters, as indicated by   
a Y in the table below.   
   
NOTE: Even if the table below indicates that a Remote PC's display adapter   
is incompatible with the display adapter on a particular Host PC, it may   
still be possible to use the Remote to control applications on that Host PC.   
To do this, temporarily re-configure the application on the Host for the   
Remote's display adapter type (if possible). Refer to the Host application's   
manual for instructions on configuring the video display type.   
   
		HOST Display   
   
	VGA     EGA     CGA     Hercules   
   
REMOTE   
Display         
    VGA    Y       Y       Y          N   
    EGA    Y       Y       Y          N   
    CGA    N       N       Y          N   
Hercules   N       N       Y          Y   
   
	Y=Yes (okay),  N=No (not okay)   
   
NOTE: Text mode applications can be remotely controlled with all combinations   
of display adapters. Also note that some adapters are multi-mode and can be   
switched between modes in various ways, depending on the manufacturer.   
Refer to your adapter's manual for details.   


