  

Write
~~~~~
Set this to "Yes" to let the caller write files to your disks by commanding 
your PC to receive with REC, HREC, XREC, YREC, GYREC, and KREC. To prevent 
the caller from writing to your disks, set this to "No".

Overwrite
~~~~~~~~~
Set this to "Yes" to give a caller with Write privileges the option to 
overwrite your files. Set it to No to keep your existing files intact; if a 
caller sends files whose names match existing files, his only options are to 
save under new names or cancel the transfer.

Print
~~~~~
Set this to "Yes" to let the caller use PRINT to run your printer. Set this 
to "No" to prohibit printing, or if your printer is prone to mechanical 
problems that make unattended printing impractical. If you let callers print, 
be sure to leave your printer on and with plenty of paper.

File management
~~~~~~~~~~~~~~~
Set this to "Yes" to let the caller use COPY, DELETE, RENAME, MKDIR, and 
RMDIR, to manage your files or directories. To prevent tampering with files 
or directories, set this to "No".

Access limited to
~~~~~~~~~~~~~~~~~     
Set this to the drive or directory to which you wish to restrict this caller's 
access. This becomes the caller's default location; commands he uses affect 
only this drive or directory, and its subdirectories.

Telephone number to call back
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Set this to the caller's phone number, so that this password can be used 
only from that location, or so that phone charges go on your bill, not the 
caller's. After a caller enters this password, your PC hangs up, waits a 
moment, then calls the specified number once. During this time, the caller 
commands his modem to answer (S0=1 for Hayes-compatible modems), but leaves 
his software configured as described in Chapter 8. After the modems reconnect, 
the caller can begin using the privileges this password confers.

Unlimited DOS use
~~~~~~~~~~~~~~~~~
Set this to "Yes" to let callers with FreeComm and HyperTerminal (the 
HYPERTRM emulator) use your operating system and programs.
(This privilege is automatically withheld from callers using other emulators, 
which are incompatible.) To use your operating system, the caller enters DOS. 
To exit the operating system and resume using FreeComm host commands, the 
caller enters EXIT. Limits to caller privileges set with other options on 
this menu no longer apply when the caller is using the operating system. So 
you should give operating system access only to people you trust implicitly. 
For more information on remote program use, see Chapter 9.

Manage list of scripts and programs caller can run
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
See Chapter 8.

Deleting passwords
~~~~~~~~~~~~~~~~~~
To delete a password, select "Manage password list" and "Delete", then select 
the line in the Password List to be deleted.

Modifying passwords and privileges
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Select "Manage password list" and "Modify" and select the desired password. 
When the Privileges menu displays, you can select "Caller's password" to 
change the password, or select and change the caller's name or privileges. 
When you're done, press ESC to return to the Answer menu.
     

                     8.7 Remote use of programs and scripts
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Answer mode can adapt to your needs. You can have it run scripts or programs 
the instant a caller logs on or logs off, or when the caller enters custom 
host commands that you define. In fact, you can list separate scripts or 
programs for each caller, with up to a dozen for each.
     
Callers with FreeComm and HyperTerminal (the HYPERTRM emulator) can see and 
use programs almost as if their monitors and keyboards were attached to your 
PC(see Chapter 9). However, all callers can use scripts and non-interactive 
programs for applications like these:

    Electronic mail After the caller enters his password, you could have a 
     script run that checks your disk for messages to that caller. See the 
     discussion of the MAIL command in Appendix E.
    Programs that prepare files  After the caller enters his password, you 
     can have a script or program (such as database, compiler, or batch file) 
     prepare reports or other files, which the caller can then pick up using 
     FreeComm host commands.
    Custom, user-defined commands  You can incorporate your own commands 
     with the existing FreeComm host commands commands that run scripts or 
     programs, to do things such as file encryption, compression, compiling, 
     mail processing, use external file transfer protocol modules (such as DSZ 
     or Jmodem), etc. Programs that perform post-call processes  After a 
     caller logs off, you could have a script or program (database, compiler, 
     batch file, etc.) process files the caller has sent, or do record-keeping 
     related to the call. You can use the following procedures to add (or 
     modify) the list of scripts or programs associated with a given password,
     regardless of the caller's software:

1.   From the Privileges menu, select "Manage list of scripts and programs 
     callers can run".
2.   Select "Add" or "Modify". (After selecting "Modify", select the line you 
     wish to modify from the list at the bottom of the menu.)
3.   Enter the line FreeComm will use to start the script or program. In 
     addition to the script or program name, this line can include any inputs 
     to be passed to the script or program. Inputs for scripts must be typed 
     here following guidelines given in Chapter 7 (multiple inputs separated 
     by commas, etc.). Inputs for programs must follow the format accepted by 
     that program. Some programs refer to such inputs as program startup 
     options or switches. You can pass the caller's name as an input by 
     including <name> in the line which starts the script or program (as 
     illustrated by the WELCOME.HP script). If you plan to select 
     "When-caller-enters-command" in the step which follows this, you may 
     type ? in place of any input that you expect the caller to supply. For 
     each ? in this line, one caller-supplied input will be substituted. 
     When callers enter commands, they can supply inputs by typing them on 
     the line with the command, separated by spaces. If a caller supplies 
     fewer inputs than expected, the excess question marks are ignored; if 
     he supplies too many inputs, his extra inputs are discarded.
4.   To indicate when the script or program is to be run, select:
     
     Following-logon--           This causes the script or program to run 
                                 immediately after the caller enters his 
                                 password. If you list more than one script 
                                 or program to run following logon, they are 
                                 run in the order they appear in the list.
     When-caller-enters-command  After selecting this, you are prompted to 
                                 enter a one-word command the caller will use
                                 to run the script or program. (It need not 
                                 be the same as the script or program name 
                                 that you entered in the previous step). This
                                 command will display along with the existing 
                                 FreeComm host commands when the caller enters 
                                 HELP, and can be entered by the caller in the 
                                 same way.
     After-disconnect--          This causes the script or program to run 
                                 immediately after the caller disconnects. If 
                                 you list more than one script or program to 
                                 be run after disconnect, they are run in the 
                                 order they appear in the list.

Compatible scripts
~~~~~~~~~~~~~~~~~~
The scripts you write for use here can display messages to the caller, accept 
caller responses, or perform complex processes. Generally, such scripts are 
written rather than learned. For information on writing scripts, get the 
FreeComm Scripting Manual from the Delrina BBS. For helpful examples, see the 
script WELCOME.HP; after a caller logs on with the password limit or unlimit, 
this script displays a brief, personalized welcome message to the caller.

Compatible programs
~~~~~~~~~~~~~~~~~~~
While callers with FreeComm and HyperTerminal can run other types of programs 
as well (see Chapter 9), all callers can use non-interactive programs. To be 
considered non-interactive, a program must run to completion without keyboard 
input from the caller, and produce no screen displays the caller must see. 
Likely prospects are compilers, file transfer protocol modules, compression 
programs, encryption programs, operating system commands, and batch files that 
run such programs. Many data base and spreadsheet programs contain programming 
languages that can be used to write applications (to generate reports, update 
files, etc.) which are non-interactive.
     
   
                          8.8 Locking the Password List
                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can lock the Password List to prevent unauthorized individuals from using 
your keyboard to examine or modify the passwords.
Once the Password List is locked, it can be accessed only with a master 
password which you define. (The master password is used only for accessing the 
password list; callers cannot use it to log on to your PC.)

To lock the password list:
~~~~~~~~~~~~~~~~~~~~~~~~~~
1.   From the Answer menu, select "Manage password list". If the password list 
     has already been locked, you must enter the existing master password to 
     proceed.
2.   Select "Lock-list".
3.   Enter the new master password. It can be up to 20 characters.
     Note:  Don't lose your master password! Once you've locked the password 
     list, the only way to examine, change, or unlock it is to select "Manage 
     password list" and enter the master password. If you do lose your 
     password, your only recourse is to delete DCL.ANS (the encrypted file 
     which contains all the Answer mode passwords) and define new passwords 
     as described in Chapter 8.

                        8.9 Switching voice calls to data
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can switch voice calls into data calls to let the other party run your 
PC's Answer mode (provided you both have modems).
     
To switch a voice call to data, select "Emit carrier" to allow a voice call 
to switch to data from the Answer menu. What happens next depends on the type 
of modem you have FreeComm either commands your modem to emit a carrier, or 
instructs you to do so.
     
When the other party hears your modem's carrier (a continuous, high-pitched 
tone), he should complete the connection as described in his modem manual. If 
he has a Hayes-compatible modem, he would issue the ATO command, leaving his 
PC configured as in Chapter 8.


                        8.10 Using a cable instead of modems
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Exchanging files with adjacent computers through a cable is not only faster 
than using diskettes, it may be the only way to exchange files between 
computers with incompatible disk formats. FreeComm makes exchanging files 
through a direct cable connection especially fast and easy. (If both PCs have 
FreeComm, see Chapter 9 for step-by-step instructions.) Here is the general 
procedure.

1.   Use a null modem cable to connect the two computers' communications ports. 
     See Appendix A for information on cables and consult your computer dealer 
     if you need assistance.
2.   Select "Direct cable connection to another computer" from the Answer menu 
     and enter the baud rate. Higher rates produce faster transfers. Almost 
     all PCs work reliably at up to 19,200 bps; many ATs and most 386 or 486 
     PCs work at up to 115,200 bps. Next, enter the communications port that 
     this PC will be using.
3.   Configure the other computer as described in Chapter 8, using the same 
     baud rate as in step 2.
     
You need not type anything further at the keyboard of the PC on which you 
selected Direct cable connection to another computer. From the keyboard of 
the other computer, sign on and use commands as described in Chapter 8.


                            8.11 Redefining the modem
                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~
To select the modem or device used for answering calls, select "Hardware" and 
"Modem" from the Answer menu.
     
The settings on this menu are used as follows.

Modem name
~~~~~~~~~~     
This lets you set the modem or device used for answering calls. If the name 
of your modem is not in the list, please read "About your modem" in Appendix A 
for recommendations. If you normally use a direct-cable connection with Answer 
mode, select Direct-cable. That way, you can answer merely by selecting "Wait 
for data calls", instead of selecting "Direct cable connection to another 
computer" and entering the baud rate and port every time.

Rate, default for Answer menu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you set the baud rate Answer mode uses when waiting for calls. 
However, if a call arrives at another baud rate and your modem shifts to that 
rate, so will Answer mode. (Some callers will find it necessary to press 
ENTER about once per second, so that Answer mode can determine the baud rate.) 

Number of rings on which to answer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you set how many rings Answer mode waits for before answering each 
call. Normally this is set to 1. You may want to set a higher number if you 
sometimes answer voice calls on the same phone line.

Additional modem setup commands
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you specify commands to append to those Answer mode issues when it 
sets up your modem to wait for calls. Normally, nothing need be set here. But 
if you want to activate other modem features or alter the modem configuration, 
look up the appropriate commands in your modem manual and enter them.
     

                      8.12 Assorted settings for Answer mode
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To set miscellaneous settings that affect Answer mode, select "Assorted 
settings" from the Answer menu.

Log calls in the file
~~~~~~~~~~~~~~~~~~~~~     
Use this to set which file is used for logging calls and file transfers. Make 
up any filename you like, or enter no filename, to disable logging. If the 
file does not exist, it will be created.
     
Each time your PC is accessed, the date, time, caller's name, call duration, 
commands used, and files transferred are logged. The log is an ASCII file, 
which you can read with the Editor, or print with ALT-F, Print. To discard 
its contents, just delete the file; a new file will be created the next time 
a call is answered.

Keep partially received files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Set this to "Yes" to keep partial files resulting from interrupted or aborted 
Zmodem or HyperProtocol transfers. Using this setting will make it possible 
for callers to send the rest of the file later. To send the rest of the file, 
callers need to use Zmodem with its file recovery feature enabled; callers 
with FreeComm will need to set Resume broken transfers to Enable on the 
Zmodem menu.


                           9.1 FreeComm to FreeComm Communications
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FreeComm is a truly general-purpose communications program, excellent both 
for accessing diverse computer systems, and for PC-to-PC communications. 
This chapter tells how to do the most popular PC-to-PC operations, giving 
step-by-step instructions which assume both PCs have FreeComm.

If you need to communicate with PCs that have different programs, use the rest 
of this manual, together with the manual from the other program. By getting 
FreeComm for both PCs, you can avoid having to sort out how dissimilar 
programs fit together and get far better performance.

FreeComm has many features that streamline communications with other copies 
of FreeComm. With them, you can:

    Call another PC and control it entirely from your end the person at the 
     other end doesn't have to type a thing.
    Transfer files between the PCs at several times the baud rate of your 
     connection.
    Run programs or use the operating system of the remote PC. You can see 
     and use programs almost as if your PC's monitor and keyboard were 
     attached to the remote PC.
    Move files between PCs through an RS232 cable at baud rates 10 to 50 
     times that of a modem.
    Log onto other PCs automatically or accept "callbacks" from other PCs.
    Do PC-to-PC file transfers when both PCs are unattended.
    Place automatic calls to series of PCs and exchange files with each.
     
The next three sections tell how to use your keyboard to connect with another 
PC and transfer files manually. Even if your goal is unattended communications 
you should begin with these sections the first step in automating most any 
task is to perform the task manually.


                            9.2 Beginning a PC-to-PC session
                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Before you begin a PC-to-PC communications session, you need to decide which 
PC is going to call and which is going to answer. This decision affects more 
than just who pays the phone bill, it determines which PC will be in control.

In communications between PCs with FreeComm, the PCs have a master-slave (or 
terminal-host) relationship. The calling PC is the master (or terminal) and 
the answering PC is the slave (or host). From his keyboard, the caller can 
command the answering computer to send or receive files, or to do other 
processes. In fact, no one even needs to be present at the keyboard of the 
answering computer.
     
Methods presented in other chapters for calling, answering, and communicating 
in general are equally applicable when the remote system has FreeComm, so you 
should read those other chapters when you need detailed information. But for 
quick results, you can just follow these condensed, step-by-step instructions:

Preparing for a session through modems
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.   To prepare one of the PCs to answer, select "Answer" from the Main menu, 
     then select "Wait for data calls". (See Chapter 8 for more detailed 
     instructions.) Nothing further needs to be typed on this PC now, nor 
     during calls.
2.   To prepare the other PC to place a call, select "Define system settings" 
     and "Modify" from the Main menu, then select "Another PC with DFC" from 
     the System List. Enter the phone number, correct the Rate if necessary, 
     and return to the Main menu. (For more detailed information, see Chapter 
     4.)
3.   To place the call, select "Call a system" and "Data-call" from the Main 
     menu, select "Another PC with DFC".
     (Instructions resume below in Logging on.)

Preparing for a session through an RS232 cable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.   Connect the PCs using a null modem cable. (See Appendix A for cable 
     details.)
2.   To prepare one of the PCs to answer, select "Answer" from the Main menu, 
     then select "Direct cable connection to another computer". Enter the baud 
     rate you want to use, and then enter the number of the COM port. Nothing 
     further needs to be typed on this PC now nor later, during a PC-to-PC 
     session.
3.   To prepare the other PC, select "Define system settings", "Modify", and 
     'Another PC via cable'. Enter the desired "Rate". Select "Communications 
     port", "Standard comm port", and enter the correct port. Then return to 
     the Main menu.
     Note: Most PCs and XTs support baud rates up to 19,200 bps, while AT, 
     386 and 486 PCs may handle up to 115,200 bps.
4.   To establish the connection, select "Call a system" and "Data-call" from 
     the Main menu, then select "Another PC via cable". Log on as described 
     below.

Logging on
~~~~~~~~~~
1.   If the prompt Enter password: doesn't display when you connect, press 
     ENTER a few times (about once per second) to make it display.
2.   Enter the password given to you by the person responsible for the other 
     PC, or enter unlimit (one of the original passwords). Passwords do not 
     display as you enter them. If the other PC won't admit you even when you 
     enter a valid password, see Chapter 8.
3.   If the prompt "Please enter your name:" displays, enter your name. Use 
     any format you like: Jane Doe, jdoe, or Jane would all be acceptable.

At this point, you (the caller) can enter commands to control the other PC as 
described in Chapter 8 and Appendix E. While the [DFCHost] prompt that 
FreeComm presents may look like the host PC's command prompt, it is actually 
a special interface which accepts only certain commands, depending on the 
password. However, authorized callers can access the host PC's real operating 
system prompt by entering DOS at the [DFC Host] prompt.
     

                   9.3 For fast, reliable file transfers... 
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
One of the main attractions of PC-to-PC communications is the ability to 
transfer files. FreeComm is outstanding for this. It transfers files 
error-free in substantially less time than other programs. 

How HyperProtocol compares to other protocols
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
While the conventional protocols (Xmodem, etc.) in FreeComm are faster than 
in other programs, HyperProtocol is faster still. Other protocols are less 
efficient because they send data in packets, and after each packet, they stop 
and wait for the receiver to send back an acknowledgement.

HyperProtocol achieves higher efficiency by sending in a continuous stream, 
including error-checking codes at adaptive intervals. Unnecessary pauses are 
eliminated: the receiver doesn't send back incessant acknowledgements that 
good data is good, it merely requests retransmission of data damaged by line 
noise. 
     
Through local phone lines or cable, HyperProtocol cuts transfer times 3% to 
20% compared to other protocols. And through long-distance lines, high-speed 
modems, ISDN's D-channel, or other connections that exhibit line delays, 
HyperProtocol cuts transfer times by 20% to 50%.

How on-the-fly file compression helps
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When FreeComm senses that the other PC also has FreeComm, it compresses files 
on-the-fly as it transfers them, to reduce the number of bytes that must be 
sent. This occurs automatically with every protocol (except Zmodem, Text, and 
CompuServe B) and adapts dynamically to the contents of each file.
     
FreeComm's compression techniques equal the compaction rates of dedicated, 
off-line compression programs. Yet compressing files is automatic and incurs 
no pre-transfer or post-transfer delay. Even the delay of writing compressed 
files to disk is avoided data remains compressed only for the instant when it 
passes between computers.
     
Program files may transfer in 30% less time, text files in 50% less time, and 
spreadsheet or database files in 50% to 80% less time. Even with modems that 
have built-in compression, FreeComm compression gives substantial gains. 
During transfer of small (under 4K), uncompressible, or pre-compressed files 
(compressed by programs such as ZIP or PKZIP), compression automatically 
switches off.

         
                           9.4 How to transfer files
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~
After you've connected as outlined in Chapter 9, you can transfer files as 
described here. Instructions in this section are directed to the caller, 
because the person who placed the call controls the entire process. (The 
answerer doesn't even have to be present).
     
All you do is enter a command at the [DFC host] prompt to make the answering 
PC send or receive, then press ALT-O and select "Transfer" to make your PC 
receive or send. Take these steps:

To make the answering PC receive
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.   Connect as described in Chapter 9.
2.   On the calling PC, type HREC and press ENTER at the [DFC host] prompt, 
     to command the answering PC to receive.
3.   Press ALT-O, select "Transfer", "Send", and "HyperProtocol", to make the 
     calling PC send. (See Chapter 3 for time-saving tips.)
4.   Enter the name of the file (or display a directory with ALT-D and select 
     from it). To send multiple files, include * or ? in the filename, or use 
     multiple-entry mode, or enter /B with a batch file name (for details, 
     see Chapters 3 and 5).
     Note: If you take too long to do steps 3 and 4, the answering PC gives 
     up waiting for the transfer to begin. Repeat steps 2 through 4 more 
     quickly.

To make the answering PC send
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.   Connect as described in Chapter 9.
2.   On the calling PC, type HSEND, a space, a filename, and press ENTER at 
     the [DFC host] prompt, to make the answering PC send. To make it send 
     multiple files, use * or ? in the filename, or use /B and a batch 
     filename as in Chapter 3.
3.   Press ALT-O, select "Transfer", "Receive", and "HyperProtocol", to make 
     calling PC receive. (See Chapter 3 for time-saving tips.)
4.   Enter the drive and/or full directory name where you want the calling PC 
     to put the file, or press ENTER with no entry, to use the calling PC's 
     current working directory.

During a transfer, you can watch how things are going if you like, but no 
participation is required. When the transfer is done, press ENTER to continue. 
To cancel a transfer that is under way, press ESC; wait a few seconds for a 
cancellation or press ESC again to cancel immediately.

File transfer options
~~~~~~~~~~~~~~~~~~~~~
To use slash options for sending, precede the filename with the desired option 
and a space, when you prepare the answering or calling PC to send. To send 
files from a directory and its subdirectories, use /S and filename which 
includes that directory and * or ?. Or use /B to send files whose names are 
listed in a file batch. (See Chapters 3 and 5 for details).
     
To use slash options for receiving, precede the filename with the desired 
option and a space, when you prepare the answering or calling PC to receive. 
Use:

     /O          to Overwrite existing files whose names are the same as 
                 received files 
     /N          to receive only files whose times and dates are Newer than 
                 existing files
     /P          to store received files where the Path in the received 
                 filename indicates. Whether a received filename includes a 
                 path depends on how it is sent; FreeComm includes the path 
                 only when files are sent with the /S option. (See Chapter 3 
                 for details.)
     
It is sometimes convenient to use slash options both in preparing one PC to 
send, and in preparing the other to receive. That is, on one PC you might use 
/S to send files from a directory and its subdirectories, and on the other PC 
use /P to receive the files into a corresponding directory and subdirectories. 
Chapter 3 gives examples.

   
                       9.5 Remote use of DOS or programs
                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After you have connected with the host PC and accessed its operating system 
as described in 9.2, you can see its command prompt, use its operating system 
commands, and run its programs.
 
Defining privileges on the answering PC
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Prior to the call, the answerer must define a password for the caller, and 
set whether the caller can use the operating system, or just specific programs. 

Compatible programs
~~~~~~~~~~~~~~~~~~~
If the answering PC is running DOS, callers can run most DOS programs that 
use 25x80 text display mode and require 460k or less memory. Programs that 
use graphics display modes, require a mouse, or reconfigure the port or 
interrupts cannot be run; this includes some communications, many TSR, and 
all Windows programs. TSRs started by a caller are removed from memory after 
the call. When the caller accesses the operating system or starts a program, 
it will occupy the existing FreeComm session on the answering PC; the caller 
cannot start additional sessions, nor switch to other, existing sessions.

What you see when running programs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You notice that programs display less quickly and smoothly when run remotely. 
The performance is impressive, however, when you consider that all that 
display data is coming through your modem, whose speed is typically 1/10,000 
that of a monitor cable.
     
The programs look exactly the same on your PC as on the answering PC unless 
the display types differ widely. If there is a monochrome display at one end 
and a CGA, EGA, or VGA at the other, then colors and character attributes are 
converted automatically.

HyperTerminal can sense when noise on your connection corrupts data, and tells 
the answering PC to re-send the data. If errors happen to slip through and 
affect the screen image, press ALT-O and select "Display" and "Refresh", to 
receive a fresh screen image. If the program you're running displays 
information in the bottom line that you need to see, you can suppress 
FreeComm's own bottom line. Press ALT-O, select "Display", "Bottom-line", then 
select "No" to turn off FreeComm's bottom line off unconditionally, or "Auto"
to have it go off only when you're running programs.
     
Tips on using programs remotely
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your role changes when you leave the [DFC host] prompt and begin using 
programs. Rather than controlling the other PC by typing FreeComm host 
commands, it's as if you were running that PC yourself. If you tell it to 
write to disk or print, it writes to its disk or prints on its printer. To 
get the file onto your disk, or print the information on your printer, you 
need to return to the [DFC host] prompt and use FreeComm host commands to 
transfer it.

To print the screen, write it to disk, or copy it to the Review buffer, press 
ALT-O, then select "Display" and "Print", "Write", or "Copy" to Review. 
Screens are updated through selective replacement of text, without scrolling 
into the Review buffer. Data arrives non-sequentially, so using the Comm 
screen "Capture" and "Print" options is impractical.

When a program requires a key that FreeComm normally uses (for example, an 
ALT- or sequence key), press ALT-O, select "Quote", then press the key. Or, 
to make the keys available indefinitely, press ALT-O and select "Send-keys". 
To restore them, press ALT-O and select Keep-keys. (To send ALT-O, press it 
once, select "Quote", and press it again.)
     
Keys that your own PC's operating system uses (NUM LOCK, CAPS LOCK, 
CTRL-ALT-DEL, etc.) are never sent; neither are non-standard keys such as 
CTRL-SHIFT, and mouse output.



Recovering from "hang-ups"
~~~~~~~~~~~~~~~~~~~~~~~~~~
The answering PC can resume waiting for calls automatically when factors 
beyond FreeComm's control cause hang-ups like these:

    The modems lose the connection or the caller hangs up while using a 
     program or the operating system.
    The caller seems to forget that he was running a program remotely, and 
     fails to type anything for 15 minutes.
    A program the caller was using locks up, and fails to send any new 
     display data to the caller for 15 minutes. FreeComm re-boots the PC, and 
     resumes waiting for calls only if you've set up the PC's AUTOEXEC.BAT 
     file correctly.
     
AUTOEXEC.BAT is a file in your boot directory containing commands your PC 
executes when it boots. (See your DOS manual for details.) To resume waiting 
for calls, it must contain the line DFC /A. You may also want to add commands 
to change directories, and to prevent FreeComm from starting every time you 
boot the PC, as this example shows:

     CD \DFC
     IF EXIST DFC.SAV DFC /A
     CD \

The first line changes to the directory containing FreeComm. The second line 
starts FreeComm and waits for calls only if FreeComm.SAV exists; FreeComm.SAV 
exists only if FreeComm was already waiting for calls before the PC was 
re-booted. The third line changes back to the root directory.
     
Note: These lines must precede any lines which require you to be present to 
enter information, such as "Time" or "Date".
     
If there is a power outage while the PC is waiting for calls, it will 
automatically resume waiting when the power comes back on.


                              9.6 Automatic logon
                             ~~~~~~~~~~~~~~~~~~~~~
If you often call another PC with FreeComm, you may want to have your program 
learn to log on for you, to save you the work. To do this, follow these steps.

1.   Select "Call a system" from the Main menu.
2.   Select "Learn-logon", then select the desired system from the System List.
3.   When you connect with the other PC, log on as usual (as described in 
     Chapter 9).
4.   When you're done logging on and the [DFC host] prompt displays, it's 
     time to stop learning the logon script. Press ALT-L to select "Learn" and 
     then select "Stop".
5.   When you're asked if the script should be compiled, select "Yes".
The next time you call, the logon will be done for you. When the logon is 
complete and the [DFC host] prompt appears, you may command the other PC as 
usual.
     

                           9.7 Automatic file transfers
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you regularly transfer certain files, you could save time by automating 
the steps involved in beginning the transfer. 

1.   Connect with the other PC and log on as in Chapter 9.
2.   Prior to doing steps that prepare the PCs for the transfer, press ALT-L 
     to start learning.
3.   Prepare the PCs to begin the transfer.
4.   When the transfer is complete, press ALT-L again, to stop learning. 
     Complete the learning process by entering a name for the script that has 
     just been learned, assigning it to a key, etc.
     
Next time you call the PC, you can do the transfer by pressing the script's 
key, or by pressing ALT-R and entering the script name.
     
     
                       9.8 Making a complete automatic call
                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you often call a certain PC to do a specific file transfer or some other 
repeatable process, you may want to have FreeComm learn to make the call for 
you. This not only saves you time and effort, it may reduce your phone bill, 
since FreeComm can do things faster than you can. 
     
Note: Before automating a call, call a few times manually, to get gamiliar 
with the steps.
     
To have FreeComm learn the call:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.   Press ALT-L to begin learning on the Main menu, and then call the other 
     PC as usual (select Call a system, etc.).
2.   After you finish logging on (or after your logon script finishes), go 
     ahead and do the file transfer or other repeatable process.
     (Variable processes can be learned, but may require some editing.)
3.   When you're done performing the process, log off.
4.   Press ALT-L to stop learning. To complete the learning process, enter a 
     name for the script, assign it to a key, etc. To make a call by running 
     this script, either press its key, press ALT-R and enter its name, or 
     include its name when you start FreeComm.
     

                            9.9 Time-delayed calling
                           ~~~~~~~~~~~~~~~~~~~~~~~~~~
Once you've got a script that makes an entire call, you can delay the call 
until phone rates are low. FreeComm can learn a sequence that starts the 
script at a given time:

1.   Go to the Main menu and press ALT-L to start learning, and press ALT-L 
     again, to bring up the Learning options.
2.   Select "Time-delay", and then "Minutes" or "Time-of-day". Enter the 
     length of time to wait, or the time when the call should take place, as 
     described in Chapter 7. No delay occurs now; it occurs only when you run 
     the sequence.
3.   Now press ALT-R and enter the name of the script that makes the call. 
     After the script finishes the call and ends, press ALT-L, and stop 
     learning (enter a sequence name, assign a key, etc.).
     
Henceforth, you can place this time-delayed call just by starting this 
sequence.


                        9.10 Multiple automatic calls
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If your business or organization has PCs spread out among several sites, 
automatic communications among them can prove very useful. You can place 
automatic calls to one PC after another to collect or distribute fresh sales 
or inventory data, or to move messages among sites. By adapting automatic 
communications to your needs, you can share timely data at a fraction of the 
cost of express mail, Wide Area Networks, leased lines, or other methods.

There are many viable strategies (topologies) regarding which PCs should call, 
which answer, when to call, and in what order. This section discusses only 
one strategy: having a central PC call others.
     
The PCs that will be answering should be prepared. To prepare the PC that will 
be placing calls:

1.   One at a time, automate the call to each PC. Each PC needs to be listed 
     individually in the System List with a logon script that does a complete, 
     "hands-free" call to that PC. In the following steps, you'll learn a 
     sequence which places calls to all the PCs, one after the other.
2.   Press ALT-L on the Main menu.
3.   Select "Call a system" and "Data-call".
4.   To start selecting PCs to be called, press CTRL-ENTER to begin multiple-
     entry mode. Move to each line in the System List that contains one of 
     the PCs and press ENTER. After you've selected all the desired PCs, 
     press CTRL-ENTER to end multiple entry mode.
5.   Enter the number of times each call should be retried, in the event that 
     its logon script fails. (Failure can stem from a noisy phone line; 
     redialing may produce a better line.)
6.   When FreeComm begins to place the first call, press ALT-L and stop 
     learning and complete the sequence. 
7.   If you prefer that the calls not actually be placed now, press ALT-A to 
     abort them; otherwise, let them run to completion.
     
To call the PCs automatically, you run the sequence you just learned: either 
press its key, press ALT-R and enter its name, or include its name in the line 
you use to start FreeComm.
     

                          9.11 Accepting a callback
                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~
When you call a PC that is configured to answer and call you back, use the 
following procedure.

1.   To prepare to place the call, select "Define system settings" and "Modify" 
     from the Main menu, then select "Another PC with DFC" from the System 
     List. Enter the phone number and, if necessary, correct the "Rate".
2.   Select "Hardware", and then "Modem".
3.   Select "Additional modem commands" and enter S0=1. FreeComm appends this 
     to commands sent to the modem before
     each call. (S0=1 makes Hayes-compatible modems answer; if your modem 
     isn't Hayes-compatible, enter its equivalent command.)
4.   Press ALT-M to return to the Main menu.
     
Once you have done this, here is how you call and log on.

1.   Select "Call a system" and "Data-call" from the Main menu, then move to 
     "Another PC with DFC" and press ENTER.
2.   When you connect, if the prompt "Enter password:" doesn't display right 
     away, press ENTER a few times (about once per second), to make it display.
3.   Enter the password given to you by the person responsible for the other 
     PC. (It won't display.)
4.   Stand by while the other PC hangs up and calls you back. If you're at 
     the pre-defined phone number and you prepared for the call as described 
     earlier in this section, the call will arrive shortly and be answered 
     automatically.
     
At this point, you can control the other PC using commands as described in 
Chapters 8. After you end this call, don't forget to command your modem not 
to answer subsequent calls; with Hayes compatible modems, you need to enter 
ATS0=0 on the Comm screen.


                                10.1 Menu Reference
                               ~~~~~~~~~~~~~~~~~~~~~
For each remote system you call, you can define on the System settings menu 
and its submenus about 100 individual settings that affect communications with 
that system. With these settings at your fingertips, you can fine-tune 
FreeComm to handle applications that defy other, less-flexible programs. 
Because initial values of the settings are fine for normal use, you can forget 
about them until situations like these arise:

    You may need to adjust settings for compatibility with remote systems 
     that use unusual ASCII protocol.
    Changes may be necessary with systems whose file transfer protocols don't 
     follow the de facto standards.
    When you change to another modem, communications device, or to a 
     direct-cable connection, you may need to change settings.
    You may want to change settings to customize how FreeComm uses colors, 
     memory or your printer.
     
Note: This chapter contains reference information in addition to what is in 
the on-line help. Each setting of the System settings menu and its submenus 
are described here. Instead of reading this entire chapter, you may simply 
turn to the section relevant to your current needs.
     

                        10.2 The System settings menu
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On the System settings menu, you can define the basic settings necessary for 
communications with each remote system. You must set the items on this menu 
according to recommendations from the remote system (except for "Name of 
system" and "Logon script", which are up to you). You can select five options 
at the bottom of the menu in order to reach submenus, which contain settings 
that seldom need changing. This is additional information to the on-line help 
on options you can select from the System settings menu.

Name of system
~~~~~~~~~~~~~~     
You might want to read about the "Sort" and "Find" options in Chapter 4, and 
create names that let you use these options effectively.

Telephone number
~~~~~~~~~~~~~~~~     
You can include special characters that affect how some modems dial. With 
Hayes-compatible modems, for example, you can include "W" to wait for the 
dial tone, "@" to wait for a 5 second silence, "!" to issue a PBX flash 
(hookflash), or "A", "B", "C", "D", "*", or "#" to generate touch tones.
     
If you are using a direct cable connection or a device that needs no phone 
number, leave the telephone number set to <none>.

Rate
~~~~
When text that displays on the Comm screen seems to contain no sensible 
sequences of letters and the bottom of the System settings menu shows many 
communications errors, your baud rate setting may be incorrect.

Bits per character
~~~~~~~~~~~~~~~~~~     
Incorrect settings may result in graphics characters appearing as regular 
characters or vice versa, mislocation of text during terminal emulation, or 
significant communications error counts at the bottom of the System settings 
menu.

Parity
~~~~~~     
When a parity bit is used, Even is more common than "Odd"; "Mark" and "Space" 
are rare. Most systems that require a parity bit also require 7 bits per 
character.
     
If the parity error count at the bottom of the System settings menu rises 
continuously, your parity may be wrong. Incorrect parity also may cause 
graphics characters to display as regular characters, or vice versa.

Stop bits
~~~~~~~~~     
If the error count at the bottom of the System settings menu rises continuously, 
your current setting may be incorrect.

Logon script
~~~~~~~~~~~~
Line noise may sometimes corrupt prompts that are important to a script, 
causing the script to stop. If noise is a persistent problem, contact the 
phone company for help. A script may also fail if a call deviates from the 
expected sequence of events. However, it is possible to edit a script to cope 
with every deviation you can foresee.

Emulation
~~~~~~~~~     
The most common types of terminals to select are TTY, ANSI, and VT100. 
Emulating the wrong terminal may cause screen control codes to show up on the 
screen and text to appear in the wrong locations. After you select the terminal 
type, a menu of settings for that terminal type will appear. Appendix C lists 
each terminal emulator, along with its keys and menu settings.

Communications port
~~~~~~~~~~~~~~~~~~~
Select this to choose the type of port to be used. After you select the port 
type, a menu of settings for that port type will appear. Select "Standard 
comm port" as your port type, if you're using an internal or external modem, 
external ISDN terminal adapter, or serial port which is installed directly on 
your PC. Settings for this port type are discussed in Chapter 10. Other port 
types for use with network interfaces such as Standard Int 14H may also 
appear here; for information on those port types.
     

                      10.3 ASCII protocols - Receiving text
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Settings on the Receiving text menu affect how FreeComm receives and displays 
text on the Comm screen, and how it saves and prints that text. To reach this 
menu, select "ASCII protocol" from the System settings menu, and then select 
"Receiving". These settings from the Receiving text menu control specific 
aspects of receiving, displaying, and saving text. 
     
Append line feeds to incoming line ends
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Usually this must be set to "No" when you're using full duplex, and "Yes" when 
you're using half duplex. If lines you receive appear double-spaced, you may 
need to change this to "No". If each line overwrites the previous line, you 
should probably change this to "Yes".

Force incoming data to 7-bit ASCII
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
For systems that send extended ASCII characters, set this to "No". (When you 
use the ANSI emulator, which must support graphics, this setting is ignored.)

Echo received characters to sender
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You may want to set this to "Yes" to do terminal-to-terminal communications; 
in this situation, you'll probably need to use half duplex and the remote 
terminal should use full duplex. (If you're communicating with another PC, 
see chapters 8 and 9 for a more convenient alternative.)

Pass only visible data to (Printer, Disk, Both)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
If you want some non-displayed characters but not others, set this to "Neither" 
and use the previous menu option to remove unwanted characters.

Tab default spacing 
~~~~~~~~~~~~~~~~~~~     
If text you receive has an irregular, misaligned appearance, you may need to 
change this to match the remote system's tab settings.

Wrap lines that exceed width of screen
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
If a remote system sends lines exactly 80 (or 132) characters long, you may 
want to set this to "No", to avoid double-spaced lines. 

Show hex values of non-displaying characters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You may be able to spot the characters or sequences that are troublesome; you 
can then remove them using other settings on this menu, or explain the 
problem to the remote system operator and have him correct it. (Some programs 
call this feature image mode or debug mode.) 

Remove these characters from incoming text
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Usually this is set to <none>. If certain characters you're receiving are 
useless or troublesome, you may want to list them here; type each as an ASCII 
hex value followed by h, separated from others by /. For example, you might 
enter 00h / 7Fh / 0Ch to remove NULs, DELs, and form feeds.

Default capture file
~~~~~~~~~~~~~~~~~~~~
Use this to define the name of the file FreeComm proposes when you begin 
capturing text. Normally this is set to CAPTURED.TXT, but you may find it more 
convenient to enter a filename specific to each system. These settings from 
the Receiving text menu control the flow of text.

XOFF/XON to control remote system
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
For systems that do not use XOFF and XON, set this to "No".

Outgoing characters used for XOFF/XON
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
If the system expects different characters, enter them as ASCII hex values 
followed by h and separated by /. 

Line-end/line-acknowledge used by remote system
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
This is almost always set to "No". Since this method has no universally 
recognized name (it's sometimes called ETX/ACK), you may need to examine how 
this method works (next paragraph) before you can identify whether it is 
supported by remote systems of interest to you.

Characters used for line-end/line-acknowledge
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
When you have set the previous setting to "Yes", use this option to define 
which character the remote system appends to each line to indicate its end, 
and which character your PC should send to acknowledge receipt of this 
line-end character. Normally, this is set to 03h / 06h (ETX and ACK). To use 
other characters, enter them as ASCII hex values followed by h and separated 
by /. 
     

                     10.4 ASCII protocols - Sending text
                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Settings on the Sending text menu affect how FreeComm transmits text that you 
type on the Comm screen or that you send using Text protocol. To reach this 
menu, select ASCII protocol from the System settings menu, and then select 
"Sending". These settings from the "Sending" text menu control the specific 
aspects of sending.

Send lines with line feeds
~~~~~~~~~~~~~~~~~~~~~~~~~~     
If lines that you send or type appear double-spaced, you may need to change 
this to "No". If each line overwrites the previous line, you should probably 
change this to "Yes".

Duplex
~~~~~~     
In full duplex, each character you type is sent without first being displayed; 
the characters appear on your screen only because the remote system sends back 
an echo of everything you type. In half duplex, each character you type is 
displayed first and then sent, and the remote system does not echo characters 
back to you.
     
When you are connected with a remote system, if every character displays twice 
on the Comm screen, you may need to switch from half duplex to full; if 
characters you type don't display at all, switching from full duplex to half 
may be the answer.

Expand empty lines to include a space
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As you send a file with Text protocol, this lets you have each blank line sent 
not just as a carriage return and line feed, but as a space, carriage return, 
and line feed.

Tabs converted to spaces
~~~~~~~~~~~~~~~~~~~~~~~~     
With most systems, you can leave this set to <none>, which sends tabs unaltered. 
But if sending tabs makes a file look irregular or misaligned on a remote 
system, you may want to set a value here.

Remove these characters from outgoing data
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
If certain characters in your files are troublesome or useless to the remote 
system, you may want to list them here; type each as an ASCII hex value 
followed by h, separated from others by /. For example, you might enter 00h / 
7Fh / 0Ch to remove NULs, DELs, and form feeds.

Break signal duration
~~~~~~~~~~~~~~~~~~~~~     
To send a break signal, press CTRL-BREAK on the Comm screen.

Answerback message
~~~~~~~~~~~~~~~~~~     
Your entry can include alphanumeric characters, and/or control and extended 
ASCII characters . 

These settings from the Receiving text menu control the flow of text.

Wait for this character after sending each line
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
For systems that display a prompt at the beginning of each line, enter the 
last prompt character; enter its ASCII hex value followed by "h". Normally, 
this is set to <none> when Duplex is set to "Half". If Text protocol waits 
indefinitely after sending the first line, it could be that you have set this 
to a character which you are never receiving.

Pause after each character/after each line
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
For systems that can accept text only at manual typing speed, try setting 
this to 200 / 250 or to the minimum settings necessary to avoid loss of 
characters. The setting in the previous paragraph is a more efficient way to 
avoid sending too fast; use it instead, whenever possible. (Some programs 
call this pacing.)

XOFF/XON to control sending
~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Set this to "No" and use other settings on the lower half of this menu to 
avoid sending too fast with systems that do not use XOFF and XON for flow 
control.

Incoming characters used for XOFF/XON
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
When systems use other characters, enter their ASCII hex value followed by h 
and separated by /.

Line-end/line-acknowledge used by FreeComm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Since this method has no universally recognized name (it's sometimes called 
ETX/ACK), you may need to examine how this method works (next paragraph) 
before you can identify whether it is used by remote systems of interest to 
you.

Characters used for line-end/line-acknowledge
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
When you have set the previous setting to "Yes", use this option to define 
which character to append to the end of each line you send, and which 
character the remote system sends back to acknowledge receipt of this 
line-end character. To use other characters, enter them as ASCII hex values 
followed by h and separated by /.


                   10.5 Communications port - Std comm port
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To select the communications port type, or to work with settings affecting 
the port, select "Communications-port". Select "Standard comm port". If you 
change to a different port, you'll need to change the "Port" name setting; 
other settings on this menu seldom need changing. To determine which 
connector pins correspond to the signal names used on this menu (CD, DTR, etc.), 
refer to the end of Appendix A.

Port name
~~~~~~~~~     
See Appendix A for a discussion of other possible entries.

Connect signal is input on CD, DSR or CTS
     
The clock in the lower-right corner of the screen counts up when this signal 
is on and stops when it goes off.

Terminal ready signal is output on DTR or RTS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you specify where your PC issues a continuous logic-level high 
signal to tell your modem or communications device that the PC is ready. The 
most common setting is RTS.

Hangup signal is output on DTR or RTS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~      
If your modem has a DTR switch, position it so that the modem hangs up in 
response to DTR.

Incoming hardware handshaking on CTS, CD or DSR
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Most modems and direct-cable connections do not call for hardware handshaking. 
With modems, devices, or direct connections that do use hardware handshaking 
(also called RTS/CTS or EIA flow control), the most common setting here is CTS.

Note: FreeComm automatically sets hardware handshaking for you, so there may 
be no need for you to set values.

Outgoing hardware handshaking on RTS or DSR
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For devices or connections that do use hardware handshaking (also called 
RTS/CTS or EIA flow control), the most common setting here is RTS.

Use port's extended hdw. buffering 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you have FreeComm take advantage of buffering in serial ports from 
certain hardware vendors for faster reliable communications under DOS and DOS 
multitasking environments such as Windows, DESQView, or DoubleDOS. FreeComm 
supports buffers in the Hayes Enhanced Serial Port (ESP), IBM PS/2 Models 90 
and 95, and ports using NS16550A serial chips (as in IBM PS/2 Models 50Z, 60, 
70, 80, and Compaq 386 or 486 PCs). Set this to "Yes" for full-time, 
full-capacity use of buffers. With systems where setting to "Yes" causes loss 
of data, set to "Auto", which responds more quickly to flow control conditions. 
Set to "No" to disable buffering. If your port lacks buffering, FreeComm will 
sense this and disregard your setting.


                 10.6 ASCII protocols - Character translation
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For each system you call, you can specify characters to be stripped or 
translated to other characters as ASCII data is received or sent on the Comm 
screen. (Files transferred with file transfer protocols are unaffected). To 
specify characters, select "Define" and "Modify" from the Main menu, choose 
the desired system, then select ASCII and Character translation. Here is 
additional information to the help of options you can select from the 
Character translation menu.

File used for translation tables
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You can view and modify by selecting "Manage translation tables".

Incoming translation used
~~~~~~~~~~~~~~~~~~~~~~~~~     
Set this to "No" if you want to disable the incoming character translations.

Outgoing translation used
~~~~~~~~~~~~~~~~~~~~~~~~~     
Set this to "No" if you want to disable the outgoing character translations.

Manage translation tables
~~~~~~~~~~~~~~~~~~~~~~~~~     
To strip a character, specify that it be switched to no character. Use the 
applicable ASCII hex character.
     

                          10.7 File transfer protocols
                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Protocol Defaults
~~~~~~~~~~~~~~~~~
To define settings affecting all file transfer protocols, select "File transfer" 
protocols and "Defaults". These options give you the flexibility to define 
separate file transfer default settings for each system, so that you can 
transfer files with minimum of keystrokes.

Receiving directory
~~~~~~~~~~~~~~~~~~~     
Enter no directory name if you wish to receive into your current directory 
(or your FreeComm working directory).

Sending directory
~~~~~~~~~~~~~~~~~     
Enter no setting here, if you want to use your current directory (or your 
FreeComm working directory).

File transfer protocol
~~~~~~~~~~~~~~~~~~~~~~     
For systems where you always use the same protocol, entering a protocol here 
will save you one keystroke per file transfer.

Prompt for filename when receiving
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Xmodem and 1K Xmodem will continue to prompt you for a filename, because these 
protocols do not pass filenames.

Xmodem/Ymodem
~~~~~~~~~~~~~
To verify or correct settings that affect operation of the Xmodem and Ymodem 
file transfer protocols, select File transfer protocols from the System 
settings menu, then select Xmodem or Ymodem to display the Xmodem & Ymodem 
menu.
     
You almost never need to change settings on this menu, because the initial 
settings work well in most circumstances. The settings here affect the 
following protocols: Xmodem Auto, Xmodem Checksum, Xmodem CRC, 1K-Xmodem, 
Ymodem and Ymodem G.

Seconds to wait to receive each packet/byte
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Slower systems such as CompuServe may need to set this as high as 30 / 10. 
(This is referred to as relaxed timing).

Error-checking method
~~~~~~~~~~~~~~~~~~~~~     
Transfers may begin a bit faster if you set this to the type you know the 
remote system supports: Enter CRC for cyclical redundancy checking or "Sum" 
for checksum. Some systems that support only checksum will exchange files 
with you only if you set this to "Sum".

Attempts to send each packet
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
When a transfer fails as a result of exceeding this limit, you may be able to 
force it to successful completion by increasing this setting and repeating 
the transfer.

Compress when possible
~~~~~~~~~~~~~~~~~~~~~~
This lets you set whether files are compressed when possible, with Xmodem and 
Ymodem protocols. Compressing reduces a file's size, so it can be sent in 
less time. This can normally be set to "Yes"; if a remote system lacks this 
compression feature, Delrina FreeComm senses this and skips compressing. Set 
this to "No" if you customarily compress your files with another program 
before you send them, or if your Xmodem transfers with a particular system 
consistently fail within the first couple of packets.

Zmodem
~~~~~~
To verify or correct settings that affect operation of Zmodem file transfer 
protocols, select "File transfer protocols" from the System settings menu, 
then select Zmodem to display the Zmodem menu. You almost never need to change 
settings on this menu, because the initial settings work well in most 
circumstances.

Packet size
~~~~~~~~~~~     
This lets you set the number of bytes in each packet. Larger packets mean 
faster transfer but slower recovery from errors. The most common setting is 
"Auto", which automatically selects a packet size appropriate for the 
circumstances.

Window size
~~~~~~~~~~~     
Specifies the maximum number of bytes Zmodem may send before it stops to wait 
for that data to be acknowledged by the receiver. The most common setting is 
"Unlimited".

Error checking size
~~~~~~~~~~~~~~~~~~~     
This lets you set the size of CRC error-checking codes used. 16 bits is usually 
adequate. Setting to 32 bits further enhances reliability at the expense of 
speed.

Seconds to wait between retries
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
This sets how long Zmodem waits between attempts to re-send packets. The most 
common setting is 10. Through networks where the receiver may lag far behind 
the sender, you may need to increase this setting.

Newline conversion
~~~~~~~~~~~~~~~~~~     
This sets whether a system to which you send a file is allowed to add a 
carriage return after each line feed in the file. Leave this set to "No" 
except when you send text files to systems that follow this different line 
end convention.

Control sequences use escape codes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Set this to "Yes" if you want Zmodem to replace all control codes with 
equivalent series of non-control codes. This may be necessary with networks 
or remote systems that have problems transmitting control codes.

Overwrite/append conditions
~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Lets you specify what a remote system (one that supports Zmodem Management 
options) is to do when you send it files having the same names as existing 
files. Choices are:
     
     Use this option   To perform this operation
     
     None              For systems that don't support Zmodem management options
     Newer or longer   Overwrites if file sent has newer time/date or larger 
                       size
     Longer or CRC     Overwrites if file sent is larger or has different 
                       contents
     Append only       Adds file sent to end of existing file
     Overwrite         Overwrites any file having same name as file sent
     Newer only        Overwrites if file sent has a more recent time/date
     Length or date    Overwrites if file sent has different size or time/date
     Never overwrite   Rejects file sent if its name matches an existing file




Automatically receive files
~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Leave this set to "Yes" if you want FreeComm to begin receiving automatically 
the instant you command a remote system to send. Files will be stored into 
your default directory; if matching filenames exist, the new ones are renamed. 
If you set this to "No", you will need to press ALT-O, T, R to begin receiving 
each time.

Keep partially received files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Set this to "Yes" to keep partial files resulting from interrupted or aborted 
transfers. Using this setting will make it feasible for you to pick up the 
rest of a file later, by setting the "Resume broken transfers" to "Enable".

Resume broken transfers
~~~~~~~~~~~~~~~~~~~~~~~     
This sets whether Zmodem file recovery (crash recovery), a feature designed 
to let you resume interrupted transfers, will occur. (Also see Keep partially 
received files, above.) Choices are:
     
     Use this option   To perform this operation
     
     Enable            Set to Enable ONLY while you transfer the remaining 
                       portion of a file, to be appended to the part that was 
                       transferred earlier. File recovery will occur whether 
                       you are sending or receiving, provided the remote 
                       computer has recovery set to "Negotiate" or "Enable".
     Disable           Set to "Disable" to prevent file recovery from occurring, 
                       even if the remote computer has file recovery enabled.
     Negotiate         Use this setting most of the time. This allows recovery 
                       to occur when file recovery is enabled on a remote 
                       computer.

Kermit
~~~~~~
To verify or correct settings that affect operation of Kermit file transfer 
protocol, select "File transfer protocols" from the System settings menu, and 
then select Kermit. You can find any information in the on-line help. You 
seldom need to change settings on this menu, because the initial settings 
work well in most circumstances.

HyperProtocol
~~~~~~~~~~~~~
To verify or correct settings that affect operation of HyperProtocol refer to 
the on-line help. Select "File transfer protocols" from the System settings 
menu, and then select HyperProtocol to change settings. However, HyperProtocol 
automatically adapts to the conditions under which it is used, there are 
relatively few details to set.


                             10.8 Hardware - Modem
                            ~~~~~~~~~~~~~~~~~~~~~~~
To select the modem or communications device you will use when communicating 
with a system, select "Hardware" from the System setting menu, and then select 
"Modem".

     
It's unlikely you'll need to make changes on this menu unless you use a 
variety of modems or communications devices.

Modem name
~~~~~~~~~~     
If your modem is not in the list but supports the extended AT command set 
(including &C1), select Hayes Smartmodem 2400; if it supports the basic AT 
command set, select Other Hayes-compatible modem; if it supports dialing 
commands that do not begin with AT, select "User-defined modem". If you are 
connecting with a system via cable alone, set this to "Direct-cable".

Additional modem setup commands
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
To activate other modem features or alter the modem configuration, look up 
the appropriate commands in your modem manual, and set them here.

Dialing method
~~~~~~~~~~~~~~     
Set it to pulse dialing if you have a phone system that cannot support tone 
dialing.

Prefix for telephone number
~~~~~~~~~~~~~~~~~~~~~~~~~~~     
If you prefer, you can enter such numbers along with the telephone number as 
described in Chapter 10.

Suffix for telephone number
~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you specify a suffix that will be added to the telephone number you 
have entered on the System settings menu. 


                            10.9 Hardware - Printer
                           ~~~~~~~~~~~~~~~~~~~~~~~~~
To set or review settings that pertain to your printer, select "Hardware", and 
then select "Printer".

Printer device name
~~~~~~~~~~~~~~~~~~~     
You can enter the name of any print device which is valid with your operating 
system (even a filename, if you prefer to print to a disk file).

Buffer size
~~~~~~~~~~~     
FreeComm prevents this buffer from overflowing by controlling the flow of 
incoming data using the flow control method set on the Receiving text menu or 
Communications port menu.

Top margin added to each page
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
This does not change text or files that you print, it merely alters appearance 
of printouts. The most common setting is 6 lines, which on most printers 
positions text about an inch from the top of the page. Set this to 0 lines 
for no top margin.

Left margin added to each page
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You may want to reduce this setting when printing text that contains a left 
margin.

Number of lines of text per page
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
This does not change text or files that you print, it merely alters the 
appearance of printouts. If your printer or top margin are different, you may 
need to use a larger or smaller number. To prevent automatic pagination, set 
this to 0.


                              10.10 Display colors
                             ~~~~~~~~~~~~~~~~~~~~~~
To set colors to taste, or to suit monitor types that simulate color with 
shading, select "Colors" from the System settings menu. Next, select "Menus", 
"Comm-screen" or "Bottom-line", depending on the facet of display you want to 
set. Press ALT-H for on-line help for any display settings. If you start 
FreeComm with the /BW option or have a monochrome display, color settings are 
ignored.

FreeComm for DOS displays by writing directly to video memory for enhanced 
speed. If necessary, start FreeComm with the /B option, to make it display 
through your PC's BIOS instead. BIOS display is desirable on PCs that exhibit 
"snow," or with older versions of Windows, DESQview, or DoubleDOS, which 
favor "well-behaved" display techniques.


                            10.11 Miscellaneous
                           ~~~~~~~~~~~~~~~~~~~~~
To set or review settings that pertain to memory usage and other assorted 
items, select "Miscellaneous".

About memory usage under DOS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FreeComm evaluates the type and amount of memory available in your PC and 
adapts automatically for fastest possible operation. On PCs with extended or 
expanded memory (memory above the 640K boundary), FreeComm uses extended or 
expanded memory as a memory cache for program overlay files, which makes the 
program run noticeably faster.

FreeComm can run in as little as 380K. If additional memory is available 
below the 640K boundary, FreeComm dynamically allocates some or all of that 
memory, depending on which FreeComm features you are using at the time, and 
on how you have set the first two options on this menu. During file transfers 
using compression and virus filtering, for example, FreeComm uses an additional 
50K.

When it is available, FreeComm will use another 70K for memory caching, to 
make scripts run faster.
     
When you jump to DOS from the Use DOS menu, or while callers run your PC 
remotely, FreeComm frees up virtually all of your PC's memory, by storing 
itself to disk. If you can create a 500K ram disk (using memory above 640K) 
for it to use, this operation will be much faster. To instruct FreeComm to 
use the ram disk, include the line TMP=<name of ram disk> in your AUTOEXEC.BAT 
file.

Unprocessed received data buffer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
FreeComm prevents this buffer from overflowing by controlling the flow of 
incoming data, using the flow control method set on the Receiving text or 
Communications port menus.

Review buffer
~~~~~~~~~~~~~     
The memory used is external to that occupied by FreeComm and with DOS the 
amount of external memory varies; if it is less than 250000 bytes, the 
setting range is reduced. Smaller settings leave more memory for the Use DOS 
menu.

Key assignment file to load on Keys menu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This lets you invoke key assignments specifically tailored to the system you're 
calling; the key assignment file listed here is automatically loaded on the 
Keys menu (that is, it becomes the entry for File used for key assignments). 

Log calls and transfers in file
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Use any filename you like; if the file does not exist, it will be created. 
Logging consumes little disk space and adds only a split-second to each 
transfer. If you want to prevent logging, enter no filename.


                                Appendix A
                               ~~~~~~~~~~~~
Modems, COM Ports, and Cables
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Delrina FreeComm has built-in support for more than 175 specific modem models, 
generic modem types, ISDN terminal adapters, and RS232 direct-cable 
connections. The fact that FreeComm knows how to operate such a wide variety of 
devices makes getting started surprisingly easy. To help you get your hardware 
set up properly, this appendix gives information on modems, port selection, 
and cables.

To install an external, stand-alone modem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Most PCs come with one or two serial ports, COM1 and COM2, to which you can 
connect a modem. To locate the COM1 or COM2 connector, see your computer 
manual. To connect the modem to the port, use a standard RS232 cable as 
described later in this appendix.

To install an internal modem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Install your modem according to instructions in your modem manual; when you 
set its switches or jumpers, keep in mind that no two devices in the PC can 
use the same address (COM1, COM2, etc.). If COM1 and COM2 are already in use, 
perhaps you can use COM3 or COM4; see "Com Port Selection".
     
COM port selection
~~~~~~~~~~~~~~~~~~     
You can select the appropriate COM port as you install FreeComm or by entering 
settings on FreeComm menus. It is unnecessary to run the DOS MODE program to 
select or prepare the COM port. Which ports you can use depends on the type 
of PC and how the PC is equipped:

PC, XT, AT, 386, or 486 with DOS

You can enter COM1 or COM2, or COM3 or COM4 if you have an internal modem 
with switches or jumpers that support these choices. If you enter COM3 or 
COM4, FreeComm will replace your entry with that port's most common port address 
and interrupt level a hex address followed by 2 to 5 (for IRQ2 to IRQ5). This 
is 3E8h, 4 for COM3 and 2E8h, 3 for COM4. You can enter different addresses 
and interrupt levels as needed.
     
If IRQ2 through IRQ5 are already being used by other devices (hard disks and 
buss mice may use IRQ2 and IRQ5; COM2 uses IRQ3; COM1 uses IRQ4), try 
configuring the modem to use IRQ4 or IRQ3, anyway. Your modem may or may not 
work when configured to the same IRQ level as COM1 or COM2, depending on 
whether your particular brand of PC supports sharing IRQs.

Zenith or Heath computers with Z304/Z404 card and DOS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You can use these computers' conventional COM1 or COM2 ports by entering COM1 
or COM2. Or you can enter COM3 to use the Z304 or Z404 card's non-standard 
port; FreeComm verifies presence of this port and replaces your entry with the 
correct address and interrupt. (The maximum speed of this port is 19,200 bps.)

PS/2 or other PC with a MicroChannel and DOS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You may enter COM1 through COM8.

RS232 Cable Specifications
~~~~~~~~~~~~~~~~~~~~~~~~~~
There are two basic types of RS232 cables: standard and null modem. Standard 
cables are for connecting PCs to modems, printers, or other peripheral devices 
(DTE to DCE), while null modem cables are for connecting one PC to another PC 
(DTE to DTE).
     
You can distinguish these cable types by which pins at one end connect to 
pins at the other. If pin 2 connects to pin 2, it's a standard cable; if 2 
connects to 3, it's a null modem cable.
     
For use with a modem, standard 25-pin to 25-pin cables should have conductors 
for at least pins 2-8 and 20.

Standard cable for connecting a 9-pin PC port to a 25-pin modem 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Send signal;

     Pin # on 25-pin cable end       Pin # on 9-pin cable end
              2 (TD)                 3 (TD)
              3 (RD)                 2 (RD)
              4 (RTS)                7 (RTS)
              5 (CTS)                8 (CTS)
              7 (GND)                5 (GND)
              8 (CD)                 1 (CD)
              20 (DTR)               4 (DTR)
              22 (RNG)               9 (RNG)

Null modem cable for connecting 9-pin PC ports to 25-pin PC ports
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Pin # on 25-pin cable end   Pin # on 9-pin cable end
            2 (TD)                2 (RD)
            3 (RD)                3 (TD)
            4 (RTS)               8 (CTS)
            5 (CTS)               7 (RTS)
            7 (GND)               5 (GND)
      6 (DSR) and 8 (CD)          4 (DTR)
           20 (DTR)           1 (CD) and 6 (DSR)

Null modem cable for connecting 25-pin PC ports to 25-pin PC ports
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Pin # on one cable end      Pin # on other cable end
            2 (TD)                3 (RD)
            3 (RD)                2 (TD)
            4 (RTS)               5 (CTS)
            5 (CTS)               4 (RTS)
      6 (DSR) and 8 (CD)          20 (DTR)
            7 (GND)               7 (GND)
           20 (DTR)          6 (DSR) and 8 CD)

Null modem cable for connecting a 9-pin PC port to a 9-pin PC port
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Pin # on one cable end     Pin # on other cable end
     1 (CD) and 6 (DSR)           4 (DTR)
     2 (RD)                       3 (TD)
     3 (TD)                       2 (RD)
     4 (DTR)                1 (CD) and 6 (DSR)
     5 (GND)                      5 (GND)
     7 (RTS)                      8 (CTS)
     8 (CTS)                      7 (RTS)


                                 Appendix B
                                ~~~~~~~~~~~~
Glossary of Program Messages
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
This appendix alphabetically lists the messages that may appear while you are 
working with FreeComm. The probable cause of each message is given, followed 
by a description of actions you can take, if appropriate.

A data connection could not be established
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You were unable to switch a voice call to a data call because the other party 
used the wrong commands to instruct his modem to emit a carrier tone, or took 
too long to issue the commands. Check for the source of the problem and try 
again.

A directory or file with that name already exists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Someone who called "Answer mode", when using the MKDIR (or MD) command, 
specified a directory or filename which was already in use. He should repeat 
the operation with a different directory name.

A filename must be entered
~~~~~~~~~~~~~~~~~~~~~~~~~~     
You either failed to enter a filename in preparing for an Xmodem or 1K Xmodem 
transfer, or someone who called Answer mode failed to enter a filename when 
using FIND, DELETE, XSEND or XREC. Repeat the operation and enter a filename.

A second function is required
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You omitted the second function from a script line that begins with "if" or 
"ifnot". Add another function at the end of the line.

Access to that directory has been denied
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Someone who called "Answer mode" attempted to access a directory which was 
outside the area to which he has been permitted access. He must restrict his 
activities to the authorized area. To change the area that the caller can 
access, see Chapter 8.

Additional files refused
~~~~~~~~~~~~~~~~~~~~~~~~     
Your call log or answer log file will contain this message if the remote 
system attempts to send more than one file after you have commanded FreeComm 
to receive a single file (by entering a single filename).

An error occurred reading the directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Someone who called Answer mode attempted to display a directory which could 
not be displayed, because the specified drive or directory does not exist or 
the drive door is open. The caller should enter a different directory name.

An illegal key sequence encountered in a command, macro, or script
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have included a key name in a macro or command (or in a type function in 
a script) which is not valid. Replace the unrecognized key name with one which 
is valid.

Bad structure
~~~~~~~~~~~~~     
Your script contains a line which does not have balanced parentheses. Correct 
the line, being certain to include an equal number of left and right 
parentheses.

Can't change to the specified drive
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Someone who called "Answer mode" attempted to use the CHDIR command to change 
to a directory which either does not exist or is on a drive whose door is 
open. The caller should enter a different directory name.

Can't compile the script
~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to run a script but it could not be compiled either due to 
absence of the compiler (DFCHP.EXE for DOS) or insufficient memory (DOS only). 
Check for presence of the compiler. If you are using DOS and cannot free up 
additional memory, you can compile the script from the DOS command line by 
entering DFCDOS <script name>.

Can't copy (or move) a file to itself
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered the same source and destination during a copy or move operation. 
Repeat the operation, specifying different source and destination.

Can't create <filename>.
~~~~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that it could not create this file. An 
accompanying message will give the reason; refer to that message (listed 
separately in this appendix) for more information.

Can't create temporary script file
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to run a script but its temporary file could not be created, 
due to insufficient disk space or too many files in your root directory. Free 
up disk space or reduce the number of files in your root directory, then try 
running the script again.

Can't find a system with that name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a system name that is not present in the System List on the Main 
menu. Repeat the operation, taking care to enter the system name exactly as 
it appears in the System List (or select it by using UP ARROW and DOWN ARROW, 
and pressing ENTER).

Can't find device <device name>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You specified a device (printer, drive, etc.) which does not exist. Specify 
only devices which do exist on your PC, such as LPT1 or COM1.

Can't find directory that contains Delrina FreeComm.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You started FreeComm from a drive or directory which does not contain the 
program without first defining a path to the drive or directory which does 
contain the program (applies only to version 2 of DOS). Use the DOS PATH 
command to define a path to the drive or directory which contains FreeComm, 
and then start FreeComm again.

Can't find drive X. Try some other drive.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You specified a drive which does not exist on your computer. Check to see what 
drives are present on your PC (A, B, C, etc.) and specify only those drives.

Can't find <filename>
~~~~~~~~~~~~~~~~~~~~~     
You specified a filename which does not exist, or is not in the specified 
directory. Repeat the operation, entering the correct filename.

Can't find specified drive. Try some other drive.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You specified a drive which does not exist on your PC. Repeat the operation 
and specify a drive which does exist.

Can't find that modem name in the list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a modem name which does not exist in the list of supported modems. 
Repeat the operation, being certain to enter a name exactly as it appears in 
the list of supported modems and devices (or select it by using UP ARROW, 
DOWN ARROW, CTRL-RIGHT ARRROW, CTRL-LEFT ARROW and pressing ENTER). If the 
name of your modem or device is not shown in the list, select an appropriate 
generic modem type such as "Other Hayes-compatible modem".

Can't find that password in the password list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a password which does not exist, when managing the password list. 
Repeat the operation, entering a password that is present in the password list.

Can't find that pattern in any system name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered characters which exist in no system's name, when using the "Find" 
option. Try entering other characters.

Can't find the .HP for that scriptname
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You tried to run a script for which there was no compiled version; this 
automatically triggering an attempt to compile the script, but the attempt 
failed because the .HP file was missing also. If the .HP file exists on 
another disk or directory, copy it to your working disk or directory and try 
running it again; if the .HP file does not exist, you will need to create it.

Can't find the specified path
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Someone who called "Answer mode" and used CHDIR and entered a nonexistent 
pathname. He should repeat the operation, including a different pathname on 
the line with the command.

Can't lock <filename>.
~~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that it could not lock this file. An accompanying 
message will give the reason; refer to that message (listed separately in 
this appendix) for more information.

Can't open <filename>.
~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that it could not could not open this file. An 
accompanying message will give the reason; refer to that message (listed 
separately in this appendix) for more information.

Can't open or create <filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You performed an operation which could not open a file (because it was 
write-protected or the maximum number of files were already open) or could 
not create a file (because the maximum number of files were already open or 
your root directory contains too many files). Check for the source of the 
error and repeat the operation. (To increase the number of files your 
operating system will allow to be open at one time, increase the FILES= 
setting in your CONFIG.SYS file and reboot.)

Can't perform transfer: invalid option specified
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have used a slash option that is incompatible with the selected protocol 
or with this type of transfer (sending or receiving). Repeat the operation, 
following slash option guidelines in Chapter 3.

Can't read all of the file.
~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have attempted to load a file into the Editor which contains lines longer 
than 253 characters. Files which contain lines longer than 253 characters 
cannot be loaded into the Editor.

Can't read <filename> from disk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which could not read the specified file either 
because the drive was not ready (door open) or the file was damaged. Check 
for the source of the problem and repeat the operation.

Can't read <filename> from drive X.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that it could not could not read this file from 
this drive. An accompanying message will give the reason; refer to that message 
(listed separately in this appendix) for more information.

Can't read from or write to the monitor in session <session name>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which attempted to use a session started from the 
Use OS/2 menu, but OS/2 could not access the session. OS/2 may prevent access 
to a session due to factors which are beyond a user's control. If the problem 
persists, contact Hilgraeve Product Support.

Can't receive into the capture file when capturing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to receive data (using "Transfer" and "Receive") into a file 
that is already being used use by "Capture"; these two operations cannot 
simultaneously write to the same file. Select "Capture" and "End", and then use 
"Transfer" and "Receive".

Can't rename the file
~~~~~~~~~~~~~~~~~~~~~     
Someone who called "Answer mode" attempted to rename a file which could not be 
renamed, because:
     
1. The file could not be found.
2. The new name was already in use.
3. The new name included a different drive name.
     
The caller should check to see which cause applies and enter new file names 
that resolve the problem.

Can't resume script execution from this program location
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your script had a type function (or ran a macro or command) which contained 
keys which departed the Comm screen, but which lacked keys necessary to return 
to the Comm screen; when the type function finished, subsequent lines in the 
script could not be executed because the Comm screen was not displayed. The 
script will resume when you return to the Comm screen. In order to avoid
having scripts "stall" at locations other than the Comm screen, be certain 
that every type which contains keys that depart the Comm screen also contains 
keys that return to the Comm screen.

Can't send the capture file when capturing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to send a file (using "Transfer" and "Send") which was already 
in use by Capture; these two operations cannot simultaneously use the same 
file. Select "Capture" and "End", and then use "Transfer" and "Send".

Can't set N baud using nearest settable rate of M
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a baud rate not supported by your communications port, so the 
baud rate has been set to the nearest possible setting. You may proceed with 
the baud rate which has been selected for you, or enter another baud rate.

Can't use wildcards in the filename
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to use * or ? in a filename, when using the "Files" option 
"Rename" or the "Host" command "Rename" (which can rename only one file at a 
time). Repeat the operation without using * or ? in the filename.

Can't write to <filename>.
~~~~~~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that it could not write this file. An 
accompanying message will give the reason; refer to that message (listed 
separately in this appendix) for more information.

Can't write <filename> to disk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which could not write to disk either because the 
disk was full, the directory already contains too many files, or the drive 
was write-protected. Check for the source of the problem and repeat the 
operation.

Can't write <filename> to drive X.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that it could not write this file to this drive. 
An accompanying message will give the reason; refer to that message (listed 
separately in this appendix) for more information.

Could not create <script name>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your script could not be compiled because the disk is full or there are too 
many files in your directory. Free up additional disk space or reduce the 
number of files in your directory, then try again.

Could not open <script name>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to compile a script file which the compiler could not open, 
either because the file cannot be found or is already in use by another 
process. Check for the source of the problem and try again.

Damaged .RDY file recompile the script
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to run a script but could not because its .RDY file either is 
corrupted or was created by a compiler other than the one supplied with your 
current revision of FreeComm. Delete the .RDY file, then run the script again; 
this will cause the script's .HP file to be compiled, producing a new .RDY 
file.

Device <device name> is not ready.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to write data to a device (printer, drive, etc.) which was not 
ready to accept data. If the device was your printer, perhaps it is off, 
off-line, or improperly connected.

Diagnostic error #N
~~~~~~~~~~~~~~~~~~~     
Unusual circumstances arising from your particular hardware, configuration, 
or application have caused a program error. If a specific sequence of steps 
consistently produces a given diagnostic error, leave comments in the Delrina 
Compuserve forum.

Dialed <system name> 20 times w/o connecting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You used "Call a system" to dial a remote system, but the call did not go 
through; the telephone number that was dialed either was busy, did not answer, 
or (data calls only) would not accept a data call. Be certain the telephone 
number is correct, then try again. If the number was busy, you might try 
calling at a different time of day.

Disk full
~~~~~~~~~     
Your attempt to compile a script failed due to insufficient disk space. Free 
up additional disk space and repeat the operation.

Disk is unformatted. Format disk and try again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
The disk you accessed appears not to have been formatted. Use your operating 
system's FORMAT program to format the disk.

Drive door is open. Close door and try again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to access a drive which was not closed. Close (or re-close) the 
drive door and try again.

Error building Directory
~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to display a directory but could not, either because of 
insufficient memory, a locked drive, or a disk error. Check for the source of 
the error and repeat the operation.

Error on device <device name> (<error type>).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to write data to a device (printer, drive, etc.) which reported 
an error of the type shown. Check the device for the cause of the error and 
try again.

Error on disk or drive (<error type>). Check disk and drive.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your operating system reported a disk or drive error of the type shown in 
parentheses, due to an apparent drive or disk defect. If you have Norton 
Utilities or an equivalent disk management program, refer to it for possible 
remedies. (With floppy disks, the problem may clear up if you open the drive, 
re-insert the diskette, and close the drive).

Error writing to specified drive. Check disk and drive.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your operating system reported a disk or drive error. If you have a disk 
management program, refer to it for possible remedies. (With floppy disks, 
the problem may clear up if you open the drive, re-insert the diskette, and 
close the drive).

Expecting a number from 0-999
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You used a non-numeric value within the parentheses of a label, branch, or 
branch subroutine function. Replace the value with a number between 0 and 999. 
(Integer variables cannot be used in these functions.)

File <filename> is damaged
~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which accessed one of the FreeComm program files 
and the file appeared to be corrupted. Either copy the file from a backup 
disk, retrieve it from the original FreeComm diskettes, or re-install FreeComm. 

File is already locked by another program.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which attempted to lock a file already locked by 
another program. Check to see which other program is using the file, have 
that program close the file, then try again.

File is read only or in use by another program.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to open or create a file which was already in use by another 
program. Check to see which other program is using the file, have that program 
close the file, then try again.

<filename> is in use by another program.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to perform a process which needs to use the specified file, 
but the file was already being used by another session. Either specify a 
different file or stop the other session from using this file, then repeat 
the operation.

Flag variable expected
~~~~~~~~~~~~~~~~~~~~~~     
You used the wrong type of argument in a script function which calls for a 
flag variable argument. Replace the argument with a flag variable, F(0) - F(9).

Incorrect password
~~~~~~~~~~~~~~~~~~     
Either you have entered the wrong password when trying to access the "Password 
List" on the Answer menu, or someone who has called "Answer mode" has entered 
an invalid password. If you encountered this message in attempting to access 
the Password List, repeat the operation and enter the precise password that 
was used to lock the Password List; if the password is lost, you can never 
again access the Password List (though you can delete the password file 
(FreeComm.ANS) and create all new passwords). If this message was encountered 
by a caller, he should enter his password again; it may have been corrupted 
by line noise when he first entered it.

Increase the FILES= entry in CONFIG.SYS and reboot.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You performed an operation which attempted to create or open a file, but the 
operating system reported that the maximum number of files were already open. 
Edit the CONFIG.SYS file (found on your boot disk, in your boot directory) by 
adding to it the line FILES=20 then reboot your computer and try the operation 
again. If this line is already present increase the number it contains.

Integer variable expected
~~~~~~~~~~~~~~~~~~~~~~~~~     
You used the wrong type of argument in a script function which calls for an 
integer variable argument. Replace the argument with an appropriate integer 
variable name, I(0) - I(9).

Label declared twice
~~~~~~~~~~~~~~~~~~~~     
You used the same number in two label statements in your script. Correct the 
script so that each label contains unique labelnames.

Line N is too long
~~~~~~~~~~~~~~~~~~     
You constructed a script line that exceeds the maximum length (128 characters). 
Avoid creating lines longer than 128 characters.

Macro sequences can't contain <ALT-L>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You are prevented from including ALT-L in a macro because macros cannot start 
learning. Avoid including ALT-L in macros.

No argument expected here
~~~~~~~~~~~~~~~~~~~~~~~~~     
Your script contains a function in which you used more than the acceptable 
number of arguments. Refer to information on that function in Chapter 12 and 
use the recommended number of arguments.

No match for text found.
~~~~~~~~~~~~~~~~~~~~~~~~     
You have entered text (a character or string) which is not present in the 
Editor or Review buffer, during a "Find" or "Replace" operation. Repeat the 
operation, entering a character or string which does occur in the text.

No passwords have been defined
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You selected an option from the Answer menu which cannot be used when no 
passwords have been defined. Define at least one password and repeat the 
operation.

No script file specified
~~~~~~~~~~~~~~~~~~~~~~~~     
You failed to specify the name of a script when running the HyperPilot 
compiler from the operating system prompt. Run the compiler again, including 
the name of the script that is to be compiled. For example, you might enter 
DFCDOS SAMPLE to compile the script SAMPLE.HP.

Not a valid filename
~~~~~~~~~~~~~~~~~~~~     
You entered characters which were not a valid filename. Repeat the operation, 
entering up to 8 characters, a period, and up to three characters. See your 
operating system manual for guidelines on use of filenames.

Not enough memory or COMMAND.COM not available
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your attempt to run a DOS command or program failed either because there is 
insufficient memory to run it or the COMMAND.COM file is not present. If you 
cannot free up additional memory, then quit FreeComm and run the command or 
program from the DOS command prompt; quitting usually does not make your 
modem hang up, so you may be able to return to FreeComm, Load the correct 
system settings, and resume an on-going call. If COMMAND.COM is absent because 
you booted from a diskette which you've since removed from the drive, 
re-insert that diskette. (With DOS 2.0 or 2.1, copy COMMAND.COM into the 
FreeComm directory.)

Not enough memory to (or for) <operation>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You attempted to perform an operation that requires additional memory and not 
enough memory was available. If the operation that caused the error is 
inconsequential (say, displaying a large directory), just skip the operation 
and go on with your work. If the operation is important, free up additional 
memory (remove TSR programs, reduce memory cache or RAM-disk size, etc.) and 
repeat the operation.

Not enough memory to perform transfer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your call log or answer log file will contain this message if you attempt to 
perform a file transfer but there is insufficient memory available for the 
transfer to begin. Free up additional memory and try again.

Not enough room on disk for <script name>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to compile a script but the compiled version of the script 
could not be stored, due to insufficient disk space. Free up additional disk 
space and try again.

Number or integer variable expected
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You used the wrong type of argument in a script function which calls for a 
numeric argument or an integer variable argument. Replace the argument with a 
number or the name of an integer variable, I(0) - I(9).

One or more selected systems are in use by another instance of the program
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to modify a group of systems or access the Preferences menu, 
but DOS reported that one or more of the systems were already in use. If 
FreeComm is installed on a network server, perhaps another person is 
simultaneously running FreeComm and one of the systems. Some versions of DOS 
report this problem even when it cannot exist (say, on standalone DOS PCs); 
if this occurs on your PC, start FreeComm with the /K option.

Out of memory in line N
~~~~~~~~~~~~~~~~~~~~~~~     
Your script is too large to be compiled. Reduce the size of the script until 
it compiles without causing this message. Maximum size depends on script 
complexity and is approximately 45K.

Overloaded operating system. Remove some running programs and try again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which needs to use resources your operating system 
could not supply, due to the number of other concurrent sessions. Close some 
sessions and repeat the operation.

Please enter a number from M to N
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a number which was out of the acceptable range. Enter a number 
which is within the valid range for this entry. (The range for each entry is 
given in Chapter 10; numbers entered in response to key functions in scripts 
must be between -231 and +231.)

Please enter a single filename
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered more than one filename for an entry which calls for only one 
filename. Repeat the operation, entering a single filename.

Please enter a time of day
~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a value which did not follow the correct format for a time of 
day entry. Repeat the operation, entering the time using the format HH:MM, 
where one minute before midnight is 23:59.

Please enter M value(s)
~~~~~~~~~~~~~~~~~~~~~~~     
You entered fewer or more values than are called for. Repeat the entry, 
including the correct number of values.

Please enter Y or N
~~~~~~~~~~~~~~~~~~~     
You entered an incorrect response. Try again, this time entering "Y" or "YES", 
or "N" or "NO", in either upper- or lower-case.

Please specify a filename
~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered no filename at a point where entering one was mandatory. Repeat 
the operation, entering a filename.

Printer buffer is full, please stand by.
(To cancel printing from <source>, press ESC)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You selected a printing operation which cannot begin until a previous printing 
job finishes. You may wait for the previous job to finish and for the current 
one to begin, or press ESC to cancel your current printing operation.

Printer is out of paper
~~~~~~~~~~~~~~~~~~~~~~~     
The operating system reported that your printer was out of paper. Put more 
paper in the printer, or if it is not out of paper, check for hardware 
problems that caused the error to be reported.

Reference to undefined label N
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your script includes a goto, gosub or branch function containing a label 
number that is not present in the script. Correct the function to use label 
numbers that do exist or add the missing label to your script.

Remove write protection from device X.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to write data to a device (printer, drive, etc.) which was 
write protected. Either refrain from writing to write-protected devices or 
remove write protection from the device.

Remove write protection from disk in drive X and try again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to access a floppy disk which is write-protected. With a 5" 
disk, remove the write protect sticker which is covering the notch on the 
side of the diskette; with a 3" disk, reposition the tab located in the 
diskette's corner so that light cannot pass through the small opening.

return() executed while not in subroutine
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You ran a script which failed because it encountered a return function which 
was not preceded by a branch subroutine function. Locate subroutines at a 
point in your script where they cannot be executed unless gosub (or branch 
subroutine) has branched to that location.

Script stopped at line N
~~~~~~~~~~~~~~~~~~~~~~~~     
Your script stopped because this line contains a function which, for some 
reason, was unable to perform its task. See Chapter 11.

Sending suspended while waiting for <XON, CTS, 0Dh, etc.>. Please stand by 
(or press ESC to force continuation)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your PC is waiting for a signal (XON, 0Dh, CTS, etc.) to resume sending, 
after having been stopped by flow control. The cause and possible remedies 
depend on which signal your PC is waiting for:

XON
     It appears that the remote system sent an XOFF character to suspend 
     sending but never sent an XON character to resume; perhaps the XON 
     character was corrupted by line noise. Wait for the XON to arrive or 
     press ESC to continue sending as though the XON had been received.

CTS, DSR or CD
     This incoming hardware handshaking signal remained off for an usually 
     long time; perhaps the external device is not generating the expected 
     signal, your cable configuration is incorrect, or the setting for 
     "Incoming hardware handshaking" is wrong (see Chapter 10). Wait for the 
     signal to go on or press ESC to ignore absence of the signal for the 
     balance of the session.

0Dh or some other character   
    A setting on the Sending text menu (Wait for this character or Line 
    end/line acknowledge) requires that sending stop and wait for this 
    character after each line is sent with Text protocol; perhaps the 
    character was corrupted by line noise or your menu setting was incorrect 
    (see Chapter 10).  Wait for the character to arrive or press ESC to 
    continue sending as though the character had been received. (If the 
    problem persists, your menu setting is probably incorrect.)

String expected
~~~~~~~~~~~~~~~
You used the wrong type of argument in a script function where an argument 
consisting of a string enclosed in quotation marks is required. Replace the 
argument with a string of text, enclosed in quotation marks. If it was your 
intention to include no string, you must do this by including an empty pair 
of quotation marks ("").

String variable expected
~~~~~~~~~~~~~~~~~~~~~~~~
You used the wrong type of argument in a script function which calls for a 
string variable. Replace the argument with a string variable name, S(0) - S(9).

Subroutines nested beyond limit of 16
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You ran a script which failed because its subroutines were nested (subroutines 
within subroutines within subroutines) beyond the permissible limit of 16. 
Make sure your script does not exceed this limit.

Temporary file <filename> is damaged
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You attempted to run a script but its temporary file has been deleted, 
overwritten or damaged by a disk error. Check to see if another program has 
deleted or overwritten the file or if the script itself contains functions 
that may do this. Restart the script so that the temporary file will be 
recreated. If the error occurs again, your disk or drive may be defective.

That file is too big to edit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You attempted to load a file into the Editor but there was insufficient disk 
space or memory for it to be loaded. The Editor can accommodate a file of 
unlimited size, provided there is sufficient memory and/or disk space. Up to 
120K of the file is kept in memory (less, if less memory is available) and 
the rest is kept on disk in a temporary disk file. Free up additional memory 
and/or disk space, then try loading the file again.

That key is restricted, please select another
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have attempted to assign a sequence to a key which cannot be used for 
this purpose. Press a key other than ALT-A, -C, -D, -R, -F, -H, -L, -M, -O, 
ESC, or ENTER.

That option is not available during block operation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to use regular Editor options such as "Paste", "Load" or 
"Replace", without first concluding the block selection (which you initiated 
by pressing ALT-B). Complete the block selection operation or press ESC to 
cancel it, then select "Paste", "Load", "Replace", etc.

That password already exists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have attempted to add to the Password List a password identical to one 
already in the List. Repeat the operation, specifying a unique password.

That script or program is not in the list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered the name of a script or program which is not shown at the bottom 
of the Privileges menu. Repeat the operation, entering the name of a script 
or program which is shown, or select it using the ARROW KEYS and ENTER.

That system is not in the list--do you want to add it?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered the name of a system that is not currently in the System List, 
after selecting "Call a system". If you answer "Yes" you can add the system 
now and call it as soon as you're finished.

That system is in use by another instance of the program
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to use a system from the System List on the Main menu, but DOS 
reported that that system was already in use. If FreeComm is installed on a 
network, perhaps another user is simultaneously running FreeComm and using 
that system. Some versions of DOS report this problem even when it cannot 
exist (say, on a standalone DOS PC); if this occurs on your PC, start FreeComm 
with the /K option.

That's an invalid drive or directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a drive or directory which did not exist, when using the Files 
option "Find". Repeat the operation, entering the correct drive or directory.

The disk is full. Remove some files from the disk and try again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which needed to write to disk, but the disk was 
full. Free up additional disk space and repeat the operation.

The file contains lines that are too long to display.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have attempted to create (or load a file which contains) a line longer 
than 253 characters, while in the Editor or Review buffer. When typing, be 
certain to end lines before they reach 253 characters in length. Files which 
contain lines longer than 253 characters cannot be loaded into the Editor.

The list of sessions is full
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to start another session, but the list already contained the 
maximum number of sessions (11). Close one of your existing sessions and 
repeat the operation.

The password list has been modified since last read
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to perform an operation on the Answer menu but could not, 
because another, concurrent FreeComm session has at the same time made changes 
to the Password List. Leave the Answer menu, then return to it so that the 
Password List will be updated to include the changes made by the other session; 
then repeat the operation you were attempting to perform.

The password list is full
~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to add another password to the Password List on the Answer menu, 
but the Password List already contained the maximum number of passwords 
(2,000). Delete any passwords which are no longer used and try again.

The script and program list is full
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to add a script or program for a caller to run, but the list 
already contained the maximum number of entries (12). You can list only 12 
scripts or programs for each caller.

The specified drive is locked
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which needed to access a drive which has been 
locked by another program. Specify a different drive or have the other 
program unlock the drive, then repeat the operation.

The system list is full
~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to add another system to the System List on the Main menu, but 
the System List already contained the maximum number of systems (2,000). 
Delete any systems that you no longer use and try again. If you may need the 
systems in the future, use Export to save them first, so you can later restore 
them with "Import".

There are no lines in the list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to delete or modify a line in the Password List (or script and 
program list) at a time when the list was empty. You must add a line to the 
list before performing these operations.

There is no script, macro or command named <sequence name>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered the name of a sequence which does not exist. Repeat the operation, 
taking care to enter the name of an existing sequence. To display a list of 
sequences from which to select, press ALT-D after pressing ALT-R.

There were no files found
~~~~~~~~~~~~~~~~~~~~~~~~~     
You performed an operation which checked for certain files and found that 
they were not present. Repeat the operation, specifying different files.

This sequence can accept no more keys. Stop learning now.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You have typed the maximum number of keystrokes that can be learned in a 
single command (256 keys). Press ALT-L and select "Abort" to discard the 
sequence or Stop to keep it. To avoid excessively long sequences, you can 
learn a series of sequences: have the first sequence do part of the task, 
then have it start a second sequence which does the next part, and so on.

Time value expected (or blank)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You failed to use a numeric argument in a function that requires that you 
specify a number of seconds, minutes, or hours. Add a number to the command 
or omit the argument to have the command use the default timeout value.

Transfer cancelled by remote system
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your call log or answer log file will contain this message if the remote 
system cancels a file transfer.

Transfer cancelled by user
~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your call log or answer log file will contain this message if you cancel a 
file transfer.

Transfer failed - <cause of failure>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your call log or answer log file contains this message because a file 
transfer could not be completed. The message is accompanied by one of the 
following causes of failure:

error limit exceeded
~~~~~~~~~~~~~~~~~~~~                                
Possible causes are: 
 1) You failed to command the remote system to begin the transfer before you 
    commanded FreeComm to begin 
 2) Your connection was excessively noisy 
 3) Your modem, the remote modem, or some other device between 
    you and the remote system was stripping out characters 
 4) You were using improper parity or stop bit settings.no response from 
    remote system
 
You either failed to command the remote system to begin the transfer before 
you commanded FreeComm to begin, or you got disconnected during the transfer.

data received out of sequence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                
Your connection was noisy or the remote system's file transfer protocol does 
not follow protocol standards.

data received with illegal format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                
You received a data packet from the remote system which did not conform to 
protocol standards.

disk is full
~~~~~~~~~~~~                                
You ran out of disk space during the file transfer.

couldn't open file
~~~~~~~~~~~~~~~~~~                                
Your operating system could not open the file, due to write protection, a 
full directory, or because the Files= statement in your CONFIG.SYS file is 
set to too small a number.

disk error
~~~~~~~~~~                                
Your operating system would not allow a file to be opened during the transfer, 
due to a disk or drive error.

TRUE/FALSE function expected
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You used improper construction in a conditional statement, following "if" or 
"ifnot" with a script function which produces no TRUE or FALSE. Replace the 
function with one that does produce a TRUE or FALSE result.

Two filenames must be entered with the command
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Someone who called Answer mode used the command COPY or RENAME but entered 
too few filenames. He should repeat the operation, including two filenames on 
the line with the command. (With the COPY command, the first filename can 
include wildcards and the second can be a directory.)

Unknown media type on device <device name>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You attempted to write data to a device (printer, drive, etc.) for which the 
operating system reported unknown media type. Check the device for the cause 
of the error and try again.

Uneven number of quote signs in argument string
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You ran a script which contained a string of text not enclosed within 
quotation marks; strings must be enclosed in quotes. This message may display 
if you forget to include the necessary quotation marks in a script function 
or if you include a quotation mark within a string but forget to precede it 
with a slash (/").

Unexpected text on this line
~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Your script contains a string of text which is not enclosed within quotation 
marks; strings must be enclosed in quotes. This message may display if you 
forget to include quotation marks or if you include a quotation mark within 
the string but forget to precede it with a slash (/").

Unrecognizable string
~~~~~~~~~~~~~~~~~~~~~     
You used the option, report, or setting function with a first argument which 
is invalid. Refer to these functions in Chapter 12 and use only the first 
arguments that are documented.

Unrecognized command line option: X
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a command line option when running the HyperPilot compiler from 
the operating system prompt; the compiler does not support command line 
options. To compile a script, enter DFCDOS followed by the script name. For 
example, entering HP5DOS SAMPLE would compile the script SAMPLE.HP.

Unrecognized function
~~~~~~~~~~~~~~~~~~~~~     
You used a script function that was misspelled or does not exist. Correct the 
spelling or refer to Chapter 12 to find the desired function.

Unrecognized slash code in argument string
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You ran a script which contained an invalid slash code. Correct the problem, 
following guidelines in Chapter 11, and try running the script again.

Use ALT-D to display a directory before using "Time"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You selected "Time" at a point when no files were displayed. Press ALT-D and 
enter a filename (which can contain wildcards) or directory name, then select 
"Time".

WARNING: Having no password specified will allow all callers to log on without 
entering a password. Do you want to proceed?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You have created a line in the Password List which has no associated password. 
Repeat the operation and enter a password, unless you truly intend for 
everyone who calls to have password-free access to the privileges specified 
in this line of the Password List.

WARNING -- no `end()' function in script
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You forgot to include an end() function in your script. Add end() to the 
script and try running it again.

YES or NO expected
~~~~~~~~~~~~~~~~~~     
You used the wrong argument type in a script function which calls for a Yes 
or No argument. Replace the argument with "Yes" or "No".

You can't modify Proposed settings' name or telephone number
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You are prevented from modifying the name and phone number of Proposed 
settings because this system is essential to basic operation and has no 
associated phone numbers. Repeat the operation, entering the name of a system 
other than Proposed settings.

You can't select that sequence with the current option
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You selected the CALL or ANSWER script when performing an operation on the 
Keys menu for which these sequences cannot be used. Because these sequences 
are essential to basic operation, they cannot be deleted. Repeat the 
operation, selecting a different sequence.

You can't select that system with the current option
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You selected Proposed settings when performing an operation for which this 
system cannot be used. Because this system is essential to basic operation 
and has no associated telephone number, it cannot be deleted nor called. 
Repeat the operation, selecting a different system.

You must enter a directory name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
You entered a destination which was not a directory, when using the Files 
option "Copy" or the Host command "COPY". Repeat the operation, entering a 
drive or directory name as the destination; when copying more than one file, 
do not include a filename in the destination.

Your communications port is not responding to commands
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This error message can result from the following:
      
1.   (DOS only, with communication port type set to Standard comm port) Your 
     port or internal modem is not functioning properly because its jumpers or 
     switches are set to the same address or interrupt levels as another 
     device in your PC. NOTE: The fact that another communications program 
     may have worked with your port or internal modem proves only that some 
     of its jumper or switch settings are correct. One reason FreeComm is 
     faster than other communications packages is that it is one of the few
     programs to fully utilize the interrupt circuitry of communication ports 
     or internal modems. In effect, other programs chug along on two 
     cylinders, while FreeComm fires up all four. When FreeComm fires up the 
     extra cylinders, however, this may reveal that their sparkplugs are 
     cross-wired--that some of the switches or jumpers on your port or modem 
     are improperly configured, and conflict with interrupts of other devices. 
     Jumpers or switches on your port or modem board may need to be repositioned 
     to resolve the conflict. For more information, read material in the "COM 
     port selection, PC, XT, AT, 386, or 486 with DOS" section of Appendix A.

Your modem's CD signal is set incorrectly
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You selected an Answer menu option which waits for calls and the modem's 
Carrier Detect signal was already on, even though no call was connected. For 
calls to be detected properly, the modem's CD signal must turn on only when a 
call is connected. Here are some remedies that may apply:
     
1.   If your modem has dip switches or jumpers, use the setting that makes CD 
     turn on only when a call is connected, rather than being forced 
     permanently on. (See Appendix A for other recommended settings.)
2.   If your modem has a software command which makes CD turn on only when a 
     call is connected, select "Hardware" and "Modem" on the Answer menu, 
     select "Additional modem setup commands" and enter that command. The 
     Hayes command for this is &C1.


Your modem isn't responding to commands
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This error message can result from the following:
      
1.   Your modem did not understand one or more of the modem commands FreeComm 
     issued to it. You can be certain that this is the cause, if the commands 
     issued to your modem appear on the screen, followed by ERROR (the modem's 
     response). Most likely, you selected the wrong modem when you installed 
     FreeComm. You can change your selection without re-running the Install
     program, by selecting Hardware and Modem on the Preferences menu 
     (described in Chapter 1). If FreeComm doesn't list your modem by name, 
     you should probably select Hayes Smartmodem 2400, Other Hayes-compatible 
     modem, or User-defined modem.
2.   If the modem commands FreeComm issued (typically AT plus other characters) 
     never even displayed, then this indicates that the modem either never 
     received the commands or failed to send an echo of the commands back to 
     your screen. There are several possible causes:
   a.  Your modem may be connected to a different port from the one you 
       selected. You can correct the port selection without re-running the 
       Install program, by selecting "Communications port" on the Preferences 
       menu.
   b.  Your modem may not be connected, may not be turned on, or your modem 
       or cable may be defective.
   c.  You are using a baud rate to which your modem cannot adapt. Correct 
       the baud rate and try again.
   d.  (DOS only, with Standard comm ports) Your port or internal modem is 
       not functioning properly because its jumpers or switches are set to 
       the same address or interrupt level as another device in your PC. The 
       fact that another communications program may have worked proves only 
       that the jumper or switch settings are partially correct. Please see 
       information on the error message "Your communications port is not 
       responding to commands, item 1".


                                    Appendix C
                                   ~~~~~~~~~~~~

Terminal Emulator Characteristics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
So that you can call and communicate with a wide variety of systems, FreeComm 
emulates a wide variety of computer terminals. Each emulator allows the Comm 
screen to display text and respond to screen control codes in a way that 
closely resembles that type of terminal. If the terminal has keys that your 
PC lacks, the emulator defines other keys you can use in their place. You can 
replace or supplement these by creating macros as described in Chapter 7.

ADM3A
~~~~~     
Makes your PC emulate a Lear Siegler ADM 3A terminal. Use ALT-I to perform 
the same function as the Here Is key on ADM 3A terminals; this sends the 
answerback message entered on the ASCII Sending menu. You can use the keys 
listed below:

     Instead of this ADM 3A key Use this key on your PC
     
     Here Is                    ALT-I
     Clear                      ALT-C
     Rubout                     DEL
     Linefeed                   CTRL-ENTER
     Break                      CTRL-BREAK

The ADM3A menu lets you reverse DEL and BACKSPACE keys, allow remote screen 
clearing, display uppercase only, and select overtype mode.

ANSI
~~~~     
Makes your PC emulate an ANSI terminal, following IBM PC ANSI.SYS standards. 
This emulator is most often used with computerized bulletin boards and other 
remote systems that send IBM PC graphics characters or ANSI color codes. This 
emulator provides complete keyboard output as well: All the PC keys send 
appropriate scan code/character code combinations. Keys that control
FreeComm (ALT-A, -R, -F, -H, -L, -M, -O, or keys that run sequences) send no 
codes, unless you first press ALT-O and select "Quote" or "Send-keys". With 
hosts that display text in the bottom line, you may want to press ALT-O, 
select "Display, "Bottom-line", and "No", to suppress FreeComm's bottom line.
     
The ANSI menu lets you reverse DEL and BACKSPACE keys, set whether 
non-alphanumeric keys send the PC's scan codes, and set the cursor type.

COMPUSRV
~~~~~~~~     
This emulator simplifies file transfers with Compuserve B protocol and is 
used solely with CompuServe Information Service. With this emulator, you can 
initiate file transfers just by commanding CompuServe to send or receive 
files (you don't need to press ALT-O, select "Transfer", etc). When using 
this emulator, you should configure CompuServe to treat your PC as an ANSI 
terminal (to begin the configuration process, enter GO TERMINAL at the 
CompuServe prompt).
     
The COMPUSRV menu lets you reverse DEL and BACKSPACE keys and set the cursor 
type.

HYPERTRM
~~~~~~~~     
HyperTerminal (the HYPERTRM emulator) is specifically for calling PCs that 
are answering with FreeComm, and is essential for remote use of programs or 
the operating system. HyperTerminal behaves much like the ANSI emulator until 
you access the programs or operating system of the answering PC. After that, 
a unique image transport system keeps your screen in step with the answering 
PC's screen, using powerful error-correction and compression techniques. For 
tips on using the HyperTerminal emulator, see Chapter 9.
     
The HYPERTRM menu lets you reverse DEL and BACKSPACE keys and set the cursor 
type.

IBM3101
~~~~~~~     
Emulates both the character mode and block mode of IBM3101 series terminals. 
Use the keys from the on-line help.
     
Details that you would set with dip switches on an IBM3101 terminal may be 
set on FreeComm's menus. Baud rate, parity, and stop bits are set on the 
System settings menu; automatic line feed and automatic new line correspond 
to Wrap lines and Append line feeds on the Receiving text menu; duplex is on 
the Sending text menu.
     
The remaining switch settings correspond to settings on the IBM3101 menu, 
which lets you reverse DEL and BACKSPACE keys and set the cursor type. You 
may also define a turnaround character, null suppression, uppercase only, 
scrolling, and select between block or characters modes.

IBM3278
~~~~~~~
Use this asynchronous terminal emulator for communicating with IBM minis or 
mainframes which: 1) are equipped with an IBM 7171, 3708, or similar protocol 
converter, or 2) are running the Yale ASCII protocol conversion program, or 
3) have equivalent, built-in protocol conversion capabilities, as with the 
IBM 9370 or AS400.
     
Note: When using IBM3278, identify yourself to the IBM mainframe as a VT-100 
terminal. The IBM3278 emulator supports screen control codes of a VT 100, 
while providing keys similar to an IBM 3270 or 3278. Use the keys from the 
on-line help.
     
If the mainframe operator has redefined the protocol converter's VT100 
conversion table, keys may not work as shown; you may need to define new keys 
as described earlier in this appendix.
     
The IBM3278 menu lets you reverse DEL and BACKSPACE keys and choose the 
desired national character set. This menu also enables you to remove all tab 
settings.

RENX3278
~~~~~~~~
Use this emulator for communicating with IBM minis or mainframes equipped 
with Renex protocol converters. Identify yourself to the IBM mainframe as a 
VT-100 terminal; this emulator supports screen control codes of a VT100, yet 
provides keys similar to those of an IBM 3270 or 3278. See the on-line help.
     
If the mainframe operator has redefined the protocol converter's VT100 
conversion table, keys may not work as shown; you may need to define new keys 
as described earlier in this appendix.
     
The RENX3278 menu lets you reverse DEL and BACKSPACE keys, set the cursor 
type, and choose the desired national character set. This menu also enables 
you to remove all tab settings.

TTY
~~~
Use this emulator with any system that calls for a TTY terminal, a Teletype, 
a glass terminal, or no terminal. This class of terminal, due to its 
simplicity and wide availability, has become a de facto standard in 
communications. With TTY terminals, you use only the regular, alphanumeric 
keys, not arrow or function keys.
     
The TTY menu lets you reverse DEL and BACKSPACE keys, and define whether 
BACKSPACE erases characters as it moves the cursor to the left.

TV925 and TV950
~~~~~~~~~~~~~~~
The TV925 and TV950 emulators respectively emulate Televideo TV925 and TV950 
terminals. Both provide full emulation of conversational (or character) mode, 
block mode, local edit mode, protected fields, and selective clear. Use the 
keys from the on-line help.
     
The TV925 or TV950 menus let you reverse DEL and BACKSPACE keys, select 
between normal, block, or local edit modes, set the cursor type, and set 
overtype mode.

VIEWPNT
~~~~~~~     
Makes your PC emulate ADDS VIEWPOINT terminals. The following keys are 
supported:

     Instead of this VIEWPOINT key     Use this key on your PC
     
     F1 through F3              F1 through F3
     Shft-F1 through Shft-F3    SHIFT-F1 through SHIFT-F3
     Return                     ENTER
     Shft-up, down, 
     right, or left arrows      UP, DOWN, RIGHT or LEFT ARROWS
     Shft-Home                  HOME
     Tab                        TAB

The VIEWPNT menu lets you reverse DEL and BACKSPACE keys, set the cursor type, 
and disable/enable scrolling.

VT52, VT100, VT102, VT220 or VT320
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
These emulators support virtually all the features of DEC VT52, VT100, VT102, 
VT220, and VT320 terminals. Each emulator fully supports cursor-control (both 
ANSI and VT52), cursor-memory, cursor-reporting, tab stops, scrolling regions, 
half- and full-duplex operation, origin mode, and host-controlled printer 
operations. Bold, reverse, underline, and blinking characters are accurately 
represented using the industry-standard capabilities of your particular monitor 
type, be it monochrome, CGA, EGA, or VGA.
     
For maximum speed and hardware compatibility, these emulators use no 
bit-mapped graphics or proprietary monitor features. The VT220 and VT320 
emulators support multinational, British, French, French Canadian, German, and 
ASCII character sets. Double-high characters display as two lines of identical 
characters.
     
To read text displayed in 132-column mode, press CTRL-RIGHT ARROW and CTRL-LEFT 
ARROW to shift between left, centre and right views. For other keys you can 
use, see the on-line help.
     
Details that you would define with setup screens on true DEC terminals are 
set on menus in FreeComm. Settings equivalent to these setup screens' Baud 
rate, Parity, Stop bits, and Terminal mode (which terminal is emulated) are 
on the System settings menu; Wrap, New line, Local echo, Tabs, and XON/XOFF 
equate to settings on the Receiving text menu; Duplex and Answerback are on 
the Sending text menu.
     
The remaining DEC setup screen options correspond to settings on FreeComm's 
VT52, VT100, VT102, VT220, and VT320 menus.
Each menu lets you set whether the PF1 - PF4 keys are also mapped to the top 
of the keypad (NUMLOCK, /, * and -); whether DEL and BACKSPACE are reversed; 
set the default keypad mode; and remove tab settings defined by the host.
     
Note: Application mode is a mode which lets you use your numeric keypad to 
perform functions instead of sending numbers. The host can switch your keypad 
ino and out of this mode, but you can set the default.
     
The VT100 and VT102 menus also let you set the cursor type, select 80- or 
132-column display mode, and choose the national character set. The VT220 and 
VT320 menus also let you set whether 8-bit control codes are used, and 
whether user-defined keys are supported.

Wang
~~~~
This emulator is used for communicating with a Wang mini that is equipped 
with an ADC or EADC protocol converter. This emulator gives you direct 
equivalents to all the keys found on a Wang VS2110 terminal. In other 
respects the Wang host computer treats your PC as though it were a VT100 
terminal (see the on-line help).
     
The WANG menu lets you reverse DEL and BACKSPACE keys and set the cursor type.

     
                                    Appendix D
                                   ~~~~~~~~~~~~

File Transfer Protocols
~~~~~~~~~~~~~~~~~~~~~~~     
FreeComm offers a wide variety of protocols: HyperProtocol (a state-of-the-art 
protocol), Zmodem, Ymodem, Ymodem G, 1K-Xmodem, Xmodem CRC, Xmodem Checksum, 
CompuServe B, Kermit, and Text (or ASCII) protocol. Having many protocols 
gives you the ability to transfer files with systems that support only 
certain protocols. 
    
This appendix describes each protocol and gives guidelines on when to use 
each. See Chapter 3 to learn how to use protocols, and Chapter 10 to set 
protocol details. 

Benchmark testing protocol speed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Independent tests have proven FreeComm's protocols are substantially faster 
than the same protocols in other programs, due to superior implementation. 
To be assured the fastest possible transfers, you need to disable some of 
FreeComm's special features. Here are some pointers for achieving maximum 
speeds.

   Turn off virus filtering and unpacking on the Preferences menu.
   Delete the log file names on the Miscellaneous menu and Assorted settings 
    menu.
   When transferring pre-compressed or totally random files, turn off 
    compression on each protocol's menu.
   For maximum terminal emulator speeds, turn off "Wait for this character 
    after sending each line" on the ASCII Sending menu.
   If you are using ports with NS16550A serial chips or Hayes ESP cards, 
    select "Communications port" on the Preferences menu and set Use port's 
    extended hdw buffering to "Yes".

HyperProtocol
~~~~~~~~~~~~~    
Use HyperProtocol whenever the remote system also has this protocol. 
HyperProtocol is the fastest, most reliable protocol over any type of 
connection. Unlike most protocols, its speed is unaffected by propagation 
delays common with MNP or other error-correcting modems, long-distance calls 
or packet-switching networks. HyperProtocol can send single files or file 
groups. See Chapter 9 for more information.
    
Note: In transfers to remote systems that also have HyperProtocol, files are 
compressed as they are sent, to cut the transfer time.

Zmodem
~~~~~~    
Zmodem is an error-correcting, streaming protocol which has become popular on 
bulletin boards. Like HyperProtocol, it maintains its speed despite 
propagation delays, though its efficiency is slightly less (98% vs 99%) and 
it lacks compression. Zmodem can send single files or file groups, and 
supports auto-download and crash recovery. When it comes to Zmodem, FreeComm 
gives you two solutions: You can use FreeComm's own built-in Zmodem, or use 
an external Zmodem protocol module. Most people prefer built-in Zmodem, 
because it's instantly available and easy to use.
    
If you prefer the external protocol, there are two scripts provided, assigned 
to CTRL--PGUP and CTRL_PGDN, which will let you transfer files using an 
external Zmodem protocol module. However, you need to pick up the Zmodem 
protocol module--which is called DSZ. (DSZ is not available from the Delrina 
BBS. DSZ is a shareware product of another company, which is solely 
responsible for the quality, maintenance, and support of the product.)
    
Once you have the DSZ module, you will need to set it up as described in the 
scripts DSZDOWN.HP and DSZUP.HP, which you can view with the FreeComm editor.




Ymodem
~~~~~~    
Ymodem (also known as Ymodem Batch) is a 1024-byte packet, error-correcting 
protocol capable of transferring single files or groups.Ymodem is generally 
faster than Xmodem over noise-free lines, but slower over noisy lines, as it 
must re-transmit 1024 byte packets rather than 128 bytes as with Xmodem. 
Ymodem is similar to 1K-Xmodem, except that 1K-Xmodem can only transfer one 
file at a time.

Ymodem G
~~~~~~~~    
Ymodem G is a variant of Ymodem which does away with packet-by-packet 
acknowledgements, and simply aborts the transfer if an error is detected. 
Ymodem G should be used only with MNP or other error-correcting modems, or 
inherently error-free connections. Ymodem G is clearly faster than Ymodem, 
Xmodem, and Kermit, but offers little over HyperProtocol or Zmodem. 
HyperProtocol or Zmodem not only afford double protection (correcting any 
errors that slip through the modems), they correct errors the modems cannot
sense - errors introduced by the PCs, cables, or ports.

Kermit
~~~~~~    
Kermit is a widely supported error-correcting protocol which is capable of 
sending file groups. While it is versatile and handles noisy connections well, 
it tends to be slower than other protocols.

Xmodem
~~~~~~    
Xmodem is a relatively simple, 128 byte packet, error-correcting protocol, 
which can transfer only one file at a time. Xmodem is generally faster than 
Ymodem if your line is noisy, but slower if it is clean, as it transmits 128 
byte packets rather than 1024 bytes as with Ymodem.
    
Note: Xmodem  normally uses Auto error-checking method used by the remote 
sustem, but you can set it to CRC or Checksum as described in Chapter 10.

1K Xmodem
~~~~~~~~~    
This 1024-byte packet, error-correcting protocol is similar to Ymodem, except 
that it can transfer only one file at a time. Some remote systems that support 
1K Xmodem refer to it as Ymodem.

CompuServe Quick B
~~~~~~~~~~~~~~~~~~    
This protocol is for use with CompuServe B, B+ and Quick B protocols that are 
available on the CompuServe Information Service.
CompuServe Quick B supports both single- and multiple-file transfers and is 
an error-correcting protocol. You may use this protocol in two ways. If you're 
using an emulator other than COMPUSRV, you operate this protocol just like 
the other protocols (as described in Chapter 3); if you're using the COMPUSRV 
emulator, CompuServe will operate the protocol for you automatically (see 
COMPUSRV in Appendix C). CompuServe Quick B has no user-definable settings so 
there is no menu in FreeComm for setting CompuServe Quick B details, as there 
is with other protocols.

Text
~~~~    
Text (ASCII) protocol is the basic method computers use for exchanging 
messages and other displayed text. When you send with Text protocol, it is as 
if you were typing on the Comm screen very fast. Text protocol generally 
cannot be used for sending files which contain non-ASCII, binary codes--files 
such as executable programs, spreadsheets, database files, and typical word 
processor documents. Text protocol is used only for sending text. However, 
most word processors have procedures you can use to create "plain ASCII" or 
"non-document" files, which can be sent with Text protocol. To recieve text, 
use Capture (see Chapter 2)
    
    
                                     Appendix E
                                    ~~~~~~~~~~~~

FreeComm Host Commands
~~~~~~~~~~~~~~~~~~~~~~     
When your PC is set up to answer calls, callers use commands to control it. 
At the answering PC while a call is in progress, you can type comments or 
instructions to the caller. You can either use CHAT as described below, or 
type messages at the [FreeComm host] prompt, beginning each with ; so it 
won't be interpreted as a command. Though it is possible to type commands on 
behalf of the caller, doing this may tend to confuse callers.

HELP
~~~~    
Displays the list of commands the caller can enter to control the answering 
PC. For more detailed help, enter HELP followed by any command shown in this 
section.

QUIT
~~~~    
Ends the call.

CHAT
~~~~    
Puts the answering PC into chat mode, so the caller can type messages to the 
answerer. If the answerer is there, he and the caller can take turns typing. 
Everything typed in chat mode is recorded in the answer log. To resume using 
commands, press ESC.

DIR <drive, directory, or filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Displays directories of files on the answering PC's disks. The filename can 
contain a drive or directory, and * or ?. Callers who are restricted to a 
particular directory or drive cannot examine files from other areas.

CHDIR <directory> or CD <directory>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Changes the current directory of the answering PC. (The current directory is 
shown along with Answer mode's [FreeComm host] prompt.) Callers who are 
restricted to a particular directory or drive can change to its 
subdirectories, but cannot change to other areas.

FIND <filename>
~~~~~~~~~~~~~~~    
Displays a list of directories where the named file is found on the answering 
PC. The filename can include * or ?, which is useful when the caller can't 
remember the full filename.

TYPE <filename>
~~~~~~~~~~~~~~~    
Displays contents of a text file stored on the answering PC. Callers can 
press CTRL-S to suspend display, CTRL-Q to resume, and CTRL-C to cancel.

SEND <filename>
~~~~~~~~~~~~~~~    
Sends a file from the answering PC to the calling computer using Text 
protocol. Only ASCII files can be transferred with text protocol. After 
entering this, the caller instructs the communications software on the 
calling computer to capture text that displays, then presses ENTER to make 
the answering PC begin sending. Callers can press CTRL-S to suspend, and 
CTRL-Q to resume, and CTRL-C or ESC to cancel.

HSEND <filename>
~~~~~~~~~~~~~~~~   
Sends a file or files from the answering PC to the calling computer using 
HyperProtocol. This command can be used only by callers whose communications 
software contains HyperProtocol. For a single file, the caller enters HSEND 
and a filename; the filename can include * or ? to specify file groups; 
multiple filenames can be entered separated by spaces. After entering this, 
the caller instructs the communications software at his end to begin 
receiving (see Chapter 9).

XSEND <filename>
~~~~~~~~~~~~~~~~    
Sends a file from the answering PC to the calling computer using Xmodem 
protocol. Since Xmodem cannot transfer multiple files, the caller must enter 
the name of a single file without * or ?. After entering this, the caller 
instructs the communications software at his end to begin receiving with 
Xmodem protocol.

YSEND <filename>
~~~~~~~~~~~~~~~~    
Sends a file or files from the answering PC to the calling computer using 
Ymodem protocol. For a single file, the caller enters YSEND and the filename; 
the filename can include * or ? to specify file groups; multiple filenames 
can be entered separated by spaces. After entering this, the caller instructs 
the communications software at his end to begin receiving with Ymodem protocol.

GYSEND <filename>
~~~~~~~~~~~~~~~~~    
Through connections that have MNP, LAP-B, PEP, V.42, X.25, ISDN or other 
error-control, callers can use this command to make the answering PC send 
with Ymodem G protocol, which is faster than Ymodem. Instead of acknowledging 
each received packet, it simply aborts a transfer if an error occurs. If both 
computers have HyperProtocol, use it instead for the fastest, most reliable 
transfers.

ZSEND <filename>
~~~~~~~~~~~~~~~~    
Sends a file or files from the answering PC to the calling computer using 
Zmodem protocol. For a single file, the caller enters ZSEND and the filename; 
the filename can include * or ? to specify file groups; multiple filenames 
can be entered separated by spaces. After entering this, the caller instructs 
the communications software at his end to begin receiving with Zmodem 
protocol.

KSEND <filename>
~~~~~~~~~~~~~~~~    
Sends a file or files from the answering PC to the calling computer with 
Kermit protocol. For a single file, the caller enters KSEND and a filename; 
the filename can include * or ? to specify file groups; multiple filenames 
can be entered separated by spaces. After entering this, the caller instructs 
the communications software at his end to begin receiving with Kermit 
protocol.
    
Note: To make the answering PC send files from a directory and its 
subdirectories, callers can enter HSEND, ZSEND, YSEND, GYSEND or KSEND, a 
space, /S and a filename. For example, HSEND /S \DB\*.DAT would make the 
answering PC send files with the .DAT extension from the \DB directory and 
its subdirectories.
    
REC <filename>
~~~~~~~~~~~~~~    
Makes the answering PC receive a file from the calling computer using text 
protocol. Only ASCII files can be transferred with text protocol. After 
entering this, the caller instructs the communications software at his end to 
begin sending the file using Text (ASCII) protocol. To indicate the end of 
the file, the caller can either press ESC or enter a period on a line by 
itself.

HREC <drive, directory, or filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Makes the answering PC receive a file or files from the calling computer 
using HyperProtocol (this command can be used only by callers whose 
communications software contains HyperProtocol). To have the answering PC 
receive into its current drive and directory, the caller enters just HREC; 
to have it receive into another drive or directory, he enters HREC and that 
drive or directory; to have it receive a file and store it under a certain 
name, the caller enters HREC and that filename. After entering any of these, 
the caller instructs the communications software at his end to begin sending 
with HyperProtocol. (Chapter 9 gives step-by-step instructions.)

XREC <filename>
~~~~~~~~~~~~~~~    
Makes the answering PC receive a file from the calling computer using Xmodem 
file transfer protocol. XREC must be followed by a single filename, which 
cannot contain * or ?. After entering this, the caller instructs the 
communications software at his end to begin sending using Xmodem protocol.

YREC <drive, directory, or filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Makes the answering PC receive a file from the calling computer using Ymodem 
protocol. To have the answering PC receive into its current directory, the 
caller enters just YREC; to have it receive into another drive or directory, 
he enters YREC and that drive or directory. After entering this command, the 
caller instructs the communications software at his end to begin sending 
using Ymodem protocol.

GYREC <drive, directory, or filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Through connections that have MNP, LAP-B, PEP, V.42, X.25, ISDN, or other 
error-control, callers can use this command to make the answering PC receive 
with Ymodem G protocol, which is faster than Ymodem. Instead of acknowledging 
each received packet, it simply aborts a transfer if an error occurs. If both 
computers have HyperProtocol, use it instead for the fastest, most reliable 
transfers.

ZREC <drive, directory, or filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Makes the answering PC receive a file from the calling computer using Zmodem 
protocol. To have the answering PC receive into its current directory, the 
caller enters just ZREC; to have it receive into another drive or directory, 
he enters ZREC and that drive or directory. After entering this command, the 
caller instructs the communications software at his end to begin sending using 
Zmodem protocol.
    
Note: After typing HREC, ZREC, KREC, YREC, or GYREC, callers can enter these 
slash options (followed by a drive or directory):

    /O  to make the answering PC overwrite its existing files when it 
        receives files with the same filenames.
    /N  to make the answering PC accept only files whose times and dates are 
        newer than its existing files.
    /P  to make the answering PC store files using directory names included 
        in received filenames.

KREC <drive, directory, or filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Makes the answering PC receive a file from the calling computer using Kermit 
protocol. To have the answering PC receive into its current directory, the 
caller enters KREC alone; to have it receive into another drive or directory, 
he enters KREC and that drive or directory. After entering this, the caller 
instructs the communications software at his end to begin sending using 
Kermit protocol.

COPY <filename> <filename, drive, or directory>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Copies the first file(s) to the second file, drive, or directory (similar to 
the DOS COPY command). The first filename can contain * or ?; the second 
cannot. This is solely for managing files on the answering PC, not for 
copying between computers (which is done with commands such as SEND or REC).

DELETE <filename> or DEL <filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     
Deletes the file(s) from the answering PC (similar to the DOS DEL command). 
The filename can include * or ?.

RENAME <filename> <filename>
  or REN <filename> <filename>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
Changes the first filename to the second filename. The filenames cannot 
include * or ?.

MKDIR <directory> or MD <directory>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
Makes a new directory on the answering PC (similar to the DOS MKDIR command).

RMDIR <directory> or RD <directory>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
Removes a directory from the answering PC (similar to the DOS RMDIR command). 
Before a directory can be removed, any files and/or subdirectories that it 
contains must first be deleted.

PRINT <filename>
~~~~~~~~~~~~~~~~  
Prints (on the answering PC's printer) the contents of a text file stored in 
the answering PC. If you authorize any callers to use this command, be sure 
to leave your printer turned on and with plenty of paper.

DOS
~~~  
Displays the answering PC's operating system prompt, enabling callers to 
execute operating system commands or programs. When callers are done using 
the operating system, they must enter EXIT to resume using Host commands.

MAIL
~~~~  
Lets callers read or send electronic mail. To authorize each caller for mail 
privileges, you need to enter script names on the Privileges menu.


                                  Appendix F
                                 ~~~~~~~~~~~~

Safe Communications
~~~~~~~~~~~~~~~~~~~     
Viruses pose a serious threat to everybody using desktop computers. A large 
percentage of these people are connected by networks or linked to other 
computer systems.
    
PCs are an excellent vehicle for business communications, and computer 
viruses threaten the safety of our communications as well as the security of 
our data. To answer this concern, FreeComm uses HyperGuard, a new antivirus 
filtering technology which combats the spread of viruses and protects PCs 
from contamination. Now that HyperGuard has been added to FreeComm, you can 
communicate safely, with virtually no risk from known viruses.
    
Existing antivirus programs are largely intended to detect or inhibit known 
or unknown viruses after they are already in your PC. Even in light of new 
HyperGuard antivirus technology, these existing programs will continue to 
serve as a valuable second line of defense. HyperGuard lays down a new first 
line of defense, by preventing known viruses from entering your PC in the 
first place.
    
To keep viruses from entering, you must guard the points of entry: diskettes, 
and modems or other communication devices. While a number of other products 
are capable of scanning files already in your system for viruses, only 
HyperGuard has the ability to stop known viruses from sneaking in through 
your modem, or infiltrating your system when you copy a diskette!
    
Virus signatures
~~~~~~~~~~~~~~~~
FreeComm's HyperGuard detects viruses by examining files for virus signatures 
(patterns of bytes) unique to each virus. As shipped, FreeComm can detect the 
Dark Avenger, Form, Joshie, and Cascade viruses, plus hundreds of others.

Virus filtering during file transfers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
FreeComm uses HyperGuard to examine every file you receive from a remote 
system, checking for viruses on-the-fly as you receive the file. This unique, 
real-time antivirus technology is the first to be incorporated in a 
communications program. The instant a virus is detected, a warning message is 
displayed identifying the virus by name and allowing you to abort the file 
transfer. If you happen to be away from your keyboard when a virus is 
detected, FreeComm will automatically abort the transfer after 30 seconds and 
place a message to that effect in your log file (e.g., CALL.LOG). FreeComm 
warns you the instant it finds a signature in any file you receive, so you 
can abort the transfer and escape infection.
    
HyperGuard filters out viruses automatically, with no additional steps on 
your part, and never impacts speed with 2,400 bps modems, even on the slowest 
PC. In fact, it seldom has any impact on speed even with 19,200 bps modems on 
286 or faster PCs. If you prefer that files not be filtered, you can turn off 
this feature on the Preferences menu, as described in Chapter 1.
    
HyperGuard can even detect viruses in .ZIP files (files compressed with PKZIP), 
unlike conventional virus scanning techniques, which cannot discern virus 
signatures in compressed files.

Virus filtering during copy or unpack operations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HyperGuard also filters out viruses as you copy files or unpack .ZIP files. 
This provides valuable protection particularly when you're copying diskettes 
or unpacking files given to you by anyone whose computer could be infected. 
If the Virus filter option on the Preferences menu is set to Yes, each file 
you copy or unpack (using ALT-F Copy or ALT-F Unpack) is filtered by 
HyperGuard. If a virus signature is found, a warning message identifies the 
virus, and offers to abort the copy operation and purge the infected file 
from the destination disk.

Scanning files on disk
~~~~~~~~~~~~~~~~~~~~~~
FreeComm also lets you scan files which are already on your disks for viruses, 
which is important at these times:

   After you first get FreeComm. It's a good idea to scan your entire hard 
    disk to see if your PC is already contaminated.
   Before you run any program which you receive thereafter. There's no need 
    to scan programs copied, unpacked, or received with FreeComm, but you 
    should scan those which arrive on your PC by other means. For example, 
    before running a new program from a diskette, you should scan the 
    diskette.

To scan files on disk, press ALT-F, select "Vscan", and specify which files 
are to be scanned. You can enter a single filename, or a filename with 
wildcards. Include /S with the filename if you wish to scan subdirectories as 
well. For example, to scan all .EXE files on drive C, you could enter 
C:\*.EXE /S.

If a scanned file contains a virus signature, a warning pops up and asks if 
you want to purge the file from your disk. If you say yes, the file is 
overwritten with zeros and then deleted, so the virus can never come back to 
haunt you, even if you accidentally unerase the file with a file recovery 
utility.

Safe unattended communications
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
Now you can set up your PC as an unattended host with little risk of callers 
uploading files carrying viruses. Simply set Virus filter to Yes on Answer 
mode's Assorted settings menu, to have FreeComm use HyperGuard to filter 
every file uploaded to your PC. If a signature is encountered, a warning 
appears on your screen, not the caller's. Unless you indicate within 30 
seconds that you want the transfer to continue, it will abort automatically 
and record the event in your answer log.
    
If a virus warning displays ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
If a virus warning displays as you're receiving, copying, unpacking, or 
scanning any file that contains executable program code ( files with .EXE, 
.COM, .OVL, .OVR, .PGM, .BIN, or .SYS extensions), it is best to get rid of 
the file immediately. If you're in the process of receiving it, abort the 
transfer and notify the remote system operator. If you're copying or scanning 
a disk, purge the infected file and warn whoever supplied it to you. If you 
have ever run the program, be sure to scan all your files, as the virus may 
have spread.
    
Text, data, and other non-executable files that cause virus warning messages 
pose less of a threat, because viruses merely lie dormant in non-executable 
files. Still, it is best to get rid of (or at least isolate) such files, and 
immediately begin searching for programs that may be spreading the virus.

Disclaimer
~~~~~~~~~~    
You assume all responsibility for the selection of FreeComm to achieve your 
intended results, for installation and use of the program, and for corrective 
action when suspected viruses are detected. Delrina assumes no responsibility 
for your safety and no liability for damage due to viruses.
    
The virus problem is evolving. There may be viruses now or in the future that 
FreeComm and HyperGuard cannot detect. You may want to use additional 
antivirus programs to protect yourself in other ways. Regardless of the 
antivirus software you use, you should continue to use appropriate backup 
procedures and physical security measures.
    
