home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware 1 2 the Maxx
/
sw_1.zip
/
sw_1
/
BBS
/
SF32_2.ZIP
/
SF32DOC.ZIP
/
SPITFIRE.DOC
Wrap
Text File
|
1992-03-20
|
499KB
|
8,950 lines
_________________________________________________________________________
___________________ ___________________
________________ S P I T F I R E ________________
_____________ ------------------------- _____________
__________ Bulletin Board System __________
_______ for MS/PC DOS _______
____ Personal Computers ____
_______________________________
____ ____
____ Version 3.2 ____
___________________
Copyright (C) 1987-1992 by Mike Woltz
-------------------------------------
Buffalo Creek Software
A Member Of
The Association Of Shareware Professionals
------------------------------------------
>>> Release Date March 20, 1992 <<<
------------------------------------------
TABLE OF CONTENTS
---------------------
# Section Title Page #
+--+------------------------------------------------+------+
Introduction.......................................... 1
<1> 1.0 Important Notice................................. 1
1.1 Copyright & Registered Trademark Notice.......... 2
<2> 2.0 SPITFIRE Hardware Requirements................... 3
2.1 Modems........................................... 4
2.2 Modem Initialization............................. 5
<3> 3.0 Getting Started.................................. 6
<4> 4.0 SPITFIRE File Paths............................. 19
4.1 SPITFIRE System Files........................... 20
4.2 SPITFIRE Work Files............................. 22
4.3 SPITFIRE Message Files.......................... 23
4.4 SPITFIRE Display Files.......................... 24
4.5 SPITFIRE Menu Files............................. 28
4.6 SPITFIRE File Clarifications.................... 31
4.7 About SPITFIRE Display Files.................... 39
4.8 Backup Files.................................... 40
4.9 THOUGHTS.BBS.................................... 41
<5> 5.0 Command Line Parameters......................... 41
5.1 SF.BAT.......................................... 42
<6> 6.0 Setting Up the System Records................... 43
6.1 Configuring Message Conference Records.......... 43
6.2 Configuring File Area Records................... 48
<7> 7.0 SPITFIRE Questionnaires......................... 52
<8> 8.0 Special Function Keys........................... 56
8.1 Available Special Function Keys................. 56
8.2 Special Function Key Definitions................ 57
<9> 9.0 Main Section Explained.......................... 69
9.1 Main Menu Example............................... 69
9.2 Explanation of Main Menu Features............... 70
<10> 10.0 Message Section Explained....................... 75
10.1 Message Menu Example............................ 75
10.2 Message Menu Explanation........................ 75
<11> 11.0 File Section Explained.......................... 83
11.1 File Menu Example............................... 84
11.2 File Menu Explanation........................... 84
11.3 Upload/Download Protocols....................... 92
11.4 Batch Download Menu............................. 92
11.5 Batch Upload Menu............................... 94
<12> 12.0 Sysop Section Explained......................... 96
12.1 Sysop Menu Explanation.......................... 96
TABLE OF CONTENTS (cont)
------------------------
# Section Title Page #
+--+------------------------------------------------+------+
<13> 13.0 Special Commands for Sysop Status.............. 100
13.1 Special Commands for Sysop..................... 101
<14> 14.0 Events Menu Example............................ 101
14.1 Events Menu Explanation........................ 102
<15> 15.0 Hardware/Software Data Flow Control............ 106
<16> 16.0 Screen Save Features........................... 106
<17> 17.0 SPITFIRE Doors Section......................... 106
17.1 SPITFIRE Doors Display Files................... 109
17.2 SPITFIRE Doors Support......................... 110
<18> 18.0 External File Transfer Protocols............... 110
18.1 External Download Protocols.................... 111
18.2 External Batch Download Protocols.............. 113
18.3 Text File External Batch Download Protocols.... 115
18.4 External Upload Protocols...................... 116
18.5 External Batch Upload Protocols................ 119
18.6 External Protocol Support...................... 120
<19> 19.0 SPITFIRE Utilizes EMS.......................... 121
<20> 20.0 SPITFIRE Net-Mail Capabilities................. 121
<21> 21.0 Operating A Multi-Node SPITFIRE................ 122
21.1 System Requirements............................ 122
21.2 SPITFIRE Configuration......................... 123
21.3 Features Unique To Multi-Node Operation........ 123
21.4 SPITFIRE Node Chat............................. 124
<22> 22.0 SPITFIRE Multi-Tasking/Network Environment..... 127
22.1 SPITFIRE With Windows 3.0...................... 127
22.2 SPITFIRE With DESQview......................... 129
22.3 SPITFIRE With LANtastic Network................ 131
<23> 23.0 SPITFIRE Companion Program..................... 133
23.1 DAILYLMT....................................... 134
23.2 SFDOOR......................................... 134
23.3 SFSENDIT....................................... 134
<24> 24.0 SPITFIRE Technical Reference Information....... 135
<25> 25.0 Comment from the Author........................ 142
Appendix A Modem Initialization Strings................... 145
Appendix B SPITFIRE Questions and Answers................. 149
Subject Index............................................. 157
Page 1
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
INTRODUCTION
------------
SPITFIRE is a bulletin board program written in Borland's Turbo
Pascal and interfaced with assembler code compiled by Borland's Turbo
Assembler. Designed on an IBM Personal Computer, SPITFIRE is
compatible with MS/PC DOS machines (IBM "Compatibles").
SPITFIRE is distributed under the "Shareware" concept. You are
encouraged to distribute this software to others, in its original,
unmodified condition, as long as you DO NOT charge for this program
in any way, shape or form.
1.0 - IMPORTANT NOTICE!
-----------------------
Thank you for taking the time and expense to obtain SPITFIRE.
Surely, after you've had a chance to look SPITFIRE over, you'll agree
it is a powerful bulletin board program which combines both speed,
flexibility and user ease.
This program, like many others, is distributed under the
"Shareware" concept. SPITFIRE can be utilized on a trial basis for
not more than 30 days or 500 callers, whichever comes first. In the
event SPITFIRE is used beyond the trial period, then a registration
fee of $85.00 in "U.S. FUNDS" is required. Please specify on your
registration form whether you wish to receive 5 1/4" disks or 3 1/2"
disks. If not specified, 5 1/4" disks will be sent. If you live
outside of the North American continent (countries other than Canada,
Mexico, the United States or provinces of the United States) an
addition $10 fee (i.e., $95.00) is required for postage and handling.
Your registration of SPITFIRE will provide you with support and
notification of future updates and revisions of SPITFIRE. Any portion
of or all such support and notification may be changed and/or
terminated at any time without notice.
Many of you will be running SPITFIRE 24 hours per day, 7 days per
week. This is more than any other program you'll use. Considering
that, it becomes apparent that the registration fee is truly minimal.
|--------------------------------------------------------------------|
| Registration is simple & easy. Send the registration fee to: |
|--------------------------------------------------------------------|
|-----------------------------|
| Buffalo Creek Software |
| Attention: Mike Woltz |
| 913 - 39th Street |
| West Des Moines, Iowa 50265 |
|-----------------------------|
Page 2
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +-
----------------------------------------------------------------------
Mike Woltz and/or Buffalo Creek Software shall in no way be held
responsible for any damage incurred while operating SPITFIRE. All
responsibility lies with the user of the software.
No part of this manual may be reproduced, transmitted, transcribed,
stored in a retrieval system, or translated into any language (natural
or computer), in any form or by any means, without the prior written
permission of Mike Woltz.
THIS SOFTWARE IS NOT FOR SALE! You are granted a limited license
to use the software described in this manual. The software may be used
or copied only in accordance with the terms set forth herein.
You may not make any changes or modifications to SPITFIRE, and you
may not de-compile, disassemble, or otherwise reverse-engineer it. You
may not rent or lease it to others.
No fee, charge or other compensation may be accepted or requested
by anyone without express written permission from Mike Woltz. This
includes disk vendors.
Operators of electronic bulletin board systems (Sysops) may post
SPITFIRE for downloading by their users without written permission
only as long as the conditions set forth herein are met. A fee may be
charged for access to the BBS as long as no specific fee is charged
for access to the SPITFIRE files.
Distributors of public domain and user supported software, such
as disk vending services, may distribute copies of SPITFIRE subject to
the above conditions only after obtaining written permission from Mike
Woltz.
1.1 - COPYRIGHT & REGISTERED TRADEMARK NOTICE
---------------------------------------------
SPITFIRE and affiliate programs distributed with it are not to be
modified or distributed in modified form without the express written
consent of Mike Woltz.
SPITFIRE is NOT to be sold, used or modified for, or with, illegal
intent under the penalty of law.
"SPITFIRE" is Copyright (C) 1987-1992 by Mike Woltz
"SPITFIRE" is a registered trademark of Buffalo Creek Software.
"Turbo Pascal" is a registered trademark of Borland International Corp.
Page 3
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
"BRK" is Copyright (C) 1985, by Solid Systems
"SEALINK" is Copyright (C) 1986 by System Enhancement Associates
"WILDFIRE" is Copyright (C) 1988, 89, 90, 91, 92 by Stephen L. Cox
"MUV" is Copyright (C) 1989, 90, 91, 92 by Buffalo Creek Software
"COLDBOOT" is Copyright (C) 1990, 91, 92 by Buffalo Creek Software
"DSZ" is Copyright (C) 1988, 89, 90, 91, 92 by Omen Technology, Inc.
"WINDOWS 3.0" is Copyright (C) 1990, 91, 92 by Microsoft
"DESQview 386" is Copyright (C) 1990, 91 by Quarterdeck Office Systems
"LANtastic" is Copyright (C) 1991 by Artisoft
"Doorway" is Copyright (C) 1987 through 1992 by Marshall Dudley
"Remdoor" is Copyright (C) 1989, 90, 91, 92 by Ken Brown
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> Minimum DOS v3.0
<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 or Message Menus
Page 4
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
then 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
rates. 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.
300 Baud - CONNECT
1200 Baud - CONNECT 1200
2400 Baud - CONNECT 2400
7200 Baud - CONNECT 7200
9600 Baud - CONNECT 9600
14400 Baud - CONNECT 14400
Error-correction modems
-----------------------
1200 Baud - CONNECT 1200/ARQ
2400 Baud - CONNECT 2400/ARQ
7200 Baud - CONNECT 7200/ARQ
9600 Baud - CONNECT 9600/ARQ
14400 Baud - CONNECT 14400/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. A list of modem initialization strings reported
to work with SPITFIRE can be found in Appendix A of this manual.
Page 5
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Mike Woltz and Buffalo Creek Software would like to express its
appreciation to US Robotics Inc., FASTCOMM COMMUNICATIONS CORP., and
Artisoft's LANtastic for their technical support and the use of their
products during the development of this version of SPITFIRE. Each of
these firms graciously provided evaluation products for testing with
SPITFIRE. These products have been proven to work flawlessly in
combination with SPITFIRE.
2.2 - MODEM INITIALIZATION
--------------------------
SPITFIRE automatically sends an "ATZ", pauses 1.5 seconds and then
sends the configured modem initialization string to the modem after
each caller. This procedure and SPITFIRE's default initialization
string (listed below) seems to work fine with most modems:
ATS0=0Q0V1E0M0H0S2=1X1
In the event you are using an USR HST and wish to run your BBS
at 19200 baud, the initialization string listed below works:
ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6
In the event you are using an 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
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 (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.
Page 6
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 need your favorite 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 /I2400 /C1.
"/I2400" indicates the top speed of your modem. You may need
to modify this to reflect the highest speed your modem is
capable of. (For example: If you have a 9600 baud modem,
change the string to read "SPITFIRE /I9600 /C1" or "SPITFIRE
/I19200 /C1"). "/C1" indicates the COMM port you are using.
In the event you are using COMM port 2, you need to change
the string to read "SPITFIRE /I2400 /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 /I2400 /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 one. Subsequently, SPITFIRE
provides similar prompts for other required files. These
include:
SFNODE.DAT
SFUSERS.DAT
SFFAREA.DAT
SFMCONF.DAT
Page 7
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 COMM port. If this happens, you will
get a message that states "COMM Port Number <x> (where <x> is
the number of the COMM Port) is not responding! SPITFIRE
halting!" If you see this message, refer to step number 2 in
this Section. If the COMM 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 as Sysop of
the system. You should 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 birthdate. SPITFIRE uses
these responses 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 #5 of this section 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.
<5> At the "SPITFIRE ready for use..." prompt you may view
or modify your modem configuration by pressing ALT+M.
Page 8
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
These keystrokes open SPITFIRE's Modem Configuration window.
The commands that you will see are listed below:
--< SPITFIRE NODE 1 MODEM CONFIGURATION >--
<S> Serial Port Number................: 1
<B> System Baud Rate..................: 19200
<I> Initialization String.............:
ATS0=0&B1&N0&H1&R2&Y3Q0V1E0M0H0S2=1X1
<M> Modem - Error Correction Type.....: Yes <1> Line COM1..: IRQ4
<E> Error Correction Message..........: ARQ <2> Line COM2..: IRQ3
<H> Hardware Data Flow Control........: Yes <3> Line COM3..: IRQ4
<A> Answer On What Ring...............: 1 <4> Line COM4..: IRQ3
<D> Display Result Messages...........: On
<C> Disconnect Delay..................: 28
<U> Use High Speed Async Routines.....: Yes
<R> Baud Rate Requirement.............: 1200
<L> Break Length..(1000=1 Second).....: 0
Enter Command or <Q>uit -
Command <S> Specifies the COMM Port being utilized by this node.
Command <B> Defines the maximum baud rate allowed by this node.
Command <I> Sets the modem initialization string appropriate for
your modem.
Command <M> Specifies whether the modem is an error correction
modem. The modem manual should provide information as
to whether it has error correction capabilities.
Press <M> to toggle this from Yes to No and vice
versa.
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, provided
it has error checking capabilities.
Command <H> Toggle the Hardware Data Flow Control between Yes and
No. For more information on this, refer to the
section - HARDWARE/SOFTWARE DATA FLOW CONTROL - of
this manual.
Command <A> Specifies on what ring SPITFIRE will answer incoming
calls. For instance, with 1, SPITFIRE answers the
Page 9
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 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 their own data buffer. The Sysop
can 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. The
SPITFIRE default for this is 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 for access to
your BBS. For instance, if this is 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 that specified 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 <1> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 1. IRQ4 is standard for COM1.
Valid options are 1 through 7.
Command <2> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 2. IRQ3 is standard for COM2.
Valid options are 1 through 7.
Command <3> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 3. Valid options are 1 through 7.
Page 10
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <4> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 4. Valid options are 1 through 7.
<6> At the "SPITFIRE ready for use" prompt, press ALT+Z.
Pressing ALT+Z opens the window which allows you to
configure SPITFIRE. The commands that you will see
are listed below:
--< SPITFIRE CONFIGURATION >--
<A> Sysop Caller Name.............: Sysop
<B> Sysop Security................: 50
<C> New Caller Security...........: 10
<D> New Caller Log On Time........: 45
<E> No Activity Time Limit........: 3
<F> Daily Time Limit..............: 60
<G> Log On Time Limit.............: 60
<H> Maximum Callers In Database...: 500
<I> Maximum Caller Daily Access...: 10
<J> # Of Callers..................: 1
<K> # Of File Description Lines...: 2
<L> Upload Time Compensation......: 1.000
<M> Drop to DOS Password..........: ***********************
<N> BBS Starting Date.............: March 20, 1992
<O> Sysop Name....................: John Doe
<P> Node Number...................: 2
<R> Private BBS Security Level....: 0
<S> Total Number Of Nodes.........: 3
<T> U/D Ratio Violation Security..: 9
ENTER COMMAND [<Q>... Quit]:
Command <A> Use this command to enter or change the Sysop Caller
Name.
Command <B> Sets the Sysop security level. Any caller with an
access equal to or greater than this numeric 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 this numeric value.
Command <C> Sets the default security level for a new caller.
Command <D> Sets the amount of time a new caller is allowed on the
BBS. (First day only)
Command <E> Sets the amount of time a caller can remain inactive
(no keyboard input) before being automatically logged
off the BBS.
Page 11
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <F> 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 <G> 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 <H> Determines the number of callers you will allow to
utilize your BBS. (i.e. - If you have this value set
at 500 and you already have 500 callers and a new
caller (501) tries to log on, the system displays the
file MAXUSERS.BBS and logs the caller off.)
Command <I> This command limits how many times a caller can call
the board each day. If this amount is exceeded, the
system will display TOOMANY.BBS and log the caller
off.
Command <J> This allows the Sysop to set the number of callers.
The reason for this command is if you are already
running an established board, you can enter the
current number of callers, so as not to start the BBS
with Caller Number 1.
Command <K> Sets the number of descriptive lines callers can input
when uploading files to the BBS. Valid options are 1
through 4. If set to 1, only single-line descriptions
are allowed. Using 2, 3, or 4 allows multi-line file
descriptions. If this option is set to allow multi-
line file descriptions and a caller uploads a file for
Sysop Only, the entire multi-line description is
written in the HEYSYSOP.LOG. If the ALT+T option
K, Uploaded By Description, is set to Yes it will
add 1 line to the description crediting the uploader.
So even if this option is set to 1, if the ALT+T
option K is set to Yes multi-line file descriptions
will result.
Command <L> Sets the time compensation for time used during an
upload. SPITFIRE defaults to 1.000. If you wish to
reward the caller with additional time for uploads,
increase this numeric value.
Command <M> 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
Page 12
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 <N> 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 <O> Allows you to change the Sysop name. This is the name
callers will see credited as the Sysop of the BBS.
Command <P> 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 set should correspond
to the appropriate node number. In other words, the
second node should be set to 2, the third node set to
3, etc. SPITFIRE supports up 255 nodes.
Command <R> 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.BBS/CLR,
if it exists, is displayed and the caller is logged
off the BBS. Those using multi-node systems should
set this individually for each node.
Command <S> 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 <T> 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.)
Page 13
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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.
After setting your configuration for SPITFIRE enter <Q> to Quit
and the "Ready..." prompt is displayed.
<7> Pressing ALT+T (from the SPITFIRE ready prompt) allows you
to configure the SPITFIRE toggle switches. A window opens
up to display the following configuration options:
-----< Toggle SPITFIRE Switches >-----
<A> US Phone Number Style..........: On
<B> Log On - Message Statistics....: On
<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> Graphics.......................: Ansi Available
Page 14
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<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> Test Files Upon Boot...........: Yes
Enter Command <<Q>... Quit>:
Command <A> This allows the Sysop to set 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 it,
all new files will be listed. Additionally, SPITFIRE
informs callers of the number of new files since the
last check and 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.
Command <D> Designates whether a new caller logging onto the
BBS for the first time is required to enter their
birthdate. If toggled to Yes, the birthdate is
required. If toggled to No, the caller is not
prompted to enter their birthdate.
If Command <I>, Second Password, is toggled to
Second Password Required, and the Require New Caller
Birthdate is changed to No, SPITFIRE will
automatically change Command <I> to One Password.
Page 15
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
**NOTE** SPITFIRE uses a caller's birthdate as the second
password, when required. It is impossible to
require a second password if the BBS does not
require the caller to enter their birthdate.
Command <E> This feature determines if a new caller logging on
the BBS can select a default file transfer protocol
after completing the new caller questionnaire. If
this is toggled to Yes, the new caller is presented
this option. If this feature is set Off, the new
caller is not automatically presented with this
option, but may still select a default file transfer
protocol from the <Y>...Your 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 to uppercase. All other characters
will be lower case. The exception to this is any
words the Sysop includes in SFUPCASE.DAT (in the
Work File Path). These words are converted to all
uppercase characters, i.e., BBS, SPITFIRE, COMM, ZIP,
etc. If toggled Off, SPITFIRE makes no attempt to
alter the description entered by the caller.
SPITFIRE's default is On.
Command <G> Toggles the BBS to 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 being
granted access. If you have the system toggled as a
Private BBS and a caller tries to log on as new caller,
then SPITFIRE displays NEWUSER.BBS/CLR (if found) and
has the new caller answer the new caller questionnaire
(if found). After the questionnaire is answered,
SPITFIRE displays PRIVATE.BBS/CLR (if found) and logs
the caller off. A note is left in HEYSYSOP.LOG to
advise the Sysop that a new caller attempted to log on.
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}
& ALL.CLR {ANSI Graphics}). In order for you to see
the ANSI Graphics locally, DEVICE=ANSI.SYS must exist
in your CONFIG.SYS file.
Page 16
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 birthdate when logging on to 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 on the last line of the file description if
this is set to Yes. If set to No, the file
description appears as entered by the caller with
no information referencing the uploader.
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.
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
Message option from the Message Menu.
Page 17
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <O> This feature provides Sysops the option of configuring
whether the system will take advantage of SPITFIRE's
comprehensive file search when callers attempt an
upload. If toggled Off, SPITFIRE searches for exact
matches. If a match is found, the callers are
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 attempted to upload SF32.ZIP, SPITFIRE
would then search for SF*.ZIP. SPITFIRE would report
individually all SF*.ZIP files it found on the BBS
and prompt the caller as to whether they still wished
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> 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.
<8> When setting up a SPITFIRE BBS for the first time, SPITFIRE
automatically creates the default file paths:
--<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> :
SPITFIRE also places the files it creates in the appropriate
file path.
Page 18
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
If you wish to modify these settings, you may do so by
pressing ALT+P at the "Ready..." prompt. Pressing ALT+P
opens the window which allows you to set the file paths
used when running SPITFIRE. An explanation of the commands
are 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 or CLR 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 files path questions.
After you've configured SPITFIRE to meet your specifications,
Quit and return to the "SPITFIRE ready for use..." prompt.
At the "SPITFIRE ready for use..." prompt, press ALT+R to
configure your Message Conference records and ALT+F to configure your
File Area records. For more information on this feature, refer to the
section - SETTING UP SYSTEM RECORDS of this manual.
Page 19
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
After you've completed that, you're ready to go!
If you encounter problems running SPITFIRE, and you're sure you've
tried everything, gather together a report of your version number along
with information pertaining to the difficulties you are experiencing
(such as System, Modem, Comm Port) and contact Buffalo Creek's BBS at
(515-225-8496) for support. Be as thorough as possible so
an accurate determination of the cause of your problem(s) can be made.
Every effort will be made to determine and correct the problem!
Please keep in mind that it is difficult at best to provide help if
you simply leave a message that says something like, "I can't make
external protocols work. What am I doing wrong?". You need to
provide specific information regarding the problem.
Furthermore, if you've had a problem which isn't covered by this
manual and were able to work it out without support, please
contact Buffalo Creek's BBS so the information you have discovered can
be shared with other users of SPITFIRE. Also, please report any unique
configurations you may discover so everyone will benefit from your
ideas.
4.0 SPITFIRE FILE PATHS
-----------------------
SPITFIRE supports paths for the files which are accessed in the
process of its execution. Using the individual file paths created
by SPITFIRE (SYSTEM, WORK, MESSAGE, DISPLAY and EXTERNAL), your
directories are more manageable.
The SYSTEM files path is the directory in which you have set up
SPITFIRE (usually C:\SF) and contains files required for the execution
of SPITFIRE. The WORK files path contains files which SPITFIRE
accesses and writes to periodically in the process of program
execution. The DISPLAY files path contains all files which are
displayed to the caller while logged on the BBS. The MESSAGE files
path contains all files used by the message section of SPITFIRE. The
EXTERNAL files path includes the files necessary to provide the caller
with optional transfer protocols other than those automatically
accessed from within SPITFIRE.
**NOTE** All DISPLAY files are optional. Should the Sysop choose
not to use these files, SPITFIRE will operate just fine. In fact,
SPITFIRE will normally display a default message when a display
file is not found. The DISPLAY files merely provide an additional
means by which the Sysop can create unique screens to personalize
their BBS system.
Page 20
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
The system files that were created when setting up SPITFIRE
MUST reside in the main SPITFIRE directory. The WORK, MESSAGE,
DISPLAY and EXTERNAL file paths are created by SPITFIRE or can be
modified by pressing ALT+P at the "SPITFIRE Ready For Use" prompt.
(Refer to the section - GETTING STARTED of the SPITFIRE manual.)
The following sections discuss, individually, files used by
SPITFIRE. After the file description, a (SYSTEM), (WORK), (MESSAGE)
or (DISPLAY) is included to help you determine in which directory the
file should be placed. No files which will be used in your External
Protocol Path will be found. These are not included in the SPITFIRE
package because these are separate programs written by other
programmers.
4.1 - SPITFIRE SYSTEM FILES
---------------------------
There are five file types that comprise SPITFIRE and allow it
to function - System, Work, Message, Display and External Protocol.
The first is SYSTEM FILES. System Files are mandatory for
SPITFIRE's operation and MUST reside in your main (also referred to
as HOME) SPITFIRE directory from which you run SPITFIRE.
SPITFIRE.EXE - Main System Program. (SYSTEM)
SPITFIRE.OVR - SPITFIRE Overlay File. (SYSTEM)
SFMAIN .MNU - SPITFIRE Main Menu. (SYSTEM)
SFMSG .MNU - SPITFIRE Message Menu. (SYSTEM)
SFFILE .MNU - SPITFIRE File Menu. (SYSTEM)
SFSYSOP .MNU - SPITFIRE Sysop Menu. (SYSTEM)
The above-mentioned files MUST be present for SPITFIRE to
run. SPITFIRE will halt if these files are not found in the directory
from which you are running your system.
The following system files will be created by SPITFIRE if they
are not already present.
SFNODE.DAT - Configuration information for this node. (SYSTEM)
SFFAREA.DAT - File Area system information. (SYSTEM)
SFMCONF.DAT - Message Conference system information. (SYSTEM)
SFEVENTS.DAT - Stores information regarding scheduled events.(SYSTEM)
Other system files which will need to reside in the main
SPITFIRE directory include:
SFREMOTE.BAT - Used for remote Drop to DOS. (SYSTEM)
SF .BAT - Batch file for invoking SPITFIRE. (SYSTEM)
Page 21
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SFMAIN .BAT - Executes Sysop configurable command option
available from the Main Menu. (SYSTEM)
SFMAIN .DAT - File created that contains caller information.
SPITFIRE creates this file when a caller uses
the Main Menu Sysop Configurable Command to
execute a third party program. This file is
automatically erased when the caller returns
to SPITFIRE. (SYSTEM)
SFMESS .BAT - Executes Sysop configurable command option
available from the Message Menu. (SYSTEM)
SFMESS .DAT - File created that contains caller information.
SPITFIRE creates this file when a caller uses
the Message Menu Sysop Configurable Command to
execute a third party program. This file is
automatically erased when the caller returns
to SPITFIRE. (SYSTEM)
SFFILE .BAT - Executes Sysop configurable command option
available from the File Menu. (SYSTEM)
SFFILE .DAT - File created that contains caller information.
SPITFIRE creates this file when a caller uses
the File Menu Sysop Configurable Command to
execute a third party program. This file is
automatically erased when the caller returns
to SPITFIRE. (SYSTEM)
SFDOOR .MNU - SPITFIRE Door Menu. (SYSTEM)
SFDOORS .DAT - File created that contains caller information.
SPITFIRE creates this when a caller uses the
SPITFIRE door feature and erases it when the
caller returns to SPITFIRE. (SYSTEM)
DOOR .SYS - Universal door file that contains caller information.
SPITFIRE creates this when a caller uses the
SPITFIRE door feature. (SYSTEM)
SFORDER .MNU - SPITFIRE Questionnaire Menu. (SYSTEM)
SFCHAT .CAP - Text file of chat captures. (SYSTEM)
CALLERS .TMP - Temporary file for recording callers activity.
This file is later appended to CALLERS.LOG file
in the WORK file path. (SYSTEM)
DAILYLMT.DAT - Determines daily time limits, number of downloadable
files and bytes, quick log on capability, number of
node chats, etc. for each security level (SYSTEM)
SFINIT .BAT - Batch file, if found, is executed after callers
log off and prior to initializing the modem. (SYSTEM)
SFLOGON .BAT - Batch file, if found, is executed after a caller
logs onto the BBS and the system information is
displayed. (SYSTEM)
SFSEC<X>.BAT - Batch file, if found, is executed after a caller
logs onto the BBS and whose security is equal to
<X> of the SFSEC<X>. (SYSTEM)
Page 22
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
BADINIT .BAT - Batch file executed when modem initialization fails,
i.e., SPITFIRE reports the modem is not responding
properly. (SYSTEM)
SPITFIRE.HLP - Help with all commands for all menus. This file can be
modified via SFHELP. Consult the documentation
accompanying SFHELP. NOTE: Systems using the
Sysop configurable command option(s) will need to
modify this help file with SFHELP to include an
explanation of the added feature(s). (SYSTEM)
SFPROTCO.HLP - Extra help with Uploads/Downloads. This is a simple
text file that you can modify with your favorite text
editor, provided it saves in ASCII format. (SYSTEM)
The SFREMOTE.BAT, SFPROTCO.HLP, SFDOOR.MNU, SFORDER.MNU, SF.BAT,
DAILYLMT.DAT, SPITFIRE.HLP, SFINIT.BAT, SFSEC<X>.BAT, SFLOGON.BAT,
SFMESS.BAT, SFMAIN.BAT, SFFILE.BAT and BADINIT.BAT may be edited to
your own personal tastes.
*NOTE* Any Sysop operating a multi-node system must have a copy of
all the system files being used by a particular node in that
node's main SPITFIRE directory. While some files such as
SPITFIRE.EXE are mandatory, other files, such as SFINIT.BAT,
may be optional.
4.2 SPITFIRE MESSAGE FILES
--------------------------
All files relating to the message conference reside in the MESSAGE
file path. SPITFIRE supports up to 255 message conferences and for
each message conference on the system a SFMSG<X>.DAT, SFMSG<X>.PTR,
SFMSG<X>.LMR and SFMSG<X>.IDX file is created. (<X> refers to the
number of the corresponding message conference and will range from
1 to 255.)
SFMSG<x> .DAT - All messages are contained here. (MESSAGE)
SFMSG<x> .PTR - Message pointers for scans, etc. (MESSAGE)
SFMSG<x> .IDX - Message index file. (MESSAGE)
SFMSG<x> .LMR - Last message read pointer file. (MESSAGE)
* NOTE * Any Sysop operating a multi-node system should be aware that
SPITFIRE allows all nodes to share a common MESSAGE file
path.
Page 23
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
4.3 SPITFIRE WORK FILES
------------------------
The third file category type is WORK FILES. Although not all
of these files are required to run SPITFIRE, you will find them
invaluable in the operation of your BBS system. These files are
accessed routinely and are periodically written to during the course
of SPITFIRE's execution. If the REQUIRED work files are not found,
SPITFIRE will create them. (SFNEWU.QUE, SFMAIN<x>.QUE, SFUPCASE.DAT,
SFNOUP.DAT and SFMSGPCK.BAT are not required and must be created by the
Sysop. SFCALLOG.DAT is not created, but included in the SPITFIRE
distribution package and must be copied over to the directory you have
configured as the WORK FILE PATH.)
SFSYSTEM .DAT - Starting date, number of callers, etc. (WORK)
SFUSERS .DAT - Caller data file. (WORK)
SFUSERS .PTR - Caller data pointer file. (WORK)
CALLERS .LOG - Record of the callers' activities. (WORK)
SFCALLOG .DAT - Stores information used to write caller's log.(WORK)
HEYSYSOP .LOG - Record of special Sysop notification. (WORK)
SFNEWU .QUE - New caller questionnaire. (WORK)
SFNEWU .ANS - Contains new caller questionnaire answers. (WORK)
SFMAIN<x>.QUE - Questionnaires at Main Menu for callers. (WORK)
SFMAIN<x>.ANS - Contains callers' responses to the Main Menu
Questionnaires. (WORK)
JOKER .DAT - List of undesirable caller names. (WORK)
SFBBSLST .DAT - Contains list of other boards to call. (WORK)
SFUPCASE .DAT - Keywords in a file description that will
be converted to uppercase. (WORK)
SFNOUP .DAT - Files the Sysop does not want uploaded. (WORK)
SFMSG .TXT - A text file that can be imported when entering
or replying to messages if logged on locally. (WORK)
SFMSGPCK .BAT - Batch file, if found, is executed immediately
after packing the message base. (WORK)
SFPURGED .USR - Listing of callers purged from the BBS. Contains
caller's name, address and security level at the
time of the purge. (WORK)
SFWHOSON .DAT - Information regarding who is logged onto
each node. (WORK)
BBSNAME .DAT - Net-mail tag line data. (WORK)
** NOTE ** Any Sysop operating a multi-node system should be aware that
SPITFIRE allows all nodes to share a common WORK file path.
Page 24
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
4.4 SPITFIRE DISPLAY FILES
--------------------------
SPITFIRE uses the following files as display files. If these
are not found, SPITFIRE will run just the same. Display files can
be created using your favorite text editor or screen generating
program.
<x> .BBS/CLR - Displays to caller at log on if the caller
record number equals #<x>. (DISPLAY)
<x>SEC .BBS/CLR - Displays to all callers with a security level
equal to <x>. (DISPLAY)
ALL .BBS CLR - Displays to all callers upon log on, unless
their security allows for a quick log on.(DISPLAY)
BULLETIN .BBS/CLR - Lists the bulletins available to the caller.
(DISPLAY)
BULLET<x>.BBS/CLR - This file displays to callers when <x> bulletin
is selected. <x> can equal 1 to 99. (DISPLAY)
CHATDONE .BBS/CLR - Displays to callers after completing a chat
with the Sysop. (DISPLAY)
DLMT .BBS/CLR - Displays to callers when downloads exceed daily
limit. (DISPLAY)
DORBUL<x>.BBS/CLR - The <x> file displays to callers when <x> bulletin
is selected from the Door Bulletin Menu, where
<x> can equal 1 to 99. (DISPLAY)
EVENTIME .BBS/CLR - Displays to a caller who logs on and has their
log on time adjusted so an on time event can
be completed at a specified time. (DISPLAY)
FILE<x> .BBS/CLR - Non-ANSI and ANSI created file menus that display
to callers whose security level is equal to <x>.
(DISPLAY)
FILST<x> .BBS/CLR - Listing of available File Areas that displays
to callers whose security level is equal to <x>.
(DISPLAY)
GOODBYE .BBS/CLR - Displays to callers when logging off the BBS.
(DISPLAY)
LOCKOUT .BBS/CLR - Displays to a callers marked as locked out
or is found in JOKER.DAT. (DISPLAY)
MAIN<x> .BBS/CLR - Non-ANSI and ANSI created main menus for each of
the corresponding security levels available
on the BBS. (DISPLAY)
MAXUSERS .BBS/CLR - Displays to new callers when the maximum number
of callers have been reached. (DISPLAY)
MSG<x> .BBS/CLR - Non-ANSI and ANSI created message menus for each
of the corresponding security levels on the BBS.
(DISPLAY)
MGLST<x> .BBS/CLR - Listing of available Message Conferences that
displays to callers whose security level is
equal to <x>. (DISPLAY)
Page 25
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NEEDSYS .BBS/CLR - Displays to callers prior to terminating the
connection when utilizing the ALT+F1 key.(DISPLAY)
NEWUSER .BBS/CLR - Displays to new callers (normally rules of
the BBS). (DISPLAY)
PRIVATE .BBS/CLR - Contains message displayed to new callers when
logging on a private system after answering the
new caller questionnaire (if found). (DISPLAY)
SF1STM .BBS/CLR - Displays to the caller when entering the Message
Section the first time per log on. (DISPLAY)
SF1STF .BBS/CLR - Displays to the caller when entering the file
section the first time per log on. (DISPLAY)
SF2SLOW .BBS - Displays to a caller who connects at a baud rate
lower than what the Sysop has configured as the
minimum baud rate allowed on the BBS. (DISPLAY)
SFASLEEP .BBS/CLR - Displays to a caller who has not entered a key-
stroke for the amount of time configured by
the Sysop in ALT+Z's No Activity Time Limit,
prior to logging them off the BBS. (DISPLAY)
SFBATCHD .BBS/CLR - Non-ANSI and ANSI created menus for the
Batch Download Menu. (DISPLAY)
SFBATCHU .BBS/CLR - Non-ANSI and ANSI created menus for the
Batch Upload Menu. (DISPLAY)
SFBDAY .BBS/CLR - Displays to a caller on their birthday. (DISPLAY)
SFDOOR<x>.BBS/CLR - Displays to callers entering the corresponding
SPITFIRE Door program. <x> can be an alphabetical
character A through Z, with the exception of G and
Q which are reserved for use by SPITFIRE.(DISPLAY)
SFDORBAK .BBS/CLR - Displays to a caller upon returning to SPITFIRE
BBS after completing a door program if the Sysop
has configured the BBS to require a password
when returning from a door. Normally prompts
used to prompt the caller for his/her password.
(DISPLAY)
SFDORBUL .BBS/CLR - Lists the door bulletins available to the caller
from the SPITFIRE Door Menu. (DISPLAY)
SFDOWN .BBS/CLR - Displays to callers prior to a download. (DISPLAY)
SFDR<x> .BBS/CLR - Non-ANSI and ANSI created door menus for each of
the corresponding security levels on the BBS.
(DISPLAY)
SFEXTDN .BBS - Contains a list of external download file transfer
protocols available on the BBS. (DISPLAY)
SFEXTUP .BBS - Contains a list of external upload file transfer
protocols available on the BBS. (DISPLAY)
SFFILES .BBS - Display file containing the names of files
available for downloading in each of the file
areas on the BBS. This is the only exception to
the rule of placing a Display File in the Display
Page 26
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
File Path. An SFFILES.BBS should be placed in
each download directory, listing the files
available for download for that particular file
area. (DOWNLOAD DIRECTORIES)
SFFILES .<x> - Listing of files available for download from a
CD-Rom file area. <x> represents the number of
the file area. (DISPLAY)
SFFILE<x>.BBS/CLR - Displays to callers when selecting a specific
file area. <x> would correspond to the area
selected. (DISPLAY)
SFIMPEXP .BBS/CLR - ANSI and non-ANSI menus displayed when logging on
locally and selecting either the <D>..Download or
<U>..Upload option from the File Menu. (DISPLAY)
SFMAINT .BBS/CLR - Displays to the caller after WELCOME1.BBS/CLR
and prior to the caller entering their name if
system maintenance is being performed. After
SFMAINT.BBS/CLR is displayed, the caller is
logged off the BBS. (DISPLAY)
SFMSG<x> .BBS/CLR - Displays to callers when selecting a specific
message conference. <x> would correspond to
the conference selected. (DISPLAY)
SFMQDONE .BBS/CLR - Displays to a caller attempting to answer a
main questionnaire a second time when it is
configured to limit callers to one response.
(DISPLAY)
SFNOD<x>.BBS/CLR - Displays to callers after the ALL.BBS/CLR
and prior to the <X>SEC.BBS/CLR. <x> would
correspond to the node number. (DISPLAY)
SFNOTIME .BBS/CLR - Displays to callers who attempt to log on after
using their daily allotted time. (DISPLAY)
SFNWSLTR .BBS - Sysop's newsletter available from the Main Menu.
Mono display (ASCII) file only. (DISPLAY)
SFORD<x> .BBS/CLR - Questionnaire Menu displayed to caller with a
corresponding <x> security level. (DISPLAY)
SFPAGED .BBS/CLR - Displays if the Sysop has the page on and a
caller attempts to page the Sysop again and the
Sysop does not answer the first page. (DISPLAY)
SFPGOFF .BBS/CLR - Displays to callers paging the Sysop and the
Sysop has the page feature turned off. (DISPLAY)
SFPRELOG .BBS - The first file displayed upon log on. (DISPLAY)
SFPROMSG .BBS/CLR - Displays to the caller prior to selecting a
default file transfer. Sysops should use this
display file to inform callers that if a default
transfer protocol is selected, External Transfer
Protocols will not be available to them. (DISPLAY)
SFRATIO .BBS/CLR - Displays to callers after a download if their
download/upload ratio exceeds your setting and
Page 27
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
a VWR (Violation Warning Ratio) exists for the
caller's security level in DAILYLMT.DAT. (DISPLAY)
SFREMIND .BBS/CLR - Displays to callers upon log on if the caller
was logged off during the previous session due
to inactivity. (DISPLAY)
SFTIMEUP .BBS/CLR - Displays to a caller whose log on time has
expired. (DISPLAY)
SFUNANS .BBS/CLR - Displays to a caller when the Sysop has the
page turned on and the Sysop does not answer
the page. If SFPAGED.BBS/CLR is found in the
display file directory, SPITFIRE will not allow
additional pages if the first page remains
unanswered. (DISPLAY)
SFUP .BBS/CLR - Displays to callers prior to an upload. (DISPLAY)
SOP<x> .BBS/CLR - Non-ANSI and ANSI file created Sysop menus for the
specified security levels. <x> would correspond
to the caller's security level. (DISPLAY)
TOOMANY .BBS/CLR - Displays to callers who exceeds the daily limit
of calls. (DISPLAY)
SYSINIT .BBS/CLR - Displays to the caller upon entering chat if the
Sysop initiated the chat. (DISPLAY)
THOUGHTS .BBS - Contains thoughts created for SPITFIRE with
THOUGHTS.EXE. (DISPLAY)
USERINIT .BBS/CLR - Displays to caller upon entering chat with the
Sysop if the caller paged the Sysop and requested
the chat. (DISPLAY)
WELCOME1 .BBS/CLR - The second file displayed upon log on. (DISPLAY)
WELCOME<x>.BBS/CLR - WELCOME2.BBS/CLR through WELCOME9.BBS/CLR
are displayed in numerical order after a caller
enters the name and password and gains access
to the BBS. (DISPLAY)
* NOTE * Any Sysop operating a multi-node system should be aware that
SPITFIRE will allow all nodes to share a common DISPLAY file
path.
SPITFIRE supports the use of ANSI/Graphics display files. The
ANSI files use the file extension .CLR (color). In the event ANSI
Graphics are available and SPITFIRE does not find the appropriate .CLR
file to display, then the appropriate .BBS file will be displayed. If
neither file is found, SPITFIRE will, in most cases, display a default
message.
IMPORTANT: When creating display files to be used with
SPITFIRE, it is recommended that the line length not exceed 255
characters. Also, in the event, ANSI/Graphics are available be
sure to load the ANSI driver (DEVICE=ANSI.SYS) from within your
CONFIG.SYS.
Page 28
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NOTE: When making ANSI graphics available to callers, duplicate
all display <filename>.BBS files to ANSI files and call them
<filename>.CLR. For an attractive BBS, offer both sets of files.
The following list of files are an EXCEPTION to this .CLR rule:
THOUGHTS.BBS SFEXTDN .BBS SFEXTUP .BBS
SFFILES .BBS SFNWSLTR.BBS SFPRELOG.BBS
SF2SLOW .BBS
SPITFIRE automatically displays SFFILES.BBS in color if the
caller selected ANSI color graphics when logging on the BBS. In the
event a file line is not colored like the others, but rather uses
the caller's default color, it is because the comma in the file size
is either not located properly or does not exist. SPITFIRE utilizes
the comma in the file size to determine the coloring of the SFFILES.BBS
listings.
4.5 SPITFIRE MENU FILES
------------------------
Menu files contain all the information needed for SPITFIRE to
dynamically build each caller's menus, dependent on the caller's
security level.
SPITFIRE displays a feature only if a caller's security level is
high enough to access it. Therefore, callers don't necessarily see
every possible choice in a given menu. This places you in control and
allows you to tailor your board for your individual needs.
The format used for the SFMAIN.MNU, SFSYSOP.MNU, SFMSG.MNU and
SFFILE.MNU is:
Command Character,Command Description,,Security Level,Command Identifier
Knowing this, let's use the following example:
B,<B>.... Bulletins,,5,A
------------------------
The "B" is the Command Character. This is the letter the
caller must type to access this particular option. In
this instance "B" is used to select Bulletins.
"<B>.... Bulletins" is the Command Description and represents
how the file entry appears in the menu on the screen.
"5" is the minimum Security Level required for the caller to
access this function...or even see it!
Page 29
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
"A" is the SPITFIRE Command Character Identifier and should
NEVER be changed. The Command Character Identifier is
constant in SPITFIRE programming. This character is
DIFFERENT for every command.
After exploring a bit, you'll find SPITFIRE allows you to
design your menus to suit your own personal taste as well as control
what commands are available to what callers. The SFFILE.MNU file that
comes with the SPITFIRE package sets the <D>.... Download A File
security at 10. While a caller is on-line, hit F2 to change the
caller's security to 9 and the Download feature is no longer available
for that caller.
THERE ARE THREE RULES CONCERNING MENU LINES!
--------------------------------------------
You CANNOT change the Command Character Identifier from what it
is in the original distribution package menu!
You CANNOT assign the same Command Letter to two commands in the
same menu!
You CANNOT make the total length of the line more than 40
characters long!
Therefore, if you wanted, you could change the Bulletins option
described above to read:
A,<A>.... Announcements,,5,A
Just remember: NEVER change the Command Character Identifier (the
last character on each entry line), and NEVER use a Command Letter more
than once in each menu.
SPITFIRE uses the following Menu Files and display menus:
SFMAIN .MNU - Main Menu (SYSTEM)
SFMSG .MNU - Message Menu (SYSTEM)
SFFILE .MNU - File Menu (SYSTEM)
SFSYSOP .MNU - Sysop Menu (SYSTEM)
SFDOOR .MNU - Door Menu (SYSTEM)
SFORDER .MNU - Questionnaire Menu (SYSTEM)
MAIN<x> .CLR - Color Main Menu (DISPLAY)
MAIN<x> .BBS - Non-ANSI Main Menu (DISPLAY)
FILE<x> .CLR - Color File Menu (DISPLAY)
FILE<x> .BBS - Non-ANSI Main Menu (DISPLAY)
MSG<x> .CLR - Color Message Menu (DISPLAY)
MSG<x> .BBS - Non-ANSI Message Menu (DISPLAY)
Page 30
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SOP<x> .CLR - Color Sysop Menu (DISPLAY)
SOP<x> .BBS - Non-ANSI Sysop Menu (DISPLAY)
SFDR<x> .CLR - Color Doors Menu (DISPLAY)
SFDR<x> .BBS - Non-ANSI Doors Menu (DISPLAY)
SFORD<x>.CLR - Color Questionnaire Menu (DISPLAY)
SFORD<x>.BBS - Non-ANSI Questionnaire Menu (DISPLAY)
SFBATCHU.CLR - Color Batch Upload Menu (DISPLAY)
SFBATCHU.BBS - Non-ANSI Batch Upload Menu (DISPLAY)
SFBATCHD.CLR - Color Batch Download Menu (DISPLAY)
SFBATCHD.BBS - Non-ANSI Batch Download Menu (DISPLAY)
SFIMPEXP.CLR - Color Local Log-on File Transfer Menu
(DISPLAY)
SFIMPEXP.BBS - Non-ANSI Local Log-on File Transfer Menu
(DISPLAY)
Refer to SPITFIRE DOORS section of this manual for information
regarding the structure of SFDOOR.MNU. Refer to the SPITFIRE
QUESTIONNAIRES section of this manual for information regarding the
structure of SFORDER.MNU.
You can use EDLIN, any text editor or screen generating program
that can create ASCII files to edit these files.
Should you edit these menu files and come up with some real nice
looking menus, please share the information so other Sysops using
SPITFIRE may benefit from your discovery.
SPITFIRE supports both color and Non-ANSI display menus. The
names of the files displayed for the color menus are:
MAIN<x>.CLR FILE<x>.CLR MSG<x>.CLR
SFDR<x>.CLR SOP<x>.CLR SFORD<x>.CLR
SFBATCHU.CLR SFBATCHD.CLR SFIMPEXP.CLR
The names of the Non-ANSI files displayed for the non color menus
are:
MAIN<x>.BBS FILE<x>.BBS MSG<x>.BBS
SFDR<x>.BBS SOP<x>.BBS SFORD<x>.BBS
SFBATCHU.BBS SFBATCHD.BBS SFIMPEXP.BBS
"x" represents the security level of the current caller. For
example, if a caller with a security level of 10 calls and selects
ANSI/Graphics, then SPITFIRE searches for files named MAIN10.CLR,
FILE10.CLR, MSG10.CLR, SFDR10.CLR, etc. to display as the color menus.
If a caller with a security level of 10 calls and chooses not to use
ANSI Graphics, then SPITFIRE searches for files named MAIN10.BBS,
FILE10.BBS, MSG10.BBS, SFDR10.BBS, etc. In the event these files are
not found, then SPITFIRE displays the default menus.
Page 31
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
The reason for different color and Non-ANSI display menu files
for each security level is to control what commands are shown to the
caller. For example, if the BBS requires a security level of 10 to be
able to download a file, then FILE10.CLR and FILE10.BBS will show the
<D>... Download A File command while FILE9.CLR and FILE9.BBS would not
show the command. A color menu file and a Non-ANSI menu file will have
to be created for each security level that you assign to callers if you
decide to have SPITFIRE display created menus rather than using
SPITFIRE 's default menus. The exception to the security defined
Non-ANSI and ANSI menus, are those used for the batch file transfer
menus and the local log on import/export menu. The batch file transfer
menus are simply named SFBATCHU.BBS/CLR and SFBATCHD.BBS/CLR. The
local log on import/export menu is named SFIMPEXP.BBS/CLR.
Buffalo Creek Software provides a utility to create the color
and non-color menu files. The name of this utility is MKSFMENU.
You can download it from Buffalo Creek's BBS at 515-225-8496.
Your SPITFIRE distribution package includes sample MAIN10.CLR,
FILE10.CLR, SFBATCHU.CLR, SFBATCHD.CLR, MSG10.CLR, SFIMPEXP.CLR,
SOP.CLR, MAIN10.BBS, FILE10.BBS, SFBATCHU.BBS, SFBATCHD.BBS and
MSG10.BBS, SFIMPEXP.BBS and SOP.BBS files.
4.6 SPITFIRE FILE CLARIFICATIONS
---------------------------------
The following files deserve a more in-depth explanation:
DAILYLMT.DAT - This file controls, per security level, the amount
(SYSTEM) of time a caller has each day, each call, kilobytes
allowed to be downloaded per day, files allowed to
be downloaded per day, node chats allowed, time
allowed per node chat, quick log on access, when and
if a caller will be warned of file ratio violation,
and when/if the file ratio violation will be
enforced.
Below is a list of abbreviations used in DAILYLMT.DAT and what each
abbreviation represents:
MPC - Minutes Per Call
MPD - Minutes Per Day
QL - Quick Log-on
DLPD - Downloads Per Day
KB - Kilobytes (allowed to be downloaded per day)
#OCA - Number Of Chats Allowed
TPNC - Time In Minutes Per Node Chat
VWR - Violation Warning Ratio
VER - Violation Enforcement Ratio
Page 32
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
A line should be created in DAILYLMT.DAT for each security level
you allow on your BBS. Each line should begin with the numeric value
of the security level whose parameters are being defined. The syntax
for each line in the DAILYLMT.DAT is:
10,MPC=45,MPD=60,QL,DLPD=15,KB=2000,Y,#OCA=5,TPNC=5,VWR=15,VER=25
where:
10 represents the security level for which the subsequent
parameters apply.
MPC=45 represents the time in minutes a caller with this security
level is allowed for each call to the BBS. This overrides the
Log On Time Limit defined at SPITFIRE's ALT+Z configuration.
MPD=60 represents the total daily time limit in minutes a caller
of this security level is allowed. This overrides the
Daily Time Limit defined at the ALT+Z SPITFIRE configuration
screen.
QL allows a remote caller with this security level to quickly
log on the BBS. This remote quick log on is similar to a local
quick log. After the initial log on, a caller of this security
is immediately displayed the Main Menu, avoiding the display of
WELCOME2.BBS/CLR to WELCOME9.BBS/CLR, ALL.BBS/CLR, etc. It
should be noted, <x>SEC.BBS/CLR and <x>.BBS/CLR will display to
callers with quick log on capability. To require a normal log
on, simply do not include QL in the DAILYLMT.DAT line.
DLPD=15 represents the maximum number of files a caller with this
security will be allowed to download each day.
KB=2000 represents the total number of kilobytes a caller with this
security level will be allowed to download each day.
#OCA=5 sets Number Of Chats Allowed (node chats) each day on a
multi-node system for this security level. SPITFIRE defaults
to 5. To disable node chats for a particular security level,
set this parameter to #OCA=0. The #OCA=<x> is only applicable
to multi-node systems.
TPNC=5 designates the Time (in minutes) Per Node Chat allowed for this
security level. SPITFIRE defaults to 5 minutes per node chat.
The TPNC=<x> is only applicable to multi-node systems.
VWR=15 represents the Violation Warning Ratio for this security level.
When the upload/download ratio exceeds 1 upload for each VWR
value downloaded, SFRATIO.BBS/CLR (if found) is displayed to
Page 33
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
the caller. Both the number of files AND the kilobytes
downloaded must exceed the ratio before SFRATIO.BBS/CLR is
displayed to the caller. If you do not wish to warn the
caller, do not include the VWR parameter in the DAILYLMT.DAT
for this security level.
VER=25 represents the Violation Enforcement Ratio for this security
level. When the upload/download ratio exceeds 1 upload for
each VER value downloaded, SPITFIRE alters the caller's
security to what the Sysop has configured at the U/D Ratio
Violation Security in the ALT+Z configuration screen. Both
the number of files AND the kilobytes downloaded must exceed
the ratio before the caller's security is altered. If
you do not wish to enforce the ratio violation for this
security level, do not include the VER parameter in the
DAILYLMT.DAT for this security level.
**NOTE** A warning should be displayed prior to enforcing the upload/
download ratio which would alter the caller's security level.
It is highly recommended that the difference between the
violation warning and the violation enforcement should be
greater than the amount of files the caller may download in
a batch download. Using the word Batch at the end of a line
in SFEXTDN.BBS limits downloads per batch to 6, so a difference
of at least 6 is recommended. Using the word Usefile, at the
end of a line in SFEXTDN.BBS limits downloads per batch to 99,
so a difference of 99 is recommended. (See section: External
Batch Download Protocols of this manual for a full explanation.)
If the difference between the violation warning and the violation
enforcement is not equal to or greater than the amount of files
a caller can download in a single batch, it is possible during
a batch download for a caller to have their security altered
without ever being warned of the impending status change.
If SPITFIRE finds the VWR and VER are 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 at the
U/D Ratio Violation Security.
Page 34
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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.
Using the example from above, all callers with a security level of 10
is allowed 45 minutes per call, 60 minutes per day, 15 downloads
per day, 2,000 kilobytes per day, 5 node chats of up to 5 minutes
per node chat, will be displayed SFRATIO.BBS/CLR when the upload/
download ratio of 1 to 15 was exceeded, and will their security
altered when the upload/download ratio of 1 to 25 is exceeded.
DAILYLMT.ZIP is included in the SPITFIRE package and can be downloaded
from Buffalo Creek's BBS. DAILYLMT.COM is a menu driven program that
is used to create and maintain DAILYLMT.DAT.
SFRATIO .BBS/CLR - It's rare when a caller's uploads exceed their
(DISPLAY) downloads. Some callers get in the habit of taking
and never give much consideration toward uploading.
This file is displayed after a download is completed
that has tipped the scales on the callers' U/D ratio
provided the DAILYLMT.DAT for the caller's security
level contains a VWR (Violation Warning Ratio).
SFRATIO.BBS/CLR will then be displayed to the caller
showing your "friendly" words of advice whenever
this situation presents itself. If you are not
concerned about a caller's U/D ratio, simply don't
include this file in your SF display file directory.
JOKER .DAT - JOKER.DAT contains a list of all names you don't
(WORK) want to allow on your board. Names like: Dr.
Phreak, Micro Muck, Lord Havoc, Nybbler, Killer,
etc.. You can create an ASCII file that has each
name listed on a separate line, such as:
Dr. Phreak
Micro Muck
Lord Havoc
Nybbler
Killer
All Callers
Page 35
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
When locking a caller out of the SPITFIRE BBS
system or marking the caller for deletion, SPITFIRE
prompts you as to whether you wish to add the name
to JOKER.DAT. If you respond with a Yes, the name
is automatically added to JOKER.DAT. SPITFIRE also
allows a caller to be locked out or marked for
deletion using ALT+A at the "Ready..." prompt or
from the Sysop Menu. A caller may also be locked
out by pressing ALT+L while caller is logged on the
BBS. A caller may be added to JOKER.DAT using any
of these features.
LOCKOUT .BBS/CLR - SPITFIRE reads JOKER.DAT line-by-line and compares
(DISPLAY) the names in the file against the caller's first
and last name. If a match is found, then the
LOCKOUT.BBS/CLR is displayed to the screen and the
' caller is logged off!
SFNWSLTR.BBS - File which displays to the callers when they
(DISPLAY) request the <N>...Newsletter from the Main Menu.
This file can be used to send a special message
to the callers regarding the system.
SFNOUP .DAT - SFNOUP.DAT contains a list of files which the
(WORK) Sysop does not wish to have uploaded to the BBS.
SFNOUP.DAT will allow complete use of DOS's wildcard
feature. You can create an ASCII file that has each
name listed on a separate line, such as:
TROJAN.*
WIN*.*
PERVERT.COM
*.GIF
When erasing a file from the file menu, SPITFIRE
prompts you as to whether you wish the file to be
added to SFNOUP.DAT. Responding with a Y for Yes
will add the erased file's name to SFNOUP.DAT.
SFFILES .BBS - Resides in each File Area and lists files available
(DL FILE AREA) for download from that area. This file is set up
using your favorite text editor. Here are some
guidelines one must follow for this to work
properly with SPITFIRE.
Page 36
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
1--------10--------20--------30--------40--------50--------60--------70
SF32-1.ZIP 325,000 03-20-92 SPITFIRE Bulletin Board System (V3.2)
The FILENAME must begin at column 1
The FILESIZE must end at column 21
The FILEDATE must end at column 31
The FILE DESCRIPTION must start at column 34
When the SFFILES.BBS displays to a caller who is
using ANSI Color Graphics and a file line is not
colored like the others, but rather uses the
caller's default color, it is because the comma in
the file size is either not located properly or does
not exist. SPITFIRE uses the comma in the file size
to determine whether the line is a file listing.
SFUPCASE.DAT - A list of keywords that are converted to or left
(WORK) in uppercase when converting file descriptions.
This is a simple text file that lists these
keywords, one per line.
SFREMOTE.BAT - This batch file is used with the remote Drop to
(SYSTEM) DOS feature and should be used with a carrier
detect utility such as WATCHDOG. If connection
is terminated while a caller is at the DOS level
the system is reset provided WATCHDOG is
used. If you have included SF.BAT in the
AUTOEXEC.BAT, SPITFIRE will automatically boot on
system start up. WATCHDOG is recommended but is
not included in the SPITFIRE package because it
was written by another author. However, it may
be downloaded from Buffalo Creek as well as from
numerous other BBS systems. When shelling to
SFREMOTE.BAT, SPITFIRE sends a parameter to
SFREMOTE.BAT which is the number of the comm port.
SF .BAT - Batch file which invokes SPITFIRE. This file
(SYSTEM) contains the necessary data for the scheduled
events feature within SPITFIRE to work properly.
Refer to section - EVENT MENU EXPLANATION - of
this manual for more information on Scheduled
Events. It also contains the data necessary to
execute programs using the SPITFIRE Door feature.
Refer to the section - SPITFIRE DOORS SECTION -
of this manual for more information on SPITFIRE
Doors.
Page 37
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SFMAIN .BAT - Batch file which executes the Sysop configurable
(SYSTEM) Main Menu option.
SFFILE .BAT - Batch file which executes the Sysop configurable
(SYSTEM) File Menu option.
SFMESS .BAT - Batch file which executes the Sysop configurable
(SYSTEM) Message Menu option.
SFMSGPCK.BAT - Batch file that executes immediately after packing
(WORK) the message base. SFMSGPCK.BAT allows net-mail
drivers to perform some necessary duties required
after packing the message base. This batch file
could also be used to control which conferences are
packed by SPITFIRE. For instance, if the Sysop
wishes to pack all Message Conferences, except
Message Conference #1, the following commands in
the SFMSGPCK.BAT could be used:
ECHO OFF
IF EXIST SFMSG01.$AT GOTO DATFOUND
GOTO END
:DATFOUND
IF EXIST SFMSG01.$TR GOTO PTRFOUND
GOTO END
:PTRFOUND
IF EXIST SFMSG01.DAT DEL SFMSG01.DAT
IF EXIST SFMSG01.PTR DEL SFMSG01.PTR
REN SFMSG01.$AT SFMSG01.DAT
REN SFMSG01.$TR SFMSG01.PTR
:END
SFINIT .BAT - Batch file executes if it exists, after a caller
(SYSTEM) hangs up and prior to the modem being initialized.
This allows utilities (such as a last 10 caller
listing or checking the integrity of uploaded files)
to be executed between callers to the BBS.
SFPGOFF .BBS/CLR - This file displays to the caller in the event
(DISPLAY) the caller pages the Sysop and the Sysop has the
page feature turned off.
SFUNANS .BBS/CLR - This file displayed to the screen in the event a
(DISPLAY) caller has paged the Sysop and the Sysop does not
answer the page.
Page 38
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SFPAGED .BBS/CLR - This file displays to the caller in the event
(DISPLAY) the Sysop has the page turned on and the caller
attempts to page the Sysop again and the first page
remains unanswered. If this file exists in the
display file directory, the Sysop will only receive
the first page. Any additional pages will cause
SFPAGED.BBS/CLR to display to the caller. If
you wish to be receive multiple pages, simply do not
include the SFPAGED.BBS/CLR files in the display
file directory.
BBSNAME .DAT - Simple one line text file that is placed in the
(WORK) Work file directory and contains information
about the BBS from which the net-mail message
originates. SPITFIRE will tag this on the end of
each net-mail message.
SFSEC<x>.BAT - This batch file, if it exists, executes after the
(SYSTEM) caller logs on the BBS, provided the caller's
security is equal to <x> in the .BAT file. One
example for utilizing this would be if your BBS
serves as a hub for net-mail. All callers who use
your BBS for mail could be assigned a set security
level. Upon logging on the BBS, the caller could
immediately begin the mail transfer process.
BADINIT .BAT - This batch file, if it exists, executes in the
(SYSTEM) event the modem fails to respond when initialized
between callers. Commands could be placed in the
batch file to issue modem commands to reset your
modem or to reboot your system with Buffalo
Creek Software's COLDBOOT utility. (COLDBOOT may
be downloaded from Buffalo Creek's BBS.)
<x>SEC .BBS/CLR - This feature allows the Sysop to send a special
(DISPLAY) notice to all callers of a certain security
level. This file is not automatically erased.
(<x>=the security level of the callers to whom you
wish to send the special message.)
<x> .BBS - This feature allows the Sysop to send a special
(DISPLAY) message to an specific caller. Once the caller has
received it, SPITFIRE automatically erases it.
Example: John Doe is Caller Record # 95 on your system. If you have
a file named "95.BBS", SPITFIRE will display this file
when John Doe logs on and then erase it after it has been
received. Your callers log will have a notation that the
special message was sent.
Page 39
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
**NOTE** In the event you use <x>.BBS to send special messages to
callers and you purge callers from the callers file by
packing SFUSERS.DAT, please note that the <x>.BBS may no
longer match the caller for whom the message was intended.
4.7 ABOUT SPITFIRE DISPLAY FILES
---------------------------------
As you can see, SPITFIRE allows you complete flexibility when it
comes to displaying files. The Sysop has nearly total flexibility in
making the board as unique as desired. In addition, SPITFIRE uses
control characters which may be built into display files for even
more control. These are:
^B - Inhibits the display of the "More Prompt"
^C - Disables a callers' ability to break out of the display
^D - Displays caller's first name
^E - Enables the "More Prompt" if previously turned off by ^B
^F - Displays the caller's city and state/province
^G - Transmits a beep over the caller's PC speaker
^J - Displays the number of files uploaded by the caller
^K - Displays the number of files downloaded by the caller
^L - Clears the display screen
^N - Allows caller to interrupt screen display - cancels a ^C
^O - Displays the caller's original log on date
^P - Exhibits a "More Prompt" in the display
^Q - Displays the number of minutes allowed this log on
^R - Displays the caller's phone number
^S - Displays the date of the caller's last call
^T - Displays the caller's password
^U - Displays the caller's birthdate
^V - Displays the caller's full name
^W - Displays the number of K uploaded
^X - Displays the number of K downloaded
^Y - Displays the caller's security level
Place these characters in display files. A few of the control
characters mentioned above deserve a more detailed explanation. When
SPITFIRE encounters a ^B, then the <More?> prompt will not interrupt
the display file. When SPITFIRE sees a ^C, the caller will not be able
to abort the screen. A ^N nullifies the affect of a previous ^C and
allows the caller to interrupt screen display once again. When SPITFIRE
sees a ^P, the <More?> prompt is displayed to the screen. It should be
mentioned that if a ^B is present in the same display as a ^P, it will
always override the ^P prompt, nulling the affect of the ^P feature.
However, a ^E can be used to nullify the effect of the ^B and allow the
Page 40
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
^P to display the <More?> prompt. When SPITFIRE encounters a ^G, a
beep is transmitted over the caller's PC speaker and a ^L clears the
display screen. The remaining control characters are self explanatory,
i.e., a ^D displays the caller's first name to the screen at that point
in the display file, a ^F will display the caller's city and state/
province to the screen at that point, etc.
Some planning is required when using display control characters. For
instance, do not use control characters that write information to the
screen (such as ^D, ^F, ^J, ^K, etc.) inside of a box. The characters
inserted will throw the box completely out of line.
^B is the extended ASCII value of 002.
^C is the extended ASCII value of 003.
^D is the extended ASCII value of 004.
^E is the extended ASCII value of 005.
^F is the extended ASCII value of 006.
^G is the extended ASCII value of 007.
^J is the extended ASCII value of 010.
^K is the extended ASCII value of 011.
^L is the extended ASCII value of 012.
^N is the extended ASCII value of 014.
^O is the extended ASCII value of 015.
^P is the extended ASCII value of 016.
^Q is the extended ASCII value of 017.
^R is the extended ASCII value of 018.
^S is the extended ASCII value of 019.
^T is the extended ASCII value of 020.
^U is the extended ASCII value of 021.
^V is the extended ASCII value of 022.
^W is the extended ASCII value of 023.
^X is the extended ASCII value of 024.
^Y is the extended ASCII value of 025.
4.8 BACKUP FILES
-----------------
When performing Sysop maintenance like Packing the Message Base
or Packing the Callers file, SPITFIRE makes "Backup" copies for you.
If disk space is a problem on your board copy the backup files to
disk or discard them. SPITFIRE backup files are listed below:
SFMSG<x>.$TR - Message Pointer Backup File
SFMSG<x>.$AT - Message Base Backup File
SFMSG<x>.$DX - Message Index Backup File
SFMSG<x>.$MR - Last Message Read Backup File
Page 41
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SFUSERS .$AT - Callers Backup File
SFMCONF .$$$ - Message Conferences Backup File
SFFAREA .$$$ - File Areas Backup File
4.9 THOUGHTS.BBS
----------------
SPITFIRE displays a thought to callers if a file named
THOUGHTS.BBS is found in the directory configured as your display
file path. The program to create THOUGHTS.BBS can be downloaded
from Buffalo Creek's BBS at 515-225-8496 or you can download a
ready-made THOUGHTS.BBS file.
5.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 COMM port to use (<x> is COMM 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.
/Ix - Initializes the System speed (<x> is modem speed).
/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
Page 42
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 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
ons only) to 38400.
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 COMM port other than COMM 1 and a modem speed different than
2400 baud. In other words, SPITFIRE is written to default to COMM port
1 and to initialize the system at 2400 baud 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 /I9600
The above example would boot SPITFIRE utilizing COMM port #2 and
initializing the system at 9600 baud rate.
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 baud rate, work path,
modem initialization string or COMM port assignment, you MUST also
change the specifications set in the SF.BAT file. It is for this
reason that the use of command line parameters is not recommended.
5.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
Page 43
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
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 is 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 and you are running SPITFIRE in a directory
named SF.
6.0 SETTING UP THE SYSTEM RECORDS
-----------------------------------
Message Conference records and File Area records comprise your
SPITFIRE system records. There are two ways to set up the system
records in SPITFIRE. The first is by using ALT key combinations
at SPITFIRE's "Ready..." prompt. The second is through the Sysop
Menu which is accessed from the Main, Message or File Menus.
SPITFIRE allows a total of 255 different Message Conferences and
65535 File Areas.
6.1 CONFIGURING MESSAGE CONFERENCE RECORDS
-------------------------------------------
Message Conference records are configured by pressing ALT+R at the
"Ready" prompt or by selecting option <M> from the Sysop Menu. When
this is done the following will display to the screen:
MESSAGE SYSTEM RECORD NUMBER 1 Of 1
Conference Description.. : "Untitled Message Conference"
Msg Conference Access... : Equal To Or Greater Than Caller Security
Public Msg Conference... : Non-Public Message Allowed
Conference Security..... : 5 Net-Mail Conference..... : No
Maximum Msg Length...... : 99 Purge Msgs Older Than... : 120 days
Caller Message Deletion. : Allowed Msg Pack Backup File.... : Yes
Delete Old Thread Msg... : Yes
Page 44
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
>>>> MESSAGE SYSTEM RECORD MENU <<<<
<N>.......... Net-Mail Toggle <M>... Conference Description
<S>...... Conference Security <#>........ Conference Access
<R>............ Record Number <A>........... Add New Record
<P>.... Public Msg Conference <U>.......... Caller Deletion
<I>.....Insert New Conference <D>........ Delete Conference
<O>.........Old Message Purge <B>..............Backup Files
<+>.......... Next Conference <->...... Previous Conference
<T>.....Delete Old Thread Msg <L>........Maximum Msg Length
<Q>..................... Quit
ENTER COMMAND - [N M S # R A P U I D + - T L Q]?
Command <N> - Net-Mail Toggle
Allows the Sysop to configure whether an individual
message conference will allow net-mail. If a message
conference is set up to allow net-mail, the callers
to the BBS are be allowed to leave messages to a person
who is not a caller on the BBS. If a message conference
is not set up to allow net-mail a caller can only leave
messages to other callers of the BBS. (This also applies
to Carbon Copy messages.)
Command <M> - Conference Description
You will notice that the default Message Conference
description is "Untitled Message Conference". Change
this to suit your needs. As an example, you may wish to
change the description of this conference to "Public
Messages".
Command <S> - Conference Security
This allows you to set the security level for this
Message Conference. You will notice that the default
security level is 5, which means that any caller with a
security of 5 or greater will be able to read messages
in this conference. If you wish to set a different
security level for this Message Conference, then select
<S> to change the security level of the conference.
Command <#> - Conference Access
You will note that SPITFIRE defaults the Message
Conference Access to "Equal To Or Greater Than". What
this means is that any caller with a security level equal
to or greater than the security level of this Message
Conference can access it. If you select <#>, SPITFIRE
will toggle this feature to "Equal To Caller Security"
and only callers with a security level equal to the
security level of the Message Conference will be able to
access this conference. Callers with a security level
greater than or less than the security level of this
conference will not be able to access this conference
(unless the caller has Sysop security).
Page 45
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <R> - Record Number
Allows you to enter a specific Message Conference record
number. After entering the number, the information for
the record number you specified is displayed.
Command <A> - Add New Record
Allows the Sysop to add a new Message Conference to the
Message base. The new record will be added after the
last existing Message Conference record. For instance,
if your system has 25 Message Conferences and the <A>
option is selected, a Message System Record Number 26
will be added.
Command <P> - Public Msg Conference
Toggles whether the Message Conference will allow
non-public messages. The default setting of SPITFIRE is
to allow non-public messages. By selecting <P> you can
toggle this feature so that only messages marked as
public are allowed.
Command <U> - Caller Deletion
Toggles whether a caller of the BBS is allowed to delete
messages. If set to Yes, the caller will be able to
delete messages either sent to or sent by them. If
this is toggled to No, a caller will not be allowed to
erase any messages. This option is set for each message
conference individually. You may toggle it one way for
one message conference and the other for another message
conference.
**** Although Buffalo Creek Software includes this feature within
SPITFIRE, it assumes no responsibility for Sysops who use this
feature. Legal judgments concerning the ownership of messages
on a bulletin board system could possibly hold Sysops liable for
denying callers control of their posted messages.
Command <I> - Insert Msg Conference
Inserts a new Message Conference record between two
existing Message Conference records. Upon selecting
this option, SPITFIRE displays the prompt "Insert before
which conference?". A new Message System Record is
inserted preceding the Message System Record number
entered here.
***IMPORTANT NOTE***
When inserting a new Message Conference the SFMSG<x>.DAT,
SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR files are
automatically reset to correspond to the appropriate
Page 46
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Message Conference. For example, assume the BBS has
five active Message Conferences and a new Message
Conference is inserted prior to Message Conference #4.
The new Message Conference becomes Message Conference
#4. The previous Message Conference #4 now becomes
Message Conference #5, therefore, the SFMSG04.DAT,
SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR are renamed to
SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX and SFMSG05.PTR.
The previous Message Conference #5 now becomes Message
Conference #6 and the SFMSG05.DAT, SFMSG05.PTR,
SFMSG05.IDX and the SFMSG05.LMR are renamed to
SFMSG06.DAT, SFMSG06.PTR, SFMSG06.IDX and SFMSG06.LMR.
Command <D> - Delete Conference
This option allows an existing Message System Record to
be deleted. Upon selecting this option SPITFIRE displays
the prompt "Delete which conference?". The number entered
here will cause that Message Conference to be removed.
***IMPORTANT NOTE***
When deleting an existing Message Conference the
SFMSG<x>.DAT, SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR
files are automatically reset to correspond to the
appropriate Message Conference. For example, let's again
assume the BBS has five active Message Conferences and
Message Conference #4 is deleted. The pre-existing
SFMSG04.DAT, SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR
files are deleted when Message Conference #4 is deleted.
The previous Message Conference #5 now becomes Message
Conference #4. The SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX
and SFMSG05.LMR are appropriately renamed to SFMSG04.DAT,
SFMSG04.PTR, SFMSG04.IDX and SFMSG04.PTR.
Command <O> - Old Message Purge
Specifies how many days old a message in this particular
conference must be prior to it being purged during
SPITFIRE's internal message packing procedure. For
instance, if this is set to 120 days, when SPITFIRE packs
this message conference any messages older than 120 days
will be purged.
Command <B> - Backup Files
Specifies whether to retain the backup files created
during SPITFIRE's internal message packing procedure.
If this is set to Yes, the SFMSG<x>.$AT, SFMSG<x>.$TR,
SFMSG<x>.$DX and SFMSG<x>.$MR backup message conference
files will remain on the drive. If this is set to No,
Page 47
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
the backup files are deleted following the completion
of the SPITFIRE's internal message packing procedure.
Command <+> - Next Conference
This option is used to move forward from one Message
System record to another. Pressing the "+" key
initiates the progression from one Message Conference
record to the next in sequential order. Upon reaching
the last record, if the "+" key is pressed, SPITFIRE
will cycle to the first Message System record.
Command <-> - Previous Conference
This option is used to cycle through the Message
System records in reverse order. Pressing the "-" key
causes the previous conference number to be displayed.
From the first Message System record, if the "-" key is
pressed, SPITFIRE will cycle to the last Message
System record.
Command <T> - Delete Old Thread Msg
This option allows the Sysop to designate whether
threaded messages will be deleted when using SPITFIRE's
internal message packer. If this is toggled to Yes,
when the message base is packed, threaded messages
older than the days set with the <O>..Old Message Purge
will be deleted. If toggled to No, threaded messages
will not be deleted from the message base.
Command <L> - Maximum Msg Length
The option allows the Sysop to configure the maximum
lines that will be allowed per message in this message
conference. Valid options range from 25 lines to 99
lines. For instance, if 50 is entered, the maximum
length for all messages in this conference would be
50 lines.
Command <Q> - Quit
Upon selecting this option, SPITFIRE will return to the
place from which the Message System Record Menu was
initiated. In other words, if invoked from the Sysop
Sysop Menu, SPITFIRE will return to the Sysop Menu.
If initiated from the "Ready..." prompt, SPITFIRE will
return to the "Ready..." prompt.
Page 48
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
6.2 CONFIGURING FILE AREA RECORDS
----------------------------------
File Area records are configured by pressing ALT+F at the "Ready"
prompt or by selecting option <F> from the Sysop Menu. When this is
done the following is displayed to the screen:
FILE SYSTEM RECORD NUMBER 1 Of 1
Download Path..... : C:\SF
Upload Path....... : C:\SF
Area Description.. : "Untitled File Area"
Area Access....... : Equal To Or Greater Than Caller Security
Area Security..... : 5 No Charge (FREE) Area..: No
Preview Area...... : No
CD Rom Area....... : No
Search File Area.. : Yes
>>>> FILE SYSTEM RECORD MENU <<<<
<F>......... Area Description <U>.............. Upload Path
<D>............ Download Path <S>............ Area Security
<&>.............. Area Access <R>............ Record Number
<A>............. Add New Area <I>.......... Insert New Area
<P>............... Purge Area <T>...... Toggle Preview Area
<+>................ Next Area <->............ Previous Area
<C>...............CD Rom Area <$>......... Search File Area
(N>.....No Charge (FREE) Area <Q>..................... Quit
ENTER COMMAND - [F U D S & R A I P T + - C $ N Q]?
Command <F> - Area Description
Notice that the default File Area description is
"Untitled File Area". Change the description so it
describes the types of files stored in this particular
file area. For example, if the files in this area
could be categorized as system utilities, a suitable
area description for this area might be "Utilities".
Select <F> to make this change.
Command <U> - Upload Path
To change the upload path, simply select <U> from the
menu. The Upload and Download paths are any legal DOS
pathnames telling SPITFIRE where it can find the files
associated with the File Area. It is possible to
configure uploads to go into a single "Recent Uploads"
File Area, or to different areas which you could specify
by subject. Here are a few examples of upload/download
paths:
The following example sends uploads to a sub-directory
called "UPLOADS" and allows the caller to download
Page 49
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
programs from a sub-directory called "GOODIES". (Note:
SF is the parent directory.)
Download Path.....C:\SF\GOODIES
Upload Path.......C:\SF\UPLOADS
In the following example, uploads are sent to the same
sub-directory where the files available for downloading
exist:
Download Path.....C:\SF\GOODIES
Upload Path.......C:\SF\GOODIES
If you're running the BBS on a floppy-based system with
uploads and download files on drive B, and not using
sub-directories, you could do the following:
Download Path.....B:\
Upload Path.......B:\
Command <D> - Download Path
You will notice that SPITFIRE sets the default download
path to the directory where SPITFIRE resides. To change
this DOS filepath, select <D> to set the path for this
File Area. In the event that the filepath set does not
exist, SPITFIRE will create it. For example, if you
set your download path to C:\UTILITY and the utility
directory doesn't exist on your drive, SPITFIRE will
create the directory. You will also notice once you
have entered the drive letter, SPITFIRE automatically
adds the colon ":" and the backslash "\" after it. If
an invalid path is entered, SPITFIRE will not accept it.
You will have to copy the files you want available for
download into this directory and create a SFFILES.BBS
(text file) listing the files in that directory. The
SFFILES.BBS file must also reside in that directory.
(The utility, MKSFFBBS, which will create your
SFFILES.BBS for each file directory, is available for
download from Buffalo Creek - 515-225-8496.)
Command <S> - Area Security
This allows you to set the security level for this File
Area. You will notice that the default security level
is 5, which means that any caller with a security of 5
or greater will be able to access this File Area. If you
wish to set a different security level for the File Area,
then select <S> to change the security level of the area.
Page 50
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <&> - Area Access
Note that SPITFIRE defaults to the File Area Access of
"Equal To Or Greater Than". This means that callers with
a security level equal to or greater than the security
level of this File Area can access it. If you select
<&>, SPITFIRE will toggle this feature to "Equal To
Caller Security". Then only callers with a security
level equal to the security level of the File Area will
be able to access this area. Callers with a security
level greater than or less than the area security level
will not be able to access it, except those callers
with Sysop security.
Command <R> - Record Number
This option allows you to enter a specific File Area
record number. Upon entering the number, all current
information for the record number you specified is
displayed.
Command <A> - Add New Area
By selecting the <A> option, a Sysop can add a new
File Area Conference to the File Area System Records.
The new record will be added after the last existing
File Area System Record. For instance, if your system
has 25 File Areas and the <A> option is selected, a File
Area Record Number 26 will be added. SPITFIRE will
allow an unlimited number of File Areas.
Command <I> - Insert New Area
By selecting <I>, a Sysop can insert a new File Area
System Record records between two existing file areas.
Upon selecting this option, you are prompted with
"Insert before which area?". A new File Area System
Record will be inserted preceding the File Area System
Record entered here.
Command <P> - Purge Area
This option allows an existing File Area System Record
to be deleted. Upon selecting this option, you will be
prompted with "Delete which area?". The number that you
enter here will cause that File Area to be removed from
the File Area System Records.
Command <T> - Toggle Preview Area
The "T" option is used to toggle a File Area's Preview
Area between Yes and No. If the Preview Area is toggled
to Yes, a caller with a security less than the required
Page 51
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Area Security will be allowed to preview this file area.
This means that the caller can access this file area,
list files, read text files, view file archives, etc. but
will not be allowed to download any files from this area.
In other words, the caller can do everything except
download from this file area. If this is toggled to No,
callers with a security less than the specified Area
Security will not be allowed access to this File Area.
Command <+> - Next Area
This option is used to move forward from one File Area
System record to another. Pressing the "+" key will
progress forward from one record to the next in
numerical order. When reaching the last record and
the "+" key is pressed, SPITFIRE will cycle to the first
File Area System record.
Command <-> - Previous Area
This option cycles through the File Area System
records in reverse order. Pressing the "-" key
will display the preceding record number. From the
first File Area System record if the "-" key is pressed
SPITFIRE will cycle to the last File Area System record.
Command <C> - CD Rom Area
The option specifies the file area as a CD Rom Area.
If this is toggled on, then SPITFIRE searches the Display
File Path for a SFFILES.<x> for the file listing of this
CD Rom Area. The <x> should correspond with the number
of the file area. For instance, if file area 15 is a CD
Rom Area then it would need to be named SFFILES.15.
SPITFIRE does not include CD Rom Areas in its search for
<N>ew files or report on file statistics if the BBS has
a CD Rom Area.
Command <$> - Search File Area
Allows Sysops to configure whether the download path
area per File Area will be searched for duplicate files
when a caller attempts an upload. If this is toggled
to Yes, the download path will be searched and if this
is toggled to No, the download path will not be searched.
As an example, Sysops using a CD-Rom file area may wish
to skip the search for these areas due to the time that
is required to scan these areas.
Command <N> - No Charge (FREE) Area
Allows the Sysop to configure whether a file area will
be a free file area or not. If this option is toggled
Page 52
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
to Yes, a caller may download files from this area and
callers statistics are not updated by either the number
of files downloaded or the kilobytes downloaded. When
toggled to No, files downloaded from this area will
update the callers statistics, increasing the number of
files and the kilobytes downloaded for each file that is
downloaded from this area.
Command <Q> - Quit
Selecting this option will return you to the place in
SPITFIRE from where the File System Record Menu was
called. In other words, you will be returned either
to the Sysop Menu or the "Ready..." prompt. SPITFIRE
will automatically save your newly configured System
Record.
7.0 SPITFIRE QUESTIONNAIRES
----------------------------
Questionnaire files are created with any ASCII text editor and
placed in the directory you have configured as your Work File Path.
The Questionnaire answer files will automatically be created by
SPITFIRE.
There are 2 types of questionnaires available for use in SPITFIRE.
There is the NEWUSER __/ SFNEWU .QUE The questionnaire file
Questionnaire \ SFNEWU .ANS The answer file
This is automatically utilized ONLY when a new caller logs on.
There is the ORDER ___/ SFMAIN<x>.QUE Poll questionnaire files
Questionnaire \ SFMAIN<x>.ANS Poll answer files
This is utilized only from the MAIN MENU when the caller selects
<Q>.. Questionnaire Menu.
SPITFIRE uses a simple procedure to utilize Questionnaires.
Questionnaires are simple text files that are interpreted by
SPITFIRE. The special control codes discussed in the section - ABOUT
SPITFIRE DISPLAY CODES - of this manual also apply to the SPITFIRE
questionnaire files. Any line in the questionnaire file will simply
Page 53
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
be displayed to the caller unless it begins with a special character.
SPITFIRE uses established first characters to determine the type of
response required by the caller. These are:
: - If the first character in the line is a colon, SPITFIRE pauses
for the caller's input. The caller must respond to the question
before SPITFIRE will continue with the questionnaire.
; - If the first character in the line is a semicolon, SPITFIRE
will pause for the callers input. But unlike the colon, the
caller is not required to respond to the question. The caller
can simply hit the Enter key and SPITFIRE will continue with the
questionnaire.
@ - If the first character in the line is an "at" sign, SPITFIRE
will pause for the caller to input a date in the format of
MM-DD-YY. SPITFIRE will automatically insert the hyphens
when the caller responds. Once the caller has entered the
response, SPITFIRE will redisplay it to the caller and ask
whether the information is correct.
# - If the first character in the line is the pound sign, SPITFIRE
will pause for the caller to input a phone number. The
format will depend on how the Sysop has the system configured.
If the Sysop has used the ALT+T to configure the phone
number to US format, then SPITFIRE will require the following
format: ###-###-####. Again, SPITFIRE will automatically
insert the hyphens when the caller responds. If the Sysop does
not have the system configured to US format, SPITFIRE will
accept any input up to 12 characters in length. Once
the caller has entered the response, SPITFIRE will redisplay
it to the caller and ask whether the information is correct.
^# - If a line begins with a caret sign followed by a number, SPITFIRE
will adjust the caller's security level equal to the number
following the caret sign provided the number is less than the
configured Sysop security. If the number used here is equal
to or greater than configured Sysop security level, the caller's
security level will not be changed. The number should be a valid
security level available on your system. SPITFIRE writes
a note in HEYSYSOP.LOG to advise you that the callers security
level was changed.
Tilde - If the first character in a questionnaire line begins with a
Symbol tilde character, the caller will be disconnected from the BBS.
This could be used by Sysops in the SFNEWU.QUE so callers could
be verified before they are allowed access to the BBS.
Page 54
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
- If a line begins with a ampersand followed by a number, SPITFIRE
will adjust the caller's time left on the system by the number
following the ampersand. &20 would provide the caller with an
additional 20 minutes.
? - If the first character in the line is a question mark, SPITFIRE
will prompt the line and automatically add a "[y/n]?". SPITFIRE
will then only accept a Y or N response from the caller. This
Yes/No question is used to branch to other special questions
depending on the caller's response. For instance, when SPITFIRE
receives a Y response to a question beginning with a question
mark, it will continue on through the questionnaire until a plus
sign, "+", is found. The text or additional questions you would
like to present to the caller who has responded with a Y should
start immediately after the plus sign. This Y series of lines
is ended with a second plus sign, "+". When the second plus
sign "+" is encountered, SPITFIRE will continue on with the
questionnaire normally. Similarly, when SPITFIRE receives a
N response to a question beginning with a question mark, it will
continue on through the questionnaire until a minus sign, "-",
is found. Any text or additional questions you would like to
present to the caller who responded with an N should be contained
between two minus signs, "-". When the second minus
sign "-" is encountered, SPITFIRE will continue on with the
questionnaire normally. It should be mentioned that any text
or questions between where the caller responds with a Y and the
first plus sign will be ignored, just as any text or questions
between where the caller responds with an N and the first minus
sign will be ignored. Each line that starts with a question
mark must be followed by a set of plus signs and minus signs.
For example:
?Are you the Sysop of a SPITFIRE Bulletin Board
+
You have made a wise choice!
+
-
You really should consider running SPITFIRE!
-
If none of the above described characters are found at the beginning
of the line, the line is simply displayed to the caller.
The caller's answers are written to either SFNEWU.ANS or SFMAIN<x>.ANS,
depending upon which questionnaire the caller is replying to. In
addition to the caller's answers, the caller's name, date and time
Page 55
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
of the response is recorded within the same file. In the new caller
questionnaire answer file, SPITFIRE will also note which node the caller
was logged on to when the questionnaire was answered.
The SFNEWU.QUE is displayed to the caller upon log on. The
SFMAIN<x>.QUE is displayed to the caller if the Questionnaire Menu is
selected from the Main Menu. The Questionnaire Menu file name
is SFORDER.MNU. The SFORDER.MNU file can be created using your
favorite text editor and the following format:
Questionnaire Topic,10,,Y,,,>,,,,NP
The first item on the line will be a description of the questionnaire
topic you have available on the BBS and is limited to 25 characters.
This is followed by a comma and the security level required for the
caller to be able to access the questionnaire. The security is then
followed by two commas and either a Y or an N. If a Y is placed after
the two commas, the caller will be allowed to answer the questionnaire
multiple times. If an N is placed after the two commas, the caller
will only be allowed to answer the questionnaire one time. This is
followed by three commas and either a "greater than" sign (>) or an
"equal sign" (=). The greater than sign makes the questionnaire menu
option available to callers who have a security level equal to or
greater than the specified security level. If the equal sign is used,
the questionnaire will only be available to callers with a security
level equal to that specified. This in turn is followed by four
commas and either an NP or a P. This delegates whether the caller's
answers will be sent to the printer. If NP is used, the answers are
not sent to the printer. If P is used the caller's responses are sent
to the printer as well as being saved to the appropriate SFMAIN<x>.ANS
file, keep in mind that your printer must be turned on and ready for
use. SPITFIRE checks to determine if your printer is properly
connected and ready for use and responds accordingly.
Optional ANSI and Non-ANSI display menu files may be created
using the SFORD[x].BBS/CLR file name. The x in SFORD[x].BBS/CLR will
correspond to the security level of the caller. As with other ANSI and
Non-ANSI display menu files, a file should be created for each
security level assigned to callers on your BBS system.
SPITFIRE will allow nine different questionnaire files to be
accessed. The files which contain the questions are SFMAIN[x].QUE.
The file SPITFIRE uses to store the caller's answers to the respective
questionnaire is SFMAIN<x>.ANS. The x in the SFMAIN[x].QUE and the
SFMAIN[x].ANS corresponds to the available questionnaire, 1 through 9.
The caller's answers are appended to the end of the appropriate answer
file. If the file does not already exist, SPITFIRE will create it.
Page 56
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
8.0 SPECIAL FUNCTION KEYS
--------------------------
SPITFIRE uses various ALT keys in combination with a letter key and
Function keys for many of its commands. To use an ALT+Key, the ALT key
and the appropriate letter key must be pressed simultaneously. (First,
press down the ALT key, then, while holding the ALT key down, press
the letter key.)
The following sections will list these special function keys used
by SPITFIRE, explain from where within SPITFIRE these commands can be
activated and the functions they perform.
8.1 AVAILABLE SPECIAL FUNCTION KEYS
------------------------------------
The special function keys available in SPITFIRE and a brief
description of their usage include:
F1 - Review Log Files
F2 - Change Security Level
F3 - Toggle Sysop Page/Bell
F4 - Toggle Printer
F5 - Check Today's Statistics
F6 - Take Five Minutes From Caller
F7 - Give Five Minutes To Caller
F8 - Toggle Full/Divided Screen
F9 - Capture Chat To Disk
F10 - Quit SPITFIRE
ALT+F1 - Log Caller Off With Message
ALT+F2 - Log Caller Off Without Message
ALT+F3 - Remove Backup/Log Files
ALT+A - Maintains Callers Database
ALT+C - Enter/Exit Chat Mode
ALT+D - Jump to DOS/Set Modem Offhook
ALT+E - Configure Events
ALT+F - Configure File Areas
ALT+J - Jump to DOS/Modem Stays On Hook
ALT+L - Lock Caller Out
ALT+M - Configure Modem
ALT+P - Configure File Paths
ALT+Q - Quick Local Log-On
ALT+R - Configure Message Conferences
ALT+S - Log On Locally/Sysop Next
ALT+T - Toggle SPITFIRE Switches
ALT+Z - Configure SPITFIRE
HOME - SPITFIRE Sysop Help Screen
Page 57
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
8.2 SPECIAL FUNCTION KEY DEFINITIONS:
--------------------------------------
Prior to each individual special function key definition, you
will notice an <O>, <R> or <B>. These are used to indicate from
where in SPITFIRE each particular function key can be utilized.
Listed below is a guide that explains what these letters represent:
<O> - Caller must be ON-LINE to perform
<R> - SPITFIRE must be at "Ready for Use" prompt to perform
<B> - Can be used BOTH when a caller's on-line or from the
SPITFIRE "Ready..." prompt.
<R> F1 (View Log File Menu)
Caller's, Heysysop Logs, Purged Caller List & New Caller's Answers
------------------------------------------------------------------
This option sets the modem off hook and allows you to view the
CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR and/or SFNEWU.ANS. These
files can be read from the SPITFIRE "Ready..." prompt without
having to log on the BBS and accessing this feature from the Sysop
Menu. You are prompted as to whether you wish to review the
Caller's log, Heysysop log, purged caller listing or caller
responses to SPITFIRE's new caller questionnaire. Upon selecting
the desired log, you are then presented with the following options
for reading the log file:
<T>..Today's Date
displays the CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR or
SFNEWU.ANS from its first entry for the current day.
<B>..Beginning Of File
CALLERS.LOG, HEYSYSOP.LOG or SFNEWU.ANS or SFPURGED.USR
is displayed from the beginning of the file, starting
with the first entry.
<S>..Specify Date
will prompt for a date to be entered and begins
displaying the CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR
or SFNEWU.ANS with the first entry of the date entered.
If the date specified here can not be found, SPITFIRE
will search for the next newer date than what was
specified and display the file from that point forward.
<Q>..Quit
Returns SPITFIRE to the Ready For Use prompt.
Page 58
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<O> F2 (Change Security Level)
--------------------------------
If a caller is ONLINE and you wish to change the caller's security
level, you can change it by pressing F2. The caller is unable to
see that you are changing the security level.
<B> F3 (Toggle Sysop Page)
----------------------------
By toggling this parameter <ON or OFF> the Sysop can decide
whether or not to be paged. If the PAGE is ON, the words "PAGE
ON" will appear on the top of your screen, provided you are using
the split screen. If the page is turned on and a caller selects
<P> for page, then the prompt bell will sound to notify you that
a caller wishes to chat with you. USERINIT.BBS/CLR will be
displayed to the screen when you respond to the page. If the
PAGE is turned off and a caller pages you, then SFPAGED.BBS/CLR
will be displayed to the caller and CHAT REQUESTED will display
if you are using the divided screen. After SFPAGED.BBS/CLR is
displayed, the caller will be prompted as to whether he/she would
like to leave a comment to the Sysop, provided the caller is not
the Sysop. SPITFIRE will not allow the Sysop to leave a comment
to him/herself.
<B> F4 (Toggle Printer)
-------------------------
This allows you to toggle the printer ON/OFF. Everything that
is written to the CALLERS.LOG will also be sent to the printer if
this toggle is on. This is useful if you wish to retain a hard
copy of your callers' activities while on-line. Keep in mind that
your printer must be turned on and ready for use. SPITFIRE
checks to determine if your printer is properly connected and
ready for use and responds accordingly.
<R> F5 (Check Today's Statistics)
-----------------------------------
While at the "SPITFIRE ready for use prompt...", if you press F5,
SPITFIRE will set the modem off hook and display the number of
calls for the day, number of uploads for the day, daily door usage
and so on...
<O> F6 (Take Five Minutes from a Caller)
----------------------------------------
When a caller is on-line, you can take 5 minutes from the caller's
log on time by pressing F6. If you press F6 in multiples, then
multiples of 5 minutes are taken from the caller's time.
Page 59
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<O> F7 (Give Five Minutes to a Caller)
--------------------------------------
When a caller is on-line, you can give 5 minutes to the callers
log on time. If you press F7 in multiples, then multiples of 5
minutes are added to the caller's time.
<B> F8 (Toggle Screen)
------------------------
This feature is used to toggle the split-screen/full-screen
option.
<O> F9 (Capture Chat To Disk/Printer)
-------------------------------
Either when responding to a caller who has paged you or when
initiating a chat pressing F9 will capture the conversation
and save it to a file called SFCHAT.CAP in the main SPITFIRE
directory. In the event SPITFIRE finds a printer attached and
ready, the Sysop is given the option of sending the capture to
the printer. There are two ways to activate the chat capture.
You can begin the chat using F9 (rather than ALT+C). This will
begin the chat and immediately save the chat to SFCHAT.CAP. Or
the F9 can be pressed any time during a chat, at which time it
will save the remaining chat to the SFCHAT.CAP file. If SFCHAT.CAP
does not exist, it will be created. If it does exist, the chat
will be appended to the existing SFCHAT.CAP file. Chats will be
differentiated in the SFCHAT.CAP file by beginning with "Chat
started with (caller name) at (date/time)" and ending with "Chat
ended at (date/time)".
<R> F10 (Terminate SPITFIRE)
-----------------------------
Pressing F10 will terminate SPITFIRE and returns you to DOS.
<O> ALT+F1 (Log Caller Off With Message)
------------------------------------------
Displays NEEDSYS.BBS/CLR and logs caller off. If a caller is
online and you need to access your system, pressing ALT+F1
displays your message via the NEEDSYS.BBS/CLR screen and
terminates the connection.
<O> ALT+F2 (Log Caller Off Without Message)
-------------------------------------------
If a caller is online and you wish to disconnect this caller,
simply press the ALT+F2 keys simultaneously and the connection
will be terminated. No message will be displayed to the caller.
<R> ALT+F3 (Remove Backup/Log Files)
-------------------------------------
When selected, this option sets the modem off hook and displays
the following menu:
Page 60
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
>>> FILE REMOVAL MENU <<<
<C>.... Erase CALLERS.LOG
<H>... Erase HEYSYSOP.LOG
<M>..... Erase SFMSG*.$??
<U>.... Erase SFUSERS.$??
FILE REMOVAL MENU - [C H M U Q]?
<C>... Erase CALLERS.LOG
Selecting this option will cause the existing CALLERS.LOG
file to be erased. SPITFIRE will automatically create a
new CALLERS.LOG file.
<H>... Erase HEYSYSOP.LOG
Selecting this option will cause the existing HEYSYSOP.LOG
file to be erased. SPITFIRE will automatically create a
new HEYSYSOP.LOG file.
<M>... Erase SFMSG*.$??
When this option is selected, all backup files from the
Message Conferences are erased.
<U>... Erase SFUSERS.$??
When this option is selected, the SPITFIRE caller's backup
files are erased.
<R> ALT+A (Maintain Callers File)
---------------------------------
At the "Ready..." prompt, when selecting ALT+A, SPITFIRE sets the
modem off hook and allows you to maintain the caller's file,
rather than logging on and maintaining the callers file from the
Sysop Menu. When this option is selected, the following screen
will be displayed:
USER RECORD NUMBER [3 of 233] Original Log.. : 07-15-91
Name...... : John Doe Subscription.. : N/A
Address... : Peoria, IL Last File Area : 10
Password.. : Doeboy Msg Conference : 1
Phone No.. : 555-151-5555 Security Level : 10
Birth date : 01-20-54 K Uploaded.... : 10
Time Left. : 25 K Downloaded.. : 122
Last Call. : 03-20-92 Expert Mode... : Off
Times On.. : 3 More Prompt... : On
Uploads... : 0 Downloads..... : 3
Purge Allowed. : Yes
Page 61
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SPITFIRE USER RECORD MENU
(+) Next Record (-) Previous Record (D) Downloads
(N) Caller Name (X) Expert (U) Uploads
(A) Caller Address (&) Delete Caller (E) Last Msg Conference
(P) Caller Password (L) Lock Caller Out (C) Last File Area
(#) Caller Phone No (T) Times On (!) Time Left
(R) Record Number (M) Subscription Date ($) More Prompt
(F) Find Caller (S) Security Level (B) Birth Date
(O) Original Log Date (@) Add New Caller (Z) Purge Allowed
ENTER COMMAND - [+ - D N X U A & E P L C # T ! R M $ F S B O @ Z Q]?
Notice that when this option is selected, SPITFIRE displays the
last caller record. Usually the first record in the caller's list is
the Sysop's. Therefore, if the Sysop would do any maintenance on the
caller's file while others are nearby, displaying the last caller's
record prevents the Sysop's password from being readily visible. This
is done to ensure the security of the BBS. (When accessed online from
the Sysop Menu, SPITFIRE displays the record for the current caller.)
Although, most of the command line options are self explanatory a
description of each feature is discussed more fully below:
Command <+> - Next Record
This option is used to move forward from one caller
record to another. Pressing the "+" key will allow you
to progress from one record to the next in numerical
order. When reaching the last record and the "+" key
is pressed you will cycle to the first caller record.
Command <-> - Previous Record
This option allows you to cycle through the caller
records in reverse order. Pressing the "-" key
will move you to the preceding record number. From
the first caller record if the "-" key is pressed
you will cycle to the last caller record.
Command <D> - Downloads
This option is used to change the number of downloads the
caller is credited as having made to the BBS. This must
be a numeric value ranging from 0-9999.
Command <N> - Caller Name
This option allows editing of the caller's name. Select
"N" and you are prompted to enter the first and last name
of the caller. When prompted for the first name, you can
also enter the first name, space and enter the last name.
Page 62
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
The information is automatically updated. SPITFIRE will
allow up to 30 character spaces for the caller's first
and last name to be entered.
Command <X> - Expert
By selecting this command line option you will toggle
the Expert status of the caller on and off. If the
Expert status is off, the caller will receive a full menu
display. If the Expert status is on, only the command
line options will be displayed to the caller.
Command <U> - Uploads
This option provides the opportunity to change the
number of uploads the caller is credited as having made
on the BBS. This must be a numeric value ranging from
0-9999.
Command <A> - Caller Address
This option provides the opportunity to change or edit
the caller's address. When <A> is selected, you are
prompted to enter the city and state/province for
the current caller record. SPITFIRE allows up to 30
character spaces for this information. Once the
corrections are made, you will be prompted regarding
whether the new information is correct.
Command <&> - Delete Caller
When you press the "&" key you toggle whether or not a
caller is marked for deletion from the SFUSERS.DAT file.
If a caller is marked to be deleted, the next time the
SFUSERS.DAT file is packed the caller will be removed from
the SFUSERS.DAT file. You will notice that when a caller
is marked for deletion a "Caller Marked For Deletion!"
will appear on the menu screen. Also, when marking
a caller for deletion, you are prompted as to whether
to add the caller's name to SPITFIRE's JOKER.DAT file
Command <E> - Last Msg Conference
This option will allow you to change the caller's last
message conference number. SPITFIRE allows 256 message
conferences and you can enter any number from 1 to the
number of the last available message conference.
Command <P> - Caller Password
Provides an opportunity to change or edit the caller's
password. When selected, you will be prompted to enter
the new password. SPITFIRE allows up to 14 characters
Page 63
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
for the input of the new password. Once the new password
is entered, it will be redisplayed and you will be
prompted to verify that the information is correct.
Command <L> - Lock Caller Out
Toggles whether a caller is locked out from the BBS. Any
caller who is locked out will be denied access to the BBS
when he/she attempts to log on. Notice that when a
caller is locked out, the words "Locked Out!" are
displayed on the menu. When locking out a caller,
SPITFIRE provides the option of adding the caller's name
JOKER.DAT.
Command <C> - Last File Area
This option will allow you to change the caller's last
file area number. SPITFIRE allows for an unlimited
amount of file areas and you can enter any number from
1 to the number of the last available file area.
Command <#> - Caller Phone No.
Provides the opportunity to change or edit the caller's
phone number. Upon selecting this option, you are
prompted to enter the new number. A sample format is
also displayed with the prompting. The format displayed
will depend on how you have configured the US Phone
format option from the ALT+T configuration window. If
the US format is toggled to Yes, the format will be
###-###-#### and the dashes will automatically be
inserted when entering the new number. If the US Phone
format option is toggled to No, the format will be
[ ] and any 12 character input will be
accepted. Regardless, of the format, after the new
phone number is entered, you will be prompted as to
whether the information is correct.
Command <T> - Times On
This option will allow you to change or edit the number
of times the caller has logged on the BBS. This number
may range from -999 to 9999. Normally you will only
use the range from 1 to 9999 but Sysops or co-Sysops
who do not wish to have their names included in top
caller bulletins may wish to use negative numbers here.
Command <!> - Time Left!
This option will allow you to enter the daily time
remaining in minutes. This number may range from
-999 to 9999 minutes remaining.
Page 64
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <R> - Record Number
This option will allow you to enter a specific caller
record number. Upon entering the number, all current
information for the record number you specified will
be displayed.
Command <M> - Subscription Date
This option allows the Subscription Date to be edited.
This option is included for Sysops who require callers
to subscribe in order to gain access to their system.
SPITFIRE's default setting is "N/A". If a Sysop wishes
to use this option, the subscription date will need to
be set. In the event, the Sysop decides to change the
Subscription Date back to "N/A", this can be done by
entering 01-01-80 as the Subscription Date.
Command <$> - More Prompt
Selecting the "$" More Prompt option from the command
line will toggle the More Prompt On and Off. If the More
Prompt is toggled On, each time a complete screen display
is received the "More, Continue" prompt is sent and the
display is paused until a keystroke is entered signaling
the display to continue. The number of lines of text
which are displayed between the "More, Continue" prompt
is determined by the caller's screen display setting set
from <Y>our Statistics of SPITFIRE's Main Menu. For
instance, if the screen display is set at 80X23, after
every 23 lines the "More, Continue" prompt will be
displayed. If the More Prompt is toggled Off, the "More,
Continue" prompt will not display and information will
continue to scroll without being paused.
Command <F> - Find Caller
When this option is chosen you are prompted to input the
full or partial name of the caller you are attempting to
find. SPITFIRE will search for any string matching what
was entered. When a match is found, SPITFIRE will report
the find and prompt you as to whether this is the caller
you were searching for. If you respond with a Y for Yes,
SPITFIRE will display that caller's record information.
If you respond with an N for No, SPITFIRE will continue
to search the caller database, informing you of any match
found, prompting whether the match is the caller you are
searching for. In the event, no match is found, SPITFIRE
will inform you no match could be found to the full or
partial name that was entered.
***NOTE*** When inputting your search criteria you will
notice that SPITFIRE is not case sensitive.
Page 65
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <S> - Security Level
Provides an opportunity to edit the security
level of the current caller record. You will be prompted
to enter the caller's new security level when this option
is selected. SPITFIRE allows up to a four digit figure
for the new security level and will only accept numeric
values.
Command <B> - Birth Date
Provides the opportunity to edit the caller's birth date.
When selected, you are prompted to enter the new birth
date. The format for entering the correction is the
numerical representation for MM-DD-YY. SPITFIRE will
automatically insert the dash between the month, the
day and the year. Once the corrections have been made,
SPITFIRE will prompt you by displaying the new birth date
entered and ask you if these changes are correct.
Command <O> - Original Log Date
Provides the opportunity to change or edit the date the
caller logged onto the BBS for the first time (original
date). When selected, you are prompted to enter the new
date of the original log on. The format for entering the
correction is the numerical representation for MM-DD-YY.
SPITFIRE will automatically insert the hyphens between
the month, the day and the year. Once the corrections
have been made, SPITFIRE will prompt you by displaying
the new date entered and ask you if these changes are
correct.
Command <@> - Add New Caller
This option provides you the opportunity to add a new
caller to the SFUSERS.DAT. Adding a new caller locally,
eliminates the necessity of the new caller responding
to the new caller questionnaire when calling the BBS for
the first time.
You will be prompted to provide certain information about
the caller before they can be added. You will need to
answer prompts regarding the caller's name, address,
password, birthdate (if required on your BBS) and phone
number. Once this information is entered, you will be
prompted for the security level you wish to assign to the
new caller. The security level you assign will determine
what features of the BBS the new caller will have access
to.
Command <Z> - Purge Allowed
This option allows you to toggle whether purging the
caller will be Allowed or Not Allowed. Normally, you
Page 66
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
will want this toggled to Purge Allowed. If purge is
allowed, and the caller has not logged on the BBS for
whatever the number of days the Sysop configures when
packing the caller file, the caller will be deleted.
However, if the purge not allowed is toggled, the caller
will not be deleted from the callers file during packing
regardless of how many days it has been since the caller
last logged on.
<O> ALT+C (Enter/Exit Chat Mode)
----------------------------------
This feature is for entering and exiting chat with a caller. You
can use this feature to answer a page or force a caller into chat.
When you answer a page, the caller's time on-line is still ticking
away. However, when you force a caller into chat, the caller's
time on-line counter is halted until the chat is finished and the
caller is returned to the system.
<R> ALT+D (Jump to DOS/Set Modem Offhook)
-------------------------------------------
This feature allows you to jump to DOS at the "Ready..." prompt
and places the modem offhook so callers attempting to phone the
BBS will get a busy signal. When you wish to go back to SPITFIRE,
type EXIT. If you are not in the proper directory when you EXIT,
SPITFIRE will automatically take you back to the directory in
which SPITFIRE resides.
<R> ALT+E (Configure Events)
------------------------------
This feature causes the Events Menu to be displayed. The Events
Menu is used to cycle through the active events in a forward or
backward direction, list events, enable an event or disable an
event. For more information on the ALT+E Events Menu refer to
the section - EVENTS MENU EXPLANATION - of this manual.
<R> ALT+F (Configure File Area Records)
----------------------------------------
While SPITFIRE is at the "SPITFIRE ready for use.." prompt, you
can select ALT+F to configure your File Area system records. This
feature allows you to do so without having to go through the
motions of logging on as Sysop and using the Sysop Menu to make
these changes. Refer to the section - CONFIGURING FILE AREA
RECORDS - of this manual for more detailed information .
<B> ALT+J (Jump to DOS - Modem Stays On Hook)
-----------------------------------------------
This feature allows you to jump to DOS when a caller is on-line
and also when you are at the "Ready..." prompt. When you wish to
go back to SPITFIRE, type EXIT. If you are not in the proper
Page 67
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
directory when you EXIT, SPITFIRE will automatically take you back
to the directory in which SPITFIRE resides. ALT+J does not set
the modem offhook.
<O> ALT+L (Lock Caller Off System)
-----------------------------------
ALT+L can be utilized to lock a caller out of your BBS while they
are on-line. Once the ALT+L is pressed to lock the caller out,
the Sysop is prompted as to whether the caller should be locked
out. If the Sysop responds with a "Y" for Yes, the Sysop is then
asked if the caller should be logged off. If ALT+L is pressed a
second time, SPITFIRE displays a message informing you the caller
is locked out and prompts you as to whether you wish to reverse
the lockout. In other words, the ALT+L is used to toggle whether
a caller is to be locked out from the BBS.
<R> ALT+M (Configure Modem)
-----------------------------
This feature sets the modem off hook and allows you to configure
your modem initialization string, COMM port, baud rate, etc. You
will also notice a toggle switch for use with an error-correction
modem. If you are using an error-correction modem, be sure to
turn this switch ON and enter the Error Correction Message
specific to your modem type.
If you are using an error-correction modem and this is not done,
when a caller logs on with an error-correction modem, the Ymodem-g
transfer protocols will not be available to the caller. (Refer to
the section - GETTING STARTED - of this manual for detailed
information.)
In the event your modem requires an initialization string
different than those listed in this manual, please forward the
information to Buffalo Creek's BBS (515-225-8496), so that the
information can be passed on to other Sysops.
<R> ALT+P (Configure File Paths)
---------------------------------
Pressing the ALT+P at the "SPITFIRE ready for use..." prompt
sets the modem off hook and opens a window which allows you to
configure the File Paths. (For more information on this, refer to
the section - GETTING STARTED and the section - FILE PATHS of this
manual.)
<R> ALT+Q (Sysop Quick Log-On/Sysop Next)
-------------------------------------------
This feature is used to log on SPITFIRE locally. It can be used
at the "Ready..." prompt or while a caller is on-line. Logging on
Page 68
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
with ALT+Q will not display the initial log on display files, but
rather takes you right to the Main Menu after entering your
name and password.
<R> ALT+R (Configure Message Conference Records)
--------------------------------------------------
While SPITFIRE is at the "SPITFIRE ready for use.." prompt, you
can select ALT+R to configure your Message Conference records.
This feature sets the modem off hook and allows you to configure
your Message Conferences without having to go through the motions
of logging on and using the Sysop Menu to make these changes.
Refer to the section - CONFIGURING MESSAGE CONFERENCE RECORDS - of
this manual for detailed information.
<B> ALT+S (Log On Locally/Sysop Next)
--------------------------------------
This feature is used to log on to SPITFIRE locally. It can be
used at the "Ready..." prompt or while a caller is on-line. If
you use this feature while a caller is on-line, then when the
caller logs off, SPITFIRE will sound a audible signal to notify
you the BBS is now available. You will then be able to log on
immediately. Logging on with ALT+S will display all the initial
display files available on the system, such as SFPRELOG.BBS,
WELCOME1.BBS/CLR, through WELCOME9.BBS/CLR and ALL.BBS/CLR.
<R> ALT+T (Toggle SPITFIRE Switches)
--------------------------------------
This feature sets the modem off hook and allows you to set the
various toggle switches contained within SPITFIRE. (For more
information on this, refer to the section - GETTING STARTED - of
this manual.)
<R> ALT+Z (Configure SPITFIRE)
--------------------------------
This feature sets the modem off hook and allows you to configure
certain aspects of SPITFIRE. (Refer to the section - GETTING
STARTED - of this manual for detailed information.)
<B> HOME (SPITFIRE Sysop Help Screen)
---------------------------------------
The "HOME" key displays a quick summary of all the special
function keys available to the Sysop. When used at the SPITFIRE
"Ready..." prompt a window will open up displaying the help
information. When used while a caller is on-line and if the
Sysop is using the divided/split screen option, the upper portion
of the screen will display the help information.
Page 69
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
9.0 MAIN SECTION EXPLAINED
---------------------------
The Main Menu is the crux of any system, being that all major
sections of the BBS are to be accessed from the Main Menu. However, it
is important to note that a caller does not have to return to the Main
Menu from the Message Section to go to the File Section (and vice-
versa). In the event there is a command on the Main Menu that you do
not wish to have functional, set the security level of that command
high enough so callers cannot see it.
As the Main Menu is described and the features explained, please
keep in mind that you can control the usage of each command by changing
the security level of the commands. In other words, you can control
what commands are available to what callers. (i.e. - If the security
level of the <B>.... Bulletins command is set at 25 then a caller with
a security level of 24 or less would not see the command or be able to
use the command.)
The Main Menu is the first focal point your callers will see after
they have gone through the log on screens. For the purpose of
discussion, each menu displayed will be as if the Sysop (with the
highest security level) were viewing it. In this case the Main Menu
would look like this:
9.1 MAIN MENU EXAMPLE
----------------------
>>>>>>>>> MAIN MENU <<<<<<<<<
<M>.......... Message Section <F>.............. File Section
<S>........... SPITFIRE Doors <B>................. Bulletins
<C>......... Comment To Sysop <#>....... List Active Callers
<L>.......... Locate A Caller *<W>............ Welcome Screen
<Q>....... Questionnaire Menu <T>........ This System's Info
<N>............... Newsletter <P>............ Page The Sysop
<G>........ Goodbye & Log Off <X>......... Xpert Mode Toggle
<Y>.......... Your Statistics <O>..... Other Bulletin Boards
<A>......... Add BBS Name & # <K>....... Main Menu Extension
<@>.......... Sysop Utilities <?>........ HELP With Commands
MAIN MENU - <M F S B C # L W Q T N P G X Y O A K @ ?>?
* The <W>... Welcome Screen is used for single node SPITFIRE BBS
system only. If you are operating a multi-node SPITFIRE BBS,
this is replaced with <W>........ Who's On/Node Chat.
Page 70
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
9.2 EXPLANATION OF MAIN MENU FEATURES
--------------------------------------
<M>.... Message Section
This feature takes a caller from the MAIN Section of SPITFIRE
to the MESSAGE Section.
<F>.... Files Section
This feature takes a caller from the MAIN Section of SPITFIRE
to the FILE Section.
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run on-line. Normally, but not
always, the third party program is a game. When the third
party program is finished, the caller is returned to
SPITFIRE.
<B>.... Bulletins
This feature allows a caller to read the available bulletins.
<C>.... Comment to Sysop
Allows a caller to enter a non-public message to the Sysop.
All comments are automatically saved to Message Conference
#1. However, these are marked and listed as Comment Number
<x> rather than Message Number <x>. In order for callers to
leave a comment to the Sysop, the Sysop must log onto the
BBS using the name configured as the Sysop Caller Name in the
ALT+Z configuration window. If the Sysop does not use the
name entered there for logging onto the BBS, callers will
not be able to leave a comment to the Sysop.
<#>.... List Active Callers
This feature will scroll the name and address of each caller
of this BBS. It also shows the last date each caller logged
on.
<L>.... Locate a Caller
This feature allows a caller to see if a another person is a
caller on this BBS. For example, if a caller selects this
feature, then the caller will be asked to enter either the
full or partial name of the person he/she is attempting to
locate. SPITFIRE will search for any string matching what
was entered. When a match is found, SPITFIRE will report
the find and prompt the caller as to whether this is the
person he/she was attempting to locate. If the caller
respond with a Y for Yes, SPITFIRE will notify the caller
when that person last logged onto the BBS. If the caller
responds with an N for No, SPITFIRE will continue to search
Page 71
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
the caller database, informing the caller of any match found,
prompting whether the match is the person attempting to be
located. In the event, no match is found, SPITFIRE will
inform the caller no match could be found to the full or
partial name that was entered.
<W>.... Welcome Screen (Single Node SPITFIRE BBS)
This feature allows a caller to review the opening screen.
This feature is only available on single node SPITFIRE BBS
systems. On multi-node SPITFIRE systems this option is
replaced with <W>........ Who's On/Node Chat.
<W>.... Who's On/Node Chat (Multi-node SPITFIRE BBS)
This feature will display information regarding what other
callers are currently logged on the other available nodes
and provide an option for entering into a node chat with a
caller on another node. (Refer to the Section - NODE CHAT
for a more detailed explanation of node chat). This feature
is only available on multi-node SPITFIRE BBS systems. On
single node SPITFIRE systems this option is replaced with the
<W>...Welcome Screen.
<Q>.... Questionnaire Menu
This feature presents the Questionnaire Menu to your callers.
Individual questionnaire files (SFMAIN<x>.QUE) are used to
present questions to your callers. The callers responses are
then stored in the corresponding answer file, SFMAIN<x>.ANS.
(For more information, please refer to the section, SPITFIRE
QUESTIONNAIRES of this manual.)
<T>.... This System's Info
This feature will show a caller certain information about the
BBS, such as Sysop's name, starting date of the BBS, total
number of calls received on the BBS, etc.
<N>.... Newsletter
This feature will display SFNWSLTR.BBS (your BBS newsletter)
to the caller. This can be used to keep the callers updated
with changes or news concerning your BBS.
<P>.... Page the Sysop
This feature notifies the Sysop that a caller has a question
or problem to chat about. If the Sysop is not available to
answer the page, SFUNANS.BBS/CLR is displayed to the caller.
If a caller attempts to page the Sysop a second time, and
SFPAGED.BBS/CLR is found, SFPAGED.BBS/CLR is displayed to
the caller and the Sysop is not paged a second time. If
Page 72
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SFPAGED.BBS/CLR is not found, the caller may page the Sysop
multiple times. If the Sysop has the page feature turned
off and a caller attempts to page the Sysop, SFPGOFF.BBS/CLR
is displayed to the caller.
<G>.... Goodbye & Log Off
This feature simply allows a caller to log off the BBS.
<X>.... Xpert Mode Toggle
This feature changes a caller's status from a novice to an
expert or vice versa. If a caller is set as a novice, then
the menu descriptions will scroll by after each command. If
a caller is set as an expert, then only the command letters
scroll by after each command.
<Y>.... Your Statistics
This feature displays certain statistics for the caller on
the BBS and provides a menu which gives the caller the
opportunity to change some information pertaining to them.
The screen and the information that can be changed are
explained below:
>>>>>> JUST FOR YOUR INFORMATION <<<<<<
Your Name : John Doe Security Level : 10
Last Time On : 03-20-92 13:04 Number Of Times On : 127
Birthdate : 01-20-54 Times On Today : 1
Files Uploaded : 19 Files Downloaded : 53
K Uploaded : 122 K Downloaded : 2631
Original Log On : 05-23-90 Subscription Date : N/A
Node Chats Left : 5
>>>>>>>> THINGS YOU CAN CHANGE <<<<<<<<
<W> Address : Peoria, IL <H> Hot Key : On
<#> Phone Number : 555-151-5555 <D> Display Size : 80X24
<S> Scroll Prompt : On <A> ANSI On/Off : On
<F> File Transfer : 1k-Xmodem <M> More Prompt : On
<P> Password : SPITFIRE <C> Change Color : 36
<Q> Quit
CHANGE MENU - [W S # H C A D M P F Q] ?
Command <W> - Provides the caller with an opportunity to change their
address. The caller is prompted to enter both the city
and state. SPITFIRE will then redisplay what they have
entered to verify the changes before saving the new
information.
Page 73
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <S> - Allows the caller to toggle SPITFIRE's Scroll Back
option On and Off. The scroll back feature is used in
connection with the display of the "< ENTER >"/"More,
Continue" prompts. If the scroll back feature is toggled
on, when the prompt is displayed and the caller enters a
keystroke to continue, the message will scroll back and
disappear from the screen. If the scroll back feature is
off, the "< ENTER >" or "More, Continue" prompt remains
displayed on the screen.
Command <#> - Allows the caller to change their phone number.
Command <H> - This feature allows the caller to toggle the Hot Key
within SPITFIRE. If toggled On, when entering the
command character of a menu, a return is entered
automatically and the command is immediately executed.
When toggled off, the caller is required to press the
<ENTER> key before the command is executed.
Command <C> - Allows the caller to select their default color settings.
The caller may select 31 through 36. The colors
associated with the numeric value are as follows:
31 - Red 32 - Green 33 - Yellow 34 - Blue
35 - Magenta 36 - Cyan 37 - White
Command <A> - Allows the caller to toggle ANSI color on and off.
Command <D> - Allows the caller to set the screen display size. When
this feature is selected, the caller is prompted to
enter a new line length. Acceptable values for the
line length range from 40 to 144. Next, the caller
is prompted to enter a new page length. Acceptable
values for the page length range from 10 to 80. The
page length determines when the "More, Continue" prompt
will display. For example, if the page length is 80,
the prompt will display after every 80 lines.
Command <M> - This toggles the More Prompt On and Off. When toggled
On, each time a complete screen display is received,
either the "< ENTER >" or "More, Continue" prompt is sent
and the display is paused until a keystroke is entered
signaling the display to continue. If the More Prompt is
toggled Off, the "< ENTER >"/"More, Continue" prompt will
not display and information will continue to scroll
without being paused.
Page 74
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Command <P> - Allow the caller the opportunity to change their log on
password.
Command <F> - Allow the caller to select their default file transfer
protocol. The caller may select from:
<1> Ascii
<2> Xmodem Checksum
<3> Xmodem CRC
<4> 1k-Xmodem
<5> SEAlink Derived
<T> Telink
<S> Select at time of transfer
Selecting any option other than <S>, Select at time of
transfer, causes the external protocol options to be
unavailable to the caller. SFPROMSG.BBS/CLR is used
to inform the caller of this when selecting a default
file transfer.
Command <Q> - Returns the caller to the Main Menu
<O>.... Other Bulletin Boards
This feature will display SFBBSLST.DAT, a listing of names,
bps rate and phone numbers of other Bulletin Boards.
<A>.... Add BBS Name & #
This feature allows a caller to add the name, bps rate and
phone number of other bulletin board systems to the BBS list,
SFBBSLST.DAT. When adding a BBS to SFBBSLST.DAT, the number
is recorded in the caller's log to provide the Sysop a means
of tracing who entered the listing.
<K>.... Main Menu Extension
This command can be set to the run a third party program
configured by the Sysop. It is set up using the necessary
commands to execute the desired option within the SFMAIN.BAT
file. It should be noted that Sysops will need to use the
SFHELP.EXE utility to modify the SPITFIRE.HLP file so it
properly explains the added option.
<@>.... Sysop Utilities
This feature takes a caller from the MAIN Section to the
SYSOP section. The BBS is maintained from the SYSOP Section.
This feature is not normally available to most callers.
<?>.... HELP with Commands
This feature will provide help for each command available
from the MAIN MENU.
Page 75
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
10.0 MESSAGE SECTION EXPLAINED
-------------------------------
The Message Menu is the point from which your callers take part
in mail exchange. The Message Menu may be selected from either the
Main Menu or the File Menu with the <M>...Message Section command
option.
As the Message Menu is described and the features explained,
please keep in mind that you can control the usage of each command by
changing the security level of the commands. In other words, you can
control what commands are available to what callers. For the purpose
of discussion, however, each menu displayed will be as if the Sysop
(with the highest security level) is viewing it. In this case the
Message Menu would look like this.
10.1 MESSAGE MENU EXAMPLE
--------------------------
>>>>>>>> MESSAGE MENU <<<<<<<<
<C>. Change Message Conference <R>............. Read Messages
<H>....... Hurry Scan Messages <B>........... Browse Messages
<N>.. Non-stop Message Capture <E>........... Enter A Message
<Y>............. Your Messages <A>........Alter Message Queue
<T>............... Text Search <F>.............. File Section
<P>............ Page The Sysop <Q>......... Quit To MAIN MENU
<S>.... SPITFIRE Doors Section <G>......... Goodbye & Log Off
<X>......... Xpert Mode Toggle <K>.... Message Menu Extension
<@>........... Sysop Utilities <?>........ HELP With Commands
MESSAGE MENU - <C R H B N E Y A T F P Q S G X K @ ?>?
10.2 MESSAGE MENU EXPLANATION
------------------------------
<C>.... Change Message Conference
This feature allows a caller to change to a different Message
Conference by entering the number of the Message Conference
he/she wishes to change to. If a caller selects <Q>uit, the
caller will remain in the current Message Conference. If a
caller presses the ENTER key, SPITFIRE will list the Message
Conferences available to the caller. If a MGLST<x>.BBS/CLR
is found it will be displayed here. After changing to a new
message conference, SPITFIRE will prompt the caller as to
whether he/she would like to read message in the conference
they have changed to.
Page 76
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<R>.... Read Messages
This feature allows the caller to read public messages and
non-public messages sent to and/or from the caller in
specified Message Conferences. The caller is presented with
five options and may elect to read:
<T>...This Message Conference
This option allows the caller to read available
messages in the current Message Conference.
<A>...All Message Conferences
This option allows the caller to read available
messages in all Message Conferences to which the
caller has access.
<O>...Only Queued Conferences
This option allows the callers to read available
messages in the Message Conferences the callers have
selected to be included in their Message Queue.
<S>...Set Conference Queue
When this option is selected, SPITFIRE will display
a list of all conferences contained in the caller's
message queue and prompt the caller as to whether to
change the current queue. If the caller selects to
change the queued message conferences, the Message
Queue Menu is displayed. For more information on
the Message Queue Menu, refer to Command <A>..Alter
Message Queue discussed below.
<Q>...Quit
This option will return the caller to the Message Menu.
During the process of reading messages, the caller will have
the following commands available to them, provided the
command is a viable option at the time. If it is not a
viable option, the command will not be shown to the caller.
<R>...Reply
Allows the caller to reply to an existing message.
When replying to a message, SPITFIRE will prompt the
caller as to whether they wish to change the message
subject. If the caller responds with a "Y", the caller
is given the opportunity to change the message subject.
If the caller responds with a "N", the message subject
remains the same as the original message. Replies to
messages with the same message subject allows the
Page 77
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
messages to be threaded together. The caller is also
prompted whether the reply should be made public
if the Message Conference allows non-public messages.
When replying to a message the caller may use the
combination CTRL+Q keys to Review/Quote Original
Message. The original message is redisplayed and
the caller is prompted to enter the line numbers
for the range of lines which he/she desires to quote.
This range is then included in their reply message
with the initials from the author of the original
message preceding each line, as such:
MW> SPITFIRE is the best BBS software available!
A quoted portion of a reply cannot be edited.
If the person replying to the message is logged on
locally, another option, the CTRL+F will allow an
existing text file to be imported into the reply.
When the CTRL+F - Import File! feature is selected,
SPITFIRE will prompt you for the path and filename
of the file to be imported. In the event, a filename
is not entered, SPITFIRE will look in the Work
directory for a file named SFMSG.TXT and import this
if it is found. If after pressing the CTRL+F keys
you decide you do not want to import a file, simply
enter a non-existent path at the prompt to abort the
process.
<D>...Delete
This option will be available only if 1) The caller has
Sysop security or; 2) If the Message Conference has
been configured to allow the caller the ability to
delete messages and the message is either being sent to
or by the caller. Deleting a message makes it
unavailable except to those with Sysop security and
will cause it to be purged from the message base the
next time the message base is packed.
<N>...Non-stop
This feature will display all appropriate messages
nonstop.
<E>... Enter A Message
This feature allows a caller to enter a message. If
the message the caller enters is not to a specific
person, then SPITFIRE addresses the message to "All
Page 78
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Callers". If the message is to a specific person and
that person is not a caller of this BBS, then SPITFIRE
will not allow the caller to enter the message unless
the BBS has been configured to allow net-mail and the
specific Message Conference has been toggled to allow
net-mail. Callers are allowed to send carbon copies of
a message to other callers. There are a total of nine
carbon copies available. SPITFIRE will automatically
prevent duplicating carbon copy messages to callers
already receiving the message. There are a total of
99 lines per message. When entering (or responding)
to a message, SPITFIRE will display the Message
Conferences available to the caller and whether the
specific Message Conference allows public or public
and non-public messages. Pressing ENTER twice when
prompted for the message subject will abort the
message.
If the person entering the message is logged on
locally, another option, the CTRL+F will allow an
existing text file to be imported into the reply.
When the CTRL+F - Import File! feature is selected,
SPITFIRE will prompt you for the path and filename
of the file to be imported. In the event, a filename
is not entered, SPITFIRE will look in the Work
directory for a file named SFMSG.TXT and import this
if it is found. If after pressing the CTRL+F keys
you decide you do not want to import a file, simply
enter a non-existent path at the prompt to abort the
process.
<ENTER>... Next Message
Pressing the enter key will cycle the caller to the
next available message to be read.
<#>... Number Of An Existing Message In This Conference
Entering a number of a specific message that is
available in the conference will cause that message
to be displayed.
<F>... Follow Msg Thread
Allows the caller to simultaneously read messages
which are threaded together by a common Message
Subject. When this option is selected the following
menu is displayed:
>>>> MESSAGE THREAD MENU <<<<
<S>........ Start Of Thread
<F>........... Forward Read
<B>.......... Backward Read
<E>.... Exit Message Thread
Page 79
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<S>...Start Of Thread will take the caller to the first
message containing the common message subject
which threads the messages together.
<F>...Forward Read will cycle through the threaded
messages in forward order one message at a time.
<B>...Backward Read will cycle through the threaded
messages in reverse order one message at a time.
<E>...Exit Message Thread will return the caller to the
original message from where the Threaded Message
Menu was activated.
<P>... Public
Allows a caller with Sysop security to toggle a public
message to non-public or to toggle a non-public message
to public.
<U>...Undelete
Allows a caller with Sysop security to undelete a
deleted message, making it available once again.
<X>...Xport
This feature is only available when a caller is logged
on locally. When selected, SPITFIRE checks to see if
a printer is attached and ready for printing. If so,
SPITFIRE provides the option of exporting the message
to the printer or saving it to a text file on disk.
If no printer is attached or it is not ready for
printing, the message is saved as a text file in the
directory designated as the Message file path. The
format for the file name it is saved to is:
MSG+message#.conference#. In other words, if
message 15 of conference 3 was Xported, it would be
saved as MSG15.3.
<C>...Copy
This feature is only available to a caller with Sysop
security. This feature actually serves two purposes.
First, it allows the caller to move the message to
another message conference. SPITFIRE will inform the
caller to whom the message is currently addressed and
prompt if this should be changed, thus, also allowing
the message to be forwarded to another caller.
<Q>...Quit
Returns the caller to the Message Menu.
Page 80
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<H>.... Hurry Scan Messages
This feature allows a caller to scan messages in a specific
Message Conference or in all Message Conferences. This scan
doesn't provide as much information regarding the messages
as the <B>rowse Messages feature.
<B>.... Browse Messages
This feature allows a caller to scan messages in a specific
Message Conference or in all Message Conferences. This
scan provides the caller with more information regarding the
messages than the <H>urry Scan Messages feature.
<N>.... Non-stop Message Capture
When this feature is executed, SPITFIRE will display all
appropriate messages non-stop. The caller normally uses
some means to capture the messages for later reading or
printing.
<E>.... Enter A Message
This feature allows a caller to enter a message. If the
message the caller enters is not to a specific person, then
SPITFIRE addresses the message to "All Callers". If the
message is to a specific person and that person is not a
caller of this BBS, then SPITFIRE will not allow the caller
to enter the message unless the BBS has been configured as a
net-mail message base and the specific Message Conference
has been toggled to allow net-mail. Callers are allowed to
send carbon copies of a message to other callers. There are
a total of nine carbon copies available . SPITFIRE will
automatically prevent duplicating carbon copy messages to
callers already receiving the message. There are a total of
99 lines per message. When entering a message, SPITFIRE
will ask what conference you would like the message saved
to. Pressing Enter selects the current Message Conference,
<L>... will list all the available Message Conferences or
you may select <Q>... to quit. If the Message Conference
you select allows non-public messages, SPITFIRE will prompt
you as to whether the message you are entering should be
saved as a public message. Pressing ENTER twice when
prompted for the message subject will abort the message.
If the person replying to the message is logged on locally,
another option, the CTRL+F will allow an existing text file
to be imported into the reply. When the CTRL+F - Import
File! feature is selected, SPITFIRE will prompt you for the
path and filename of the file to be imported. In the event,
a filename is not entered, SPITFIRE will look in the Work
Page 81
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
directory for a file named SFMSG.TXT and import this if it is
found. If after pressing the CTRL+F keys you decide you do
not want to import a file, simply enter a non-existent path
at the prompt to abort the process.
<Y>.... Your Messages
This feature will display the caller's message statistics.
The caller receives a report on the number of new messages
they have waiting to be read, the number of messages they
have already received, the number of messages the caller
has sent and the total number of messages available on
the BBS. The caller is then prompted if they would like
to read their messages.
*NOTE* If the caller is recognized as the Sysop of the BBS, he/she
will also be prompted as to whether he/she would like to
preview messages. If the Sysop replies with a Yes, SPITFIRE
allows you to read your messages, but does not mark them
as being received. (For more information on the Message
Preview feature, refer to section SPECIAL COMMANDS FOR
SYSOP of this manual.)
<A>.... Alter Message Queue
This feature allows a caller to include specific message
conferences in his/her message conference queue. Conferences
not included in the caller's message queue will be ignored.
When a caller selects the <A>...Alter Message Queue option,
the caller is presented with the following sub-menu:
>>>> MESSAGE QUEUE MENU <<<<
<A>...... Add A Conference <C>....... Current Queue List
<D>... Delete A Conference <I>.. Include All Conferences
<L>.. List Msg Conferences <R>... Remove All Conferences
<S>.... Select Conferences <Q>..... Quit To Message Menu
<A>...Add A Conference allows a caller to enter a
specific number corresponding to the Message
Conference number the caller wishes to have added
to their message conference queue.
<D>...Delete A Conference allows a caller to enter a
specific number corresponding to the Message
Conference number the caller wishes to have
deleted from their message conference queue.
<L>...List Msg Conferences will display all message
conferences on the BBS to which the caller
has access.
Page 82
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<S>...Select Conferences will individually display all
message conferences on the BBS to which the
caller has access and prompt the caller as to
whether to include the conference in their
message conference queue.
<C>...Current Queue List will display to the caller the
message conferences currently contained
in their message conference queue.
<I>...Include All Conferences will place all available
message conferences in the caller's message
queue.
<R>...Remove All Conferences will remove all message
conferences from the caller's message queue with
the exception of the first Message Conference.
SPITFIRE requires that all callers have Message
Conference 1 in their queue.
<Q>...Quit To Message Menu will return the caller to
the Message Menu.
** SPECIAL NOTES ABOUT QUEUED CONFERENCES **
Conferences not included in the caller's queue will not be
scanned when SPITFIRE scans for new messages. For this
reason, when a caller attempts to leave a message to another
caller in a message conference that the caller does not have
selected in their queue, SPITFIRE will not allow the caller
to send the message. Also, a caller may delete any message
conference from their message queue, except for the first
message conference. The first message conference will remain
active to all callers.
<T>.... Text Search
This feature allows a caller to search for specific text in a
message. SPITFIRE supports a multi-word text search of up to
6 key words at one time. The text search only searches the
current Message Conference, for messages sent to or from the
caller and public messages. When the text is found in a
message, SPITFIRE will display the subject of the message.
<F>.... File Section
This feature takes the caller from the MESSAGE Section of
SPITFIRE to the FILE Section.
Page 83
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<P>.... Page the Sysop
This feature notifies the Sysop that a caller has a question
or problem to chat about. If the Sysop is not available to
answer the page, SFUNANS.BBS/CLR is displayed to the caller.
If a caller attempts to page the Sysop a second time, and
SFPAGED.BBS/CLR is found, SFPAGED.BBS/CLR is displayed to
the caller and the Sysop is not paged a second time. If
SFPAGED.BBS/CLR is not found, the caller may page the Sysop
multiple times. If the Sysop has the page feature turned
off and a caller attempts to page the Sysop, SFPGOFF.BBS/CLR
is displayed to the caller.
<Q>.... Quit To MAIN MENU
This feature takes a caller from the MESSAGE Section of
SPITFIRE to the MAIN Section.
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run on-line. Normally, but not
always, the third party program is a game. When finished
with the third party program, the caller is returned
to SPITFIRE.
<X>.... Xpert Mode Toggle
This feature changes a caller's status from novice to expert
or vice versa. If a caller is set as a novice, then the menu
descriptions will scroll by after each command. If a caller
is set as expert, then only the command letters scroll by
after each command.
<K>.... Message Menu Extension
This command can be used to run third party programs which
are configured by the Sysop. It is set up by including the
necessary commands to execute the desired option within the
SFMESS.BAT file. It should be noted that Sysops will need
to use the SFHELP.EXE utility to modify the SPITFIRE.HLP
file so it properly explains the added option.
<G>.... Goodbye & Log Off
This feature simply allows a caller to log off the BBS.
<@>.... Sysop Utilities
This feature takes a caller from the MESSAGE Section to the
SYSOP Section. The BBS is maintained from the SYSOP Section.
<?>.... HELP With Commands
This feature will provide help for each command available
from the MESSAGE MENU.
Page 84
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
11.0 FILE SECTION EXPLAINED
----------------------------
It is from the File Menu that all file related activity is
accessed. The File Menu may be selected from either the Main
Menu or the Message Menu with the <F>...File Section command option.
The Sysop has the ability to control which features are available to
the callers by adjusting the security level within the SFFILE.MNU
For the purpose of discussion, each menu displayed will be as if the
Sysop (with the highest security level) were viewing it. In this case,
the File Menu would look like this:
11.1 FILE MENU EXAMPLE
-----------------------
>>>>>>>>> FILE MENU <<<<<<<<<
<C>......... Change File Area <L>.. List Files In This Area
<E>............. Erase A File <G>........ Goodbye & Log Off
<D>.......... Download A File <U>............ Upload A File
<H>.. Help On Upload/Download <P>........... Page The Sysop
<M>.......... Message Section <Q>........ Quit To MAIN MENU
<S>........... SPITFIRE Doors <N>................ New Files
<T>.. Text Search Description <F>.............. Find A File
<X>........ Xpert Mode Toggle <?>....... HELP With Commands
<K>..... File Menu Extension <@>.......... Sysop Utilities
<V>...... View A File Archive <R>......... Read A Text File
FILE MENU - <C L E G D U H P M Q S N T F X ? K @ V R>?
11.2 FILE MENU EXPLANATION
---------------------------
<C>.... Change File Area
This feature allows a caller to change to a different File
Area. If <Q>uit is selected, the caller remains
in the current File Area. If the ENTER key is pressed,
SPITFIRE will list the File Areas available to the caller.
<L>.... List Files In This Area
This displays the files (SFFILES.BBS) in the current
File Area that are available for the caller to download.
When listing files, SPITFIRE offers file tagging for ease
of downloading. SPITFIRE precedes each file in the list
with an alphanumeric character. As each screen completes
displaying, the caller is prompted to enter the alpha
character(s) associated with a file(s) to be downloaded.
When the file download transfer is begun, SPITFIRE
Page 85
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
automatically inserts the name of the file(s) tagged
for downloading.
<E>.... Erase A File
This feature allows callers to erase a file from a File Area.
Normally this feature is only available to callers with Sysop
security. When erasing a file from the file menu, SPITFIRE
prompts you as to whether you wish the file to be added to
SFNOUP.DAT. Responding with a Y for Yes adds the erased
file's name to SFNOUP.DAT.
<G>.... Goodbye & Log Off
This feature simply allows a caller to log off the BBS.
<D>.... Download A File
This feature allows a caller to download a file, provided the
caller hasn't exceeded the maximum daily download limit and
the caller has enough time left to make the download. The
caller does not have to be in any specific File Area to
perform a download. If the caller starts a download while in
a File Area marked as a CD-ROM File Area and the file to be
downloaded isn't found in that area, SPITFIRE asks the caller
whether to search the other File Areas. SPITFIRE allows the
caller to automatically log off after the completion of the
download by placing a backslash "\" after the name of the
file to be downloaded. Upon completing a download, SPITFIRE
notifies the caller of the number of downloads he/she has
remaining for the day.
When the caller is prompted for the name of the file to
download, if the filename and period is input, SPITFIRE
automatically adds the ZIP extension. If, for example,
SF32. is entered, SPITFIRE initiates the download of
SF32.ZIP. If the period is not added, SPITFIRE does
not add the file extension.
When the Download A File option is selected by a caller who
is logged on locally, the IMPORT/EXPORT Menu is displayed.
The ANSI/non-ANSI screen for this menu, SFIMPEXP.BBS/CLR,
is displayed if found. Otherwise, the following default
SPITFIRE menu is displayed:
>>>> IMPORT/EXPORT MENU <<<<
<I>...... Import A File <E>............ Export A File
<R>...... Remove A File <T>.. Text Search Description
<F>........ Find A File <L>... List Files (This Area)
<C>... Change File Area <Q>........ Quit To File Menu
<G>... Goodbye & Log Off
ENTER COMMAND <I E R T F L C Q G ?>
Page 86
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<I>... Import A File
Allows a file to be added to copied from another
drive and/or directory to a SPITFIRE file area.
SPITFIRE prompts the caller to enter the path
name of the file to be copied and also prompts
for a description of the file being copied. The
filename, size, date and description of the file
being copied is added to the SFFILES.BBS for the
file area the file is being copied to.
<E>... Export A File
Allows a file to be copied to a drive and/or
directory not set up as a SPITFIRE file area.
The caller is prompted for the name of the
file to be copied and the path to which the
file will be copied to.
<R>... Remove A File
Allows a file to be erased from the SPITFIRE
file area and removed from the appropriate
SFFILES.BBS. When a file is removed, the
caller is prompted as to whether the file should
be added to SFNOUP.DAT.
<T>... Text Search Description
Allows a caller to search for certain text within
a file description. The caller can search in a
specific File Area or in all File Areas. This
feature ONLY searches the file description and not
the file name, date or size. However, when the
matching text is located, these are displayed.
<F>... Find A File
Allows a caller to search a specific File Area or all
File Areas for a specific file. Wildcards are
allowed, with the exception of *.*. If a caller
enters a file name without the file extension,
SPITFIRE automatically adds a ".*" to the file name.
If there is a match, the file name, size, date and
description are shown, provided the file is
listed in the SFFILES.BBS.
<L>... List Files (This Area)
Displays the SFFILES.BBS for the current file
area that is available for the caller to download.
When listing files, SPITFIRE offers file tagging
for ease of downloading. SPITFIRE precedes each
file in the list with an alphanumeric character. As
Page 87
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
each screen completes displaying, the caller is
prompted to enter the alpha character(s) associated
with a file(s) to be downloaded. When the caller
begins the file download transfer, SPITFIRE
automatically inserts the name of the file(s) the
caller has tagged for downloading.
<C>... Change File Area
Allows a caller to change to a different File Area.
If the caller selects <Q>uit, the caller remains
in the current File Area. If the caller presses the
ENTER key, SPITFIRE lists the File Areas that are
available to the caller.
<Q>... Quit To File Menu
Allows the caller to exit the IMPORT/EXPORT Menu and
return to the File Menu.
<G>... Goodbye & Log Off
Allows the caller to log off the BBS.
<U>.... Upload A File
This feature simply allows a caller the opportunity to upload
a file. The caller can be compensated additional time on the
BBS for the upload. The amount of the additional time is set
by the Sysop. SPITFIRE allows the caller to automatically
log off after the completion of the upload by placing a
backslash, "\", after the name of the file to be uploaded.
By using a forward slash, "/", at the beginning of the file
description, a caller can upload a file for Sysop only. When
a file is uploaded for Sysop only, the Sysop is notified in
HEYSYSOP.LOG.
After the name of the file to be uploaded is entered,
SPITFIRE prompts the caller to stand by while it
checks to see if the file already exists. While checking
for the file, SPITFIRE checks for the same file with
a different extension. For example, if a caller attempts
to upload SF32.PAK and SF32.ZIP is found, the caller is
be notified of the existing file and is queried as to
whether the upload should be continued. If the Sysop
has toggled the Comprehensive Upload Search to On
(ALT+T configuration), during the search, SPITFIRE removes
any trailing digits from the file name. If a caller
attempts to upload SF31.ZIP and SF32.ZIP was found, the
caller is notified of the existing file and queried as to
whether the upload should be continued.
Page 88
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
When the Upload A File option is selected by a caller who
is logged on locally, the IMPORT/EXPORT Menu is displayed.
The ANSI/non-ANSI screen for this menu, SFIMPEXP.BBS/CLR,
is displayed if found. Otherwise, the following default
SPITFIRE menu is displayed:
>>>> IMPORT/EXPORT MENU <<<<
<I>...... Import A File <E>............ Export A File
<R>...... Remove A File <T>.. Text Search Description
<F>........ Find A File <L>... List Files (This Area)
<C>... Change File Area <Q>........ Quit To File Menu
<G>... Goodbye & Log Off
ENTER COMMAND <I E R T F L C Q G ?>
<I>... Import A File
Allows a file to be added to copied from another
drive and/or directory to a SPITFIRE file area.
SPITFIRE prompts the caller to enter the path
name of the file to be copied and also prompts
for a description of the file being copied. The
filename, size, date and description of the file
being copied is added to the SFFILES.BBS
for the file area the file is being copied to.
<E>... Export A File
Allows a file to be copied to a drive and/or
directory not set up as a SPITFIRE file area.
The caller is prompted for the name of the
file to be copied and the path to which the
file will be copied to.
<R>... Remove A File
Allows a file to be erased from the SPITFIRE
file area and removed from the appropriate
SFFILES.BBS. When a file is removed, the
caller is prompted as to whether the file should
be added to SFNOUP.DAT.
<T>... Text Search Description
Allows a caller to search for certain text within
a file description. The caller can search in a
specific File Area or in all File Areas. This
feature ONLY searches the file description and not
the file name, date or size. However, when the
matching text is located, these are displayed.
<F>... Find A File
Allows a caller to search a specific File Area or all
File Areas for a specific file. Wildcards are
Page 89
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
allowed, with the exception of *.*. If a caller
enters a file name without the file extension,
SPITFIRE automatically adds a ".*" to the file name.
If there is a match, the file name, size, date and
description are shown, provided the file is listed
in the SFFILES.BBS.
<L>... List Files (This Area)
Displays the SFFILES.BBS for the current file
area that is available for the caller to download.
When listing files, SPITFIRE offers file tagging
for ease of downloading. SPITFIRE preceeds each
file in the list with an alphanumeric character. As
each screen completes displaying, the caller is
prompted to enter the alpha character(s) associated
with a file(s) to be downloaded. When the caller
begins the file download transfer, SPITFIRE
automatically inserts the name of the file(s) the
caller has tagged for downloading.
<C>... Change File Area
Allows a caller to change to a different File Area.
If the caller selects <Q>uit, the caller will remain
in the current File Area. If the caller presses the
ENTER key, SPITFIRE lists the File Areas that are
available to the caller.
<Q>... Quit To File Menu
Allows the caller to exit the IMPORT/EXPORT Menu and
return to the File Menu.
<G>... Goodbye & Log Off
Allows the caller to log off the BBS.
<H>.... Help On Upload/Download
This feature describes the various file transfer
protocols available to the caller. The help information
comes from SFPROTCO.HLP and may be edited with your
favorite text editor, provided it saves in ASCII format.
<P>.... Page The Sysop
This feature notifies the Sysop that a caller has a question
or problem to chat about. If the Sysop is not available to
answer the page, SFUNANS.BBS/CLR is displayed to the caller.
If a caller attempts to page the Sysop a second time, and
SFPAGED.BBS/CLR is found, SFPAGED.BBS/CLR is displayed to
the caller and the Sysop is not paged a second time. If
SFPAGED.BBS/CLR is not found, the caller may page the Sysop
Page 90
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
multiple times. If the Sysop has the page feature turned
off and a caller attempts to page the Sysop, SFPGOFF.BBS/CLR
is displayed to the caller.
<M>.... Message Section
This feature takes a caller from the FILE Section of SPITFIRE
to the MESSAGE Section.
<Q>.... Quit To Main Menu
This feature takes a caller from the FILE Section of SPITFIRE
to the MAIN Section.
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run on-line. Normally, but not
always, the third party program is a game. When finished
with the third party program, the caller is returned to
SPITFIRE.
<N>.... New Files
This feature allows a caller to search a specific File Area
or all File Areas since a specific date or since the last
time the caller searched for new files. In addition to
listing the new files, a file statistics message is
displayed to the caller with the number of new files
received since last checked, the total number of files
available for download on the BBS and the number of bytes
of downloadable files which exist on the BBS. SPITFIRE does
not include any CD-ROM File Areas in the search for new
files. SPITFIRE does not report file statistics on a BBS
containing CD-ROM File Area(s) since the statistics are not
accurate due to skipping the CD-ROM File Area(s).
When listing new files, SPITFIRE offers file tagging
for ease of downloading. SPITFIRE precedes each file in
the list with an alphanumeric character (with the exception
of S which is used to Stop the file display). As each screen
completes displaying, the caller is prompted to enter
the alpha character(s) associated with a file(s) to be
downloaded. When the caller begins the file download
transfer, SPITFIRE automatically inserts the name of the
file(s) the caller has tagged for downloading.
<T>.... Text Search
This feature allows a caller to search for certain text
within a file description. SPITFIRE supports multi-word text
searches and allows up to 6 key words to be searched for at
one time. The caller can search a specific File Area or all
Page 91
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
File Areas. Please note that this feature searches ONLY the
file description and not the file name, date or size. These
are displayed, however, when the matching text is located.
<F>.... Find A File
This feature allows a caller to search a specific File Area
or all File Areas for a certain file. Wildcards are allowed,
with the exception of *.*. If a caller enters a file name
without the file extension, SPITFIRE automatically adds a
".*" to the file name. If there is a match, the file name,
size, date and description are shown, provided the file
is listed in the SFFILES.BBS.
<X>.... Xpert Mode Toggle
This feature changes a caller's status from a novice to an
expert or vice versa. If a caller is set as a novice, then
the menu descriptions scroll by after each command. If
a caller is set as an expert, then only the command letters
scroll by after each command.
<?>.... HELP With Commands
This feature displays help for each command available
from the FILE MENU. This feature is augmented with
SFHELP.EXE, which creates separate help screens for each
individual command. For more information on SFHELP.EXE,
consult the documentation accompanying it. This program is
available for download on Buffalo Creek's BBS.
<K>.... File Menu Extension
This command can be used to run third party programs which
are configured by the Sysop. It is set up by including the
necessary commands to execute the desired option within the
SFMESS.BAT file. It should be noted that Sysops need to
use the SFHELP.EXE utility to modify the SPITFIRE.HLP file
so it properly explains the added option.
<@>.... Sysop Utilities
This feature takes a caller from the FILE Section to the
SYSOP Section. The BBS is maintained from the SYSOP Section.
This feature is not normally available to most callers.
<V>.... View A File Archive
This feature allows a caller to view the contents of a ZIP
file. The caller sees the file name, file size and file
date of each file within the compressed ZIP file. The caller
does not have to be in a specific file area to utilize this
feature.
Page 92
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<R>.... Read A Text File
This feature allows a caller to read a text file available
for download. The caller may want to use this feature and
simply capture the text to save downloading the file. The
caller does not have to be in a specific File Area to utilize
this feature.
11.3 UPLOAD/DOWNLOAD PROTOCOLS
-------------------------------
The following is a list of Upload & Download protocols available
by SPITFIRE:
1) Ascii
2) Xmodem Checksum
3) Xmodem CRC
<* D/L only> 4) 1K-Xmodem <Ymodem>
5) SEAlink Derived
6) Telink
* 7) Ymodem Batch
* 8) SEAlink Derived Batch
9) Ymodem-g <Error-correction modems>
* 10) Ymodem-g Batch <Error-correction modems>
SPITFIRE does not allow a caller to download files with a .COM,
.EXE, .ARC, .ARJ, ZIP, or PAK extension when using the ASCII transfer
protocol.
Batch transfers using the External Protocol drivers are supported
by SPITFIRE. (For more information refer to the section - EXTERNAL
FILE TRANSFER PROTOCOLS - of this manual.)
11.4 BATCH DOWNLOAD MENU
------------------------
In order for the Batch Download Menu to be displayed the caller
must have selected to download a file from the File Menu and then
selected a file transfer protocol that is capable of doing batch
downloads. It is possible for a caller to do a batch download without
ever having the Batch Download Menu displayed to them. The Batch
Download Menu is displayed if, after filling their batch queue, the
caller responds "N" when prompted as to whether to begin the batch
transfer now or if when their batch queue is empty and the caller
presses return when asked to enter the name of the file to be
downloaded.
Page 93
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
The SPITFIRE default Download Batch Menu looks like this:
>>>> BATCH DOWNLOAD MENU <<<<
<A>...... Add To Batch Queue <V>..View Tagged/Queued List
<D>.... Download Batch Queue <R>... Remove File From List
<S>... Start New Batch Queue <L>.. List Files (This Area)
<C>........ Change File Area <Q>....... Quit To File Menu
<?>.................... Help <G>....... Goodbye & Log Off
BATCH MENU - [A V D R S L C Q ? G]?
<A>... Add To Batch Queue
This feature allows the caller to enter the name of the
files(s) to be added to the batch queue. SPITFIRE does not
allow the caller to exceed their daily download limit or time
limit.
<V>... View Tagged/Queued List
This feature allows the caller to review the file(s) they have
tagged or added to the batch queue. SPITFIRE also informs the
caller of the approximate time required for the file transfer
of each file, as well as the total approximate time to transfer
the entire batch queue.
<D>... Download Batch Queue
This feature simply starts the batch download provided the
caller has files to download listed in the batch queue. Before
the download(s) are started, the caller is prompted as to
whether they wish to log off when the transfer is finished. If
the answer is Yes, SPITFIRE automatically logs the caller
off after the download(s) are complete.
<R>... Remove File From List
If the caller changes his/her mind about including a
file in their list of files to download, this feature allows
removal of that file from the list.
<S>... Start New Batch Queue
In the event the caller decides to start over, this feature
allows the caller to clear all file names currently contained
in the batch queue.
<L>... List Files (This Area)
This feature displays the files in the current File Area
which are available for the caller to download. The file's
name, file size, file date and a brief description of the
file are displayed to the caller.
Page 94
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<C>... Change File Area
This feature allows the caller to change to a different File
Area. If the caller selects <Q>uit, the caller remains in
the present File Area. If the caller presses the [ENTER] key,
SPITFIRE lists the File Areas available to the caller. If
a number corresponding to an available File Area is entered,
SPITFIRE makes that File Area the current File Area.
<Q>... Quit To File Menu
This feature takes the caller from the Batch Section of
SPITFIRE to the File Section of SPITFIRE. If this is selected,
the caller's batch queue is cleared.
<?>... Help
This feature offers a brief description of the various
commands available from the Batch Download Menu.
<G>... Goodbye & Log Off
This feature simply allows the caller to log off the BBS.
11.5 BATCH UPLOAD MENU
----------------------
For the Batch Upload Menu to be displayed, the caller must
select to upload a file from the File Menu and select a file
transfer protocol that is capable of doing batch file transfers.
It is possible for a caller to do a batch upload without ever having
the Batch Upload Menu displayed to them. The Batch Upload Menu is
displayed if, after filling their batch queue, the caller responds
"N" when prompted as to whether to begin the batch transfer now or
if when their batch queue is empty and the caller presses return
when asked to enter the name of the file to be uploaded.
SPITFIRE's default Upload Batch Menu looks like this:
>>>>> BATCH UPLOAD MENU <<<<<
<A>...... Add To Batch Queue <W>... What's In Batch Queue
<U>...... Upload Batch Queue <R>.. Remove File From Queue
<S>... Start New Batch Queue <L>.. List Files (This Area)
<C>........ Change File Area <Q>....... Quit To File Menu
<?>.................... Help <G>....... Goodbye & Log Off
BATCH MENU - [A W U R S L C Q ? G]?
<A>... Add To Batch Queue
This feature allows the caller to enter the name of the
files(s) to be added to the batch queue. SPITFIRE prompts
the caller to enter the file name and a description of the
file to be uploaded.
Page 95
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<W>... What's In Batch Queue
This feature allows the caller to review the file(s) that have
been added to the batch queue. SPITFIRE displays the
file name(s) and a brief description of the files currently
contained in the batch queue.
<D>... Upload Batch Queue
This feature simply starts the batch upload provided that the
caller has files to upload listed in the batch queue. Before
the upload(s) are started, the caller is prompted as to
whether they wish to log off when the transfer is finished. If
the answer is <Y>es, SPITFIRE automatically logs the caller
off after the upload(s) are complete. If the caller fails to
provide a description for a file in a batch upload, SPITFIRE
provides a default description: "No Description Provided".
<R>... Remove File From Queue
This feature allows a caller to remove a file from the
batch queue if the caller changes their mind as to
whether a file should be included.
<S>... Start New Batch Queue
In the event the caller decides to start over, this feature
allows the caller to clear all file names currently contained
in the batch queue.
<L>... List Files (This Area)
This feature displays the files in the current File Area
which are available to the caller. The file's name, file size,
file date and a brief description of the file are displayed
to the caller.
<C>... Change File Area
This feature allows the caller to change to a different File
Area. If the caller selects <Q>uit, the caller remains in
the present File Area. If the caller presses the [ENTER] key,
SPITFIRE lists the File Areas available to the caller. If
a number corresponding to an available File Area is entered,
SPITFIRE makes that File Area the current File Area.
<Q>... Quit To File Menu
This feature takes the caller from the Batch Section of
SPITFIRE to the File Section of SPITFIRE. If this is selected,
the caller's batch queue is cleared.
<?>... Help
This feature offers a brief description of the various
commands available from the Batch Upload Menu.
Page 96
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<G>... Goodbye & Log Off
This feature simply allows the caller to log off the BBS.
12.0 SYSOP SECTION EXPLAINED
-----------------------------
Almost all the Sysop utilities are contained in SPITFIRE. No
external programs are needed to do normal, day-to-day maintenance.
However, it is our hope that people will implement utilities for
SPITFIRE. In the event you are interested in writing such a utility
and need detailed information regarding how SPITFIRE interacts with
different support files, please feel free to contact Buffalo
Creek's BBS (515-225-8496).
>>>>>>>> SYSOP MENU <<<<<<<<
<D>.............. Drop To DOS <E>................. Event Menu
<F>............... File Areas <G>.......... Goodbye & Log Off
<H>............ List Comments <I>.......... Pack Callers File
<J>........ Pack Message Base <R>.... Remove Backup/Log Files
<M>...... Message Conferences <P>......... Print Callers File
<Q>........ Quit To MAIN MENU <U>............. Modify Callers
<V>........... View Log Files <X>.......... Xpert Mode Toggle
SYSOP MENU [D E F G H I J R M P Q U V X]?
12.1 SYSOP MENU EXPLANATION
----------------------------
<D>.... Drop to DOS
This feature allows you to drop to DOS from a remote
location. You need to use the ALT+J feature or ALT+D
feature to drop to DOS locally. When this feature is used
from a remote location, SPITFIRE does not allow the caller
to drop to DOS unless the drop-to-DOS password is properly
entered. This password is configured using the ALT+Z
command at the "Ready..." prompt. It is recommended that
this feature be made available to only trusted callers (if
made available at all.) When this feature is utilized,
SPITFIRE shells to SFREMOTE.BAT and sends a parameter
which indicates the COMM port being used.
<E>.... Event Menu
This option is used for maintaining events used on the
BBS. It is used to List Events, Enable An Event and
to Disable An Event. For more detailed information, refer
to the EVENTS MENU EXPLANATION section of this manual.
Page 97
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<F>.... File Areas
This displays the File Area System Record's Menu. From
this menu, you are able to configure or modify the File
Area System Records. For more detailed information,
refer to the section - CONFIGURING FILE AREA RECORDS of
this manual.
<G>.... Goodbye & Log Off
This feature simply allows the caller to log off the BBS.
<H>.... List Comments
This feature searches Message Conference #1 for messages
addressed to you. If any messages are found, then SPITFIRE
shows them to you. If there are no messages found, then
SPITFIRE notifies you that there are no messages addressed
to you.
<I>.... Pack Callers File
This feature allows you to pack SFUSERS.DAT. When using
this feature, SPITFIRE will purge any caller marked for
deletion from the caller's file. Also, SPITFIRE gives you
the opportunity to purge inactive callers. When you select
this feature, SPITFIRE asks if you wish to purge inactive
callers. If you answer "Y", then you will be asked whether
to purge callers that haven't called for <x> amount of days.
The value of <x> is determined by you. Those callers who
haven't logged on for <x> amount of days are then purged
from the caller's file. SPITFIRE allows you to toggle
whether a purge will be allowed or not allowed for each
caller. If a caller has been toggled to "purge not
allowed," the caller is not purged (even if they have
not called for the <x> amount of days specified here.)
If you are operating a multi-node system, SPITFIRE does not
allow you to pack the callers file while a caller is on any
of the available nodes. Also, if you are packing the
callers file and a caller attempts to log on, after entering
their name and password, SPITFIRE notifies the caller that
system maintenance is being performed, asks the caller to
call back later and then logs the caller off the BBS. The
Sysop may create their own ASCII/ANSI display screen,
SFMAINT.BBS/CLR, which is displayed here, if found.
<J>.... Pack Message Base
When this feature is selected, Sysops are asked if they are
sure they want to pack the message base. A "Y" response
enables SPITFIRE to go through the message files purging all
messages that have been marked as deleted. When configuring
Page 98
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Message Conference records Sysops should have also specified
a number of days old for purging messages from each message
conference. Any messages older than the number of days
specified for the individual message conferences will also
be purged, provided it is not a threaded message and the
Message Conference was set not to allow purging of threaded
messages. It is recommended that this is done on a regular
basis for a couple of reasons:
<1> Disk space.
<2> Speed (SPITFIRE works faster with fewer messages).
On multi-node systems, SPITFIRE will not permit packing of
the message base while a caller is on any of the available
nodes. Also, if while packing the message base a caller
attempts to log on, after entering their name and password,
SPITFIRE notifies the caller that system maintenance is
being performed, asks them to call back later. It then
logs the caller off the BBS. The Sysop may create their
own ASCII/ANSI display screens, SFMAINT.BBS/CLR, which are
displayed here if found.
<R>.... Remove Backup/Log Files
When selected, this option displays the following menu:
>>> FILE REMOVAL MENU <<<
<C>.... Erase CALLERS.LOG
<H>... Erase HEYSYSOP.LOG
<M>..... Erase SFMSG*.$??
<U>.... Erase SFUSERS.$??
FILE REMOVAL MENU - [C H M U Q]?
<C>... Erase CALLERS.LOG
Selecting this option causes the existing CALLERS.LOG
file to be erased. SPITFIRE automatically creates a
new CALLERS.LOG file.
<H>... Erase HEYSYSOP.LOG
Selecting this option causes the existing HEYSYSOP.LOG
file to be erased. SPITFIRE automatically creates a
new HEYSYSOP.LOG file.
<M>... Erase SFMSG*.$??
When this option is selected, all backup files from the
Message Conferences are erased.
<U>... Erase SFUSERS.$??
When this option is selected, the SPITFIRE caller's backup
files are erased.
Page 99
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<M>.... Message Conferences
This displays the Message Conference System Record's Menu.
From this menu, Sysops can configure or modify the
Message Conference System Records. For more detailed
information, refer to the section - CONFIGURING MESSAGE
CONFERENCE RECORDS.
<P>.... Print Callers File
This feature prints out a hardcopy list of callers' names,
their cities and phone numbers. This can only be executed
locally.
<Q>.... Quit to MAIN MENU
This feature takes you from the Sysop Utility Section of
SPITFIRE to the MAIN MENU.
<U>.... Modify callers
This feature is the same as selecting ALT+A at the
"Ready..." prompt. The menu that accompanies this
selection is self-explanatory. This feature is used to
change statistics on any caller and to manually add new
callers. For further information, refer to the section -
SPECIAL FUNCTION KEY DEFINITIONS of this manual.
<V>.... View Log Files
This option allows Sysops to view SPITFIRE's log files
including CALLERS.LOG, HEYSYSOP.LOG,SFPURGED.USR and
SFNEWU.ANS. These files can be read from the SPITFIRE
"Ready..." prompt without having to log on the BBS and
accessing this feature from the Sysop Menu. Sysops are
prompted as to whether to review the Caller's log,
Heysysop log, purged caller listing or caller responses to
the new caller questionnaire. Upon selecting the desired
log, Sysops are then presented with the following options
for reading the log file:
<T>..Today's Date
begins displaying the CALLERS.LOG, HEYSYSOP.LOG,
SFPURGED.USR or SFNEWU.ANS from its first entry for
the current day.
<B>..Beginning Of File
displays the CALLERS.LOG, HEYSYSOP.LOG, SFNEWU.ANS
or SFPURGED.USR from the beginning of the file,
starting with the first entry.
<S>..Specify Date
prompts for a date to be entered and will begin
displaying the CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR
Page 100
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
or SFNEWU.ANS with the first entry for the date that
is entered. If the date specified here can not be
found, SPITFIRE searches for the next newer date
than what was specified and displays the file from
that point forward.
<Q>..Quit
Returns you to the Sysop Menu.
<X>.... Xpert Mode Toggle
This feature changes caller status from a novice to an
expert or vice versa. If set as a novice, the menu
descriptions scroll by after each command. If set as an
expert, only the command letters scroll by after each
command.
13.0 SPECIAL COMMANDS FOR SYSOP STATUS
---------------------------------------
Definition of Sysop Status
--------------------------
A caller with Sysop Status is defined as any caller that has a
security level equal to or greater than the Sysop security level as
set using the ALT+Z feature at the "Ready..." prompt.
The Message section has a few "Special Commands" for callers with
Sysop Status.
When a system is configured to allow a caller the ability to
delete messages, it's important to note that only the sender and
receiver can delete messages, except for callers with Sysop Status.
Any caller with Sysop status can read, delete, and un-delete any
message.
The <P>rivate command is a toggle that can be used to make a
non-public message public and a public message non-public.
The <C>opy command will allow a caller with Sysop security to
move a message to another Message Conference and forward the message
to another caller other than the original recipient of the message.
Last in the message arena is the <U>ndelete command. Anyone with
Sysop Status will automatically be able to read all the messages in
the message system, even if they have been deleted. Those who see a
message which has been marked for deletion may undelete it by using
this command. Callers are not able to read deleted messages unless
their access level is equal to or greater than Sysop Status.
Page 101
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
When a message is Undeleted, changed from Non-public to Public or
changed from Public to Non-public, the message is re-displayed so
the change can be verified. When a message is changed from Non-public
to Public, an option is given allows the message to be addressed to
"All Callers".
If a caller with Sysop Status attempts to upload a file that
already exists, that caller is given the opportunity to overwrite
the file. The caller is warned that the file already exists and is
given the option to overwrite it. SPITFIRE does not allow any other
caller without Sysop Status this privilege.
13.1 SPECIAL COMMANDS FOR SYSOP
--------------------------------
The Sysop is determined within the ALT+Z configuration window.
The name entered here for Sysop caller name is whom SPITFIRE considers
to be the Sysop of the BBS. It is to this caller that comments to
Sysop are left by callers (at the Main Menu.)
The Sysop has one feature available to them that no other callers
have, regardless of the caller's security. When selecting the option
to read messages, if recognized as the Sysop, callers are prompted as
to whether they wish to preview messages. This means that they will
be able to read messages but the messages will not be marked as having
been received. A handy use for this feature may be when Sysops don't
have time to respond to all their messages. They can still read the
messages and respond to those they choose. Callers will not see that
Sysops have received the message and feel slighted by the fact that
there was no response. Sysops can re-read messages later and respond
when they have more time to devote to responding to messages.
Also, those with Sysop-Level security have an "unlimited" number of
daily node chats of "unlimited" duration.
14.0 EVENTS MENU EXAMPLE
------------------------
It is possible for a Sysop to automatically execute specific
programs automatically by setting these programs up as a scheduled
event using SPITFIRE's Events Menu.
>>>>>>>> EVENTS MENU <<<<<<<<
<L>............ List An Event <E>.......... Enable An Event
<D>......... Disable An Event <Q>..................... Quit
<+>............... Next Event <->........... Previous Event
EVENTS MENU - [L E D Q + -]?
Page 102
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
14.1 EVENTS MENU EXPLANATION
-----------------------------
<L>.... List An Event
SPITFIRE supports 13 events <A..M>. Sysops who select
this feature are asked which event <A..M> they wish to
view. If the event selected is not configured,
SPITFIRE states that this event is not active. If the
event selected is configured, then SPITFIRE displays
the time of the event, the day of the event, whether
the event is active and whether it has been completed
that day.
<E>.... Enable An Event
This feature is used to activate one of the 13 scheduled
events available. Sysops who select this feature are
asked which event they wish to create. If they select
one that is already active, SPITFIRE notifies them that
the event selected is already active and they are asked
whether they wish to change it. If the requested
event designation is not active, Sysops are asked for
the time of the event (expressed in military time.
Example: 22:00 = 10pm). Next they are asked which day
the event should be scheduled for.
The format looks like this:
0=Sunday, 1=Monday, 2=Tuesday, etc....7=All!
Sysops are then prompted as to whether the event should
be marked as having been completed for the day. If they
reply with N for No, and the event is configured to be
executed at a time earlier than when it is created, the
event is executed upon exiting the Events Menu. If they
reply with N for No, and the event is configured to be
executed at a time later than when it is created, it is
executed at the next scheduled time. If they reply with
Y, for Yes, the event is not executed until the next
designated scheduled time after the day it is created.
Finally, Sysops are prompted as to whether the event
should be marked as an on time event. When an event is
marked as an on time event, when a caller logs onto the
BBS, SPITFIRE checks their time against any on time event
that has not been completed for that day. If the event is
scheduled to run during the amount of time the caller has,
SPITFIRE reduces their amount of time on the BBS by that
amount. For example, if a caller is allowed 60 minutes when
Page 103
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
logging onto the BBS, and SPITFIRE checks for an on time
event and determines an on time event is to be executed in
25 minutes, the time the caller is allowed on the BBS for
the current call is changed to 25 minutes.
**NOTE** Even though an event is marked as an on time event, it
is possible that a caller could gain additional time on the
BBS preventing the event from being executed on time. For
example, the BBS could be configured to allow additional
time for file uploads (i.e. 2 to 1 time compensation for
uploads) or offer time bank programs where the caller can
withdraw stored online time.
After having selected the desired scheduled event and
designating the time and day the event is to be
performed, Sysops need to modify the SF.BAT file with
their favorite text editor. For illustration purposes,
let's assume Sysops wish to execute Buffalo Creek
Software's SFLOG to create a bulletin of the weekly
activity on their BBS. SFLOG requires Sysops to
specify the bulletin filename that the information will
be written to by adding a "/BULLET<x>" to the command
line parameter. Our example will use the file BULLET1.
To simplify this explanation, assume all files are being
run from the default directories, and the event will be
event A.
The Sysop will need to select <E>.... Enable An Event
from the Sysop Utilities Menu and then choose A as the
event to be created. They are then prompted for the time
the event will be performed. Let's assume a time of 01:00.
Next, the Sysop is prompted for the day the event will
be performed. Let's assume they wish to run the event
every Sunday, so 0 is entered. When prompted whether to
mark the event as being completed they type Y. Finally,
Sysops are prompted as to whether the event should be an on
time event and N is entered.
The SF.BAT file for Event A will look like this:
:EVENT_A
REM Place Event Commands Here
GOTO LOOP
What is required next is to include all necessary DOS
commands which are needed to run the SFLOG program
and enter those in place of the "REM Place Event Commands
Here". A completed SF.BAT for Event A appears as:
Page 104
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
:EVENT_A
CD\SF\WORK
SFLOG /BULLET1
COPY BULLET1.* \SF\DISPLAY
ERASE BULLET1.*
CD\SF
GOTO LOOP
With the event set up in the previously described manner,
every Sunday morning at 1:00 am (or immediately after a
caller logs off since it has not been marked as an on time
event), SFLOG creates a list of the BBS weekly activity.
SFLOG must be located in the same directory as CALLERS.LOG
(WORK). Therefore, the batch begins by changing to that
directory. SFLOG is then executed and BULLET1.BBS/CLR are
created. The bulletins are then copied to the DISPLAY file
directory and to conserve disk space the BULLET1.BBS/CLR
files in the WORK directory are deleted.
<D>.... Disable An Event
This feature is used to disable an event that has been
configured previously. If the event is currently active,
SPITFIRE asks the Sysop whether they are certain they want
to disable it. Responding with "Yes" disables the scheduled
event.
<Q>.... Quit
This feature takes the caller from the Events Menu and
returns them to where SPITFIRE was prior to calling up
the Events Menu, either the "SPITFIRE ready..." prompt
or the Sysop Utilities Menu.
<+>.... Next Event
This option is used to move forward from one Event to
another. Pressing the "+" key progresses from one
event to the next in alphabetical order. When the last
event is reached (Event M) and the "+" key is pressed
SPITFIRE cycles to the first event, Event A.
<->.... Previous Area
This option enables Sysops to cycle through the Events in
reverse order. Pressing the "-" key moves to the
preceding event. From Event A, if the "-" key is pressed
SPITFIRE will cycle to Event M, the last event.
Page 105
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
IMPORTANT NOTE REGARDING SCHEDULED EVENTS!
------------------------------------------
SPITFIRE has the capability of marking an event as an "on-time"
event, which causes the event to be executed at the exact time for
which it has been set up. When an event is marked as an on time event,
when a caller logs onto the BBS, SPITFIRE checks their time against
any on time event that has not yet been completed for that day. If the
event is scheduled to run during the amount of time the caller has,
then SPITFIRE reduces their amount of time on the BBS by that amount.
For example, if a caller is allowed 60 minutes when logging onto the
BBS, and SPITFIRE checks for an on time event and determines an on time
event is to be executed in 25 minutes, the time the caller is allowed
on the BBS for the current call is changed to 25 minutes.
**NOTE** Even though an event is marked as an on time event, it
is possible that a caller could gain additional time on the BBS
preventing the event from being executed on time. For example, the
BBS could be configured to allow additional time for file uploads
(i.e. 2 to 1 time compensation for uploads) or offer time bank
programs where the caller can withdraw stored online time.
Marking an event as on time event might be necessary for running
programs that require a specific time to be executed. Such an
instance might be importing daily net-mail where Sysops are given
a designated amount of time for connecting with your hub. Usually
this will not be necessary.
When an event is not marked as an on time event, unlike most
other Bulletin Board Systems, if a caller is on-line when an event is
scheduled to occur, SPITFIRE waits until the caller logs off and then
performs the scheduled event. In this fashion, the caller is not
interrupted or subject to a forced log-off.
Please note the Event M is reserved for use to Pack the Message
Base. At the scheduled time you designate, SPITFIRE initiates Event M
to pack the message base by purging all messages marked for deletion
or older than the days specified in the ALT+Z configuration, provided
the message is not a threaded message and the Message Conference was
set not to allow purging of threaded messages. SPITFIRE creates
message base backup files. Refer to the section - BACKUP FILES - of
this manual.
Immediately after completing the scheduled event M, SPITFIRE
looks for SFMSGPCK.BAT in the work file directory. If it exists,
SPITFIRE shells to and executes the commands within the
SFMSGPCK.BAT. This batch is intended to perform duties required by
Page 106
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
some net-mail utility drivers. If SFMSGPCK.BAT is not found or once
it has been completed, SPITFIRE returns to the "Ready..." prompt.
Packing the message base should be done routinely to conserve disk
space.
15.0 HARDWARE/SOFTWARE DATA FLOW CONTROL
----------------------------------------
When Sysops select ALT+M to configure your modem, they will
notice a Hardware Data Flow Control switch. This switch is turned on
(Yes) when Sysops use a modem that automatically adjusts to the
baud rate of the incoming call rather than depending upon the software
to reset the baud rate of the COMM port. If the switch is set to
Yes, then SPITFIRE does not adjust the COMM port to the baud rate of
the incoming call. If the switch is set to No, then SPITFIRE adjusts
the COMM port to the baud rate of the incoming call. One case of
having this switch set to YES is when using a USR HST modem at 19200
baud. In this case Sysops need to use the modem initialization string
mentioned earlier in this manual. Those who are not sure if their
modem adjusts to the baud rate of the incoming call should refer to
their modem manual.
16.0 SCREEN SAVE FEATURE
-------------------------
SPITFIRE contains its own Screen Save Feature to prevent
screen-burn. Sysops who are presently using a memory-resident
screen-save utility should discontinue its usage in favor of
this feature.
17.0 SPITFIRE DOORS SECTION
---------------------------
This feature is designed to allow the use of third party
programs (normally referred to as door programs) which are not a part
of SPITFIRE. SFGUESS is a sample door program written to demonstrate
how to configure a door program for use with SPITFIRE BBS. SFGUESS
is included in the SPITFIRE Bulletin Board System package and can
be played on a BBS once it has been set up to run SPITFIRE
Door Programs.
The following step-by-step set up procedure for installing
SFGUESS is presented to simplify and assist Sysops with the door
installation process:
Page 107
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
For this example, it is assumed that there are not any doors
presently set up. It is also assumed that SPITFIRE is being run on
drive C in a directory named SF. In the event Sysops are running
SPITFIRE on a different drive and/or in a different directory than
C:\SF, then the SF.BAT file example (listed below) will have to be
altered to reflect the correct drive and directories.
A brief explanation of the SPITFIRE Door Menu structure is
beneficial to understanding the installing of a SPITFIRE door.
SPITFIRE supports up to 24 doors. Alphabetical characters are
used to initiate the door commands, A through Z, with two exceptions.
The G (Goodbye) is used to log the caller off the BBS and Q (Quit)
returns the caller to the Main Menu. Therefore, the SFDOOR.MNU file
can have a maximum of 24 lines, one for each door program available
on the system.
What follows is a step-by-step description of the procedure
utilized to configure a SPITFIRE Door. The first thing to do is
create the file named SFDOOR.MNU, using a favorite text editor.
When created, SFDOOR.MNU is placed in the system files directory.
When configuring only door A, SFDOOR.MNU will have only 1 line.
For demonstration purposes, this line can look like any of these:
Guess A Number,SEC>=10
Guess A Number,SEC=10
Guess A Number,SEC<10
The name of the door (as it appears in the Door Menu) comes
first in the line and is limited to 25 characters. This is followed by
a comma, which is used to tell SPITFIRE where to end the name of
the door and where to start reading the security level of the door.
The Sysop controls access to the door through the security function.
Using SEC>=[x], where [x] is the numeric value of the security level,
any caller with a security equal to or greater than [x] can access
the door. If SEC=[x] is used on a caller with the security level of
[x] can access the door and if SEC<[x] is used only a caller with the
security level less than [x] can access the door. Using SPITFIRE's
default menus, this door does not display to any caller with a security
level less than 10.
Buffalo Creek Software provides a menu driven utility that easily
creates and/or modifies the SFDOOR.MNU file. SFDOOR.ZIP is included
in the SPITFIRE package and can be downloaded from Buffalo Creek's BBS.
The next step in setting up the door is to create a sub-directory
of the SF directory named DOOR_A and move the SFGUESS.EXE file into
the DOOR_A directory. The DOS manual can be referred to for information
on how to create directories.
Page 108
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
The SF.BAT file is edited by loading into a favorite text editor
starting at a line that reads :DOOR_A. Place the door A commands
(valid DOS commands, program execution, etc.) between :DOOR_A and
GOTO LOOP. That portion of the SF.BAT file should be changed to
read as listed below:
:DOOR_A
COPY SFDOORS.DAT C:\SF\DOOR_A
CD\SF\DOOR_A
SFGUESS
ERASE SFDOORS.DAT
CD\SF
GOTO LOOP
:DOOR_B
After saving the changes in the SF.BAT file to disk, boot
SPITFIRE using the SF.BAT file. At the "SPITFIRE ready for..."
prompt, log on locally either using the ALT+S or ALT+Q
keystrokes. At the Main Menu, select "<S>... SPITFIRE Doors".
The Door Menu should appear something like this:
>>>>>>>>> DOOR MENU <<<<<<<<<
<A>... Guess A Number <?>... Door Bulletins
<Q>... Quit <G>... Goodbye
DOOR MENU - <A ? Q G>?
If <A> is selected at this point, SPITFIRE displays a message
that states "Executing Door A... Please stand by!". At this point,
SPITFIRE writes a text file named SFDOORS.DAT and a file named DOOR.SYS
to the drive. (SFDOORS.DAT contains necessary caller information for
executing doors on a SPITFIRE BBS and DOOR.SYS is the universally
accepted format containing caller information by those attempting to
standardize the door caller information file. These files are created
when a caller enters a door and SFDOORS.DAT is automatically erased
when the caller returns to SPITFIRE.) SPITFIRE, after creating the
SFDOORS.DAT and DOOR.SYS files, terminates, sending the appropriate
DOS ERRORLEVEL to the SF.BAT file. In the case of door A, SPITFIRE
sends an ERRORLEVEL of 34 to SF.BAT which causes the commands placed
between :DOOR_A and GOTO LOOP to be executed. In the event the
correct commands were entered between :DOOR_A and GOTO LOOP, SFGUESS
will run. When the door is finished running, SPITFIRE re-boots
and the caller is returned. If the Sysop has the BBS configured to
require a password when returning from a door, the caller is prompted
for their password.
If a caller enters a door while logged on SPITFIRE, there are
up to three tests SPITFIRE performs when a caller returns to SPITFIRE,
after exiting the door program. First, SPITFIRE must find SFDOORS.DAT
Page 109
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
in the system files directory. Second, SPITFIRE must find a carrier
detect. And third, if the Sysop has configured the BBS to require a
password when returning from a door, the caller must enter the correct
password when prompted for it. In the event a door is entered during a
local log on, SPITFIRE will perform the following test(s): SPITFIRE
must find the SFDOORS.DAT file and, if the Sysop has configured the BBS
to require a password when returning from a door, the correct password
must be entered.
There are numerous door programs, usually Shareware products,
available for download from Buffalo Creek's BBS as well as most
other bulletin boards. Sysops who do not wish to run third party
programs with SPITFIRE through the Door feature, should set the
security level of the SPITFIRE Door command in the SFMAIN.MNU,
SFFILE.MNU and SFMSG.MNU files high enough so that callers cannot
access it.
SPITFIRE Doors can be accessed by a caller from the Main Menu,
File Menu and Message Menu, provided the caller's security level is
high enough. As previously mentioned, SPITFIRE supports the use
of 24 different doors. However, there are third party programs that
can turn these 24 doors into hundreds of doors. One example of such
a program is WILDFIRE, which is Shareware from Steve Cox. The newest
release of WILDFIRE can be downloaded from Buffalo Creek's BBS and
Flite-Line BBS (402) 421-2434.
17.1 SPITFIRE DOORS DISPLAY FILES
---------------------------------
SPITFIRE uses certain display files during the use of the
Doors feature, if such files are found. It is important to note
that SPITFIRE works perfectly without these display files. Listed
below are the display files that can be used in conjunction with
the SPITFIRE door feature:
SFDORBUL .BBS/CLR - Non-ANSI and ANSI list of door bulletins
which are available to the caller. This is
displayed to the caller just prior to the
door menu (if available) or when selecting
the <?> command from the door menu. (DISPLAY)
DORBUL<x>.BBS/CLR - Non-ANSI and ANSI <x> file that is displayed
when the corresponding <x> is selected from
the SPITFIRE door bulletin list. This file
can be used to display top score bulletins
created by many of the available door game
programs. (DISPLAY)
Page 110
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SFDR<x> .BBS/CLR - Non-ANSI and ANSI door display menu file
displayed to the caller with a corresponding
<x> security level. (DISPLAY)
SFDOOR<x>.BBS/CLR - Non-ANSI and ANSI screen that is displayed
to the caller after selecting the corresponding
<x> door option and prior to the <x> door
being executed. This file might be used to
send the caller a special message about the
door. (DISPLAY)
SFDORBAK .BBS/CLR - Non-ANSI and ANSI screen displayed to the
caller after quitting the door program and
prior to returning to SPITFIRE. This is
normally used simply to welcome the caller
back to SPITFIRE. (DISPLAY)
17.2 SPITFIRE DOORS SUPPORT
----------------------------
Configuring the use of doors with SPITFIRE is supported by
Buffalo Creek Software for registered callers of SPITFIRE. Please keep
in mind once a caller executes a door, SPITFIRE is totally terminated
from memory and control is passed to the SF.BAT where the commands
configured by the Sysop are executed. Sysops who have problems
with the door program itself should read the documentation and then
contact the author of the program. Please keep in mind that once a
caller has entered a door, SPITFIRE is completely out of memory and has
NO responsibility for the operation of the door program.
18.0 EXTERNAL FILE TRANSFER PROTOCOLS
-------------------------------------
This feature is designed to allow the use of file transfer
protocols which are not part of SPITFIRE but are rather provided
by sources other than Buffalo Creek Software. An example is ZModem,
a popular protocol written by Chuck Forsberg. There are no External
Protocols distributed with SPITFIRE because they are usually
Shareware products. Buffalo Creek Software most likely has no right
to distribute them with the SPITFIRE program. However, there are
many available for download from Buffalo Creek's BBS, as well as most
other bulletin boards.
It should be noted that SPITFIRE does not allow callers to select
an external protocol as their default file transfer protocol. This is
important for callers to know, so SPITFIRE has provided a means to
notify the caller that External Protocols exist.
Page 111
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
When a new caller logs on for the first time and the Sysop has
configured the BBS to require the New Caller Default Protocol option to
display or when callers use the "<Y>... Your Statistics" from the Main
Menu to change their default file transfer protocol, SPITFIRE displays
SFPROMSG.BBS/CLR just before a default file transfer protocol selection
is made. The SFPROMSG.BBS/CLR message can state that if a default file
transfer protocol is chosen, the external protocol option will not be
available. Callers wishing to utilize external protocols should set
their default to <S>.. Select At Time Of Transfer.
18.1 EXTERNAL DOWNLOAD PROTOCOLS
--------------------------------
SPITFIRE allows up to 14 external protocols <A..N> to be utilized
for downloads. It may be best at this point to go through setting up
an external download protocol, step by step.
To start, an assumption is being made that Sysops have a copy of
DSZ (Forsberg's ZModem). Those without a copy may download it from
Buffalo Creek's BBS. The Sysop will need to use their favorite text
editor to create a display file named SFEXTDN.BBS. This is a simple
text file which will contain the names of the external protocols
that are available.
For the purpose of setting up ZModem as the first external
download protocol, the SFEXTDN.BBS file has but one line and
looks something like this:
<A> ZModem
Sysops need to place SFEXTDN.BBS in the directory configured as
the Display Files Path. To verify, or modify, the EXTERNAL TRANSFER
FILE PATH, press ALT+P at the SPITFIRE "Ready..." prompt. Selecting
option D allows modification of SPITFIRE's default setting. An
assumption (for demonstration purposes) is being made here that
SPITFIRE is run on the C drive in a directory named SF and that the
External Transfer path is C:\SF\EXTNOD1.
The next step is to place DSZ in the directory set up as
the External Transfer Path (example... C:\SF\EXTNOD1). Next, using
a favorite text editor, a batch file is created named SFEXTDNA.BAT
in the directory designated as the External Transfer Path. SPITFIRE
shells to this batch when a caller selects <A>... from the download
protocol list. It is appropriate at this point to show the suggested
contents of this batch file.
Page 112
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
ECHO OFF
BRK OFF
Echo Executing SPITFIRE'S External Protocol #1
CD\SF\EXTNOD1
DSZ %2 sz %3
CD\SF
BRK ON
Now that SFEXTDNA.BAT, with the above listed commands, resides
in the directory set up as the External Transfer Path, the first
External Download Protocol has been configured. The actual contents
of the batch files in use depends upon the specific protocols.
The above is only a sample batch file that should work well with
DSZ.
Before the commands in the above described batch file are
explained, it is important to note when a caller selects <B>...
from the download protocol list, SPITFIRE shells to a batch file
named SFEXTDNB.BAT. As stated before, there are fourteen external
protocols allowed and are denoted by command letters "A" thru "N".
These command letters are used to shell from SPITFIRE to the
corresponding batch files.
A = SFEXTDNA.BAT B = SFEXTDNB.BAT C = SFEXTDNC.BAT
D = SFEXTDND.BAT E = SFEXTDNE.BAT F = SFEXTDNF.BAT
G = SFEXTDNG.BAT H = SFEXTDNH.BAT I = SFEXTDNI.BAT
J = SFEXTDNJ.BAT K = SFEXTDNK.BAT L = SFEXTDNL.BAT
M = SFEXTDNM.BAT N = SFEXTDNN.BAT
An explanation of these batch files and what SPITFIRE does in
preparation to use these batch files is appropriate and important
for Sysops to know and understand.
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the download. If allowable, then SPITFIRE copies the selected file
to the directory configured as the External Transfer Path. PLEASE NOTE
THAT SPITFIRE COPIES THE SELECTED FILE. THIS MEANS THERE MUST BE
ENOUGH DISK SPACE AVAILABLE FOR THE FILE TO BE COPIED. If all tests
were passed and the file was successfully copied, SPITFIRE switches to
the directory configured as the External Transfer Path and stays in
memory but shells to the appropriate batch file (as described above).
Keep in mind that SPITFIRE is resident in memory, as well as a second
copy of the command processor (COMMAND.COM) so the external file
transfer protocol requires some memory. Therefore, the minimum memory
requirement of 256K, stated earlier in the manual, may be insufficient
for systems including the external protocol file transfer options.
Page 113
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Upon performing this shell, SPITFIRE passes at least three
parameters to the appropriate batch file. The first parameter is the
baud rate. The second parameter being passed is the number of the
COMM port being used. The third parameter is the name of the file to
be downloaded. This passed information is needed by most external file
transfer programs and can now be used with DOS batch commands. The
filename is passed in ASCII text as %3. The baud rate is %1, a number
representing baud rate of the caller, such as 2400. The COMM port %2
is the number of the COMM port being used (1,2,3 or 4). Those who are
not familiar with the use of the % command in batch files, should refer
to the DOS manual for specific details.
When the external protocol file transfer program has finished
its work, control is automatically returned to SPITFIRE. Once control
is returned, then SPITFIRE switches back to the directory in which the
SPITFIRE system files reside. SPITFIRE then erases the file that was
copied to the directory configured as the External Transfer Path for
download. Finally, SPITFIRE checks the amount of time that has passed
during the shell to the external protocol batch file. In the event
SPITFIRE discovers that the time spent in the shell was at least
30% of the estimated transfer time, the number of downloads,
K downloaded, etc. of the caller is updated. In the event the time
spent in the shell was less than 30% of the estimated transfer time,
SPITFIRE assumes that the transfer was not successful and the
caller's data is not updated.
Sysops will notice the example batch file (above) has a command
to change to the directory configured as the External Transfer Path.
They will also notice there is a another command to change back to the
SPITFIRE system files directory. These commands do not have to be in
the batch files created because SPITFIRE will automatically perform
these chores. However, it is quite permissible for the commands to be
in the batch file where they can act as a safeguard. Sysops will
finally notice a command BRK OFF at the beginning of the batch file
example, as well as a BRK ON at the end. BRK is a Shareware utility
distributed by Solid Systems of Newport News, Virginia. It is used to
disable and enable the CTRL+BREAK, which can be used to terminate a
batch file. Sysops may need this utility for the protection of their
systems. BRK.ZIP can be downloaded from Buffalo Creek's BBS.
18.2 EXTERNAL BATCH DOWNLOAD PROTOCOLS
--------------------------------------
SPITFIRE also allows for batch downloads to be transferred
with the use of external protocols, provided the external protocol
is written to include batch transfers. Much of the information
Page 114
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
discussed in the section - EXTERNAL DOWNLOAD PROTOCOLS - also applies
to the External Batch Download Protocols. However, there are some
significant differences which warrant mentioning.
The SFEXTDN.BBS file is created using a favorite text
editor. It lists the names of the external batch file protocols
that are available. On the same line, the protocol description
is followed by a comma and the word BATCH. Continuing to use DSZ
as an example, the SFEXTDN.BBS file might now look like this:
<A> Zmodem
<B> Zmodem Batch,Batch
The SFEXTDN.BBS must reside in the path assigned as the Display
File Path. The DSZ must be placed in the directory configured as
the External File path. Using a favorite text editor, create a
SFEXTDN<A..N>.BAT file which contains the commands necessary to
execute the batch download. In the above example, SFEXTDNB.BAT
needs to be created to perform external Zmodem batch downloads from
SPITFIRE.
The commands for the SFEXTDNB.BAT file should look like this:
BRK OFF
ECHO OFF
ECHO EXECUTING EXTERNAL PROTOCOL # 2
CD\SF\EXTNOD1
DSZ %2 sz %3 %4 %5 %6 %7 %8 %9
CD\SF
BRK ON
The commands used for Zmodem batch pass the same command line
parameters (explained above in the EXTERNAL DOWNLOAD PROTOCOLS section)
as the single file Zmodem transfer with the addition of %4, %5, %6, %7,
%8, %9. The %3 through %9 are the file names the caller enters if the
batch download external protocol is selected. SPITFIRE allows up to
seven files to be transferred during an external batch download. %3
through %9 represent the file names the caller includes in the batch
queue.
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the download. If allowed, SPITFIRE copies the selected files to
the directory configured as your External Transfer Path. PLEASE NOTE
THAT SPITFIRE COPIES THE SELECTED FILES. WITH EXTERNAL BATCH DOWNLOADS
IT IS DOUBLY IMPORTANT TO THAT ENOUGH DISK SPACE BE AVAILABLE FOR THE
FILES TO BE COPIED. However, in adding files to the batch queue if
SPITFIRE discovers the addition of another file exceeds the amount
Page 115
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
of available disk space or exceeds the number of daily allotted
downloads for the caller, an appropriate message is displayed prior
to downloading the files presently in the batch queue.
18.3 TEXT FILE EXTERNAL BATCH DOWNLOAD PROTOCOLS
------------------------------------------------
SPITFIRE can be configured to create a text file in the EXTERNAL
directory which contains a list of the files to be downloaded. By
using the file list, the path and name of each file is stored in a text
file. By using the text file, it is no longer necessary for SPITFIRE
to copy the files into the EXTERNAL directory. It should be mentioned
that the external protocol must have the capability of reading this
text file. DSZ is one such external protocol.
There are several advantages to using this particular method with
batch transfer protocol downloads. First, because files are no longer
required to be copied to the EXTERNAL directory, downloads can be
performed much faster. Speed is important for multi-node systems.
Secondly, you eliminate the risk of running out of disk space since
files are duplicated when copied to the EXTERNAL directory for
downloading. Also, the number of files that can be downloaded in a
single batch transfer is significantly increased using the text file.
Where the typical batch download (discussed in the previous section of
the manual) allows 7 files to be downloaded per batch; using the
text file allows 99 files to be downloaded per batch.
To initiate an external batch download protocol using a textfile,
simply add
,UseFile
at the end of the line of your SFEXTDN.BBS where the text file feature
is to be used. For example, here is a sample SFEXTDN.BBS:
<A> Zmodem,UseFile
<B> Zmodem Batch,Batch,UseFile
The SFEXTDN.BBS must reside in the path assigned as the Display
File Path.
The DSZ must be placed in the directory configured as the
External File path. Using a favorite text editor, Sysops should
create a SFEXTDN<A..N>.BAT file which contains the commands necessary
to execute the batch download. In the above example, SFEXTDNC.BAT is
created to perform an external Zmodem batch download from SPITFIRE.
Page 116
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
The commands for the SFEXTDNC.BAT file should look like this:
BRK OFF
ECHO OFF
ECHO EXECUTING EXTERNAL PROTOCOL # 2
CD\SF\EXTNOD1
DSZ %2 sz @C:\SF\EXTNOD1\SFEXTRAN.LST
IF ERRORLEVEL 1 GOTO END
IF ERRORLEVEL 0 GOTO GOOD
:GOOD
APPENDIT ZMODEM.TXT \SF\CALLERS.TMP
:END
CD\SF
BRK ON
Note that the commands used in the SFEXTDNC.BAT (above example) uses
the text file C:\SF\EXTNOD1\SFEXTRAN.LST. This is the text file where
SPITFIRE stores the names of the files which the caller has selected
for download.
It should again be noted that when an External Protocol is selected,
SPITFIRE does all the normal tests to be sure it is permissible for the
caller to perform the download. In adding files to the batch queue if
SPITFIRE discovers the addition of another file exceeds the number of
daily allotted downloads for the caller, an appropriate message is
displayed prior to downloading the files presently in the batch
queue.
18.4 EXTERNAL UPLOAD PROTOCOLS
------------------------------
SPITFIRE allows up to 14 external protocols <A..N> to be utilized
for uploads. Since SPITFIRE handles external protocols for uploading
slightly different than downloading, it is a good idea at this point to
go thru setting up an upload external protocol, step by Step. To begin,
Sysops need to obtain a copy of DSZ (Forsberg's ZMODEM.) Those
without a copy can download it from Buffalo Creek's BBS. Using a
favorite text editor, they create a display file named SFEXTUP.BBS,
a simple text file which contains the names of the external protocols
that are available. For the purpose of setting up ZModem as the first
upload external protocol, the SFEXTUP.BBS file has one line that looks
something like this:
<A> ZModem
SFEXTUP.BBS is placed in the directory configured as the Display
Files Path. To verify, or modify, the EXTERNAL TRANSFER FILE PATH,
press ALT+P at the SPITFIRE "Ready..." prompt. Selecting option D
Page 117
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
allows modification of SPITFIRE's default setting. An assumption (for
demonstration purposes) is made that SPITFIRE is run on the C drive in
a directory named SF and that the External Transfer path is
C:\SF\EXTERNAL.
The next step is to place DSZ in the directory set up as
the External Transfer Path (example... C:\SF\EXTERNAL). Next, using
a favorite text editor, a batch file is created named SFEXTUPA.BAT
in the directory designated as the External Transfer Path. SPITFIRE
shells to this batch file when a caller selects <A>... from the upload
protocol list. At this point, prior to executing the commands within
the batch file, SPITFIRE sets the attribute of all files contained in
the External Transfer Path (in this example, C:\SF\EXTERNAL) to Read
Only. This is done to prevent callers from uploading and overwriting
files which exist in your External Transfer Path. It is appropriate
at this point to show the suggested contents of this batch file:
Echo Off
BRK OFF
Echo Executing External Protocol #1
CD\SF\EXTERNAL
DSZ %2 restrict rz %3
CD\SF
BRK ON
Now that SFEXTUPA.BAT, with the above listed commands, resides
in the directory set up as the External Transfer Path, the first upload
External Protocol is successfully configured. The actual contents of
the batch files in use will depend on the specific protocols. The
above is only a sample batch file and should work well with DSZ.
Before the commands in the above described batch file are
explained, it is important to note when a caller selects <B>... from
the upload protocol list, SPITFIRE shells to a batch file named
SFEXTUPB.BAT. As stated before, there are fourteen external protocols
allowed and they are denoted by command letters "A" thru "N". Through
their use, SPITFIRE shells to the corresponding batch files.
A = SFEXTUPA.BAT B = SFEXTUPB.BAT C = SFEXTUPC.BAT
D = SFEXTUPD.BAT E = SFEXTUPE.BAT F = SFEXTUPF.BAT
G = SFEXTUPG.BAT H = SFEXTUPH.BAT I = SFEXTUPI.BAT
J = SFEXTUPJ.BAT K = SFEXTUPK.BAT L = SFEXTUPL.BAT
M = SFEXTUPM.BAT N = SFEXTUPN.BAT
Now, an explanation of these batch files and what SPITFIRE does
in preparation to use them is appropriate and important to know and
understand.
Page 118
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the upload. If all tests were passed, SPITFIRE changes to the
directory configured as the External Transfer Path and stays resident
in memory but shells to the appropriate batch file (as described
above). Keep in mind that SPITFIRE is resident in memory as well as a
second copy of the command processor (COMMAND.COM), consequently the
external file transfer protocol is going to require some memory.
Therefore, the minimum memory requirement of 256 K stated earlier in
the manual, may be insufficient for systems including the external
protocol file transfer options.
Upon performing this shell, SPITFIRE is passing four parameters
to the appropriate batch file. The first parameter is the baud rate.
The second parameter passed is the number of the COMM port being used.
The third parameter is the name of the file to be uploaded. The fourth
parameter is the path in which the file to be uploaded is to reside
(i.e. - C:\SF\UPLOADS). This passed information is needed by most
external file transfer programs and can now be used with DOS batch
commands. The filename is passed in ASCII text as %3. The baud rate is
%1, a number representing baud rate of the caller, such as 2400. The
COMM port %2 is the number of the COMM port being used (1,2,3 or 4).
Sysops who are not familiar with the use of the % command in batch
files should refer to their DOS manual for specific details. The
"restrict" parameter is a feature of DSZ which prevents the uploader
from specifying the file path when uploading to the BBS.
When the external protocol file transfer program has finished
its work, control is automatically returned to SPITFIRE. Once control
is returned, SPITFIRE resets the attributes of all files in the
External Transfer Path (in this instance, C:\SF\EXTERNAL) back to
archive. Then, SPITFIRE changes back to the directory in which the
SPITFIRE system files reside. SPITFIRE now checks to see if the file
that was to be uploaded exists in the File Area in which the uploaded
file should reside, if all went correctly. If SPITFIRE finds the file
in the appropriate File Area, the caller is credited with the upload
and other clean-up chores are performed. SPITFIRE will then
automatically move the uploaded file to the directory the Sysop has
configured as the file upload path (i.e. - C:\SF\UPLOADS). In the
event SPITFIRE does not find the file in the appropriate File Area,
SPITFIRE assumes that the upload was aborted.
Notice that the example batch file (above) has a command to change
to the directory configured as the External Transfer Path. Also notice
that there is a another command to change back to the SPITFIRE system
files directory. These commands do not have to be in the batch files
created because SPITFIRE automatically performs these chores. However,
it is quite permissible for them to be in the batch file so they can
Page 119
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
act as a safeguard. Finally, notice a command BRK OFF at the beginning
of the batch file example, as well as a BRK ON at the end. BRK is a
Shareware utility distributed by Solid Systems of Newport News,
Virginia. It is used to disable and enable the CTRL+BREAK, which can
be used to terminate a batch file. Sysops may need this utility for
the protection of their systems. BRK.ZIP can be downloaded from
Buffalo Creek's BBS.
18.5 EXTERNAL BATCH UPLOAD PROTOCOLS
------------------------------------
SPITFIRE also allows for batch uploads to be transferred with the
use of external protocols, provided the external protocol is written to
include batch upload transfers. Much of the information discussed in
the EXTERNAL UPLOAD PROTOCOLS section of this manual also applies to
External Batch Upload Protocols. However, there are some significant
differences which warrant mentioning.
When creating the SFEXTUP.BBS file, Sysops use a favorite text
editor to list the name of the external batch file protocol that is
available. On the same line, the protocol description is followed by a
comma and the word BATCH. Continuing to use DSZ as an example, the
SFEXTUP.BBS file might now look like this:
<A> Zmodem
<B> Zmodem Batch,Batch
The SFEXTUP.BBS must reside in the path assigned as the Display
File Path.
The DSZ.COM must be placed in the directory configured as the
External File path. Next, using a favorite text editor, a
SFEXTUP<A..N>.BAT file is created which contains the commands
necessary to execute the batch upload. For the above example,
SFEXTUPB.BAT needs to be created to perform external Zmodem batch
uploads with SPITFIRE.
The commands for the SFEXTUPB.BAT file should look like this:
BRK OFF
ECHO OFF
ECHO EXECUTING EXTERNAL PROTOCOL # 2
CD\SF\EXTERNAL
DSZ.COM %2 restrict rz
CD\SF
BRK ON
Page 120
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Note, when using DSZ, do NOT list the % file and path parameters on
the command line or it is possible that the uploaded files will end
up with the wrong names. For example, say the caller entered the first
file name to upload as FILE1.ZIP and the second file to be uploaded
as FILE2.ZIP. Then, rather than sending FILE1.ZIP first, FILE2.ZIP
was sent first and FILE1.ZIP was sent second. FILE1.ZIP would be
named FILE2.ZIP and FILE2.ZIP would be named FILE1.ZIP. However,
the lack of % file parameters allows DSZ to receive more files than
the amount specified by the caller. To overcome this problem,
SPITFIRE creates a simple little text file containing the names of
all files within the External Transfer Path just prior to shelling
to the appropriate batch file. Then when control is returned to
SPITFIRE, it checks the files in the External Transfer directory
against the files listed in the previously created text file. If
additional file(s) are found, and if such file(s) do not already exist
in a File Area, SPITFIRE prompts the caller for a description of
the file. If a description is entered by the caller, then SPITFIRE
moves the file to the appropriate File Area and updates the
SFFILES.BBS. If the caller hangs up or does not enter a description,
SPITFIRE uses the default description, "No Description Provided".
%4 represents the directory the Sysop designated as their upload
directory and %3, %5, %6, %7, %8, %9 are the file names. SPITFIRE
allows up to six files to be uploaded during an external batch upload.
After selecting the batch transfer protocol the caller is prompted
to enter the name of the file to be uploaded and provide a brief
description for each file to be uploaded. The "restrict" parameter
is a feature of DSZ which prevents the uploader from specifying
the file path when uploading to the BBS.
As explained in the EXTERNAL UPLOAD PROTOCOLS section of this
manual, SPITFIRE automatically moves the uploaded file(s) to the
directory the Sysop has configured as the upload file path.
18.6 EXTERNAL PROTOCOL SUPPORT
------------------------------
Configuring the use of external file transfer protocols is
supported by Buffalo Creek Software for registered users of SPITFIRE.
Those who have problems with the external file transfer program
itself are urged to read the documentation and then contact the
author of the program.
Page 121
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
19.0 SPITFIRE UTILIZES EMS (Expanded Memory)
--------------------------------------------
Upon boot-up, SPITFIRE automatically attempts to copy
SPITFIRE.OVR to EMS. If there is adequate EMS available, SPITFIRE
will access it from there. This will increase the speed at which
SPITFIRE operates and save wear and tear on the drive. If this is done,
SPITFIRE upon boot-up displays the message "EMS memory is used for
SPITFIRE.OVR".
20.0 SPITFIRE NET-MAIL CAPABILITIES
------------------------------------
SPITFIRE supports net-mail in two basic formats. In the
first format, SPITFIRE is used in conjunction with a front-end
type program where net-mail messages are imported and made available
to callers. SPITFIRE also supports PC Relay style of net-mail which,
when used in conjunction with a Universal Text Interface (UTI) program
will directly import net-mail into SPITFIRE's message base.
Using SPITFIRE with a front-end program requires the use of such
programs as BinkleyTerm or FrontDoor for sending and receiving
net-mail messages. Sysops who run their copy of SPITFIRE with a
front-end type program will have to boot SPITFIRE using the baud rate
of the caller as a command line parameter. For example:
SPITFIRE 2400
NOTE: The SF.BAT file included with the
SPITFIRE package should be used even with
a front-end program. Using the SF.BAT file,
the front-end program should boot SPITFIRE
in this manner - SF 2400. Then within the SF.BAT
file the SPITFIRE command would have to be followed
by a %1. {Example - SPITFIRE %1}
When SPITFIRE is booted in the above manner, SPITFIRE assumes
there is a caller and begins the process of logging the caller on.
When the caller logs off, then SPITFIRE does not recycle to the
"SPITFIRE ready for use..." prompt but rather terminates so control
can be returned to the front-end program.
It should be noted that if SPITFIRE is used with a front-end
program, the scheduled events feature within SPITFIRE becomes basically
inoperative since events are run while SPITFIRE is at the "SPITFIRE
ready for use..." prompt. However, when used in this environment,
SPITFIRE does check when the caller logs off to see if an event is
scheduled to run.
Page 122
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Certain features within SPITFIRE allow it to be compatible with
specific net-mail drivers.
When configuring the BBS, the Sysop must use the ALT+Z to toggle
their BBS to allow net-mail. In addition, when configuring the
individual Message Conferences the Sysop must toggle the net-mail
option of that particular Message Conference to allow net-mail.
If the BBS and the Message Conference is configured to allow net-
mail, when a caller enters a message, the caller will be prompted
as to whether they wish to send the message via net-mail. If the
caller responds with a Y for Yes, the caller can send a message to
someone who is not a caller on the BBS. Furthermore, the message is
marked as a net-mail message, which allows utilities, such as the
SFUTI<x> listed above, to go through and extract the net-mail messages
for processing and exchange with other BBS systems. The SFUTI<x>
serves as a conversion driver between SPITFIRE and the PC Relay
net-mail software and allows messages transferred between other
BBS systems to be imported directly into SPITFIRE's existing
message base.
21.0 OPERATING A MULTI-NODE SPITFIRE
-------------------------------------
The SPITFIRE Bulletin Board System is fully capable of operating in
a multi-node BBS environment. A multi-node BBS system is one that
allows multiple copies of SPITFIRE to run, having two or more nodes
that share a significant number of the files used during system
operation. When configured for multi-node operation, all nodes of a
SPITFIRE BBS share files contained in the WORK, MESSAGE and DISPLAY
file paths. The SYSTEM and EXTERNAL protocol file paths must be set up
individually for each node.
21.1 MULTI-NODE BBS REQUIREMENTS
--------------------------------
In order to operate SPITFIRE in a multi-node environment, the Sysop
must either be using a multi-tasking software or have multiple computer
systems networked together. Under most circumstances, each node the
Sysop wishes to install will require its own telephone line and modem.
The exception to this being, if in either the multi-tasking or network
environment, the Sysop configures a copy of SPITFIRE BBS with a
maximum baud rate of 0 (making that node only accessible by local
logons).
Page 123
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
21.2 CONFIGURING SPITFIRE FOR MULTI-NODE OPERATION
--------------------------------------------------
In general, SPITFIRE is configured much the same for multi-node as
it is for a single node system. (Refer to the GETTING STARTED section
of this manual for more detailed information.) However, there are
several configuration options the Sysop must be sure to set correctly
when installing or expanding to a multi-node system.
To begin, press ALT+Z to open SPITFIRE's configuration window.
Modifications must be made so that a node number is assigned for the
individual node being configured and the total number of available
nodes entered. Also, it is possible to configure one or more of the
available nodes as a private BBS. If this is done, be sure to use the
ALT+Z option to set the security required for accessing the private
node being configured. For any node not configured as a private BBS,
simply have the security required set to zero. These settings need to
be appropriately configured for each node on the system.
In addition, when operating SPITFIRE in a multi-node environment,
the DOS SHARE program is normally required to be used. This can be
accomplished by placing SHARE in the AUTOEXEC.BAT so SHARE is loaded
each time that the computer is booted.
21.3 FEATURES UNIQUE TO MULTI-NODE OPERATION
---------------------------------------------
When operating a multi-node SPITFIRE BBS system, one of the options
available from the Main Menu is <W>...Who On. If a caller selects this
option, information is displayed to the screen telling the caller of
anyone else who is simultaneously logged on to any of the other
available nodes. The information of who is on the various system nodes
is stored in SFWHOSON.DAT, which resides in SPITFIRE's Work File Path.
Several features unique to the multi-node SPITFIRE environment
relate to packing the message base or caller's file. It is extremely
important that there is no other BBS activity during the packing of
these files. Therefore, certain safeguards are included in SPITFIRE
which monitor activity on all nodes to prevent system access when
packing of these files is in progress. Similarly, SPITFIRE will not
allow these files to be packed if there is activity on any of the
available nodes.
SPITFIRE does not allow a Sysop to use the internal SPITFIRE
commands for packing the caller file or packing the message base while
a caller is logged on one of the other nodes. If the Sysop attempts
this, the following message will be displayed: "Sysop, you are not
Page 124
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
allowed to pack the caller's file/message base while other nodes are
busy." Depending upon which activity is trying to be performed, either
the text of caller's file or message base will display in the above
message.
If a caller attempts to log onto the system when SPITFIRE is
packing the message base or caller's file, SPITFIRE displays the
following message, "A maintenance operation is presently being
performed! Please call back in a few minutes." Upon logging on
the caller is shown the SFPRELOG.BBS and the WELCOME1.BBS/CLR but after
entering their name and password the above message will be displayed.
Sysops may create their own screen for displaying the maintenance
message if preferred. This screen, SFMAINT.BBS/CLR displays
immediately after the caller enters their name, replacing SPITFIRE's
default message mentioned above.
If configured as a multi-node system, when booted, SPITFIRE checks
to determine whether maintenance is being performed (packing the
callers file and packing the message base). In the event SPITFIRE
discovers that maintenance is being performed, the following message
is displayed:
Report - Maintenance Being Performed.
Pausing Until Maintenance Is Complete.
Press Any Key To Return To DOS.
SPITFIRE then goes into a loop and continues to check the
maintenance status indefinitely until the maintenance has been
completed. When the maintenance is completed, SPITFIRE continues
initialization and waits for a caller. During the time while SPITFIRE
is doing the continuous maintenance check loop, if a key is pressed
SPITFIRE terminates and returns to DOS. In other words, when booting
SPITFIRE, if it is discovered that maintenance is being performed by
another node, SPITFIRE loops until the maintenance status changes or
until the Sysop presses a key to return to DOS.
21.4 NODE CHAT
--------------
On a multinode SPITFIRE 3.2 BBS, callers are able to chat with
callers on another node via the Node Chat feature. This feature is
accessed via the "<W>ho's On The Other Node?" Menu Selection which is
found on the Main Menu.
Configuring Node Chat
---------------------
To set up Node Chat, the Sysop may need to edit DAILYLMT.DAT. Node
Chat parameters are specific to each security level. The default values
allow for five Node Chats of five minutes each per day. To set
Page 125
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
specific values for a given security level, the following parameters
(preceded by ONE comma) may be appended to any security level's entry
in DAILYLMT.DAT:
#OCA=(Number Of Node Chats Allowed Each Day)
TPNC=(Time In Minutes Permitted For Each Node Chat)
An example DAILYLMT.DAT might look like this:
4,MPC=0,MPD=0,DLPD=0,#OCA=0,TPNC=0 (Zero Permitted, Zero Minutes)
5,MPC=30,MPD=30,DLPD=10,KB=2000 (Default Number And Time)
10,MPC=60,MPD=60,DLPD=15,KB=5000,#OCA=10,TPNC=20
(10 Chats Daily, 20 Minutes Each)
20,MPC=60,MPD=60,DLPD=15,KB=5000,TPNC=30
(Default Number, 30 Minutes Each)
30,MPC=60,MPD=60,DLPD=15,KB=5000,#OCA=20
(20 Chats Daily, Default Time)
To use default values for both Number Of Chats Daily and Time Per Chat
for ALL security levels, no changes need to be made to DAILYLMT.DAT.
* It is REQUIRED that ALL nodes on a multinode SPITFIRE BBS have *
* a common WORK directory in order to be available for Node Chat! *
Initiating Node Chat
--------------------
When a caller selects "<W>ho's On...", they are presented with a
summary of activities on the other nodes. Callers on the other nodes
are NOT available for Node Chat under the following circumstances:
* when they are chatting with the Sysop (Local Chat)
* when they are using a Door
* when they are already in another Node Chat
* when they are reading or entering messages
* when they are involved in the transmission of files
* when they are listing files
* when they are logging onto the BBS
* when those of Sysop-Level Security are using Sysop Utilities
The caller desiring the Node Chat sees something like this:
" Checking other nodes, please stand by...
Node 1 - (1st Caller) ................... Available for chat!
Node 2 - (2nd Caller) ................... Available for chat!
Node 3 - Busy Caller ................... Transmitting file!
(1st Caller), would you like to initiate a Node Chat? <y/n> "
Page 126
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
A <y>es response then asks the caller:
" Chat with which node # "
If the caller who desires a node chat enters a valid node number, the
caller on the desired node is notified that a Node Chat with them is
requested and by whom. They then see something like this:
" (1st Caller) would like to chat!
Would you like to chat with (1st Caller)? <y/n> "
while the first caller sees:
" Awaiting other node response...Press ESC to abort! "
If the chatted caller agrees to chat, Node Chat occurs. If the chatted
caller does not want to chat, the caller who requested the chat is
returned to the BBS after a short period of time. They are free to
request another Node Chat later or attempt to chat with another node.
Node Chat Procedure
-------------------
Once a Node Chat request is agreed upon and both callers are
connected, the caller who requested the chat is presented with the
following:
" Establishing connection...please stand by...
CTRL+X to xchange chat control when at "CHAT:"
ESC to terminate chat!
Hello, (1st Caller)! What can I do for you?
CHAT: "
while the chatted caller is presented with the prompt:
" Establishing connection...please stand by...
WAIT: "
Only the caller who is at the "CHAT:" prompt may type. SPITFIRE's Node
Chat feature sends typed text to the other node and word wraps
text that spans more than one line. When the chatting caller has
finished their thought and wishes to switch control to the other
caller, control of the chat may be exchanged by hitting <CTRL+X>.
Doing so presents the "CHAT:" prompt to the other caller while
the first caller switches to the "WAIT:" prompt. At that time, the
second caller may type.
Page 127
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
In order to terminate Node Chat and return to other activities,
either caller may hit <ESC>. This shortly ends the Node Chat and
returns both callers to the section of the BBS that they were in before
the Node Chat began. If either caller drops carrier for any reason,
the Node Chat is terminated and the other caller is returned to the
BBS.
22.0 SPITFIRE MULTI-TASKING/NETWORK ENVIRONMENT
------------------------------------------------
In order to operate a multi-node SPITFIRE BBS system, SPITFIRE
must be configured to run in either a multi-tasking or networked
environment. In a multi-tasking environment multiple copies of
SPITFIRE need to be loaded on one computer with the aid of such
multi-tasking programs as Windows 3.0 or DESQview. In a networked
environment individual copies of SPITFIRE need to be loaded on any
number of computers that are networked together via such networking
systems as LANtastic. The following sections discuss the procedure
for installing SPITFIRE in such environments.
22.1 SPITFIRE WITH WINDOWS 3.X
-------------------------------
In order to run SPITFIRE 3.2 under MS Windows 3.0, Sysops need to
create a PIF (Program Information File). Windows uses PIFs to run DOS
applications. A PIF file tells Windows the name and the location of
the DOS (non-Windows application) program being run and describes the
necessary memory and hardware requirements. A PIF file is required
whether running a single node or a multi-node BBS.
To create a PIF file, Sysops must run the PIF editor which is
located in the Accessories Group.
Memory Requirements:
-------------------
Windows sets a MINIMUM value of 128K for all programs that it runs
via a PIF file. However, Windows assigns ALL available memory to all
PIF applications unless told to do otherwise. Even though SPITFIRE
normally requires more than 128K to run, you will probably not need
to increase this value.
Sysops who intend to drop to DOS from the SPITFIRE window and
are running in Real or Standard Mode could increase the memory
requirements. In 386 Enhanced Mode, a better way would be to open
another DOS window.
Page 128
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
All other values are the Windows default PIF values. If running
Windows 3.X in 386 Enhanced Mode, click on ADVANCED options to examine
additional parameters and settings. It is not possible to see these
settings while running in Real or Standard Mode without pulling down
the Mode Option and select 386 Enhanced Mode. Enhanced options are
meaningless when running Windows in Real or Standard Modes. Under
Multitasking Options (ADVANCED), set both Background Priority and
Foreground Priority to 50 for more equitable sharing of time slices
between windows.
Hardware Requirements:
---------------------
To run multiple active SPITFIRE windows on the screen, Sysops MUST
run in 386 Enhanced Mode. This REQUIRES a 386SX or 386DX CPU. 2MB of
RAM is recommended, but the more the better! Sysops MUST install the
HIMEM.SYS driver that is included on the Windows 3.X diskettes
according to parameters applicable to their systems. The popular
QEMM386 program (Version 5.1 and greater) may be substituted for
HIMEM.SYS with appropriate parameters. Sysops should ideally be running
the SMARTDRV cache program as it is designed to work with Windows.
Remember to load ANSI.SYS in your CONFIG.SYS if ANSI graphics is
available on the BBS!
Sysops running the BBS on an 8086, 8088 or 80286 can run SPITFIRE
while running Windows, but it will NOT run in a window. It will
instead run in "exclusive mode", that is to say, full screen. When
switching back to the main Windows screen, SPITFIRE will "freeze"
(as will any other DOS application.) Running an application in this
manner is generally referred to as running "under" windows as opposed
to running "in" windows which refers to the 386 Enhanced "in a
window" style.
Additional Information:
----------------------
To run SPITFIRE 3.2 in a DOS window, select Background and Windowed
as options when creating your SPITFIRE PIF file. This will allow
viewing of one or several nodes on the screen at the same
time as well as other Windows applications. Background windows do not
"freeze" when you are running Windows in 386 Enhanced Mode.
If running a multi-node setup, it is suggested to name the batch
files and PIF files based upon their node number (SF1.BAT, SF1.PIF,
etc.) In addition, there are Windows applications which allow creation
of custom Icons which are unique for each node.
Page 129
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
To load Windows automatically and have it bring up the SPITFIRE
window(s), first edit AUTOEXEC.BAT and have it run WIN.COM. Next,
edit WIN.INI, and set "RUN=SF1.BAT SF2.BAT", etc. to automatically
boot up all SPITFIRE nodes. Make sure to leave a space between all
items listed on the WIN.INI "RUN=" line. If running Windows 3.1 or
greater, all SF.BAT files can be placed in the StartUp Group which
will automatically run them when Windows 3.1 loads.
When configuring SPITFIRE to operate multi-node in the Windows
environment and when attempting to boot node 2 you incur a
runtime error 162, this is caused by having the DOS SHARE loaded
in memory. A runtime error 162 is hardware failure.
22.2 RUNNING SPITFIRE 3.2 UNDER DESQVIEW 386
--------------------------------------------
In order to run SPITFIRE 3.2 under DESQview 386, Sysops need to
create a .DVP (DESQview Program Information File). DESQview uses
DVPs to run DOS applications. A DVP file tells DESQview the name and
location of the DOS (non-DESQview application) program being run and
describes the necessary memory and hardware requirements. A DVP
file is required whether running one or multiple nodes.
To create a DVP file, select Open Window, then Add a Program from the
popup DESQview menu that appears when the ALT key is tapped. See below
for further information.
Memory Requirements:
-------------------
SPITFIRE 3.2 requires 256K of RAM per node. If the BBS includes
programs that are run from DOS using SFMAIN.BAT, SFMESS.BAT or
SFFILE.BAT, Sysops need to allocate more memory depending upon the
size of the application that they are running. This is necessary
because SPITFIRE is still in memory at this time. It is
therefore recommended that at least two megabytes be installed
on a system that is to run SPITFIRE in a DESQview environment.
Since a disk cache dramatically improves performance when
multitasking, it is recommended that one be used with DESQview.
A more realistic setup would be 4MB of RAM with a 2MB cache.
Page 130
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Hardware Requirements:
---------------------
A 386SX or 386DX or greater is required to run DV in 386 mode. Doing
so involves running XDV.COM which places itself in high memory and
activates the true multitasking capabilities of 386 Protected Mode.
DVP File Setup:
--------------
Below are suggested settings for the DVP file that is needed.
Settings will vary with different systems. It is VERY important to
set Close on exit to [N]; otherwise, the window will disappear after
EVERY call! Some items are blank, some are the defaults, and some
are suggested settings. Careful comparison and a little thought is
needed to optimize a system for DESQview.
Change A Program
Program Name............:SPITFIRE 3.2 Node 1
Keys to Use on Open Menu:SF Memory Size (in K):500
Program...:SF1D.BAT
Parameters:
Directory.: C:\SF
------------------------------------------------------------------
Options:
Writes text directly to screen.......:[Y]
Displays graphics information........:[N]
Virtualize text/graphics (Y,N,T).....:[T]
Uses serial ports (Y,N,1,2)..........:[1]
Requires floppy diskette.............:[N]
Press F1 for advanced options Press <- when you are DONE
------------------------------------------------------------------
Change a Program Advanced Options
System Memory (in K)........0 Maximum Program Memory Size (in K)
Script Buffer Size.......1000 Maximum Expanded Memory Size (in K)
Text Pages: 1 Graphics Pages: 0 Initial Mode: Interrupts:00 to FF
------------------------------------------------------------------
Window Position:
Maximum Height: 25 Starting Height: Starting Row....:
Maximum Width.: 80 Starting Width.: Starting Column.:
------------------------------------------------------------------
Page 131
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Shared Program
Pathname..:
Data......:
------------------------------------------------------------------
Close on exit (Y,N,blank)..:[N] Uses its own colors...........[Y]
Allow Close Window Command.:[Y] Runs in background (Y,N,blank)[Y]
Uses math coprocessor......:[N] Keyboard conflict (0-F).......[0]
Share CPU when foreground..:[Y] Share EGA when foreground/zoom[Y]
Can be swapped out (Y,N,bl):[N] Protection level (0-3)........[0]
Press F1 for standard options Press <- when you are DONE
------------------------------------------------------------------
Starting It All Up:
------------------
If ANSI Graphics are featured on the SPITFIRE BBS, Sysops MUST load
DVANSI.COM, a file that comes with the DESQview software, before
opening each SPITFIRE window. To do so, create a batch file such as:
(SF1D.BAT)
C:
CD C:\DV
DVANSI
CALL SF1.BAT
As above, DESQview runs SF1D.BAT, not SF1.BAT directly when it is run
by the DVP file described. In order to have DESQview load the SF DVP
applications immediately, hit SHIFT+ALT when the DESQview Menu is
displayed. This will enter Learn mode. Select Start Script, and then
select the key that should activate this macro and run the script. Make
sure that the Script Name begins with an Exclamation point (!). The
Script that begins with an ! will be automatically loaded. Give the
Script a name like !STARTUP. Then, hit the exact keystrokes that are
used to start the "default" startup windows. When all of the windows
are on the screen, hit SHIFT+ALT a second time. The Learn Menu will
reappear. Select Finish Script to end this Script Macro recording.
When exiting DESQview next, tell it to Save Scripts.
Make sure to have the AUTOEXEC.BAT end with the line "XDV". This will
enable the system to boot DESQview which will in turn boot the SPITFIRE
Setup in case of a power interruption.
22.3 RUNNING SPITFIRE 3.2 ON A LANTASTIC NETWORK
------------------------------------------------
Running SPITFIRE 3.2 on a Local Area Network allows maximum speed as
well as capability of all multi-node strategies. While hardware that
is required is considerable, LAN systems allow for performance not
possible using a multitasking system.
Page 132
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Information discussed in this section while specific to the LANtastic
Network is similar to other LAN systems such as Novell, etc.
Memory Requirements:
-------------------
LANtastic requires less memory than any LAN currently on the market.
On a file SERVER (the CPU which contains hard disk(s) in use by the
Network), three programs must be loaded which require about 40K.
On a WORKSTATION (a CPU that may have no disks at all), two programs
are used and require about 14K. In addition, the DOS SHARE program
must be loaded on all WORKSTATIONS. If the machine is an 80386
which has high memory available, any or all of these drivers can be
loaded there, freeing up conventional memory.
Hardware Requirements:
---------------------
A Local Area Network contains at least one SERVER and a WORKSTATION.
Some just contain Servers, meaning that they all share hard drives.
While fast CPUs such as 80286 or 80386 machines yield superior
performance, 8086 and 8088 based compatibles can be used. In
addition, Diskless Workstations which boot from ROM then connect to
the Network can be utilized.
Each machine must have a Network card installed. The 2MB/sec cards
made by LANtastic or Ethernet Compatible 10MB/sec cards can be used.
One 8 or 16 bit slot per CPU is required where appropriate. Cables
and terminating resistors are supplied with the Network Startup Kits.
Starting It All Up:
-------------------
LANtastic provides an excellent software installation program which
is executed for each Server and Workstation on the Network. After
installing all necessary hardware, the software must be installed.
If any nodes utilize the SPITFIRE printer option, the LANtastic
software must be configured accordingly so the printer can be
shared across the Network. Setting redirector buffers to anything
other than the default may yield unpredictable printouts. If the
default number of buffers cannot be used, experimentation may be
necessary to determine the correct number of buffers for the LAN.
Page 133
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
Set up a separate SPITFIRE directory for each machine, and edit
each CONFIG.SYS and AUTOEXEC.BAT to both load all the LANtastic
programs used and to automatically boot SPITFIRE. Set CONFIG.SYS
FILES= to the number of nodes multiplied by 25 files per node on
Servers. For example, if the Network has one Server and three
Workstations associated with it, and all have SPITFIRE nodes set
up on them, set FILES=100 on the Server and FILES=25 on each
associated Workstation. These numbers might need to be increased
further when used with net-mail systems.
Workstations that boot when the associated Server is still
booting or not available will wait until the Server comes online.
This will occasionally yield the familiar "gleep" sound known by
anyone who has been near a LANtastic Network! Once the Server
finishes its boot routine, it will bring up its SPITFIRE Node and
all others on associated Workstations will follow.
In the event that any machines on the Network use OS/2 instead of
DOS, it is important to remember that DOS does NOT recognize any
drive or partition that has been formatted with the OS/2 High
Performance File System (HPFS). It is therefore recommended that
any HPFS partitions be the final drive on the system so that the
LAN will not have to "skip over" a drive that is not available.
Multitasking On A LAN:
----------------------
Each machine, whether a Server or a Workstation, can have at least
one node installed. In order to install other nodes on the Network,
additional machines can be added. At this time, DESQview can ONLY
be used on WORKSTATIONS! Windows 3.X can be used on both Servers and
Workstations providing LANtastic NOS of 4.0 or greater is in use.
Running DESQview on a LANtastic Server will cause the system to
crash. DESQview 386 and Windows 3.0 (in 386 Enhanced Mode) can be
successfully run on a Workstation yielding as many nodes as memory
and available serial ports will allow. See the previous sections on
running SPITFIRE under DESQview and Windows for further information.
23.0 SPITFIRE COMPANION PROGRAMS
---------------------------------
Several SPITFIRE companion programs are included within the
SPITFIRE distribution package. These programs are designed to
work with SPITFIRE. Each program is optional and executed
independently of SPITFIRE. It should be noted that the following
programs all contain individual documentation that should be referred
to for complete details. Buffalo Creek Software provides these
programs with SPITFIRE and hopes they are found to be assets in the
operation of a SPITFIRE BBS.
Page 134
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
23.1 DAILYLMT
-------------
DAILYLMT provides an easy to use menu program for creating or
editing SPITFIRE's DAILYLMT.DAT file. It easily allows SPITFIRE
Sysops to add, change or delete security levels within DAILYLMT.DAT.
In addition, an option is provided for the Sysop to review the contents
of the existing DAILYLMT.DAT file. The responses to DAILYLMT's prompts
set the minutes per call, minutes per day, downloads per day, quick
log-on status, kilobytes per day, number of chats allowed, time per
node chat, violation warning ratio and violation enforcement ratio
for each security level. DAILYLMT uses the information that
has been input to format individual lines in the DAILYLMT.DAT file.
23.2 SFDOOR
-----------
SFDOOR is a SPITFIRE utility that is used to create and or modify
SPITFIRE's SFDOOR.MNU file. SFDOOR is menu driven for ease of use and
aids the Sysop in installing or deleting door programs on a SPITFIRE
BBS. SFDOOR also provides an option for reviewing the current
SFDOOR.MNU file. When adding or changing the SFDOOR.MNU file, Sysops
provide information regarding the title for the door's name; whether
the security will be greater than or equal to, equal to, or less than;
and the security level required to access the door. SFDOOR will
then update the SFDOOR.MNU file accordingly.
23.3 SFSENDIT
-------------
SFSENDIT is a SPITFIRE utility that is used to flag files for
sending to a specific caller or group of callers with a common security
level. The file flagged for sending must exist in a SPITFIRE File Area
although it need not be listed in the SFFILES.BBS. SFSENDIT stores
the file area and the filename in the SFUSERS.DAT file. When the
caller next logs on the BBS, he/she is notified that the file is
there for them to download.
SFSENDIT is a limited to flagging one file per caller or group of
callers with a common security level. Similar utilities
exist that offer more complex file flagging schemes. If SFSENDIT
does not meet a Sysop's needs, they can those other utilities.
However, it should be mentioned that it is possible to send more than
one file at a time by compressing the desired files together into one
file. Also, SFSENDIT does not work when a caller is logged on locally.
Page 135
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
If the file downloaded is in a free file area, the caller's statistics
are not updated. If the file downloaded is in a non-free file area,
the callers download statistics are adjusted.
SFSENDIT is menu-driven and easy to use. SFSENDIT provides
options for flagging a file for download by caller or security level,
removing flags by caller or security level, and viewing flags set
by caller or security level.
24.0 SPITFIRE TECHNICAL REFERENCE INFORMATION
----------------------------------------------
There are absolutely no plans whatsoever to release the source
code for SPITFIRE. However, we do feel some information may be of use
to our Sysops to help them understand how SPITFIRE works. If there is
something you would like to know which is not covered in this
documentation, please ask via Buffalo Creek's BBS (515)-225-8496.
We will make the information available to you, if possible.
There is certain information that is required for those interested
in writing utilities and other third party type programs for SPITFIRE.
Listed below are the Turbo Pascal record types that SPITFIRE uses.
When a caller goes through a Door or uses any of the Sysop
configurable features from each menu, SPITFIRE creates a simple
text file named SFDOORS.DAT, SFMAIN.DAT, SFMESS.DAT or SFFILE.DAT in
the SPITFIRE HOME directory. This text file contains necessary
information for the caller to return to SPITFIRE. The text file is
erased when control is returned to SPITFIRE. The following page
contains a list of the information written to each line of the text
file:
Page 136
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
User Number (* the record number in SFUSERS.DAT of the caller *)
User Name (* the full name of the caller *)
Password (* the password of the caller *)
First Name (* the first name of the caller *)
Baud Rate (* baud rate of the caller - i.e. 2400 { 0 if local } *)
Comm port (* COMM port being used by SPITFIRE *)
Time Left (* number of minutes the caller has left this log-on *)
Time (* number seconds since midnight when entering the door *)
Path (* the path in which SPITFIRE.EXE resides {C:\SF\} *)
Ansi_On (* TRUE if caller is using ANSI else FALSE *)
SecLevel (* the security level of the caller *)
Uploads (* the number of uploads the caller has made *)
Downloads (* the number of downloads the caller has made *)
This Time (* total number of minutes allowed for this call *)
Time On (* number of seconds since midnight when logged on *)
Extra Time (* number of seconds the caller has gained since log-on *)
Sysop Next (* TRUE if Sysop next feature has been activated *)
Front End (* TRUE if SPITFIRE was booted from a front end program *)
No DTE Lock (* TRUE if configured for Software Data Flow Control *)
MaxBaud (* maximum baud of the system *)
ErrCorrect (* TRUE if error correction connection *)
LastMConf (* last message conference *)
LastFArea (* last file area *)
Node Number (* Node on which the caller is logged *)
DLs Per Day (* Number of files allowed to be downloaded per day *)
DLs Today (* Number of files the caller has downloaded this day *)
Daily Bytes (* Number of downloadable bytes per day *)
Bytes Today (* Number of bytes the caller has downloaded this day *)
TotalUK (* Number of K bytes uploaded by the caller *)
TotalDK (* Number of K Bytes downloaded by the caller *)
Phone # (* The callers phone number *)
City/State (* The callers city and state *)
Log On Time (* Number of minutes allowed per day *)
Page 137
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
TYPE
UserDefaults = (HotKey,Reserved,Pause);
(* SFMSG[x].PTR *)
MessagePtr = Record
MDate : String[17];
FromWho,
ToWho,
OrgTo : String[30];
Subject : String[40];
NetMail,
MsgSent,
PurgeWhenSent,
ThreadMsg,
ThreadStart,
Private,Deleted,
Received : Boolean;
Where,
NumberofRecords : Word;
Conference : Integer;
MsgNumber,
OrgMsgNumber : LongInt;
FireNetReserved : Array[0..40] Of Char;
Extra : Array[0..40] Of Byte;
End;
(* SFMSG[x].IDX *)
MessageIdx = Record
FromWhoCRC,
ToWhoCRC,
MsgNumber,
OrgMsgNumber : LongInt;
End;
(* SFMSG[x].DAT *)
MessageBody = Record
MsgData : String[127];
End;
(* SFFAREA.DAT *)
FileSystem = Record
FSec : Integer;
FDesc : String[40];
FilePath,
UploadPath : String[60];
ShowToAll,
FEqual,
CDRom,
SearchArea,
FreeDLArea : Boolean;
Extra : Array[1..86] Of Byte;
End;
Page 138
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
(* SFMCONF.DAT *)
MsgSystem = Record
MSec : Integer;
NetMailConf : Boolean;
MDesc : String[40];
MEqual,
PublicMsgConf,
AllowDelete,
BackupNeeded : Boolean;
DaysOld : Word;
DelOldThdMsg : Boolean;
NoOfLines : Word;
Extra : Array[1..75] Of Byte;
End;
(* SFMSG[X].LMR *)
LastMessage = Record
LMsgRed : LongInt;
End;
(* SFUSERS.PTR *)
UsersPtr = Record
Name : String[30];
End;
(* SFUSERS.DAT *)
Users = Record
UserName,
CallingFrom : String[30];
Password,
TimeDate : String[14];
PhoneNumber : String[12];
BirthDate : String[8];
SecurityLevel : Integer;
Uploads,
Downloads,
TotalUK,
TotalDK : LongInt;
TimesOn,
TimeLeft,
Last_M_Conf,
Last_F_Area,
TransPro : Integer;
Defaults : Set Of UserDefaults;
FirstLogDate : String[8];
SubscriptionDate : LongInt;
ConfQueue : Array[0..31] Of Byte;
ExtraBytes : Array[1..75] Of Byte;
AllowPurge,
BadLastOff,
Page 139
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
ScrollBack,
Xpert,
LockedOut,
Deleted : Boolean;
Linelen,
Pagelen,
OnToday,
Illegal,
DLToday,
ForeGround : Byte;
ExtraWord : Word;
DLBytes : LongInt;
NewFCheck : String[8];
OrgSecurity,
ChatsToday : Integer;
FileStr : String[12];
FileArea : Word;
DeleteFile : Boolean;
Extra : Array[1..5] Of Byte;
End;
(* SFEVENTS.DAT *)
EventSchedule = Record
Active : Byte;
DoneToday : Boolean;
Time : Real;
WhichDay : Byte;
End;
(* SFSYSTEM.DAT *)
SysRec = Record
NoInputTime : Byte;
CallsToday,
MsgToday,
UpToday,
DownToday,
DailyLimit,
DailyLogons,
LogonLimit,
SysopSecurity,
NUS,
NUTL,
Available,
Available2,
MaxUsers : Word;
FileDescAmt,
NotUsed2 : Byte;
DoorsAmt : Integer;
Callernum : LongInt;
LastDate : String[8];
StartDate : String[18];
DOSPassword : String[28];
Page 140
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SysopName,
SysMsgName : String[30];
USPhone,
ConvertDesc,
HeySysop,
AddUpedBy,
CommentQue : Boolean;
NumberOfNodes : Byte;
ExtraBoolean,
BootUpTests,
ScanAllMsg,
OfferDefault : Boolean;
ViolationSec : Integer;
NUBirthDate,
CompFileSrch,
DrRetPassword : Boolean;
ExtraBytes : Array[0..86] Of Byte;
End;
(* SFWHOSON.DAT *)
NodesDat = Record
UserNo : Integer;
Mode : Char;
DBytes : Array[1..3] Of Byte;
End;
(* SFNODE.DAT *)
NodeSysRec = Record
DirectScrn,
ShowResult,
Nothing,
PrinterOn,
AnsiAvl,
Private,
SecondPassword,
Page_On : Boolean;
MinimumBaud : Word;
MsgInfo,
NewFileInfo,
SoftControl,
ErrChk : Boolean;
CorrectionMsg : String[3];
WorkPath,
DisplayPath,
ExtranPath,
MsgPath : String[28];
ModInitStr : String[56];
ComPort : Word;
RingNo,
Node : Byte;
MaxBaud,
TimeToday : LongInt;
Page 141
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
TimeComp : Real;
LastDate : String[8];
PrivateSec : Integer;
HangUpDelay : Byte;
UseHiSpeed,
AvailBoolean : Boolean;
IRQ1,
IRQ2,
IRQ3,
IRQ4,
IRQ5,
IRQ6,
IRQ7,
IRQ8 : Byte;
BreakLen : Word;
ExtraBytes : Array[0..21] Of Byte;
ColorMonitor : Boolean;
End;
Page 142
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
24.0 COMMENT FROM THE AUTHOR
-----------------------------
Undoubtedly there are features that can be added to SPITFIRE.
Your suggestions and comments will be appreciated and considered for
future releases, however, you must realize that not all ideas will
or can be implemented. SPITFIRE will more than do the job for you.
However, plans are already in the making for improvements and
additions. Hopefully, with your help SPITFIRE will simply get
better and better.
There were many people who offered suggestions and discovered
problems during the development of SPITFIRE. It would be nice to list
the names of those people but surely I would leave someone out. I do,
however, feel it important to make note that Jacque Shipley kept track
of all the changes and improvements in SPITFIRE version 3.2 and
spent a tremendous amount of time revising the manual.
As mentioned earlier, SPITFIRE is written in Borland's Turbo
Pascal. This entire program was written by yours truly (Mike Woltz).
I would be remiss if I didn't mention that Jacque Shipley, Ira
Lichtenstein and Rick Fournier were very instrumental in maintaining
this manual.
It has taken nearly five years to get SPITFIRE to this point
(maybe I'm slow). This opportunity is taken to thank my wife Ann,
my children Mason, Jesse & Amanda and my grandson Joshua for
tolerating the countless number of hours that were spent writing
and testing SPITFIRE. Lord knows, I could be a better husband,
father and grandpa. I would also like to thank God for giving me the
ability to write this program.
This opportunity is taken to thank each Sysop who has gone to
the expense of registering SPITFIRE. I have had the pleasure of
meeting and working with thousands of people in my life. I think
I am safe in saying that for the most part, SPITFIRE Sysops are SUPER,
top-shelf people. Without these Sysops' support, patience,
cooperation, suggestions, etc., none of this would be possible.
I would like to mention one last thing that has become a concern
to me. After putting nearly five years of my life into SPITFIRE, I
have attempted to keep the cost of this software as reasonable as
possible. I have noticed lately that there are many third party
utilities, etc. being written for SPITFIRE and I have also noticed
that in some cases the registration fee for these utilities is nearly
half the cost of SPITFIRE. It doesn't seem right to charge $20.00 to
$35.00 for a SPITFIRE utility that can be written in a day or two and
I would ask those authors to attempt to keep their prices comparable
to the SPITFIRE project. No rip-offs, OK? Thank you!
Page 143
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NOTES:
Page 144
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NOTES:
Page 145
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
APPENDIX A
----------
MODEM INITIALIZATION STRINGS
----------------------------
The following is a list of modems and their corresponding initial-
ization strings which have been reported to work with SPITFIRE Bulletin
Board Systems.
MODEM MODEM INITIALIZATION STRING
----------------------------------------------------------------------
<1> 96 Fax/Modem 2400..........................ATS0=0Q0V1E0M0H0S2=1X1
<2> ACEEX Fax 9624 Internal 9600 {MNP5}.....ATS0=0Q0V1M5&C1E0H0S2=1X1
<3> ACEEX 2400..................................ATS0=0Q0VE0M0H0S2=1X1
<4> ATI 2400 ETC MNP1-5.........AT&Q5&C1&U1&D0&T5M0H0W1X5V1E0S2=1S0=0
<5> ATI 2400 ETC..................AT&F1&B0&C1&D0&T5M0H0V1E0X2S2=1S0=0
<6> Alpha Concord 1200.........................ATS0=0Q0E0M0V1H0S2=1X1
<7> Amstrad MC 2400......................ATS0=0Q0V1E0M0H0S2=1X2&C1&D0
<8> Amstrad PPC Internal 2400............ATS0=0Q0V1E0M0H0S2=1X2&C1&D0
<9> Anchor..(External 2400).............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0
<10> Anchor..(Internal 2400)....................ATS0=0Q0V1E0M0H0S2=1X4
<11> Anchor..(Internal 2400).............AT&C1&D2&T5M0H0X4V1E0S2=1S0=0
<12> Avatex 1200 HC.............................ATS0=0Q0V1E0M0H0S2=1X1
<13> Avatex 1200I........................ATX1E0M0H0V1S0=0S1=1S9=1S10=2
<14> Avatex 2400 External.............ATS0=0Q0V1E0L0M0&D0&C1X1H0S2=1&W
<15> Avatex 2400II..............................ATS0=0Q0V1E0M0H0S2=1X1
<16> Bit Blitzer 2400................AT&C1&D2E0V1M0S2=1S0=0S6=1S10=1X1
<17> CMP 2400.....................................ATS0=0Q0E0M0H0S2=1X4
<18> CVI Internal 2400 Baud.....................ATS0=0Q0V1E0M0H0S2=1X1
<19> Capetronics MD 1207...1200 Baud..............ATE0V1Q0M0S2=1S0=0X1
<20> Capetronics...........1200 Baud............ATV1E0Q0M0H0S0=0S2=1X1
<12> Cardinal 2400.......................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0
<13> Commstar 2400..(Internal)..................ATS0=0Q0V1E0M0H0S2=1X4
<14> Compaq Internal 2400........................AT&F&C1&D2&B1V1S2=1&W
<15> CompuCom Speedmodem Combo 19200
AT&F2*H2%C1S0=0S2=1&C1&D2\C1Q0V1E1M0H0X4&W
<16> CompuCom SpeedModem Champ 14400
AT&F2*H2%C0S0=0S2=1&C1&D2V1Q0M0X1H0&W
<17> Computer Peripherals 2400..................ATS0=0Q0V1E0M0H0S2=1X1
<18> Computer Peripherals Hook-up 2400s.......AT&FS0=0Q0V1E0M0H0S2=1X4
<19> Evercom 24E................AT&C1&D0&T5M0H0X1V1E0S2=1S0=0\N3\V1\C1
<20> Everex 24...(Internal 2400).........AT&C1&D0&T5M0H0X1V1E0S2=1S0=0
<21> Everex Internal 1200.......................ATS0=0Q0V1E0M0H0S2=1X1
<22> Everex......(Internal 2400).........ATM0E0V1H0X1&D0&T5&L1S0=0S2=1
<23> Everex Internal 2400 MNP 5...AT\N3\Q3\V1\G1\J0%C1&C1&D2X4S2=1S0=0
<24> Fastalk 2400..(External)...................ATS0=0Q0V1E0M0H0S2=1X1
<25> Fastcomm 9696.v32.............ATS0=0S2=1S10=2&H1&I1&M4V1M0X1#X1&W
Page 146
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<26> FastComm HSD 9642T V32V42 9600
TE0M0Q0V1&H1&I1&C1&D3&M4&N0&U0&Q6#X1S46=9W2S0=0S2=1H0X4&W
<27> Franklin FM-2400E..........................ATS0=0Q0V1E0M0H0S2=1X1
<28> Galaxy Networks 38400..........ATS2=1H0S0=0M3V1E0X4Q0&D0W2\V1\Q3:
<29> GVC External 2400..............................ATS0=0V1E0M0S2=1X1
<30> GVC Internal 2400................ATS0=0&C1&D2Q0V1E0M1L3H0S2=1X4&W
<31> GVC v32 v42..............ATE0H0M0Q0X4V1S0=0S2=1S10=75\Q2\N6\V1&D0
<32> GVC 9600 V.32/V.42.....................AT&C1&D2%C1\Q3\J1\N6\V1\L1
<33> GoldStar GSM2400 (External).............ATS0=0Q0V1E0M0H0S2=1X1&C1
<34> Hayes 1200..(External).....................ATS0=0Q0V1E0M0H0S2=1X1
<35> Hayes 1200..(Internal).....................ATS0=0Q0V1E0M0H0S2=1X4
<36> Hayes 2400..(External)..............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0
<37> Hayes 2400..(Internal).....................ATS0=0Q0V1E0M0H0S2=1X4
<38> Hayes 2400.................................ATS0=0Q0V1E0M0H0S2=1X1
<39> Hayes 2400..........................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0
<40> Hook-up 2400S..............................ATS0=0Q0V1E0M0H0S2=1X4
<41> Hook-up 2400...............................ATS0-0Q0V1E0M0H0S2=1X1
<42> IBM Model 5842 2400........................ATS0=0Q0V1E0M0H0S2=1X1
<43> Kyocera KM1200D............................ATS0=0Q0V1E0M0H0S2=1X1
<44> Laser 2400.................................ATS0=0Q0V1E0M0H0S2=1X1
<45> Leading Edge 2400...................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0
<46> Magitronic MB2450..(Internal)..........AT&C1&D2M0H0X1V1E0S2=1S0=0
<47> Megatronics - Internal 2400................ATS0=0Q0V1E0M0H0S2=1X4
<48> Mikon Super Modem...(2400 External)........ATS0=0Q0M0V1E0S2=1X1&W
<49> Motorola 2400..................ATS0=0Q0V1EM0Hos2S10=1X1&C1&D2*MR1
<50> MultiTECH V32.AT&E1&E4&E7&E12$BA0$MB9600$SB19200S0=0S2=1V1M0H0&Q1
<51> MultiTech MultiModem V32...............AT&C1&D2M0X1V1E0Q0S2=1S0=0
<52> Multitech 224EC (2400 Internal)............ATS0=0Q0V1E0M0H0S2=1X1
<53> NEC N2420/30HN.............................ATS0=0Q0V1E0M0H0S2=1X6
<54> Netcomm 1234SA Datalock 2400....AT&C1&D2E0V1M0S2=1S0=0S6=1S10=1X1
<55> Omnitel Encore 2400 HB...............AT&F&C1&D2M0H0X1V1E0S2=1S0=0
<56> Packard Bell 1200..........................ATS0=0Q0V1E0M0H0S2=1X1
<57> Packard Bell 2400 Internal.........ATS0=0&C1&D2Q0V1E0M0H0S2=1X4&W
<58> Penril 2400 DataLink.......................ATS0=0Q0V1E0M0H0S2=1X1
<59> Practical Peripheral (Int 2400)...AT&C1&D2M0H0X1V1E0S7=30S2=1S0=0
<60> Practical Peripheral 2400....................ATS0=0Q0V1E0H0S2=1X1
<61> Practical Peripheral 1200 Baud.............ATS0=0Q0V1E0M0H0S2=1X1
<62> Prentice Popcomm 2400 (c200)........AT&C1&D2&T5M0V1E0Q0X1S2=1S0=0
<63> Prentice 2400..............................ATS0=0Q0V1E0M0H0S2=1X1
<64> Prometheus ProModem 2400 B/2...............ATS0=0Q0V1E0M0H0S2=1X4
<65> Prometheus 2400........................ATE1V1X3X4Q0&C1&D2S2=1S0=0
<66> Smart One..(Best Data Products of CA)......ATS0=0Q0V1E0M0H0S2=1X1
<67> SmartLink (2400 External)................ATE1X1V1Q0M0H0S0=0S2=1&W
<68> SmartOne 2400........................ATS0=0Q0V1E0M0H0S2=1X1&C1&D2
<69> Smarteam.....................................ATS0=0V1E0M0H0S2=1X1
<70> Supra 2400.................................ATS0=0Q0V1E0M0H0H2=1X1
<71> Supra 2400 MNP Internal..........................AT&F2%C\C1M0S2=1
<72> Supra 2400 External..................ATS0=0&C1&D3L3M1V1S2=1E0H0&W
Page 147
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
<73> SupraModem2400 I...........................ATS0=0Q0V1E0M0H0S2=1X4
<74> SupraModem 2400 Plus v.32/v.43.......AT&F2\V2S0=0Q0V1E0M0H0S2=1X1
<75> Tandy 2400..............................ATS0=0Q0&D2V1E0M0H0S2=1X1
<76> Tempo Everex 9600..........................ATS0=0Q0V1E0M0H0S2=1X1
<77> Twincom 38400 v.32/42i...............ATS0=0Q0V1E0M0W2S2=1X1&C1&D2
<78> US Robotics Courier 2400...................ATS0=0Q0V1E0M0H0S2=1X1
<79> USR Courier HST 14400..........ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6
<80> US Robotics HST 9600......(9600 Baud)......ATS0=0Q0V1E0M0H0S2=1X1
<81> US Robotics Sportster...............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0
<82> USR HST 9600..(19200 Baud).....ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6
<83> US Robotics Dual Standard (v32bis/v42bis)
ATS0=0&B1&H1&K3&N0&R2&Y3B0Q0V1E0M0H0S2=1X6
<84> USR Dual Standard 38400......ATS0=0B0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6
<85> VIVA 2400m External MNP5....ATH0Q0V1E0M0S0=0S2=1X1&C1&D2\N3\Q3\V1
<86> VIVA 2400 MNP External...........................AT&F2%C\C1M0S2=1
<87> Zoom 2400 Internal Modem...................ATS0=0Q0V1E0M0H0S2=1X4
<88> Zoom 2400..............................AT&C1&D2M0H0X1V1E0S2=1S0=0
<89> Zoom Fax 9600.......................................ATS7=55S11=60
<90> Zuckerboard Model ZCom24/AT 2400....AT&C1&D2&T5M0V1E0Q0X1S2=1S0=0
<91> Hayes Ultra 9600..ATS0=0S95=2N1W2X4&C1&D2&K3&Q5&R0V1Q0L2S2=1S36=7
Page 148
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NOTES:
Page 149
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
APPENDIX B
----------
SPITFIRE QUESTIONS AND ANSWERS
------------------------------
QUESTION: Why is the "Do You Want ANSI Graphics? <y/N>" displayed
each time a caller logs on the BBS?
ANSWER: Some BBS software stores in the caller's file whether a
caller uses ANSI, and if so, then each time the caller logs
on, ANSI graphics are automatically displayed. When creating
SPITFIRE it was decided to provide the caller with the
opportunity to select the display preferred at each log-on.
There are two basic reasons for including this prompt to each
caller upon log on. First, some callers may call the BBS
from different locations. For instance, many callers call
the BBS from work as well as from home and while they may
have a color monitor at home, they may not at work. In such
a case, they would not want to use color graphics each time
they log-on. Also, observation has proven that a caller may
sometimes choose ANSI graphics and other times not. This may
be due to the amount of time a caller has to spend on the
board since ANSI graphics display slower than those created
in ASCII. For whatever their reasons may be, SPITFIRE
demonstrates increased flexibility by allowing the caller to
make that choice.
QUESTION: With SPITFIRE at the "Ready For Use..." prompt, the phone
rings and SPITFIRE simply does NOT answer the phone, but
rather stays at the "Ready For Use..." prompt. Why?
ANSWER: SPITFIRE relies on verbose result codes to determine an
incoming call, the baud rate of the incoming call and whether
the incoming call is an error correction modem. This problem
would indicate that the modem initialization string is not
correct. You should try using a different initialization
string. Your modem initialization string requires a V1 in it
because this tells your modem to send verbose result codes.
This manual contains a list of several initialization strings
which have been tested and are known to work with the various
modems listed. Also, please note, that the initialization
string must contain the numeric character 0 (zero) and NOT
the alphabetical character O.
Once you have discovered an initialization string that works
with your modem, please report said string and the complete
name and information pertaining to your modem so this
information can be added to this manual.
Page 150
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
QUESTION: When attempting to jump to DOS with the Alt+J command, the
screen blinks but nothing happens. What can be done to
rectify this?
ANSWER: Depending on the individual's system, occasionally the Alt+J
command which allows the Sysop to drop to DOS appears to be
inoperative. The situation can easily be corrected by
setting the path statement in your AUTOEXEC.BAT file so
SPITFIRE can locate COMMAND.COM thru your path.
QUESTION: Why am I unable to Drop To DOS from a remote location
using the Sysop Menu's Drop To DOS feature?
ANSWER: Some systems do not like to redirect their I/O through
a serial port. In such cases, the problem can often be
corrected by using a program written specifically for this
purpose. It is suggested you use either Doorway by Marshall
Dudley or Remdoor by Ken Brown. Both Doorway and Remdoor
incorporate remote drop to DOS capability and are available
for download from Buffalo Creek's BBS. Also, please bear in
mind, SPITFIRE releases control to the SFREMOTE.BAT file
during the remote drop to DOS and lies dormant in memory.
QUESTION: Documentation for external door installation refers to
a file called SFDOORS.DAT. I can not find this file on
my drive. Was it neglectfully not included in my SPITFIRE
package?
ANSWER: When executing a door, SPITFIRE creates two files containing
pertinent caller information required for door operation.
These files are SFDOORS.DAT, required by SPITFIRE, and
DOOR.SYS, a universal format door caller information file.
These are only used during door operation and once the
caller returns to SPITFIRE, SFDOORS.DAT is automatically
erased. Similarly, SFMAIN.DAT, SFFILE.DAT and SFMESS.DAT
created during execution of the Main, File and Message
Menu's Sysop configurable command option are erased when
the caller returns to SPITFIRE.
QUESTION: When a caller uploads a file to "Sysop Only", how is the
Sysop made aware of the uploaded file?
ANSWER: SPITFIRE incorporates two techniques by which the Sysop
is notified that a file has been uploaded privately. A
message is written both in the CALLERS.LOG and also
the HEYSYSOP.LOG file that informs the Sysop that a file
Page 151
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
has been uploaded for "Sysop Only". The CALLERS.LOG and the
HEYSYSOP.LOG file can be viewed from the Sysop Menu and
by pressing F1 at the "Ready..." prompt. These files
should be checked regularly to keep the Sysop aware of the
various BBS activities.
QUESTION: When a caller logs on using the ANSI Color Graphics option,
when the SFFILES.BBS is displayed, occasionally a line in
the file is displayed only in the caller's default color.
Why is this?
ANSWER: In the event a file line is not colored like the others, but
rather uses the caller's default color, that is because the
comma in the file size is either not located properly or does
not exist. SPITFIRE cues off the comma in the file size to
determine the coloring of the SFFILES.BBS listings.
QUESTION: After successfully running SPITFIRE for sometime, all of
a sudden upon booting up, a message is displayed that the
SFNODE.DAT file was not found. Why did this happen?
ANSWER: When SPITFIRE is installed, a file named SFNODE.DAT is
created. This file contains information as to what drive
and directory the SPITFIRE system and work files exist.
If after using the program, the Sysop changes the location
of SPITFIRE (for example, SPITFIRE was originally booted up
on a floppy and then moved to Drive C), SPITFIRE will
continue to look for the files in the originally specified
location. The easiest way to rectify this situation is to
the /P command line parameter to set the drive and directory
used in SPITFIRE. Another option would be to erase the
existing SFNODE.DAT file and allow a new one to be created.
SPITFIRE will automatically assign the default path to the
one in which SPITFIRE.EXE resides.
QUESTION: After adding new files to the various file areas for the
callers to download, I noticed that when a caller logs
onto the BBS and does a check for new files, these files
are not displayed. What is the problem?
ANSWER: There are basically two reasons this could happen. The
first being, it is possible the files were copied into the
download directories but not added to the appropriate
SFFILES.BBS file. Another possible explanation would be
Page 152
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
that the file name, file size, file date and file
description has not been located in the exact specified
place in the SFFILES.BBS. Refer to the section - SPITFIRE
FILE CLARIFICATIONS - of this manual for further information
regarding this subject.
QUESTION: Why are callers unable to view the contents of a ZIP file
after selecting <V>iew A File Archive from the File Menu?
ANSWER: This feature will only work with MS/PC DOS archive files.
It could be that the ZIP file in question was archived by a
system other than MS/PC DOS and then uploaded to your BBS.
QUESTION: The callers log reveals "Message sent and erased" for a
caller who logged onto the BBS. What does this mean?
ANSWER: This would depict a special notice ( <x>.BBS; refer to the
section - SPITFIRE FILE CLARIFICATION - of the manual for
further explanation regarding this subject) was left for a
specific caller. Once the caller receives this message it is
automatically erased. The CALLERS.LOG displays the above
mentioned message to inform the Sysop the message was sent
and then erased.
QUESTION: The HEYSYSOP.LOG reveals a message that a specific archived
file fails the CRC check. What does this mean?
ANSWER: Anytime the Sysop is notified that an archived MS/PC DOS file
fails the CRC check, this means that the specified file is
corrupt and should be erased from your system.
QUESTION: What is the purpose of the SPITFIRE.OVR overlay file?
ANSWER: By accessing the overlay file, many SPITFIRE procedures and
functions are called into memory only when they are needed
rather than being held in memory continuously. Thus the
overlay file drastically reduces the amount of memory which
is required to run SPITFIRE. This is very significant to
Sysops running SPITFIRE in a multi-tasking or networking
environment that is required for multi-node operation.
Page 153
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
QUESTION: I recently registered a door program and was requested by
the author to add him to the caller's file. This was so he
could call the BBS and upload my registered version. The
call was long distance and he wanted to avoid the time
required to complete the log-on questionnaire. Is this
possible to add a caller to the callers file?
ANSWER: A caller may be added to the SFUSERS.DAT file by selecting
ALT+A at the SPITFIRE "Ready For Use..." prompt. A caller
may also be added by using the <U>... Modify Callers feature
found within the Sysop Menu.
QUESTION: Why does SPITFIRE limit the number of files allowed in
an external batch download to seven files and in an
external batch upload to six?
ANSWER: These limits are set by DOS rather than SPITFIRE. DOS
will only allow a command line to contain a specific
number of characters. The seven files for the batch
download and the path for the upload directory and the
six files allowed in a batch upload attain the allowable
DOS limits. SPITFIRE can be configured through the
UseFile feature to allow 99 files per download batch,
provided the external protocol has this capability.
QUESTION: When running SPITFIRE, I get a Runtime error 004 and
SPITFIRE stops. Why?
ANSWER: This runtime error problem is caused by too many files
being open at one time. You will need to increase the
number of files that DOS will allow to be opened at once
by changing your CONFIG.SYS file. Refer to your DOS
manual for further information regarding this subject.
Your system will have to be rebooted after changing your
CONFIG.SYS file.
Page 154
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
QUESTION: Why am I able to upload files that are contained in the
SFNOUP.DAT file? As I understand this is a list of files
which should not be able to be uploaded to the BBS.
ANSWER: SFNOUP.DAT has no affect on any caller with Sysop status.
In other words, any caller with a security equal to or
greater than what you have designated as Sysop security
for your system may upload files, even though they may
be contained in your SFNOUP.DAT.
QUESTION: Why are callers unable to leave a comment to Sysop on my
BBS?
ANSWER: Before SPITFIRE will allow a comment to be left to a Sysop,
the Sysop must be a caller of the BBS. The name the Sysop
uses to log onto the BBS must be the same as the Sysop Caller
Name configured using the ALT+Z configuration window. If a
Sysop enters Sysop as the Sysop Caller Name and then logs
onto the BBS using their real name, SPITFIRE will not allow
a comment to be left to the Sysop because Sysop is not a
caller of the BBS. In this example, the Sysop would need to
change the Sysop Caller Name from Sysop to their real name.
Once this is done SPITFIRE will allow comments to be sent to
the Sysop. In other words, the Sysop caller name must be the
same as the name used for logging onto the BBS.
QUESTION: I just updated my bulletin number #9, yet when a caller
logs on, SPITFIRE does not list bulletin number #9 as being
updated. Why?
ANSWER: For purposes of speed, SPITFIRE stops searching the drive
for new bulletins once a bulletin file is not found. For
example, let's say that SPITFIRE finds BULLET[1..7].BBS
and then does not find BULLET8.BBS. In such case, SPITFIRE
Page 155
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
then stops the search and will not find BULLET9.BBS even
though it may exist on the drive. There are two ways to fix
this. The first and most logical way is to keep your
bulletins in numeric order. The second way would be to
create dummy bulletin files so SPITFIRE will find the dummy
file and continue its search for updated bulletins.
QUESTION: When attempting to boot SPITFIRE or when attempting to
log-on the BBS, I am told that a maintenance operation
is being performed and that I should call back later. There
is no maintenance operation being performed. What do I do?
ANSWER: This could be caused by a number of things which are not
important to discuss. The way to cure the problem is to
erase the SFWHOSON.DAT file found in the WORK directory.
When you reboot SPITFIRE, a new SFWHOSON.DAT will be created.
QUESTION: When I attempt to log-on SPITFIRE, I am told that I am
already logged on another node but I am not. What do I do?
ANSWER: This could be caused by a number of things which are not
important to discuss. The way to cure the problem is to
erase the SFWHOSON.DAT file found in the WORK directory.
When you reboot SPITFIRE, a new SFWHOSON.DAT will be created.
Thank you very much for selecting SPITFIRE.
Page 156
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NOTES:
Page 157
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 1
<x>.BBS/CLR 24
SEC.BBS - 6, 26, 32
19200 - 5, 6, 8, 106, 145, 147
38400 - 5, 6, 42, 146, 147
1K-XMODEM - 6, 72, 74, 92
<<<<<< A >>>>>>
ALL.BBS - 6, 15, 26, 32, 68
Allowdelete - 138
Alt+A - 6, 35, 56, 60, 99, 153
Alt+C - 6, 56, 59, 66
Alt+D - 6, 56, 66, 96
Alt+E - 6, 56, 66
Alt+F - 6, 18, 25, 48, 56, 59, 66
Alt+F1 - 6, 25, 56, 59
Alt+F2 - 6, 56, 59
Alt+F3 - 6, 56, 59
Alt+J - 6, 56, 66, 67, 96, 150
Alt+L - 6, 35, 56, 67
Alt+M - 5, 6, 7, 42, 56, 67, 106
Alt+P - 6, 18, 20, 42, 56, 67, 111, 116
Alt+Q - 6, 56, 67, 68, 108
Alt+R - 6, 18, 43, 56, 68
Alt+S - 6, 7, 56, 68, 108
Alt+T - 6, 11, 13, 53, 56, 63, 68, 87
Alt+Z - 6, 10, 15, 25, 32, 33, 56, 68, 70, 96, 100, 101, 105, 122,
123, 154
ANSI - 3, 6, 13, 15, 24, 25, 26, 27, 28, 29, 30, 31, 36, 55, 72, 73,
85, 88, 97, 98, 109, 110, 128, 131, 136, 140, 149, 151
ANSI.SYS - 3, 6, 15, 27, 128
APPENDIX A - 4, 5, 145
APPENDIX B - 149
ARC - 6, 51, 84, 91, 92, 118, 152
ARQ - 4, 6, 8
ASCII - 6, 22, 26, 30, 34, 35, 40, 52, 74, 89, 92, 97, 98, 113, 118,
149
AUTOEXEC.BAT - 6, 36, 43, 123, 129, 131, 133, 150
<<<<<< B >>>>>>
BPS - 6, 74
Backup Files - 6, 40, 44, 46, 47, 60, 98, 105
BADINIT - 6, 22, 38
Batch - 6, 20, 21, 22, 23, 25, 31, 33, 36, 37, 38, 41, 42, 92, 93,
94, 95, 104, 105, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120,
128, 131, 153
Batch Download - 6, 25, 30, 33, 92, 93, 94, 113, 114, 115, 153
Batch Upload - 6, 25, 30, 94, 95, 119, 120, 153
Baud Rate - 4, 6, 8, 9, 25, 41, 42, 67, 106, 113, 118, 121, 122,
136, 149
BBSNAME - 6, 23, 38
Beep - 6, 39, 40
Binkleyterm - 121
Page 158
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 2
BRK - 3, 4, 112, 113, 114, 116, 117, 119
BRK OFF - 112, 113, 114, 116, 117, 119
BRK ON - 112, 113, 114, 116, 117, 119
BRK.DRV - 3
Buffalo Creek'S Bbs - 1, 6, 19, 31, 34, 38, 41, 67, 91, 107, 109,
110, 111, 113, 116, 119, 135, 150
BUFFERS - 3, 132
Bulletins - 6, 24, 25, 28, 29, 63, 69, 70, 104, 108, 109, 154, 155
BULLET<x>.BBS/CLR - 24, 103
<<<<<< C >>>>>>
CALLERS.TMP - 116
CALLERS.LOG - 6, 9, 21, 57, 58, 60, 98, 99, 104, 150, 151, 152
SFCALLOG - 6, 23
Capture Chat To Disk - 6, 56, 59
Cd-Rom - 6, 14, 26, 51, 85, 90
Chat - 6, 21, 24, 27, 31, 32, 34, 56, 58, 59, 66, 69, 71, 72, 83,
89, 101, 124, 125, 126, 127, 134, 139
CHATDONE - 6, 24
Check Today's Statistics - 6, 56, 58
Command Line Parameters - 5, 6, 41, 42
COMMAND.COM - 4, 112, 118, 150
Conference - 6, 14, 16, 17, 18, 20, 22, 24, 26, 37, 41, 43, 44, 45,
46, 47, 50, 56, 60, 61, 62, 68, 70, 75, 76, 77, 78, 79, 80, 81, 82,
96, 97, 98, 99, 100, 105, 122, 136, 137
Configure - 4, 5, 6, 7, 9, 10, 12, 13, 14, 15, 16, 18, 23, 25, 26,
33, 41, 43, 44, 47, 48, 51, 52, 53, 56, 63, 66, 67, 68, 70, 74, 77,
78, 80, 83, 91, 96, 97, 99, 100, 102, 103, 104, 105, 106, 107, 108,
109, 110, 111, 112, 113, 114, 115, 116, 117, 118,
CONFIG.SYS - 3, 4, 6, 15, 27, 128, 133, 153
CRC - 6, 74, 92, 152
<<<<<< D >>>>>>
DAILYLMT.DAT - 6, 11, 12, 21, 22, 27, 31, 32, 33, 34, 124, 125, 134
Delete - 6, 10, 43, 44, 45, 46, 47, 50, 61, 62, 66, 77, 79, 81, 82,
97, 100, 104, 134, 137, 139
Desqview - 3, 127, 129, 130, 131, 133
Device - 3, 6, 15, 27
Disconnect Delay - 6, 8, 9
Display - 4, 6, 7, 8, 9, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 24,
25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41,
43, 45, 46, 47, 48, 50, 51, 52, 53, 54, 55, 57, 58, 59, 60, 61, 62,
63, 64, 65, 66, 67, 68, 69, 71, 72, 73, 74, 75
Display File Control Character - 6, 39, 40
Display File Path - 6, 18
DLMT - 6, 24
Doors - 3, 6, 30, 36, 69, 70, 75, 83, 84, 90, 106, 107, 108, 109,
110, 139
DORBUL - 6, 24, 109
DOS - 1, 3, 4, 5, 6, 10, 11, 12, 20, 35, 36, 41, 42, 48, 49, 56, 59,
66, 96, 103, 107, 108, 113, 118, 123, 124, 127, 128, 129, 132, 133,
139, 150, 152, 153
Page 159
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 3
Download - 2, 6, 12, 13, 14, 21, 22, 24, 25, 26, 29, 30, 31, 32, 33,
34, 35, 36, 38, 39, 41, 48, 49, 51, 52, 60, 61, 72, 84, 85, 86, 87,
89, 90, 91, 92, 93, 94, 107, 109, 110, 111, 112, 113, 114, 115, 116,
119, 134, 135, 136, 138, 150, 151, 153
DSZ - 3, 111, 112, 114, 115, 116, 117, 118, 119, 120
DVANSI - 131
DVP - 129, 130, 131
<<<<<< E >>>>>>
Edlin - 6, 30
Ems - 121
Erase - 6, 21, 35, 38, 45, 60, 84, 85, 86, 88, 98, 104, 108, 113,
135, 150, 151, 152, 155
Ethernet - 132
Eventime - 6, 24
Events - 6, 36, 43, 56, 66, 96, 101, 102, 104, 105, 121, 139
Exit - 6, 56, 66, 67, 78, 79, 87, 89, 102, 108, 130, 131
External Protocols - 6, 19, 110, 111, 113, 116, 117, 119
<<<<<< F >>>>>>
F1 - 6, 25, 56, 57, 59, 130, 131, 145, 151
F2 - 6, 7, 29, 56, 58, 59, 145, 146, 147
F3 - 6, 56, 58, 59
F4 - 6, 56, 58
F5 - 6, 56, 58
F6 - 6, 56, 58
F7 - 6, 56, 59
F8 - 6, 56, 59
F9 - 6, 56, 59
F10 - 6, 56, 59
File Area - 6, 14, 18, 20, 24, 26, 35, 41, 43, 48, 49, 50, 51, 56,
60, 61, 63, 66, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96,
97, 118, 120, 134, 135, 136, 151
File Tag - 84, 86, 89, 90
FILE<x>.BBS/CLR - 24, 29, 30
FILST<x>.BBS/CLR - 24
Free File - 6, 51, 135
Frontdoor - 121
<<<<<< G >>>>>>
GOODBYE - 6, 7, 24, 69, 72, 75, 83, 84, 85, 87, 88, 89, 93, 94,
96, 97, 107, 108
<<<<<< H >>>>>>
Hardware - 3, 6, 8, 106, 127, 128, 129, 130, 131, 132
HEYSYSOP.LOG - 6, 11, 15, 23, 53, 57, 60, 87, 98, 99, 140, 150,
151, 152
High Speed Async Routines - 6, 8
HIMEM.SYS - 128
<<<<<< I >>>>>>
Initialization String - 4, 5, 6, 7, 8, 9, 41, 42, 67, 106, 145, 149
Page 160
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 4
<<<<<< J >>>>>>
JOKER.DAT - 6, 23, 24, 34, 35, 62, 63
<<<<<< L >>>>>>
Lantastic - 3, 5, 127, 131, 132, 133
LOCKOUT.BBS/CLR - 6, 24, 35, 67
Loop - 103, 104, 108, 124
<<<<<< M >>>>>>
Main Menu - 6, 7, 15, 20, 21, 23, 24, 26, 29, 32, 35, 37, 52, 55, 64,
68, 69, 70, 74, 75, 83, 84, 90, 96, 99, 101, 107, 108, 109, 123, 124
MAIN<x>.BBS/CLR - 23, 24, 29, 30
Maintenance - 6, 26, 40, 61, 96, 97, 98, 124, 155
MAXUSERS - 6, 11, 24, 139
Message Conference - 6, 18, 20, 22, 24, 26, 37, 41, 43, 44, 45, 46,
47, 56, 60, 62, 68, 70, 75, 76, 77, 78, 79, 80, 81, 82, 96, 97, 98,
99, 100, 105, 122, 136
Message Files Path - 6, 17
MGLST<x>.BBS/CLR - 24, 75
MKSFMENU - 6, 31
Modem - 3, 4, 5, 6, 7, 8, 9, 19, 21, 22, 37, 38, 41, 42,
56, 57, 58, 59, 60, 66, 67, 68, 106, 122, 145, 146, 147, 149
Move - 6, 7, 47, 51, 61, 79, 100, 104, 107, 118, 120, 151
MSG<x>.BBS/CLR - 24, 26, 29, 30
Multi-Tasking - 6, 16, 122, 127, 152
Multi-Node - 6, 12, 22, 23, 27, 32, 69, 71, 97, 98, 115, 122, 123,
124, 127, 128, 129, 131, 152
MUV - 3
<<<<<< N >>>>>>
NEEDSYS.BBS/CLR - 6, 25, 59
Network - 122, 127, 131, 132, 133, 146, 152
Net-Mail - 6, 23, 37, 38, 42, 43, 44, 78, 80, 105, 106, 121, 122, 133
Newsletter - 6, 26, 35, 69, 71
NEWUSER.BBS/CLR - 6, 15, 25, 52
Node Chat - 6, 21, 31, 32, 34, 69, 71, 72, 101, 124, 125, 126, 127, 134
Novell - 132
<<<<<< O >>>>>>
Old Message Purge - 6, 44, 46, 47
OS/2 - 133
<<<<<< P >>>>>>
Pack - 2, 6, 20, 23, 29, 31, 34, 36, 37, 39, 40, 42, 43, 46, 47, 62,
66, 77, 96, 97, 98, 105, 106, 107, 121, 123, 124, 133, 146, 150
Pack Message - 96, 97
Pak - 87, 92
Password - 6, 7, 10, 11, 12, 14, 15, 16, 25, 27, 39, 60, 61, 62,
63, 65, 68, 72, 74, 96, 97, 98, 108, 109, 124, 136, 138
Paths - 6, 17, 18, 19, 20, 48, 56, 67, 122
Pif Files - 128
Page 161
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 5
Preview Area - 6, 48, 50
PRIVATE.BBS/CLR - 6, 12, 15
Protocols - 3, 4, 6, 18, 19, 25, 26, 33, 41, 67, 89, 92, 110, 111,
112, 113, 114, 115, 116, 117, 119, 120
Purge Allowed - 6, 60, 61, 65, 66
<<<<<< Q >>>>>>
QEMM - 128
Questionnaires - 6, 23, 30, 52, 71
Queue - 6, 16, 75, 76, 81, 82, 92, 93, 94, 95, 114, 115, 116
Quick Log - 6, 21, 24, 31, 32, 67
<<<<<< R >>>>>>
RATIO - 6, 10, 12, 13, 26, 27, 31, 32, 33, 34, 134
Registration - 1, 142
Result Message - 4, 6, 8
<<<<<< S >>>>>>
Sealink - 3, 6, 74, 92
Server - 132, 133
SF.BAT - 5, 6, 22, 36, 42, 103, 107, 108, 110, 121, 129
SF1STF - 6, 25
SF1STM - 6, 25
SF2SLOW - 6, 9, 25, 28
SFASLEEP - 6, 25
SFBATCHD - 6, 25, 30, 31
SFBATCHU - 6, 25, 30, 31
SFBBSLST.DAT - 6, 74
SFBDAY - 6, 25
SFCHAT.CAP - 6, 59
SFDOOR.Mnu - 6, 22, 30, 107, 134
SFDOORS.DAT - 108, 109, 135, 150
SFDORBAK - 6, 25, 110
SFDORBUL - 6, 25, 109
SFDOWN - 6, 25
SFDR<x>.BBS/CLR - 25, 30
SFEVENTS - 6, 20, 139
SFEXTDN - 6, 25, 28, 33, 111, 112, 114, 115, 116
SFEXTDN,<x>.BAT - 111, 112, 114, 116
SFEXTUP - 6, 25, 28, 116, 117, 119
SFEXTUP<x>.BAT - 117, 119
SFFAREA - 6, 20, 41, 137
SFFILE.BAT - 6, 22, 129
SFFILE.MNU - 6, 28, 29, 84, 109
SFFILES.BBS - 6, 26, 28, 36, 49, 84, 86, 88, 89, 91, 120, 134,
151, 152
SFFILE.DAT - 135, 150
SFIMPEXP - 6, 26, 30, 31, 85, 88
SFINIT.BAT - 4, 6, 22
SFLOGON.BAT - 6, 22
SFLOG - 6, 21, 22, 103, 104
Page 162
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 6
SFMAIN.BAT - 6, 22, 74, 129
SFMAIN.MNU - 6, 28, 109
SFMAINT - 6, 26, 97, 98, 124
SFMAIN.DAT - 135, 150
SFMAIN<x>.QUE/ANS - 23, 52, 54, 55, 71
SFMCONF - 6, 20, 41, 138
SFMESS.BAT - 6, 22, 83, 91, 129
SFMESS.DAT - 135, 150
SFMQDONE - 6, 26
SFMSG.MNU - 6, 28, 109
SFMSGPCK - 4, 6, 23, 37, 105, 106
SFNEWU - 6, 23, 52, 53, 54, 55, 57, 99, 100
SFNODE - 6, 20, 26, 140, 151
SFNOTIME - 6, 26
SFNOUP - 6, 23, 35, 85, 86, 88, 154
SFNWSLTR - 6, 26, 28, 35, 71
SFORDER.MNU - 6, 22, 30, 55
SFORD<x>.BBS/CLR - 26, 30
SFPAGED.BBS/CLR - 6, 26, 27, 38, 58, 71, 72, 83, 89
SFPRELOG.BBS - 6, 26, 28, 68, 124
SFPROMSG.BBS/CLR - 6, 26, 74, 111
SFPROTCO.HLP - 6, 22, 89
SFRATIO.BBS/CLR - 6, 26, 32, 33, 34
SFREMIND.BBS/CLR - 6, 27
SFREMOTE.BAT - 6, 20, 22, 36, 96, 150
SFSEC<x>.BAT - 6, 21, 22, 38
SFSENDIT - 134, 135
SFSYSOP.MNU - 6, 28
SFSYSTEM - 6, 23, 139
SFTIMEUP.BBS/CLR - 6, 27
SFUP.BBS - 6, 15, 23, 27, 36
SFUPCASE.DAT - 6, 15, 23, 36
SFUSERS - 6, 7, 13, 23, 34, 39, 41, 60, 62, 65, 97, 98,
134, 136, 138, 153
SFWHOSON.DAT - 6, 23, 123, 140, 155
SF.BAT - 5, 6, 22, 36, 42, 103, 107, 108, 110, 121, 129
SMARTDRV - 128
SOP<x>.BBS/CLR - 27, 30
SPITFIRE.HLP - 6, 22, 74, 83, 91
SPITFIRE.Ovr - 6, 20, 121, 152
SYSINIT - 6, 27
Sysop Utilities - 6, 69, 74, 75, 83, 84, 91, 96, 103, 104, 125
<<<<<< T >>>>>>
Telink - 6, 74, 92
This System's Info - 6, 69, 71
THOUGHTS.BBS - 6, 28, 41
Tilde - 6, 9, 53
TOOMANY.BBS - 6, 11, 27
Page 163
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 7
<<<<<< U >>>>>>
Undelete - 6, 10, 79, 100, 101
Upload - 6, 10, 11, 12, 13, 14, 16, 17, 22, 23, 25, 26, 27, 30,
32, 33, 34, 35, 37, 39, 48, 49, 51, 58, 60, 61, 62, 72, 84, 87,
88, 89, 92, 94, 95, 101, 103, 105, 116, 117, 118, 119, 120, 136,
137, 138, 150, 151, 152, 153, 154
Usefile - 6, 33, 115, 153
USERINIT.BBS/CLR - 6, 27, 58
Utilities - 2, 6, 37, 48, 69, 74, 75, 83, 84, 91, 96, 103, 104,
122, 125, 134, 135, 142
<<<<<< W >>>>>>
WATCHDOG - 6, 36
WELCOME1.BBS/CLR - 6, 26, 27, 68, 124
WELCOME<x>.BBS/CLR - 27
Wildcards - 86, 88, 91
Wildfire - 3, 109
Windows - 3, 127, 128, 129, 131, 133
Work Files Path - 6, 17, 19
<<<<<< X >>>>>>
Xmodem - 6, 72, 74, 92
Xpert - 6, 69, 72, 75, 83, 84, 91, 96, 100, 139
<<<<<< Y >>>>>>
YMODEM - 6, 41, 67, 92
YMODEM-g - 6, 41, 67, 92
<<<<<< Z >>>>>>
ZIP - 6, 15, 17, 34, 36, 85, 87, 91, 92, 107, 113, 119, 120, 152
ZMODEM - 110, 111, 114, 115, 116, 119
Page 164
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.2 - March 20, 1992 +-
----------------------------------------------------------------------
NOTES: