Contents of the ADDEXT.DOC file
Addext V 5.0 (C) Copyright 1990 PC Development Group
(C) Copyright 1990 Craig Kootsillas
The C Line RBBS (901) 427-1680
Addext was developed to aid in the implementation of external
file transfer protocol drivers.The target telecommunications
program is ProComm (because of its implementation of 'hot keys')
but it can be used along with any telecommunciations package that
allows for shelling to an external program. It also can be used
by any telecommunications program that allows for dropping to
DOS -- AddExt then would be invoked from the command line.
There are other programs "out there" that achieve the same
results, but none (to my knowledge) automatically build the
protocol drivers' command line -- something that takes time,
effort, and sometimes a bit of trial and error.This program was
designed to make it easy to take advantage of the speed of the
new protocols not implemented in the more popular
Addext will build command lines for the following file transfer
CModem -- by Lavio Pareschi
Lynx -- by Matthew Thomas
Kermit-- PCKermit by Jan A. van der Eijk
YModem-- As implemented by Omen Technology's DSZ
ZModem -- by Omen Technology
K9XModem -- by Crater Rim Software
JModem -- by Richard B. Johnson as implemented by Crater Rim
MegaLink -- by Paul Meiners Super8k -- by Crater Rim
Super8k -- by Crater Rim Software
MPt -- by Matthew Thomas
Updates will be made available as new protocols are written. Note
that the command lines are written specifically for the drivers
as outlined above. Omen Technology's DSZ for ZModem and the SK&J
archive for JModem, K9XModem and Super8k. Command lines for
other implementations of the drivers may differ from these. All
protocol drivers are available for download on The C Line RBBS.
WHY ADD EXTERNAL PROTOCOL DRIVERS
First, credit is due to Ward Christensen -- the author of the
XModem file transfer protocol. However, as more developers have
entered the protocol writing arena faster and more efficient
protocols have come into existence with enhancements such as
larger data blocks (which result in faster data transfer), full
duplex streaming operations (sending and receiving data
simultaneously) and transfer resumption (being able to resume an
aborted transfer without having to start over).
XModem does not offer these enhancements. In addition, most
telecommunication software packages implement only XModem, YModem
(XModem with larger blocks), and Kermit (a full duplex streaming
protocol). Because most bulletin boards (commercial and private)
limit on-line time -- either on a call-by-call basis or on a
total-per-day basis, it is important to transfer files as quickly
and efficiently as possible.
The problem is that there is no standardization of command line
syntax. Implementing a new protocol can really be a headache --
especially for people new to "bbsing".
SETTING IT UP
1. Place ADDEXT.EXE into the directory you run your
telecommunications program from.
2. Place the executable files for all the protocols you want to
implement into the same directory. These drivers can be
downloaded from The C Line RBBS as:
CMODEM1.ZIP for CModem
KRMT210.ZIP for PCKermit
LYNX302.ZIP for Lynx
MLINK16.ZIP for MegaLink
SK&J0340.ZIP for JModem, K9XModem and Super8K
DSZ42489.ZIP for ZModem
MPT.ZIP for MPt
Although it is not necessary, I recommend that you read the
documentation for each of these protocol drivers.
-- Enter ProComm and access the SETUP menu (ALT-S).
-- Select FILE/PATH OPTIONS.
-- Select F for User Hot Key 1 and enter 'ADDEXT'.
-- Enter Telex and access the SETUP menu (ALT-O).
-- Select FILE/PATH options (F)
-- Select H for editor options and enter 'ADDEXT'.
-- At present, QModem does not support shelling to
another program. When you're ready to transfer
files, enter (ALT - D) to drop to DOS. When at
the command line, enter "ADDEXT".
Follow your normal download procedure on the board. When
prompted to begin your transfer, enter ALT-J if using ProComm,
ALT-A if using Telix, and ALT-D followed by "ADDEXT" if using
This will execute AddExt.EXE. Upon loading, the program looks
for its configuration file (addext.cfg) in the current working
directory. If it is not found, or it is from a previous version,
you will be prompted for your upload and download paths. AddExt
then will verify that the paths exist. Enter the full pathname
from the root directory (either C:\path\path or \path\path).
Unlike other external file transfer protocol shells, AddExt
detects the active COM port* and baud rate, passing them to the
protocol drivers. This is particularly useful if you call a
variety of on-line services at different speeds. It also allows
you to adapt to line noise by dropping down in speed without
having to rewrite your configuration file.
You then will be presented with a menu of protocols currently
supported by AddExt.exe. Choose the protocols for which you
have drivers available in the current directory. This information
will be written to the configuration file, you will not have to
enter it again.
The order that you select the protocols is important. Your choices
will be presented to you during transfers in the order that they
were selecting during the configurations process. In other words
the first protocol you select will be at the top of the menu and
will become your default protocol.
After configuration, you then will be asked if you are uploading or
downloading. You can toggle through the options with your keypad
or you can make your selection by entering "u" for upload or "d"
Next you will be presented with a menu of protocols that you set
up. Select the same protocol that you selected on the board. Note
that the menu "wraps around". In addition, you will be given the
option to change your default paths.
If the protocol and transfer direction requires a filename, you
will be presented with a menu of files in your current upload path.
You can select the file to upload either by highlighting it and
pressing 'enter', or by typing in the filename. If you are uploading
AddExt will verify the existence of the file in your specified path.
If not found you'll be given the option to change paths, reenter the
filename, or abort the transfer.
Please let me know of any bugs that you encounter. In addition,
please offer any criticisms or suggestions you may have.
You are free to use and distribute AddExt provided you do not use
it in a commercial environment, do not charge for it and distribute
it in an unmodified form.
Although no problems have been encountered to date, you are using this
software at your own risk.
Register your copy of AddExt by sending $10.00 to:
982 Lower Brownsville Road
Jackson, TN 38301
Registration of AddExt insures that you will receive a copy of the
next release of AddExt.With your registration fee, please include
your name and address.
Please feel free to leave any comments or criticisms of AddExt as a
message to the Sysop on The C Line.
Mycroft (408) 927-0105
SoftWare XChange (904) 463-0027
Because the IRQ lines and base addresses of com ports beyond
COM2 are not standardized, AddExt does not support the use of
COM ports beyond COM2.
Craig Kootsillas 12/16/90
The C Line RBBS