Source: SPITFIRE.DOCEdition: searchable Web reading editionPresentation: historical wording retained
6.0 - COMMAND LINE PARAMETERS
-----------------------------
Command Line Parameters can be used to make SPITFIRE start-up with
a different configuration. Command Line Parameters are what you type
at the DOS prompt (or send to the program from a batch file) when you
boot SPITFIRE.
/Cx - Sets which COM port to use (<x> represents the
number of the COM port).
/E - Used with front end programs for detecting error
correction modem connections, making the Ymodem-g
file transfer protocols available. This /E must
be used in conjunction with baud rate parameter.
/M - Sets the initialization string used with your
modem.
/N - Allows SPITFIRE to be terminated without hanging
up the phone or re-initializing the modem. This
allows a second copy of SPITFIRE to be run as a
door. NOTE: A baud rate parameter must be specified
prior to the /N or it has no affect.
/P - Sets the drive and directory used as the SPITFIRE
Work File Path.
/Tx - Used with frontend programs and sets the amount of
time allotted to the caller. This allows systems
running under a frontend program to pass the
amount of time remaining before a frontend scheduled
event. This only applies to the first caller on
immediately after SPITFIRE is booted since SPITFIRE
will terminate and return control to the frontend
program when the caller logs off. This could
also be used when running SPITFIRE as a door.
(x indicates the amount of time in minutes the
caller is allowed.)
(baud rate) - This represents the numerical value for the highest
possible baud rate of your system. This allows
SPITFIRE to be booted without initializing the
modem so it can be used in conjunction with some net
mail software programs. Refer to the section -
SPITFIRE NET-MAIL CAPABILITIES - of this manual for
further information. The range of allowable baud
rates for SPITFIRE are 0 (allows local log on only)
to 115200.
The use of these Command Line Parameters is not usually necessary.
An exception might be when you are originally booting SPITFIRE for the
very first time or if your configuration has changed. When originally
booting SPITFIRE you should only use Command Line Parameters if you are
using a COM port other than COM 1. In other words, SPITFIRE is written
to default to COM port 1 so you will not have to use Command Line
Parameters unless these defaults are different from what you plan to
use while running SPITFIRE.
SPITFIRE /C2
The above example would boot SPITFIRE utilizing COM port #2.
It should also be mentioned that any Command Line Parameters
assigned from the DOS prompt or included in the SF.BAT file will
override those set by using ALT+M or ALT+P at the SPITFIRE "Ready
Prompt". Anytime a change is made in the COM port assignment, work
path, or modem initialization string, you MUST also change the
specifications set in the SF.BAT file. It is for this reason that
the use of command line parameters in SF.BAT is not recommended.
6.1 - SF.BAT
------------
It is advisable to use the SF.BAT to boot SPITFIRE. Some of the
advantages for using a batch file to invoke SPITFIRE are listed below:
If an error occurs, and you're using the SF.BAT included with
your SPITFIRE package, SPITFIRE will automatically reset with the
SF.BAT file. The SF.BAT file, included with your SPITFIRE package,
is vital for running Scheduled Events and Door programs. More
information regarding Scheduled Events and Door programs may be found
in other sections of this manual.
If you have the AUTOEXEC.BAT file written to automatically boot
SPITFIRE upon system startup and there is a power outage, then SPITFIRE
will automatically reboot when power is restored. To configure the
AUTOEXEC.BAT file to automatically boot SPITFIRE upon system startup,
the last two commands in the AUTOEXEC.BAT file should resemble this:
CD\SF
SF
The above example assumes you are running SPITFIRE on the drive
you are booting from, you are running SPITFIRE in a directory named SF
and you are using the SF.BAT file to invoke SPITFIRE.