* MODEM COMMUNICATIONS FOR FALCON 3.0, MiG-29 AND F/A-18 HORNET *


This focus of this document is how to achieve successful modem to modem
communications within Falcon, MiG-29 and F/A-18 Hornet.  The basics of using
the communication screens and the steps involved in calling another player
are adequately covered in the your software manuals.  This discussion will
go beyond the basics and give you specific suggestions to help overcome
problems establishing a connection.  Since the procedures and modem commands
outlined here apply equally well to ALL the programs, I'll use the term
"Falcon" as a shortcut to simplify the discussions.

Establishing modem to modem communications in Falcon can be extremely
frustrating.  Even if you have no difficulties getting your modem to
communicate with online services or BBS's, you may find yourself unable to
connect with another player in the Falcon environment.  First off, don't
panic.  Problems of this kind are quite common.  Getting communications to
work can sometimes take a good deal of luck.  With "luck", this will help
you overcome any problems you may encounter in playing Falcon via modem.

I strongly urge ALL players having problems to read through the "general
notes" section before moving on to the specifics.  The comments contained
therein apply regardless of the type or speed of connection.  The following
two sections will provide some background into how Falcon communications
work and what goes on during game play and setup.  While not directly
concerned with "specific" problems, they may nonetheless provide some
interesting material to help you better understand how Falcon works and why
it sometimes doesn't.


* THE MECHANICS OF FALCON COMMUNICATIONS *

Falcon's communication routines differ greatly from those employed by your
communications programs.  Most problems occur during the initial connection
between the modems.  The reason for this is that Falcon doesn't "parse" or
"examine" the responses coming from the modem during the "handshake" phase
of the connection.  Falcon merely watches the serial port and treats ALMOST
ANY incoming information as a sign that a connection has been established. 
While communication programs "understand" what the modems are telling them,
Falcon does not.  

This can become an even more serious problem during High Speed connections.
It is not unusual for a brief burst of "noise" to result from the initial
exchange of data carriers, etc..  In addition, connections employing data
compression or error correction often include extra "connect messages" from
the modem.  These include information about the connection type, DTR/DTE
speeds, etc. and are sent during the handshaking process, even before the
connection is fully established.

As a result, Falcon often interprets this "garbage" or "extra information"
from the serial port as indicating a connection exists when it doesn't. 
Falcon will move on to the next phase in it's connection process too soon
and a system lock up is generally the result.  For this reason, using the
DIRECT method of connection (covered later on) will often succeed where
other methods fail.  By going DIRECT, you take control of establishing a
connection away from Falcon and allow the game to proceed on the basis of an
already established modem to modem link.


* WHAT'S GOING ON DURING SETUP AND PLAY *

Falcon transmits a great deal of data during setup.  This includes theater
data, information on the environmental settings, aircraft settings, etc.
etc. etc..  This is sent in a "packet" fashion, that is to say, the caller
sends data, then the other machine sends a short "got it" message back, then
the caller sends more data, etc.  You'll notice that the "caller" is doing
most of the work, and transmitting most of the data (for those with external
modems, you can see this process by watching the RD/SD lights.)  During this
process, if there are any errors in transmission occur you'll notice a slow
down in the rate of progress due to data re-transmittals since both
computers must have ALL the information before the game may proceed.

During actual play, Falcon doesn't wait for data acknowledgements, rather,
the data is sent as a "stream" towards the other end.  The data stream
includes information not only about the location of the aircraft and the
status of weapons fired, but also contains "velocity vectors" indicating how
fast you're moving and how fast you are changing in attitude <pitch and
roll>.  From this information, the computer on the other end can make it's
"best guess" as to where you will be by the time the next "clean" packet of
data is received.  If there are transmission errors, the computer will
proceed with it's "best guess" until it gets solid piece of information.

This is why there may appear to be a lot of jumping around by the other
plane (or "warping" as it's commonly called) at low baud rates or over noisy
phone lines.  The computer "projects" the anticipated flight path based on
position and vectors, but "teleports" the opponent to the next known point
in space when it gets the next fix.  The less "good" information being
received, the more warping there will be.  With bad connections, you also
may not get hits because the shots are either being lost in bad data
packets, or are being directed at a point where the other plane "was" or
where the computer thinks it "could be" rather where it really is.

If enough data packets are lost, Falcon may become entirely unable to
re-synchronize the players.  When this occurs, you will each end up chasing
"ghost" planes.  These are phantoms of the last known position and velocity
vectors that Falcon received and have no basis in reality to where your
opponent really is.  Obviously, you can't "kill" a ghost plane.  Even if
your weapons appear to hit it, the other side doesn't register the hit
because it's not really there!  Under these conditions, the only option is
to end the round and restart from the WAR ROOM.  If the condition occurs
repeatedly, you may need to hang up and try the call over again, or attempt
connection at a slower baud rate.

Obviously, a clean, high speed connect will result in smoother movement of
the other plane and good registration of the weapons impacts.  However, high
speed connection are not without problems of their own.  Due to the greater
density of the data stream, high speed connections are more sensitive to
phone line quality.  Modems equipped with data compression and error
correction can often help alleviate a lot of these problems and improve the
quality of game play.

Despite the occasional problem caused by warping and synchronization loss,
data streaming play is actually a very ingenious and effective way to treat
game play communications.  By allowing your computer to operate independently
of the modem, Falcon runs at full speed.  While you may see your opponent's
plane jumping around, your plane handles exactly the same as it does in single
player mode.  Some game publishers that support modem play use the
"transmit/acknowledgement" method of communications during game play.  The
difference compared to Falcon is dramatic.  There is almost NEVER any warping
in these games because the computer will NOT refresh the screen unless it has
received a valid data packet.  However, what results is a very low screen
update rate.  Movement occurs in a "stop action" manner, and it becomes
extremely hard to exert fine control over your own aircraft.  Try executing
maneuvers in INSTANT ACTION or RED FLAG while you blink your eyes rapidly and
you'll get the picture.  In the worst cases, the screen will "freeze"
completely if several data packets in a row get corrupted while being sent
over the lines.

All things considered, Falcon's communication routines are an excellent
compromise between speed and accuracy.  Higher speed modems and the
implementation of data compression and error correction all contribute to
make Falcon one of the most realistic and fluid air combat simulations
available.


* GENERAL NOTES AND CONSIDERATIONS FOR ALL FALCON CONNECTIONS *

Before attempting ANY Falcon connection, you should verify that both you and
your opponent have compatible versions of Falcon installed.  Versions are
constantly being updated and the "newest" versions are not always compatible
with their predecessors.  As a general rule, don't try to connect dissimilar
versions of Falcon.  You can obtain current upgrade patches from a variety
of BBS's and online services, or you can contact Spectrum Holobyte directly
and they will send out upgrade diskettes free of charge.

For best results, both players should choose squadrons based in the KUWAIT
theater.  All head to head play in Falcon takes place in this theater
regardless of the default location for the chosen squadron.  Make life
simpler for yourself and the program by using the Kuwait theater.

Both players should select the same baud rate while in Falcon.  The baud
rate should equal the "highest" available speed of the "slowest" modem.

Players whose modems are equipped with V.42bis data compression and error
correction hardware can use higher baud rates within Falcon by utilizing one
of the V.42bis programs written by Ken "Stinger" Richardson.  Stinger's
modifications to the Falcon code to enable the use of data compression can
result in a 25-35% increase in the speed of Falcon communications.  Not only
do you connect faster, but game play is more fluid and stable.  V.42bis
patches and TSR's are available only for Falcon versions 3.01 and above as
well as all versions of MiG-29 and Hornet.  You should verify that you have
the correct V.42bis support program for the version of Falcon you are
running.

Special modem initialization strings and other procedures will generally be
required to utilize Stinger's V.42bis programs.  See the section on V.42bis
connections for specific details.

Players with 14,400 baud modems who are not using Stinger's programs may
attempt to connect in Falcon at 19,200 baud.  However, you may find that the
fastest and most reliable connects are made at 9,600 baud.  Falcon DOES NOT
support ANY form of error correction, data compression or speed buffering
without the installation of Stinger's programs.  If you are NOT running
these programs, or if new version of Falcon release for which Stinger's
programs are not yet available, you MUST disable V.42bis data compression,
error correction and speed buffering while using Falcon.  See the section on
Non-V.42bis connections for more details.

If you are using a high speed modem, verify that your serial port has a high
speed UART (Universal Asynchronous Receive/Transmit) chip installed.  The
best UART for high speed communications is the 16550A.  A 16450 UART chip
generally works reasonably well, but you may not be able to utilize baud
rates in excess of 19,200 without incurring data transmission errors.  If
your computer has an 8450 or 8550 UART, consider upgrading your serial port. 
If you are using an external modem, it is especially critical that you check
your UART and ensure that you are using a high quality, shielded serial
cable. 

By default, Falcon utilizes the "stored zero profile" in your modems NVRAM
(Non-Volatile RAM) to set your modem parameters.  You will want to ensure
that your stored settings are correct in order for Falcon to work.  I'll be
discussing what settings to use in greater detail as they can vary widely
amongst different modem manufacturers and different types of Falcon
connections.  See the appropriate sections for more details.

NOTE:  Some modems will incorrectly set the values &C0 &D0 in response to the
&F command to reset factory defaults.  The correct default values should be
&C1 &D2.  Setting these to "zero" causes the modem to indicate a continous
"on-line" status and in some cases can interfere with the establishment of a
connection.  Verify the results of issuing an AT&F command by typing AT&V
(works for most modems) in order to see the contents of the ACTIVE PROFILE
while you are in your communications program.  If in doubt, when directed
to use AT&F, use the command AT&F&C1&D2 instead.

ALWAYS REBOOT your computer between any failed attempts to establish
connections in Falcon.  If you have an internal modem, you should perform a
COLD boot.  If your modem is external, power down the modem and perform
either a COLD or WARM boot.

Have a communications program handy so that you may issue commands to your
modem, modify your stored profiles, and if necessary establish a DIRECT
communications link for Falcon.  A direct link is generally the easiest way
to get connected if your modem is especially recalcitrant and you're still
having problems.  For best results, use a DOS communications program.  Using
ANY communications program for WINDOWS will only complicate matters.  It is
extremely difficult to achieve a DIRECT link in Falcon using Windows.

Have your modem documentation available to verify modem command strings, S
register settings, etc..  Modem manufacturers may change the command strings
without notice.  The information provided here is the best available at this
time, but be prepared to verify all commands before executing them.

If your modems establish a connection, but Falcon remains stuck on either
the "MODEM STATUS: DIALING", "MODEM STATUS: WAITING" or "WAITING FOR OTHER
SIDE TO CONNECT" messages, try the following procedure:

     1.   Answer "NO" to the "USE MODEM DEFAULTS" question that appears when
          you press "ACCEPT" at the Falcon communications screen.

     2.   You'll see the following commands presented in turn:  "ATZ",
          "ATE0V0Q0", and either "ATS0=1" or "ATDx" (the former if set to 
          "ANSWER", the latter if set to "CALLER" in Falcon).

     3.   Press <ENTER> as each of the above strings is presented, pausing a
          moment before moving on to the next one.

               IMPORTANT NOTE:  The above assumes that all initialization
               strings for your modem have been properly saved to the
               "stored zero profile".  Please refer to the specific strings
               listed for differing modems and connection types in the
               following sections where appropriate.

     4.   A final "blank" command box will appear.  DO NOT hit <ENTER> until
          the modems have established the connection (ie. the handshaking
          noises have stopped) and you've waited a second or two in order to
          allow the connection to settle.

NOTE:  The above procedure may also be used if you choose NOT to modify the
contents of your "stored zero profile" for a specific Falcon connection.
Simply append the appropriate strings to the "ATE0V0Q0" command.  DO NOT use
the AT&F command in your string in this case.  For example:

     Player X has set up his "stored zero profile" for use with V.42bis high
     speed data connection.  He wishes to play using a plain 9600 connection
     for a particular game.  Rather than reinitialize his modem, he answers
     "NO" to the "USE MODEM DEFAULTS" question, replaces the ATE0V0Q0
     command string with ATE0V0Q0&Q0N0S37=9 and proceeds according to the
     instructions above.  This works ONLY for a single session, if the
     connection is broken and/or needs to be reattempted, the string must be
     entered again.  (Specific strings may vary, see the detailed sections
     below for the string to use with your modem.)

If you can establish a connection but find that Falcon "locks up" inbetween
rounds, try turning off the Music and Animation clips that play between
rounds, while setting up, etc. etc..  On some systems, the added overhead of
the music and video causes problems.

If your modems fail to establish a connection at all, or if they hang up
before a connection can be established, it is advised that you attempt a
connection directly with your standard communications packages to ensure
that the modems are not experiencing a basic incompatibility.  If you cannot
establish a connection with a communications program, you will certainly not
be able to establish one with Falcon.  Problems of this sort are often very
difficult to track down, modems are finicky beasts at times.  Use your
communications programs to ascertain what types of connections are possible,
and by all means consider using the DIRECT method for Falcon.


* 2400 BAUD CONNECTIONS WITHOUT V.42bis COMPRESSION *

2400 baud connections are generally trouble free.  Since virtually every
modem conforms to the basic HAYES command set, problems here are most often
the result of some setting in your "stored 0 profile" that is not in line
with the factory defaults.

>From your communications program, go into terminal mode so that you can
"talk" to your modem.  Restore your modem to it's factory defaults by typing
<AT&F>.  After you see the "OK" response, type <AT&W> to save these settings
into your "stored 0 profile."

If the modems establish a connection, but Falcon remains stuck on either the
"MODEM STATUS: DIALING" or "MODEM STATUS: WAITING" messages, follow the
directions indicated in the GENERAL NOTES section above.

If you still have problems, consider establishing a DIRECT connection as a
last resort.  The procedures for "going direct" are outlined at the end of
this document.


* HIGH SPEED CONNECTIONS WITHOUT V.42bis COMPRESSION *

High speed connections (9,600 baud or higher) present a much greater
challenge to modems in general and Falcon in particular.  The data stream
more densely packed and hence more prone to interference by line noise,
etc..  Also, there is no single accepted standard command set like there is
for 2400 baud communications.

Most High Speed modems today also support V.42bis data compression and error
correction routines.  You'll definitely want to use these capabilities if
possible.  In general, there are only two reasons why you would want to use
a high speed connection without V.42bis.  The first is obvious ... one or
both player's modems do not support V.42bis compression or your version of
Falcon has not been upgraded (with patches or TSR's) to support it.  The
second is if you are unable to establish a connection using V.42bis
compression.  This is occasionally the situation when phone lines are noisy,
or other problems arise such that connection is impossible.

Be advised that Falcon DOES NOT support any form of data compression, error
correction or speed buffering unless you are running Stinger's V.42bis
support programs.  Users of 14,400 baud modems may initially attempt a
connection at 19,200 baud within Falcon, however, the fastest and most
stable connections may generally be obtained by forcing a 9,600 baud carrier
and using 9,600 baud within Falcon.  This condition varies greatly depending
upon the particular modems involved in the connection, the computers, and a
host of other imponderables.  Only experimentation will determine whether
14,400 baud works better in any particular case.

One final note for non-V.42bis connections that is not covered in the
following troubleshooting procedures.  Some modem/computer combinations seem
to work better if modem flow control is disabled.  This is generally not
necessary, but is worth a try if all else is failing.  The commands to
disable flow control should be added to the initialization strings given,
and placed BEFORE the final &W command.  Some of the common commands are:

     &K0       Works for the vast majority of HAYES COMPATIBLE modems.
     *F0       Works for DIGICOMM modems.
     /Q0       Works for GVC Modems.
     \Q0       Works for INFOTEL modems.
     \Q0       Works for INTEL modems.
     &H0       Works for US ROBOTICS modems.

Under NO CIRCUMSTANCES should Software Flow Control (XON/XOFF) be enabled.


* TROUBLESHOOTING FLOW CHART FOR NON-V.42bis CONNECTIONS *

     1.   Determine your modem manufacturer.

          ACEEX
          BEST DATA
          IMAGE COMMUNICATIONS
          PRACTICAL PERIPHERALS
          ZOOM
          Unlisted modem which is 100% HAYES EXTENDED COMMAND SET compatible

          For Any of the above     Proceed to step 2a

          ACCESS                   Proceed to step 2b
          BOCA                     Proceed to step 2c
          DIGICOM SYSTEMS          Proceed to step 2d
          GATEWAY TELEPATH         Proceed to step 6
          GVC                      Proceed to step 2e
          INFOTEL                  Proceed to step 2f
          INTEL                    Proceed to step 2g
          SUPRA                    Proceed to step 2a
          US ROBOTICS              Proceed to step 2h

     2.   Using your communications program, save the appropriate modem
          initialization string to the "stored zero profile" by typing the
          following command strings:

          a.   AT &F &Q6 &W                      Proceed to step 3
          b.   AT &F &M6 &W                      Proceed to step 3
          c.   AT &F &Q6 &W                      Proceed to step 4
          d.   AT &F *E0 &W                      Proceed to step 4
          e.   AT &F /N0 &W                      Proceed to step 3
          f.   AT &F \N0 &W                      Proceed to step 3
          g.   AT &F "H0 \N0 %C0 -J0 &W          Proceed to step 4
          h.   AT &F &K0 &W                      Proceed to step 3

     3.   At the Falcon communications screen, both players select 19,200
          baud as the modem speed if both modems are 14,400 baud.  If one or
          both modems are 9,600 baud, proceed to step 5 first.  When you
          press "ACCEPT" and are presented with the "USE MODEM DEFAULTS"
          question:

          a.   Answer "YES" ... if a connection is established, you're all
               set.  If connection fails, proceed to step 3b.

          b.   Answer "NO" ... you'll be presented with a series of
               "command" boxes.  The first box will show "ATZ", press
               <ENTER> and continue.  The second box will show "ATE0V0Q0",
               press <ENTER> and continue.  The third box will show either
               "ATS0=1" if you selected "ANSWER" mode, or "ATDT" followed by
               the phone number if you are the caller.  Press <ENTER> and
               continue.  The final box will be blank.  DO NOT PRESS <ENTER>
               until the modems have completed their handshaking procedure
               and all the connection tones have ceased completely.  Wait a
               couple seconds to allow the carrier to settle before pressing
               <ENTER> a final time.  If a connection is established, you're
               all set.  If the connection fails, proceed to step 5.

     4.   At the Falcon communications screen, both players select 19,200
          baud as the modem speed if both modems are 14,400 baud.  If one or
          both modems are 9,600 baud, proceed to step 5 first.  

          When you press "ACCEPT" and are presented with the "USE MODEM
          DEFAULTS" question, answer "NO" ... you'll be presented with a
          series of "command" boxes.  The first box will show "ATZ", press
          <ENTER> and continue.  The second box will show "ATE0V0Q0", using
          the backspace key, edit the line to read "ATE1V1Q1", press <ENTER>
          and continue.  The third box will show either "ATS0=1" if you
          selected "ANSWER" mode, or "ATDT" followed by the phone number if
          you are the caller.  Press <ENTER> and continue.  The final box
          will be blank.  DO NOT PRESS <ENTER> until the modems have
          completed their handshaking procedure and all the connection tones
          have ceased completely.  Wait a couple seconds to allow the
          carrier to settle before pressing <ENTER> a final time.

          If a connection is established, you're all set.  If the connection
          fails, proceed to step 5.

     5.   Attempt a connection using a 9,600 baud carrier rather than a
          14,400 baud carrier.  Re-enter the initialization string requested
          in step 2, adding the following additional commands so that the
          final portion of the initialization string reads as follows:

          ... N0 S37=9 &W

          If you were requested to use either &Q6 or &M6, replace those
          values with &Q0 or &M0.

          It may be useful for both players to add the above commands to
          their initialization strings.

          Retrace the procedures listed in the steps above, however, rather
          than selecting 19,200 baud in Falcon, both players should select
          9,600 baud.  Ignore comments directing you back here to step 5. 
          If a connection is established, you're all set.  If connection
          STILL fails, proceed to step 7.

     6.   For unknown reasons, TELEPATH modems are especially resistant to
          establishing a connection through Falcon.  Attempts to connect at
          speeds higher than 9600 baud are nearly always futile.  A few
          users have reported some success with the following procedure: 
          Both players should select 9600 baud in Falcon.  Answer "NO" to
          the "USE MODEM DEFAULTS" question, replace the "ATZ" string with
          AT&FX4N0S37=9 and then proceed normally as outlined in 3b above.

          The only method that seems to reliably establish connections is to
          use a DIRECT connection at 9600 baud.  Initialize the modem with
          the following string BEFORE calling or answering:

          AT &F &K0 &Q6 \G0 %C0 %M0 \N0 S37=9

          (NOTE:  Substitute S37=6 if you need to connect at 2400 baud.)

     7.   Attempt to establish a connection between the modems using a
          standard communications program employing the initialization
          strings provided above for your particular modem.  If a connection
          is established, attempt to initiate Falcon using the DIRECT method
          (see section later on for details on "going direct").  If you are
          unable to establish a connection between the modems, retry after
          restoring the modems to factory defaults and/or lowering the baud
          rate.  If you are STILL unable to establish a connection, seek
          additional assistance from qualified personnel ... you have a
          serious problem.

NOTE:  Unless specifically directed, the procedures outlined above are
intended to be executed only by the player following this flow chart.  It is
nonetheless very useful at times for BOTH players to use either procedure 3b
or 4 as indicated by their particular modem brands.  This is the next best
thing to using a DIRECT method of connection.


* CONNECTIONS UTILIZING V.42bis DATA COMPRESSION *

Ken "Stinger" Richardson has made a major contribution to Falcon
communications with the creation of his V.42bis communications patches and
TSR's.  By modifying Falcon to support hardware flow control (RTS/CTS), he
has opened up the capability of connecting at higher speeds with greater
reliability and stability.  Modems equipped with V.42bis data compression
can establish connections at up to 4 times their nominal baud rate. 
Connections at 38,400 baud or even 57,600 baud are possible in Falcon with
this modification.  

While you won't really obtain a 4x increase in throughput, you will see an
increase from 25-35% over non-V.42bis connections.  In addition, the error-
correction employed in connections of this type means that you'll get fewer
bad data packets which will result in significantly less jitter and warping
in the movements of the opponent's plane while playing Falcon.

Most 14,400 V.42bis modem manufacturers specify 57,600 baud as the speed to
use, some modems work more reliably at 38,400 baud.  There is no significant
difference between 38,400 or 57,600 in the Falcon environment, so use the
one that works most reliably for you.  Users of 9600 baud V.42bis modems
should NOT use speeds higher than 38,400 baud at any time.  Remember that
whatever speed you choose, BOTH players must choose the same speed in
Falcon.

The following conditions are required from your modem in order to utilize
the V.42bis programs and should be saved in your "stored zero profile"
command set.

     1.   V.42bis must be ENABLED.

     2.   Hardware Flow Control (RTS/CTS) must be ENABLED.  Be sure that
          under NO circumstances do you have Software Flow Control
          (XON/XOFF) enabled.

     3.   Reporting of any extended result codes must be DISABLED.  The
          modem should only report "CONNECT" when it establishes
          communications.  No reporting of error correction, protocols,
          DTR/DTE rates, etc. should be passed to Falcon.

Be sure that both players are running the appropriate versions of the
V.42bis patch/programs.  DO NOT attempt to connect dissimilar versions.

V.42bis support for version 3.01(.1) of Falcon is a "patch" to the
FALCON3.EXE file.  Since version 3.02 of Falcon, and for all versions of
MiG-29 and Hornet, support is provided via a small TSR program.  Since
several other TSR support programs for Falcon are available, it is important
to be aware of the "order" in which these are loaded.  For best results, you
should load the V.42bis support program BEFORE any other TSR's.  If you end
up using the DIRECT method to connect Falcon, be sure to load the V.42bis
TSR program BEFORE you go to your communications program to attempt the
connection.


* TROUBLESHOOTING FLOW CHART FOR V.42bis CONNECTIONS *

     1.   Determine your modem manufacturer.

          ACEEX
          BEST DATA
          IMAGE COMMUNICATIONS
          PRACTICAL PERIPHERALS
          ZOOM
          Unlisted modem which is 100% HAYES EXTENDED COMMAND SET compatible

          For Any of the above     Proceed to step 2a

          ACCESS                   Proceed to step 2b
          BOCA                     Proceed to step 2c
          DIGICOM SYSTEMS          Proceed to step 2d
          GVC                      Proceed to step 2e
          INFOTEL                  Proceed to step 2f
          INTEL                    Proceed to step 2g
          SUPRA                    Proceed to step 2h
          US ROBOTICS              Proceed to step 2i

     SPECIAL NOTE FOR GATEWAY TELEPATH OWNERS:  You CANNOT utilize a V.42bis
     connection with this modem.  See the section on NON-V.42bis connections
     for additional details.

     2.   Using your communications program, save the appropriate modem
          initialization string to the "stored zero profile" by typing the
          following command strings:

          a.   AT &F &K3 &Q5 W0 &W               Proceed to step 3
          b.   AT &F &K3 &M5 W0 &W               Proceed to step 3
          c.   AT &F &K3 &Q5 W0 &W               Proceed to step 4
          d.   AT &F *F3 *E9 *M0 &W              Proceed to step 4
          e.   AT &F2 /N6 /Q3 %C1 &W             Proceed to step 3
          f.   AT &F2 \V0 \Q3 &W                 Proceed to step 3
          g.   AT &F "H3 \N3 \Q3 \V0 &W          Proceed to step 4
          h.   AT &F2 &K3 &Q5 W0 &W              Proceed to step 3
          i.   AT &F &B1 &H1 &R2 &A3 X0 &W       Proceed to step 3

     3.   At the Falcon communications screen, both players select 57,600
          baud as the modem speed if both modems are 14,400 baud.  If one or
          both modems are 9,600 baud, both players should select 38,400 baud
          as the modem speed.  When you press "ACCEPT" and are presented
          with the "USE MODEM DEFAULTS" question:

          a.   Answer "YES" ... if a connection is established, you're all
               set.  If connection fails, proceed to step 3b.

          b.   Answer "NO" ... you'll be presented with a series of
               "command" boxes.  The first box will show "ATZ", press
               <ENTER> and continue.  The second box will show "ATE0V0Q0",
               press <ENTER> and continue.  The third box will show either
               "ATS0=1" if you selected "ANSWER" mode, or "ATDT" followed by
               the phone number if you are the caller.  Press <ENTER> and
               continue.  The final box will be blank.  DO NOT PRESS <ENTER>
               until the modems have completed their handshaking procedure
               and all the connection tones have ceased completely.  Wait a
               couple seconds to allow the carrier to settle before pressing
               <ENTER> a final time.

          If a connection is established, you're all set.  If the connection
          fails, proceed to step 5.

     4.   At the Falcon communications screen, both players select 57,600
          baud as the modem speed if both modems are 14,400 baud.  If one or
          both modems are 9,600 baud, both players should select 38,400 baud
          as the modem speed.  When you press "ACCEPT" and are presented
          with the "USE MODEM DEFAULTS" question:

          a.   Answer "NO" ... you'll be presented with a series of
               "command" boxes.  The first box will show "ATZ", press
               <ENTER> and continue.  The second box will show "ATE0V0Q0",
               using the backspace key, edit the line to read "ATE1V1Q1",
               press <ENTER> and continue.  The third box will show either
               "ATS0=1" if you selected "ANSWER" mode, or "ATDT" followed by
               the phone number if you are the caller.  Press <ENTER> and
               continue.  The final box will be blank.  DO NOT PRESS <ENTER>
               until the modems have completed their handshaking procedure
               and all the connection tones have ceased completely.  Wait a
               couple seconds to allow the carrier to settle before pressing
               <ENTER> a final time.  If a connection is established, you're
               all set.  If the connection fails, proceed to step 4b.

          b.   Lower the baud rate selected in Falcon (must be done by BOTH
               players) to 38,400 and/or 19,200 baud and repeat step 4a.  

          If a connection is established, you're all set.  If the connection
          fails, proceed to step 5.

     5.   Re-enter the initialization string requested in step 2, adding the
          following additional commands so that the final portion of the
          initialization string reads as follows:

          ... S25=125 S26=125 &W

          It may be useful for both players to add the above commands to
          their initialization strings.

          Retrace the procedures listed in the steps above.  If a connection
          is established, you're all set.  If connection STILL fails,
          proceed to step 6 if you are using 14,400 baud modems.  If you are
          using 9,600 baud modems, proceed to step 7.

     6.   Attempt a connection using a 9,600 baud carrier rather than a
          14,400 baud carrier.  Re-enter the initialization string requested
          in step 2, adding the following additional commands so that the
          final portion of the initialization string reads as follows:

          ... N0 S37=9 S25=125 S26=125 &W

          It may be useful for both players to add the above commands to
          their initialization strings.

          Retrace the procedures listed in the steps above, however, rather
          than selecting 57,600 baud in Falcon, both players should select
          either 38,400 or 19,200 baud.  If a connection is established,
          you're all set.  If connection STILL fails, proceed to step 7.

     7.   Attempt to establish a connection between the modems using a
          standard communications program employing the initialization
          strings provided above for your particular modem.  If a connection
          is established, attempt to initiate Falcon using the DIRECT method
          (see section later on for details on "going direct").  If you are
          unable to establish a connection between the modems, retry after
          restoring the modems to factory defaults and/or lowering the baud
          rate.  If you are STILL unable to establish a connection, seek
          additional assistance from qualified personnel ... you have a
          serious problem.

NOTE:  Unless specifically directed, the procedures outlined above are
intended to be executed only by the player following this flow chart.  It is
nonetheless very useful at times for BOTH players to use either procedure 3b
or 4a as indicated by their particular modem brands.  This is the next best
thing to using a DIRECT method of connection.


* GOING DIRECT, THE CONNECTION OF LAST RESORT *

Ok, so you've tried and tried ... well, there's one last way to get Falcon
to connect, and in most cases, this will work where all else has failed.

A DIRECT connection in Falcon means that a connection between the two modems
has already been established, and communications are operating normally
between the two modems.  You can verify this fact if you and your opponent
are able to chat back and forth in your terminal program.  As far as Falcon
is concerned, this is the equivalent of hooking up two computers via a NULL
MODEM cable for a straight serial port to serial port connection.

In order to utilize this method, you'll need a communications program that
allows you to EXIT TO DOS without dropping the connection.  Don't confuse
this with the DOS SHELL offered in some programs, Falcon requires ALL of
your computers available memory in order to run.  Shells just don't provide
sufficient memory resources.  Most full function communications programs
provide this capability, ProComm, QModem and Telix for example, check your
program documentation for complete instructions.  DO NOT ATTEMPT THIS WITH A
WINDOWS COMMUNICATIONS PROGRAM.  Windows will complicate matters enormously
since it generally takes complete control over the serial ports.

Choose the speed you'll be using in Falcon, 2400 through 19,200 baud for
non-V.42bis connections, 38,400 or 57,600 baud for V.42bis connections. 
Utilizing one of the above listed strings, set up your modem, then either
dial the other player with the ATDx command (replace x with the phone number
to dial) or place your modem in auto-answer mode by using the ATS0=1
command.

Once you've connected, EXIT TO DOS and start Falcon.  At the comms screen,
make all the normal choices, with one exception.  Choose DIRECT rather than
MODEM as the form of connection.  Also, be sure that one player selects
CALLER, and the other player selects ANSWER.  When you choose ACCEPT, Falcon
should start communicating and setting up for a game.  If the modems seem to
sit at the "WAITING FOR OTHER SIDE TO CONNECT" message for an unusually long
time, perform a COLD BOOT and try again lowering the connection speed a
notch or lowering the carrier speed.  In general, NON-V.42bis connections
are easier to establish, so you might want to try that as well.

* CONCLUDING COMMENTS *

I would like to express thanks to all the people who have contributed in
order to make this document possible.  For your help in providing modem
strings, time and tips, I offer a VERY snappy salute.

Special thanks are in order for Ken "Stinger" Richardson for his continuing
efforts to provide state of the art support programs for Falcon.  Please
show your support of his efforts by registering your copies of his programs.

If you have any information on modems not covered in this discussion, or if
you find any errors in this document, please forward that along so that it may
be included in future revisions.  Direct comments, corrections, suggestions
to:  Victor "Duke" Zaveduk @ CompuServe 76711,27 ... thank you in advance for
your help in making Falcon more enjoyable for everyone!


Wishing you all successful connections and happy hunting ... CHECK SIX!

Victor "Duke" Zaveduk, CINC CompuServe Falcon Ladder
Revised March, 1994

