Source: SPITFIRE.DOCEdition: searchable Web reading editionPresentation: historical wording retained
2.0 - SPITFIRE HARDWARE REQUIREMENTS
------------------------------------
The following are considered the minimum equipment requirements
for running SPITFIRE:
<1> MS-DOS/IBM compatible personal computer
<2> At least 256K memory
<3> DOS version 3.0 or higher
<4> Fixed disk (preferable)
<5> Modem
SPITFIRE requires several files being open at the same time.
For this reason, you will need to have the following files and buffers
set in your system's CONFIG.SYS file, located in your root directory.
SPITFIRE may not work properly if this is not done!
CONFIG.SYS should have the following settings:
FILES=25
BUFFERS=30
DEVICE=ANSI.SYS
DEVICE=BRK.DRV
The "DEVICE=BRK.DRV" is optional, however, if your system supports
the use of SPITFIRE Doors, External File Transfer Protocols, or any
of the Sysop Configurable commands from the Main, File, Message or
Sysop Menus, the use of BRK (or some similar utility) is certainly
recommended. More information regarding the use of BRK is provided in
the EXTERNAL FILE PROTOCOLS section of this manual.
If you are unfamiliar with how CONFIG.SYS works, consult your DOS
manual. If you do not configure your system to allow at least 25 files
to be open at once, you may have a problem with SPITFIRE aborting and
displaying a message of Runtime error 004.
SPITFIRE supports a number of features which cause it to search
the PATH for COMMAND.COM. To work properly, SPITFIRE must be
able to find COMMAND.COM residing in a directory set up in your path
statement. These features are the ability to jump to DOS, the Sysop
configurable features from each menu, execution of the SFINIT.BAT or
the SFMSGPCK.BAT and external file transfer drivers. In the event you
are unfamiliar with setting a PATH, please refer to your DOS manual.
2.1 - MODEMS
------------
SPITFIRE automatically determines your incoming callers' baud
rate. In order for this to work, your modem must be able to send
verbose result codes. Appendix A contains a list of modems and their
corresponding initialization strings which have been reported to work
with SPITFIRE. SPITFIRE determines the baud rate of incoming calls
by receiving the verbose result code from your modem when the modem
establishes carrier detect. Listed below are examples of verbose
result messages returned by most modems.
Non-Error Correction Modems Error Correction Modems
--------------------------- -----------------------
300 Baud - CONNECT
1200 Baud - CONNECT 1200 1200 Baud - CONNECT 1200/ARQ
2400 Baud - CONNECT 2400 2400 Baud - CONNECT 2400/ARQ
7200 Baud - CONNECT 7200 7200 Baud - CONNECT 7200/ARQ
9600 Baud - CONNECT 9600 9600 Baud - CONNECT 9600/ARQ
14400 Baud - CONNECT 14400 14400 Baud - CONNECT 14400/ARQ
16800 Baud - CONNECT 16800 16800 Baud - CONNECT 16800/ARQ
28800 Baud - CONNECT 28800 28800 Baud - CONNECT 28800/ARQ
SPITFIRE's default modem initialization string seems to work with
many modems. Some modems, however, may require a unique initialization
string. There are three modem register settings that MUST exist in
your modem initialization string for SPITFIRE to work properly. They
are S0=0, V1 and S2=1.
There are a number of firms (modem manufacturers, etc) who
graciously provided evaluation products for testing with SPITFIRE.
Mike Woltz and Buffalo Creek Software would like to express much
appreciation to these firms for their help and support. These firms
are not listed for fear that we would omit a name.
2.2 - MODEM INITIALIZATION
--------------------------
When SPITFIRE is booted, it sends the Pre-Initialization string
the Sysop configures at the ALT+M SPITFIRE Async Configuration window,
waits for modem response and then sends the configured modem
initialization string to the modem after each caller. This procedure
seems to work fine with most modems.
In the event you are using a USR HST Dual Standard and wish to
run your BBS at 38400 baud in V.32 mode, the initialization string
listed below works:
ATS0=0B0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X6^M
Should you need to change the modem initialization string, you
select ALT+M at the "SPITFIRE ready for use" prompt. Appendix A
contains a listing of modems and corresponding initialization
strings which have been reported to work with SPITFIRE. The modem
initialization string can also be altered at the DOS prompt by
entering the following command line parameters:
SPITFIRE /M ATS0=0Q0V1E0M0H0S2=1X1^M (Your Initialization String)
Using the same command line parameters, the modem initialization
string can be included within the SF.BAT file. Please note, however,
the command line parameters set in SF.BAT will always override those
set by using ALT+M at the "SPITFIRE ready for use" prompt.
The configuration of SPITFIRE in conjunction with most modems
is relatively simple. One of the first things which you need to be
concerned with is whether your modem is configured to report a
carrier even when there is not a carrier. Many (most) modems,
by factory default, are configured to constantly report a carrier
even when there is not an actual carrier. When initializing the
modem, SPITFIRE will provide the error message "Modem Reporting
Carrier" when the modem is configured to falsely report a carrier.
In such case, it is recommended that you change the factory
defaults using the below listed procedure:
1) Load your favorite terminal program (QMODEM, TELIX or
whatever).
2) At the OK prompt, enter AT&C1&D2&W ... You should then see
another OK prompt.
3) Return to DOS and then boot SPITFIRE. SPITFIRE should no
longer provide the error message "Modem Reporting Carrier".
In the event you are using a 2400 baud modem or slower (non-high
speed FAX modem), then the below listed configuration should work:
Baud Rate: 2400
Pre-Init String: ATZ^M
1st Choice
Init String: ATS0=0V1Q0E0H0M0S2=1X1^M
2nd Choice
Init String: AT&F1S0=0V1&C1&D2Q0E0H0M0S2=1X1^M
3rd Choice
Init String: AT&FS0=0V1&C1&D2Q0E0H0M0S2=1X1^M
4th Choice
Init String: AT&FS0=0V1Q0E0H0M0S2=1X1^M
Off Hook String: ATM0H1
Hardware Data Flow Control: Yes
DTR Hangup: Yes
In the event you are using a high speed FAX modem, then the below
listed configuration should work:
Baud Rate: 19200 for 14400 bps modem
Baud Rate: 38400 for 28800 bps modem
Baud Rate: 57600 for high speed modem
if you are using a 16550 UART chip
Pre-Init String: ATZ^M
1st Choice
Init String: AT&F1S0=0V1&C1&D2Q0E0H0M0W2S95=3S2=1X4^M
2nd Choice
Init String: AT&FS0=0V1&C1&D2Q0E0H0M0W2S95=3S2=1X4^M
3rd Choice
Init String: AT&FS0=0V1Q0E0H0M0S2=1X4^M
Off Hook String: ATM0H1
Hardware Data Flow Control: Yes
DTR Hangup: Yes
In the event the above information doesn't work correctly with
your modem, then please feel free to contact Buffalo Creek Software
for help.
The 'Pre-Init String Failure' error message is for informational
purposes. Your system may work just fine even though you see this
informational error message. Such informational error message simply
means that your modem did not return an OK after the configured
pre-initialization string was sent to it.