Source: SPITFIRE.DOCEdition: searchable Web reading editionPresentation: historical wording retained
3.0 - GETTING STARTED
---------------------
If you're like most computer users, you're probably not thrilled
with the prospect of reading the entire documentation of SPITFIRE. Most
folks are going to boot this program and try to run SPITFIRE without
reading further. So here are some quick guidelines regarding your
initial setup of SPITFIRE.
<1> Create a directory named SF on the drive on which you intend
to run SPITFIRE. Copy all SYSTEM FILES into your newly
created SF directory. (Listed in the SPITFIRE SYSTEM FILES
section of this manual.)
<2> Included in the SPITFIRE package is a file named SF.BAT.
You may use any text editor (as long as it saves in ASCII
format) to modify this file. Examine the default values
(such as target and source drives) and configure them to
comply with your setup. (Example: The default drive
specification is C: and if you're running SPITFIRE on drive
D, then you'll need to change this to D: ). After finishing
that, look for the line that contains SPITFIRE /C1. "/C1"
indicates the COM port you are using. In the event you are
using COM port 2, you need to change the string to read
"SPITFIRE /C2". After you've made these changes, be certain
to save your modified file to disk.
** NOTE ** The default command line parameters are used for
booting SPITFIRE on your system for the first time. After
setting these parameters in SPITFIRE by using the ALT+M modem
configuration window, any unnecessary command line parameters
(i.e., SPITFIRE /C1, etc.) should be removed from your SF.BAT
file.
<3> Now you are ready to boot SPITFIRE by using your SF.BAT
file. When first booting SPITFIRE, you will get the prompt
"SFSYSTEM.DAT not found! Do you wish to create it? <Y/n>".
SPITFIRE defaults to "Y" and by pressing <ENTER> or entering
"Y" for yes, SPITFIRE creates the required SFSYSTEM.DAT file.
Subsequently, SPITFIRE provides similar prompts for other
required files. These include:
SFNODE.DAT
SFUSERS.DAT
SFFAREA.DAT
SFMCONF.DAT
By pressing <ENTER> or "Y" at each prompt, SPITFIRE will
automatically create the file and place it in the appropriate
directory.
The first thing to be concerned with is not properly
assigning the correct COM port. In the event you have
the wrong COM port configured, it is possible that SPITFIRE
will lock up at this point. In such case, refer to step
number 2 in this section. If the COM Port is properly
assigned, you will then be prompted for the Sysop's Name.
The name you enter here is the name that the callers will
see credited as being the Sysop of the system. You will most
likely want to enter your real full name.
Next, SPITFIRE will ask you for a Sysop Caller Name. It
is recommended you answer this prompt with "Sysop". (The
name you enter here, should be the name that you use to log
on the BBS.) SPITFIRE addresses all comments left for the
Sysop to this configured name.
SPITFIRE will next prompt you to input a password, phone
number, city, state/province and date of birth. SPITFIRE
uses the responses entered here to automatically add you as
the first caller in the SFUSERS.DAT file.
If your modem is malfunctioning, disconnected or turned
off, SPITFIRE will display the message "Your modem is not
responding properly! Do you wish to continue? <y/n>".
Answer "Y" and SPITFIRE will progress to the "SPITFIRE ready
for use..." prompt. Press ALT+M to modify the modem's
initialization string to one which will work properly with
your modem. (Refer to the section, SPITFIRE ASYNC
CONFIGURATION for configuring SPITFIRE for your modem.)
<4> At the "SPITFIRE ready for use..." prompt, press ALT+S to
log on locally as Sysop. When asked for your name, you must
enter the same name as you entered as the Sysop Caller Name
when configuring SPITFIRE. (If you use the name "Sysop", the
system will ask for a last name. Simply press <ENTER> and
continue.) Next enter the password you previously selected.
At the Main Menu, press F2 and set your security level to
999. Now move from menu to menu and view the various
features. After viewing, and experimenting with the various
features, log off by pressing G for Goodbye, and next press
Y to answer Yes to the "Are you sure you want to logoff?"
prompt. SPITFIRE will reset, and the "SPITFIRE ready for use"
prompt will appear at this point.
3.1 - SPITFIRE ASYNC CONFIGURATION
----------------------------------
The SPITFIRE Async Configuration is used to view or modify your
modem configurations such as serial port, initialization strings, baud
rate, etc. AT the "SPITFIRE ready for use..." prompt, press the ALT
key, and while holding it down, next press the M key. This keystroke
combination opens the SPITFIRE Async Configuration window. The commands
that you will see are listed below:
--< SPITFIRE NODE 1 ASYNC CONFIGURATION >--
<I> Initialization String............ :
ATS0=0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X1^M
<A> Answer String.................. : ATA
<F> Fax Connection Result Msg...... : FAX <1> Line COM1.. : IRQ4
<P> Pre-Initialization String...... : ATZ^M <2> Line COM2.. : IRQ3
<O> Offhook String................. : ATH1 <3> Line COM3.. : IRQ4
<S> Serial Port No................. : 1 <4> Line COM4.. : IRQ3
<B> System Baud Rate............... : 19200 <5> Line COM5.. : IRQ0
<E> Error Correction Message....... : ARQ <6> Line COM6.. : IRQ0
<H> DTE Locked..................... : Yes <7> Line COM7.. : IRQ0
<N> Number Of Rings................ : 1 <8> Line COM8.. : IRQ0
<D> Display Result Messages........ : On <F1> Base COM1.. : 03F8
<C> Disconnect Delay............... : 28 <F2> Base COM2.. : 02F8
<U> Use High Speed Async Routines.. : Yes <F3> Base COM3.. : 03F8
<R> Baud Rate Requirement.......... : 1200 <F4> Base COM4.. : 02F8
<L> Break Length..(1000=1 Second).. : 100 <F5> Base COM5.. : 0000
<M> DTR Hangup..................... : Yes <F6> Base COM6.. : 0000
<F7> Base COM7.. : 0000
<F8> Base COM8.. : 0000
Enter Command or <Q>uit -
Command <I> Sets the modem initialization string appropriate for
your modem. In most cases, a carriage return (a ^M)
should be placed at the end of your initialization
string. However, some modems do not require the
carriage return. If this is the case with your modem,
simply do not include the ^M at the end of your
initialization string.
** NOTE ** The caret sign (^) is entered by pressing the shift
key, in combination with the numeric 6 key and should
not to be confused with the caret sign which is used
to indicate a control character when creating SPITFIRE
Display Files.
Command <A> Allows the Sysop to configure the answer string that
is required by the modem in order for the modem to
receive both Fax and data calls. In the event you
do not have your system configured to receive Fax
calls, this option should be set to ATA. If the
system is configured to receive Fax calls, then
you should use the answer string supported by your
particular modem.
Command <F> Specifies the FAX Connection Result Message which
allows SPITFIRE to distinguish that the incoming
call is a Fax call. Enter the Fax Connection Result
Message that is appropriate for your particular modem.
For example, the USR Courier HST Dual Standard with
Fax uses +FCO. SPITFIRE defaults to +FCO as the FAX
Connection Result Message.
Command <P> Specifies the pre-initialization string sent to the
modem prior to initializing the modem. ATZ^M should
be used in most instances. However, some modems do
not require the carriage return (^M). If this is
the case with your modem, simply use ATZ here.
** NOTE ** The caret sign (^) is entered by pressing the shift
key, in combination with the numeric 6 key and should
not to be confused with the caret sign which is used
to indicate a control character when creating SPITFIRE
Display Files.
Command <O> Defines the off hook string required by your modem.
Most modems use the standard ATH1 to set the modem
off hook. However, some newer modems, due to a change
in FCC regulations, will only leave the modem off hook
for 30 seconds when the ATH1 command is used. The off
hook string allows the Sysop to enter the string which
will allow the modem to remain off hook for an extended
period of time. For example, the Zoom 28.8 uses ATX1D;
as its extended off hook string.
Command <S> Specifies the COM Port being utilized by this node.
Command <B> Defines the maximum baud rate allowed by this node.
The maximum COM port speed in SPITFIRE is 115200.
Command <E> Specifies the Error Correction Message for your
particular modem if an error correction modem is
being used. For instance, US Robotics uses ARQ.
Please refer to your modem manual to determine the
error correction message used by your modem, providing
it has error checking capabilities.
Some of the newer model modems use different result
codes when an error correction connection is detected.
SPITFIRE is hard coded to automatically search for the
ARQ, MNP and REL result codes which indicate an error
correction connection has been made. In addition to
these, SPITFIRE will search for the error correction
control message the Sysop configures here.
Command <H> Specifies whether the BBS is being configured to
operate at a locked baud rate. If toggled to Yes,
and the BBS is configured to a maximum baud rate of
57600, when an incoming call is received SPITFIRE
leaves the COM port open at 57600 regardless of the
speed of the incoming call. In other words, when set
to Yes, it is the modem's responsibility to control
the flow of data. This is equivalent to hardware
flow control. If toggled to No, and the BBS is
configured to a maximum baud rate of 57600, when an
incoming call is received, SPITFIRE adjusts the COM
port speed to match that of the incoming call. Or,
SPITFIRE assumes responsibility to control the flow
of data. This is equivalent to software flow control.
Command <N> Specifies on what ring number SPITFIRE will answer
incoming calls. For instance, with 1, SPITFIRE answers
the incoming call on the first ring. Most often, you
will want this set to 1.
Command <D> Toggles On or Off SPITFIRE's display of the modem's
verbose message. For instance, when toggled On, and a
caller logs on at 2400 baud, CONNECT 2400 is displayed
to the screen, and is also recorded in the CALLERS.LOG.
If this is toggled Off, the CONNECT message will not be
written to the screen or recorded in the CALLERS.LOG.
Command <C> Specifies the disconnect delay. This feature is for
modems utilizing a data buffer. The Sysop may use
this option to configure the amount of time to delay
the disconnect, allowing the data contained in the
modem buffer to be displayed to the caller. SPITFIRE
defaults to 28, which is adequate for the 5k buffer
in the US Robotics HST.
Command <U> This switch should be set to On provided your system
operates properly using high speed routines. If your
display files are not properly shown to the remote
caller, then turn this switch Off.
Command <R> This switch sets the minimum baud rate required to
access your BBS. For instance, if set at 1200, a
caller must connect at a baud rate between 1200 and
the maximum baud rate of your BBS. Callers connecting
at baud rates less than the rate configured here will
be shown SF2SLOW.BBS and the caller will be logged off
the system. This is a variable option, and can be set
to disallow callers with a baud rate of 65535 or less.
Command <L> Sets the break length for each tilde found in the
modem initialization string. If the break length is
set at 500, each time SPITFIRE finds a tilde symbol
in the modem initialization string, it will pause for
1/2 second.
Command <M> When this option is toggled to Yes, SPITFIRE will
disconnect the caller and place the modem in command
state by lowering the DTR. When set to No, SPITFIRE
places the modem in command state by sending the escape
code (ASCII 001) three times to the modem, requiring
the modem's S2 register to be set to 1. It is
recommended that this toggle be set to Yes.
Command <1> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM port 1. IRQ4 is standard for COM1.
Valid options are 1 through 15.
Command <2> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM port 2. IRQ3 is standard for COM2.
Valid options are 1 through 15.
Command <3> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM port 3. IRQ4 is standard for COM3.
Valid options are 1 through 15.
Command <4> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM port 4. IRQ3 is standard for COM4.
Valid options are 1 through 15.
Command <5> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM Port 5. Valid options are 1 through 15.
Command <6> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM Port 6. Valid options are 1 through 15.
Command <7> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM Port 7. Valid options are 1 through 15.
Command <8> Allows the Sysop to configure the IRQ SPITFIRE will
use for COM Port 8. Valid options are 1 through 15.
Command <F1> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 1. 03F8 is standard for COM1.
Command <F2> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 2. 02F8 is standard for COM2.
Command <F3> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 3. 03F8 is standard for COM3.
Command <F4> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 4. 02F8 is standard for COM4.
Command <F5> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 5.
Command <F6> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 6.
Command <F7> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 7.
Command <F8> Allows the Sysop to configure the base address SPITFIRE
will use for COM port 8.
3.2 - SPITFIRE CONFIGURATION
----------------------------
The SPITFIRE Configuration Window allows the Sysop to configure
a variety of system options for their BBS. At the "SPITFIRE ready for
use" prompt, press ALT+Z. The ALT+Z keystroke combination opens the
SPITFIRE Configuration window. The commands that you will see are
listed below:
--< SPITFIRE CONFIGURATION >--
<A> Sysop Caller Name............ : Sysop
<B> Sysop Name................... : John Doe
<C> Drop to DOS Password......... : ***********************
<D> BBS Starting Date............ : July 15, 1999
<E> Daily Time Limit............. : 60
<F> Log On Time Limit............ : 60
<G> Maximum Callers In Database.. : 500
<H> Maximum Caller Daily Access.. : 10
<I> # Of Callers................. : 1
<J> # Of File Description Lines.. : 20
<K> Upload Time Compensation..... : 1.000 <1> Expired Security... : 0
<L> New Caller Security.......... : 10 <2> Expiration Warning. : 0
<M> New Caller Log On Time....... : 45 <3> Sysop Security..... : 50
<N> No Activity Time Limit....... : 3 <4> Node Chat Drive.... : E
<O> Node Number.................. : 2 <5> Default ANSI Color. : 32
<P> Private BBS Security Level... : 0
<R> Total Number Of Nodes........ : 3
<S> U/D Ratio Violation Security. : 25
<T> Upload Disk Space Requirement : 100K
ENTER COMMAND [<Q>... Quit]:
Command <A> Use this command to enter or change the Sysop Caller
Name.
Command <B> Allows you to change the Sysop name. This is the name
callers will see credited as the Sysop of the BBS.
Command <C> Sets the password that is needed to drop to DOS from
a remote location. The default is a blank line. To
use this feature, 'a drop to DOS' password must be
configured. The configured password is disguised by
asterisks, and is never visible. Should you forget
the drop to DOS password, it can be reconfigured.
Command <D> This command sets the starting date of your bulletin
board. If you are already running an established
board, you can enter the original starting date of
your BBS rather than the date of your conversion to
SPITFIRE.
Command <E> Sets the amount of time per day a caller is allowed on
the board. Refer to the section on SPITFIRE FILE
CLARIFICATION in this manual for more information on
setting daily time limits in SPITFIRE's DAILYLMT.DAT.
Command <F> Sets the amount of time allowed per call for each
caller. Refer to the section on SPITFIRE FILE
CLARIFICATION in this manual for more information on
setting daily time limits in SPITFIRE's DAILYLMT.DAT.
Command <G> Determines the number of callers you will allow to
utilize your BBS. (i.e. - If this value is set
at 500 and you already have 500 callers and a new
caller (501) tries to log on, the system displays the
file MAXUSERS.[BCR], if it exists, and logs the caller
off the BBS.)
Command <H> This option limits how many times a caller can call
the board each day. If this number is exceeded, the
system will display TOOMANY.[BCR], if it exists, and
log the caller off the BBS.
Command <I> This allows the Sysop to set the number of callers.
The purpose of this command is to allow Sysops already
running an established board to enter their current
number of callers, so as not to start the BBS with
Caller Number 1.
Command <J> Sets the number of descriptive lines callers can input
when uploading files to the BBS. Valid options are 1
through 20. If set to 1, only single-line descriptions
are allowed. Using 2 through 20 allows multi-line file
descriptions. If this option is set to allow multi-
line file descriptions, and a caller uploads a file
the entire multi-line description entered by the caller
is written to the CALLERS.LOG. Also, if the file is
uploaded for Sysop Only, the entire multi-line
description entered by the caller is written in the
HEYSYSOP.LOG.
If the ALT+T option, Uploaded By Description, is set to
Yes it will add 1 line to the description crediting the
caller who uploaded the file. So even if this option
is set to 1, if the ALT+T's Uploaded By Description is
set to Yes multi-line file descriptions will result.
** NOTE ** If any SPITFIRE utility, such as SFCHKUP, uses the
file description contained in the file's FILE_ID.DIZ
to replace the description entered by the caller then
there is no limit to the number of descriptive lines
allowed by SPITFIRE.
Command <K> Sets the ratio for the amount of time a caller is
compensated in relation to the amount of time spent
uploading. SPITFIRE defaults to 1.000. If you wish
to reward the caller with additional time for uploads,
increase this numeric value. For instance, if this is
set at 2.000 and a caller spends 10 minutes uploading,
the caller is compensated 20 minutes after the upload
is completed.
Command <L> Sets the default security level for a new caller.
Command <M> Sets the amount of time a new caller is allowed on the
BBS. (First day only)
Command <N> Sets the amount of time a caller can remain inactive
(no keyboard input) before being automatically logged
off the BBS.
Command <O> Sets the Node Number for this particular node of the
BBS. If you are not operating a multi-node system,
this should be set to 1. If you are operating a
multi-node BBS, the node number entered here should
correspond to the appropriate node number. In other
words, the second node should be set to 2, the third
node to 3, etc. SPITFIRE supports up to 255 nodes.
Command <P> This command sets the security required to access the
BBS if the BBS has been toggled to be a private BBS.
If a caller attempts to log on the BBS and does not
have a security equal to or greater than what the
Sysop has set here, the display file, PRIVATE.[BCR],
if it exists, is displayed to the caller, and the
caller is logged off the BBS. Multi-node systems
should set this option for each individual node.
Command <R> Sets the total number of nodes available on your
system. For single node systems, a 1 is entered,
and for multi-node systems, it would be equivalent
to the total number of nodes supported in your system
setup. SPITFIRE supports up to 255 nodes.
Command <S> Specifies the security level that a caller will be
changed to if the upload/download ratio is violated.
SPITFIRE's DAILYLMT.DAT file defines parameters for
determining if and when a caller's security is
adjusted for violating the upload/download ratio. The
DAILYLMT.DAT file must define a VWR (Violation Warning
Ratio) and a VER (Violation Enforcement Ratio). The
VWR and VER should be defined for each security level
on the BBS for which the Sysop desires to monitor
upload/download requirements. (Refer to the section -
SPITFIRE FILE CLARIFICATIONS - for further information
on SPITFIRE's DAILYLMT.DAT.)
If SPITFIRE finds the VWR and VER is defined for the
security level of the caller, each time a file is
downloaded, SPITFIRE performs the following
calculations to determine if a caller has violated
the upload/download ratio requirement:
The number of files downloaded by a caller is divided
by the number of files uploaded AND the number of
kilobytes downloaded by the caller is divided by the
number of kilobytes uploaded by the caller. SPITFIRE
must verify that both the file ratio, and the kilobyte
ratio have been violated. If the results of both the
file, and kilobyte calculation are greater than the
value defined for the VER (Violation Enforcement
Ratio), SPITFIRE will then alter the caller's security
level to that configured here at the U/D Ratio
Violation Security.
** NOTE ** SPITFIRE will return the caller to their original
security once the caller's upload/download ratio is
again within the required ratio limits. SPITFIRE's
SFUSERS.DAT file contains a field which stores
information regarding the caller's original security
level. When a caller uploads a file to the BBS,
SPITFIRE first checks to see if the caller's current
security level is less than their original security.
If so, SPITFIRE performs the same computations as
described above. If the results of the file or
kilobyte calculation is less than the VER (Violation
Enforcement Ratio), the caller's original security
level is restored. Keep in mind, for this to work
properly, the VER (Violation Enforcement Ratio) must
be configured the same for both security levels, the
security that is being monitored and the U/D Ratio
Violation Security entered here.
Command <T> Allows the Sysop to configure the amount of disk
space which must be available on the upload drive
before a caller will be allowed to perform an upload.
The default is 100K.
Command <1> Defines the security level a caller will be returned
to in the event their subscription to the BBS should
expire. When a caller logs on and the caller's
subscription has expired, then SPITFIRE will
display SFSUBCHG.[BCR] and will alter the caller's
security level to this pre-determined level. At the
time a caller's security level is altered, SPITFIRE
records the event in the CALLERS.LOG. If you do not
intend to use the subscription features of SPITFIRE,
simply set this value to 0.
Command <2> Allows the Sysop to configure the number of days
prior to a caller's subscription expiring that the
caller will be warned. SPITFIRE uses the number of
days entered here in conjunction with the subscription
date (date the subscription will expire which is
maintained in the caller's record) to warn the caller
of the impending subscription expiration. SPITFIRE
displays SUBWARN.[BCR] to warn the caller of the
approaching subscription expiration. SPITFIRE also
records that the warning was issued to the caller in
the CALLERS.LOG. If you do not intend to use the
subscription features of SPITFIRE, simply set this
value to 0.
Command <3> Sets the Sysop security level. Any caller with an
access equal to or greater than this value can read
all messages (public and non-public), undelete
messages, delete any message, copy a message and
overwrite existing files when uploading (the filename
already exists) as well as being able to perform other
functions not available to callers with a security
level less than what is configured here.
Command <4> Specifies the drive letter which will be used to read
and write the node chat file. Due to the constant
access required of this file during the process of a
node chat, it is highly recommended that a RAM drive
be created for use as the node chat drive.
DOS comes with the necessary software to create a
RAM drive. Refer to your DOS manual for instructions
on creating a RAM drive.
Command <5> This option allows the Sysop to set the default ANSI
color that will be used for new callers to the BBS.
Valid options are 31 through 36. The colors
associated with the numeric value are 31 Red, 32 Green,
33 Yellow, 34 Blue, 35 Magenta, 36 Cyan, and 37 White.
After completing your SPITFIRE Configuration, enter <Q> to Quit
and the "Ready..." prompt is displayed.
3.3 - TOGGLE SPITFIRE SWITCHES
------------------------------
The Toggle SPITFIRE Switches allows the Sysop to toggle the
availability of specific SPITFIRE features when configuring their
BBS. The Toggle SPITFIRE Switches window is opened by pressing ALT+T
at the SPITFIRE ready prompt. A window opens up to display the
following configuration options:
-----< Toggle SPITFIRE Switches >-----
<A> US Phone Number Style......... : On <1> Mandatory Msg Scan..... : On
<B> Log On - Message Statistics... : On <2> Use RIP Command Lines.. : No
<C> Log On - New File Statistics.. : On
<D> Require New Caller Birthdate.. : Yes
<E> New Caller Default Protocol... : Yes
<F> File Description Conversion... : On
<G> Type Of BBS................... : Public BBS
<H> ANSI Graphics................. : Ansi Available
<I> Second Password............... : One Password
<J> Direct Screen Writes.......... : Yes
<K> Uploaded By Description....... : Yes
<L> Password Failure Comment...... : No
<M> Require Door Return Password.. : No
<N> Scan All Msg Conferences...... : Yes
<O> Comprehensive Upload Search... : On
<P> Color Monitor................. : Yes
<R> RIP Graphics.................. : Yes
<S> Search CD Rom Area SFFILES.... : No
<T> Test Files Upon Boot.......... : Yes
<U> Use International Characters.. : No
Enter Command <<Q>... Quit>:
Command <A> Allows the Sysop to configure whether the BBS will
use the US phone number format (###-###-####) or
allow SPITFIRE to accept any 12 character string
entered by the caller. SPITFIRE defaults to the US
Phone Number Style set to On.
Command <B> This feature enables the Sysop to determine whether
callers will be prompted with their message statistics
when logging on the BBS. If this is set On, the
caller is notified upon log on of any new messages,
number of received messages, messages sent by the
caller and total number of messages on the BBS.
SPITFIRE's default is On.
Command <C> Allows the Sysop to designate whether callers are
prompted with new file statistics when logging on. If
this is set to On and the caller elects to view new
files, a list of all new files will be displayed to
the caller. Additionally, SPITFIRE informs callers of
the number of new files since last checked, as well as
the total downloadable files and bytes available on
the system. SPITFIRE's default is On. SPITFIRE will
not check for new files or report file statistics on a
file area that is configured as a CD-ROM file area.
When toggled On, the caller may tag files from the
new files listing for download. After the list has
finished displaying, and if the caller has tagged
files for download, SPITFIRE will prompt the caller as
to whether to begin the file download process. If the
caller responds with a "Y", SPITFIRE will then prompt
the caller as to whether he/she would like to be
logged off after the download is completed. If the
caller responds with a "Y", when the download is
completed, the caller is automatically logged off
the BBS. In such an instance, it is possible for
a caller to log on the BBS, perform a file download
and log off the BBS without ever reaching the Main
Menu of the BBS.
Command <D> Designates whether a new caller logging onto the
BBS for the first time is required to enter their
date of birth. If toggled to Yes, the birthdate is
required. If toggled to No, the caller is not
prompted to enter their date of birth.
If Second Password option is toggled to Second
Password Required, and the Require New Caller
Birthdate is changed to No, SPITFIRE will
automatically change the Second Password option to
One Password.
**NOTE** SPITFIRE uses a caller's date of birth as the second
password, when required. It is not possible to
require a second password if the BBS does not
require the caller to enter their date of birth.
Command <E> This feature determines if a new caller logging onto
the BBS is allowed to select a default file transfer
protocol after answering the new caller questionnaire.
If toggled to Yes, the new caller is automatically
presented with this option. If this feature is set
to Off, the new caller is not automatically presented
with this option, but may still select a default file
transfer protocol from the <Y>our Statistics option
of the Main Menu.
Command <F> Toggles SPITFIRE's File Description Conversion On
and Off. When toggled On, SPITFIRE automatically
converts the first character of each word in the file
description entered by the caller to upper case. All
other characters will be lower case. The exception
to this would be any words which SPITFIRE finds in
SFUPCASE.DAT (in the Work File Path). Any words the
Sysop places in SFUPCASE.DAT are converted to all
upper case characters, i.e., BBS, SPITFIRE, COM, ZIP,
etc. If toggled Off, SPITFIRE makes no attempt to
alter the description entered by the caller. SPITFIRE
defaults to setting this On.
*** NOTE *** When using SFCHKUP or similar utilities
to replace the file description entered by the caller
with the FILE_ID.DIZ text, regardless of the File
Description Conversion toggle, SPITFIRE will not alter
the imported FILE_ID.DIZ description.
Command <G> Toggles the BBS as a Private or Public system. If you
toggle this as a Private BBS, then the caller's name
must be found in the callers file and the caller's
security must be equal to or greater than that
configured for option <R> Private BBS Security Level
at the ALT+Z configuration screen prior to the caller
being granted access.
If the caller's name is found in the caller data base
but the caller's security is not equal to or greater
than the configured Private BBS Security Level, then
PRIVATE.[BCR], if it exists, is displayed to the
caller and the caller is logged off the BBS.
Command <H> Toggles ANSI graphics On or Off. If you wish to offer
ANSI graphics, you must create .CLR files to match the
display .BBS files you have, (i.e., ALL.BBS {non-ANSI}
and ALL.CLR {ANSI Graphics}). In order for you to see
the ANSI Graphics locally, DEVICE=ANSI.SYS must exist
in your CONFIG.SYS file.
Command <I> Toggles password prompt. If toggled to One Password,
the caller simply enters their password. If toggled
to Second Password Required, after entering the
first password, the system prompts the caller for
their birth date. Should the caller not know their
birth date, the system logs them off.
**NOTE** If the BBS is configured not to require a caller to
enter their date of birth when logging onto the BBS
the first time, SPITFIRE automatically sets this
option to One Password, if it is not already. The
Second Password Required is only available when
callers are required to enter their birth date.
Command <J> Toggles the Direct Screen Write feature on and off.
If you are running SPITFIRE in a multi-tasking
environment, you will want to set this to No to
disable direct screen writing. Otherwise, set this
to Yes because using direct screen writes increases
the speed of the display.
Command <K> Toggles whether a line is added to the file
description crediting the caller who uploaded the
file. The line, "Uploaded By <Caller's Name>" will
appear as the last line of the file description if
this is set to Yes. If set to No, no information
referencing the uploader will appear in the file
description.
Command <L> Toggles whether a caller who is unable to enter
their password may leave a Comment To The Sysop. If
toggled to "No", the caller is not prompted for a
comment. When toggled to "Yes", the caller is given
the option of leaving a comment to the Sysop before
being logged off the BBS.
Command <M> Toggles whether the BBS requires a caller to enter
their passwords when returning to SPITFIRE from the
door section of the BBS. If toggled to No, entering
their password is not required when returning from a
door.
Command <N> This feature allows Sysops to designate the message
scan parameters. When set to Yes, all message
conferences are included in the scan. When set to No,
only messages in the caller's queued conferences are
scanned. This affects both the log on message scan
and the scan performed when selecting <Y>...Your
Messages option from the Message Menu.
Command <O> This feature provides Sysops the option of configuring
whether the system will take advantage of SPITFIRE's
comprehensive file search when a caller attempts an
upload. If toggled Off, SPITFIRE searches for exact
matches. If a match is found, the caller is informed
that the file already exists on the BBS. When toggled
On, SPITFIRE trims any trailing digits from the file
name during the search, replacing the numeric values
with the '*' wildcard. For instance, if a caller
attempts to upload SF35.ZIP, SPITFIRE would search for
SF*.ZIP. SPITFIRE will report individually each
SF*.ZIP file it finds on the BBS and prompt the caller
as to whether they still wish to continue with the
upload.
**NOTE** The Comprehensive Upload Search does not prevent
callers from uploading the file. This feature is
meant only to make the callers aware that another
version of this file already exists on the BBS.
Hopefully the majority of callers are responsible
enough not to upload older versions of existing files,
but rather only the more current, updated versions.
Command <P> This feature allows the Sysop to toggle whether or
not the monitor used for the BBS is a color monitor.
Command <R> Allows the Sysop to configure whether RIP Graphics
will be made available to callers of the BBS. If
toggled to Yes, when a caller logs on the BBS,
SPITFIRE will test to determine if the caller is using
a RIP terminal program. If the caller is not using a
RIP terminal communications program the caller is
prompted with: "Do You Want ANSI Graphics? <y/N>".
If the caller is using a RIP terminal program, the
caller is prompted to select one of the following
graphic formats: <A>nsi, <R>ip, or <N>one. If RIP
Graphics is selected, *.RIP display files will be
displayed to the caller, if found.
Command <S> Toggles whether a File Area configured as a CD-Rom
Area (refer to the section, Configuring File Area
Records) will search SFFILES.<x> during file searches
rather than the CD-Rom drive. This option provides
the Sysop the capability of configuring SPITFIRE to
work with a CD-Rom in the most efficient manner. If
it is faster to search the CD-Rom drive, then toggle
this option to No. However, if it is faster to search
the SFFILES.<x>, then toggle this option to Yes.
Command <T> Toggles whether SPITFIRE tests the various message
base files to assure that the files are in working
condition. If toggled On, when SPITFIRE is booted
the message base files are tested. If toggled Off,
no tests are performed. Sysops with numerous message
conferences may wish to toggle this Off to speed
the boot process. SPITFIRE defaults to On and this
setting is recommended to ensure file integrity.
Command <U> Allows the Sysop to configure whether to allow
keyboard input of non-English characters, with
an ASCII value of 128 to 175. These characters
are used in countries outside the United States.
Command <1> Allows the Sysop to configure whether SPITFIRE will
perform the message base scan when a caller logs on
the BBS. When toggled On SPITFIRE will automatically
scan the message base for new messages the first time
a caller logs onto the BBS each day. If the caller
makes additional calls to the BBS that day, then the
message base scan will be optional. If toggled Off,
the caller will be prompted as to whether he/she
would like to review the BBS message statistics.
Command <2> Toggles whether the SPITFIRE command lines will be
displayed to callers logging onto the BBS using the
RIP Graphic format. If toggled to Yes, SPITFIRE will
display the menu command lines after the RIP menus are
displayed. If toggled to No, SPITFIRE's menu command
lines will not be displayed after the RIP menus are
displayed.
3.4 - CONFIGURING SPITFIRE FILE PATHS
-------------------------------------
When setting up a SPITFIRE BBS for the first time, SPITFIRE
automatically creates the default file paths. SPITFIRE will place any
file which it creates in the appropriate file path. If you wish to
modify these settings, you may do so by pressing ALT+P at the SPITFIRE
"Ready..." prompt. Pressing ALT+P opens the SPITFIRE File Path window
which allows the Sysop to configure the file paths that will be used
when running SPITFIRE.
--<SPITFIRE FILE PATHS>--
<A> Work Files Path..................: C:\SF\WORK
<B> Message Files Path...............: C:\SF\MESSAGE
<C> Display Files Path...............: C:\SF\DISPLAY
<D> External Transfer Path...........: C:\SF\EXTNOD1
ENTER COMMAND <<Q>...Quit> :
An explanation of each command is listed below:
Command <A> Specifies the directory in which the SPITFIRE Work
Files reside. (For more information on this refer
to the section FILE PATHS in this manual.) All files
belonging in the Work File Path are specified as such
with a (WORK) in the file description in the section -
SPITFIRE WORK FILES.
Command <B> Allows you to specify the directory in which the
SPITFIRE Message Files will reside. All files
belonging in the Message File Path are specified
as such with a (MESSAGE) in the file description in
the section - SPITFIRE MESSAGE FILES.
Command <C> Specifies the directory in which the SPITFIRE Display
Files reside. All files with a BBS, CLR or RIP
extension are Display Files and should reside in the
directory you designate here. (For more information
refer to the section on FILE PATHS in this manual.)
All files belonging in the Display File Path are
specified as such with a (DISPLAY) in the file
description in the section - SPITFIRE DISPLAY FILES.
Command <D> Allows you to specify the directory from which you
opt to run the SPITFIRE External Transfer Protocols.
All files which you are using to run the External
Transfer Protocols must reside in the directory you
designate here. (For more information refer to the
section - EXTERNAL FILE TRANSFER PROTOCOLS of this
manual.)
Establishing specified file paths provides Sysops with more
manageable directories. However, if the Sysop prefers, all files can
be accessed from the SF directory. Simply enter C:\SF in response to
each of the above file path questions.
After you've configured SPITFIRE to meet your specifications,
Quit and return to the "SPITFIRE ready for use..." prompt. The next
thing to be concerned about when setting up a SPITFIRE BBS is
configuring your system records.