/begin "Starting BreakOut-II"
Under this communications editor "panel," you 
are automatically "live," and on-line in one 
of three modes:

1. Interactive controlling COMP
2. Interactive controlling COMS
3. Passively MONITOR the communications circuit

If you wish to monitor a communications circuit
but have only a single available
communications "port," use the optional Laptop 
Monitor Adapter (LMA).

You may ask for help at anytime by pressing F1 or
Shift+F1.
/end

/begin "Exiting BreakOut-II"
From the communications "panel," press "Alt+X," or 
select the File:Exit menu item.

If you wish to temporarily exit to "DOS," then 
select the File:Drop to System menu item. Be careful
not to run any application that may modify 
communications ports or the interrupt controller.
/end

/begin "Selecting the appropriate video"
"Now," you select the video adapter of choice the
first time you operate BreakOut-II. If you don't 
specify an "adapter when BRKOUT is started," VGA 
is assumed. 

You may select the color scheme that best fits
your video adapter.  Once you select the video "color,"
BreakOut-II will remember your choice. Color palettes
do not take effect until you exit BreakOut-II and start
BRKOUT over.
/end

/begin "Optimizing communications performance"
"First," make sure that if you operating at speeds
greater than 9600 baud that you are using BreakOut-II
on at least a 386 CPU (or faster).

Use the VGA display adapter - it is optimized for
the fastest screen display performance. If you are
using the VGA43 or VGA50 "mode," change it to VGA by
starting BreakOut-II as follows:
"   BRKOUT VGA"

You can temporarily disable the display
of data events (which can be slowed down by writing to
multiple "viewers," by unchecking the View:Display
menu item. If that is "unacceptable," try selecting
the View:Single menu item to display all data events
on a single row.
/end

/begin "Getting help"
You may ask for help at anytime by pressing F1 or
Shift+F1.

If you are still not "satisfied," please scan through the
'"Troubleshooting"' chapter of the User's Manual.

If you need personnal "help," contact your distributor.
Our distributors are trained to help you.
/end

/begin "Working with configuration files"
Configuration files use an extension of CFG. The
current configuration file is referenced in the 
BREAKOUT.INI file. Each configuration file 
includes the following information:

o Video adapter type
o Communications mode
o Primary (DCE) port settings
o Secondary (DTE) port settings
o Default communications event used in the editor
o Time stamp enabled status
o Display character set filename
o Keyboard map filename
o Underlined cursor status
o Video palette number
o Communications panel viewer format
o Unified port settings status
/end

/begin "Using the LMA"
Although the LMA is an option to "BreakOut-II," follow
the instructions on the card that comes with the LMA
device.

The LMA (short for Laptop Monitor Adapter) uses a printer
port instead of your secondary communications port
(known as COMS in BreakOut-II). You must make sure of 
the following:
1. The LMA has been properly configured with SETCOM
2. The LMA has supplied power (12Vdc or battery)

Failure to not follow those two rules could cause 
BreakOut-II to hang.
/end

/begin "Using accelerator keys"
BreakOut-II has several ways to accelerate keystrokes.

The event editor has assigned Microsoft Word-like 
accelerator keys to specific menu items. These are
generally Ctrl keys. These keys are not used in the
communications panel since Ctrl keys are normally 
critical for transmitting data interactively to a 
receiving DCE.

Alt key combinations are used to bring down and select
menu items. Alt+F4 and Alt+X universally exits the 
current panel. Macro keys are used to record and then
playback common activities. Macros use function keys
(such as Shift+F2).
/end

/begin "What am I allowed to distribute?"
You are allowed to distribute free of charge to other
BreakOut-II licensed users:

1. Custom help files (with .HL* filename extensions)
2. DCS files (with .DC* filename extension)
3. Macro files (with .MAC filename extension)
4. Captured files (with .CAP filename extension)
5. BCL files (source .BCL and object .BE*)
6. Configuration files (with .CFG filename extension)
7. Keyboard map files (with .KMP filename extension)
8. Custom palette files (with .PAL filename extension)
9. Trigger files (with .TRG filename extension)
10. Soft font files (with either .EGA or .VGA extension)

Since every system may have different "configurations," it
is not recommended that you distribute SETCOM port 
configuration files (.CPC filename extension).
/end

/begin "Is the BMC working?"
If you are getting incorrect communication activity 
while the BMC is plugged "in," try the following:

1. Make sure communications panel reflects monitor mode
2. If data or signals in either COMP or COMS, switch
"   cables (COMP in COM2, COMS in COM1) and see if some"
"   data and/or signal activity shows."
3. Execute SETCOM to see if COMP and COMS are detected
4. Try a null modem device in communications circuit
5. Find more detail in '"Troubleshooting"' chapter
/end

/begin "Is the LMA working?"
If BreakOut-II hangs while the LMA is "connected,"
there may the chance that the LMA is no longer 
communicating.

Make sure that the LMA has proper power supplied or
that the battery is sufficiently charged. If in 
"doubt," you may always exit BreakOut-II and 
run SETCOM. SETCOM will validate that the LMA is
properly configured.

Just to make sure that there isn't a battery
"problem," always try the LMA with the supplied 12Vdc
power supply.
/end

/begin "How do I re-transmit DCE events?"
Once you have captured both DTE and DCE "events,"
you may wish to retransmit only the DCE events.
Since BreakOut-II only supports transmitting DTE
events you will need to follow these steps:
1. Go into event editor
2. Save DCE events as DTE events with DCE_DTE.BES
3. Clear the workspace (within the editor)
4. Load back the just-saved file
5. Select all events
6. Return back to communications panel
7. Transmit Selected workspace events

That is all there is to it! You can even assign
a macro key to this and execute it with a single
keystroke.
/end
