ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / MISC / SF_31.ZIP / SF31DOC.ZIP / SPITFIRE.DOC

Wrap

Text File | 1991-06-24 | 448.2 KB | 8,308 lines

_________________________________________________________________________ ___________________ ___________________ ________________ S P I T F I R E ________________ _____________ ------------------------- _____________ __________ Bulletin Board System __________ _______ for MS/PC DOS _______ ____ Personal Computers ____ _______________________________ ____ ____ ____ Version 3.1 ____ ___________________ Copyright (C) 1987, 88, 89, 90, 91 by Mike Woltz ------------------------------------------------ Buffalo Creek Software A Member Of The Association Of Shareware Professionals ------------------------------------------ >>> Release Date June 24, 1991 <<< ------------------------------------------ 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....................... 19 4.2 SPITFIRE Work Files......................... 21 4.3 SPITFIRE Message Files...................... 21 4.4 SPITFIRE Display Files...................... 22 4.5 SPITFIRE Menu Files......................... 26 4.6 SPITFIRE File Clarifications................ 29 4.7 About SPITFIRE Display Files................ 35 4.8 Backup Files................................ 36 4.9 THOUGHTS.BBS................................ 37 <5> 5.0 Command Line Parameters..................... 37 5.1 SF.BAT...................................... 38 <6> 6.0 Setting Up the System Records............... 39 6.1 Configuring Message Conference Records...... 39 6.2 Configuring File Area Records............... 43 <7> 7.0 SPITFIRE Questionnaires..................... 47 <8> 8.0 Special Function Keys....................... 50 8.1 Available Special Function Keys............. 51 8.2 Special Function Key Definitions............ 51 <9> 9.0 Main Section Explained...................... 63 9.1 Main Menu Example........................... 64 9.2 Explanation of Main Menu Features........... 64 <10> 10.0 Message Section Explained................... 67 10.1 Message Menu Example........................ 67 10.2 Message Menu Explanation.................... 68 <11> 11.0 File Section Explained...................... 75 11.1 File Menu Example........................... 75 11.2 File Menu Explanation....................... 76 11.3 Upload/Download Protocols................... 82 11.4 Batch Download Menu......................... 82 11.5 Batch Upload Menu........................... 84 <12> 12.0 Sysop Section Explained..................... 86 12.1 Sysop Menu Explanation...................... 86 TABLE OF CONTENTS (cont) ------------------------ # Section Title Page # +--+------------------------------------------------+------+ <13> 13.0 Special Commands for Sysop Status........... 90 13.1 Special Commands for Sysop.................. 91 <14> 14.0 Events Menu Example......................... 91 14.1 Events Menu Explanation..................... 92 <15> 15.0 Hardware/Software Data Flow Control......... 96 <16> 16.0 Screen Save Feature......................... 96 <17> 17.0 SPITFIRE Doors Section...................... 96 17.1 SPITFIRE Doors Display Files................ 99 17.2 SPITFIRE Doors Support...................... 99 <18> 18.0 External File Transfer Protocols........... 100 18.1 External Download Protocols................ 100 18.2 External Batch Download Protocols.......... 103 18.3 External Upload Protocols.................. 105 18.4 External Batch Upload Protocols............ 108 18.5 External Protocol Support.................. 109 <19> 19.0 SPITFIRE Utilizes EMS...................... 109 <20> 20.0 SPITFIRE Net-Mail Capabilities............. 110 <21> 21.0 Operating A Multi-Node SPITFIRE............ 111 21.1 System Requirements........................ 111 21.2 SPITFIRE Configuration..................... 111 21.3 Features Unique To Multi-Node Operation.... 112 21.4 SPITFIRE Node Chat......................... 113 <22> 22.0 SPITFIRE Multi-Tasking/Network Environment. 115 22.1 SPITFIRE With Windows 3.0.................. 116 22.2 SPITFIRE With DESQview..................... 118 22.3 SPITFIRE With LANtastic Network............ 120 <23> 23.0 SPITFIRE Technical Reference Information... 122 <24> 24.0 Comment from the Author.................... 129 Appendix A Modem Initialization Strings................131 Appendix B SPITFIRE Questions and Answers............. 133 Subject Index Page 1 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ----------------------------------------------------------------------- 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, 88, 89, 90, 91 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.1 - June 24, 1991 +- ---------------------------------------------------------------------- "BRK" is Copyright (C) 1985, by Solid Systems "SEALINK" is Copyright (C) 1986 by System Enhancement Associates "WILDFIRE" is Copyright (C) 1988, 1989, 1990, 1991 by Stephen L. Cox "MUV" is Copyright (C) 1989, 1990, 1991 by Buffalo Creek Software "COLDBOOT" is Copyright (C) 1990, 1991 by Buffalo Creek Software "DSZ" is Copyright (C) 1988, 1989, 1990, 1991 by Omen Technology, Inc. "WINDOWS 3.0" is Copyright (C) 1990, 1991 by Microsoft "DESQview 386" is Copyright (C) 1990, 1991 by Quarterdeck Office Systems "LANtastic" is Copyright (C) 1990 by Artisoft "Doorway" is Copyright (C) 1987 through 1991 by Marshall Dudley "Remdoor" is Copyright (C) 1989, 1990, 1991 by Ken Brown 2.0 - SPITFIRE HARDWARE REQUIREMENTS ------------------------------------ The following are considered the minimum equipment requirements for running SPITFIRE: <1> MS/PC DOS Personal Computer <2> At least 256K Memory <3> Fixed Disk (preferable) <4> 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.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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. In the event 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 giving a message of Runtime error 004. SPITFIRE supports a number of features which cause SPITFIRE to search the directories you have specified in your PATH for COMMAND.COM. For these features 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 either 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 tested 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. SPITFIRE defaults to the codes listed below: 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 The SPITFIRE default modem initialization string seems to work with many modems. However, some modems 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 known to work with SPITFIRE can be found in Appendix A of this manual. Page 5 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Mike Woltz and Buffalo Creek Software would like to take this opportunity 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 were gracious enough to provide evaluation products for testing with SPITFIRE and whose products have 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.1 - June 24, 1991 +- ---------------------------------------------------------------------- 3.1 GETTING STARTED -------------------- If you're like most, you're probably not too thrilled with the prospect of reading such a comprehensive document as this. 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> You should have received a file named SF.BAT with your SPITFIRE package. You may need to use 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: Default on drive specification is C: and if you're running SPITFIRE on drive D, then you'll have to change it to D:). After finishing that, look for the line that contains SPITFIRE /I2400 /C1. "/I2400" indicates the top speed of your modem. You may have to change this to the highest speed your modem is capable of. (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. If you are using COMM port 2, you need to change the string to read "SPITFIRE /I2400 /C2". After you've made your 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 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 return or entering "Y" for yes SPITFIRE will create one. Next you will get the prompt "SFNODE.DAT not found! Do you wish to create it? <Y/n>". SPITFIRE defaults to "Y" and by pressing return or entering "Y" for yes SPITFIRE will create one. Next you will get the prompt "SFUSERS.DAT not found! Do you wish to create it? <Y/n>". SPITFIRE defaults to "Y" and by pressing Page 7 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- return or entering "Y" for yes SPITFIRE will create one. Next you will get the prompt "SFFAREA.DAT not found! Do you wish to create it? <Y/n>". SPITFIRE defaults to "Y" and by pressing return or entering "Y" for yes SPITFIRE will create one. Then you will get the prompt "SFMCONF.DAT not found! Do you wish to create it? <Y/n>". SPITFIRE defaults to "Y" and by pressing return or entering "Y" for yes SPITFIRE will create one. The first thing we have to be concerned with is the dilemma of not having properly assigned the correct COMM port. In this event, you will get a message that states "COMM Port Number ? is not responding! SPITFIRE halting." If that happens, refer to step number 2 in this Section. If all goes well, you will then be prompted for the Sysop Name. The name you enter here is the name that users will see credited as Sysop of the system. You should enter your real full name. After that, SPITFIRE will ask you for a Sysop User Name. It is recommended you answer this prompt with "Sysop". It should be noted, that the name you enter here, should be the name that you use to log-on the BBS. Also, it is to this name, that all comments to the Sysop from your users, will be addressed. At this time SPITFIRE will prompt you to input password, phone number, city, state/province and birthdate. SPITFIRE uses the responses you enter here to automatically add you as the first user in the SFUSERS.DAT file. If your modem is malfunctioning, is turned off or not connected, SPITFIRE will then relay 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 the ALT+M keys to modify the modem initialization string to one that is proper 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 User Name when configuring SPITFIRE. (If you use the name "Sysop", the system will ask for a last name. Here you can simply hit <RETURN> and continue.) Then enter the password you have selected previously. When you get to the Main Menu, press F2 and set your security level to 999. Now move from menu to menu and view the various features. After you have viewed and experimented with the various features, log off in a normal fashion. You should see SPITFIRE reset and the "SPITFIRE ready for use" prompt should appear at this point. <5> At the "SPITFIRE ready for use..." prompt you can view or modify your modem configuration by pressing ALT+M Page 8 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- simultaneously. This opens SPITFIRE's Modem Configuration window. The commands that you will see are listed below: --< SPITFIRE NODE 1 MODEM CONFIGURATION >-- <S> Serial Port Number................: 1 Baud Rate.........................: 19200 Initialization String.............: ATS0=0&B1&N0&H1&R2&Y3Q0V1E0M0H0S2=1X1 <1> Line COM1..: IRQ4 <M> Modem - Error Correction Type.....: Yes <2> Line COM2..: IRQ3 <E> Error Correction Message..........: ARQ <3> Line COM3..: IRQ4 <H> Hardware Data Flow Control........: Yes <4> Line COM4..: IRQ3 <A> Answer On What Ring...............: 1 <D> Display Result Messages...........: On <C> Disconnect Delay..................: 28 Use High Speed Async Routines.....: Yes <R> Baud Rate Requirement.............: 1200 Enter Command or <Q>uit - Command <S> is used to specify the COMM Port being utilized by this particular node. Command should be used to enter the maximum baud rate allowed for this node. Command is used to enter the modem initialization appropriate for your modem. Command <M> is used to specify whether the modem is an error correction modem. Pressing <M> will toggle this from Yes to No and vice versa. Command <E> allows you to enter 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> allows you to 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> allows you to specify on what ring, SPITFIRE will answer the incoming call. For instance, Page 9 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- with 1, SPITFIRE will answer the incoming call on the first ring. Most often, you will want this set to 1. Command <D> will allow you to toggle On and Off whether SPITFIRE will display the modem's verbose message. For instance, when toggled on if a user logs on at 2400 baud, CONNECT 2400 will be displayed to the screen and 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> allows you to specify the disconnect delay. This feature is for modems which utilize 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 This switch should be turned on provided your system will operate properly using the high speed routines. In the event your display files are not properly shown to the remote caller, then turn this switch off. Command <R> This switch determines the minimum baud rate a caller must use to access 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. If a caller connects at a baud rate less than what is specified here, SF2SLOW.BBS will be displayed and the caller will be logged off the system. This is a variable option and will disallow callers with a baud rate of 65535 or less. 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. Command <4> Allows the Sysop to configure the IRQ SPITFIRE will use for COMM port 4. Valid options are 1 through 7. Page 10 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <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 User Name...............: Sysop Sysop Security................: 50 <C> New User Security.............: 10 <D> New User Log On Time..........: 45 <E> No Activity Time Limit........: 3 <F> Daily Time Limit..............: 60 <G> Log On Time Limit.............: 60 <H> Maximum Users.................: 500 Maximum User Calls Per Day....: 10 <J> Number of Callers.............: 1 <K> Upload/Download Ratio Prompts.: 10 <L> Upload Time Compensation......: 1.000 <M> Drop to DOS Password..........: Spitfire <N> BBS Starting Date.............: June 1, 1991 <O> Sysop Name....................: John Doe 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> Allows you to change the Sysop User Name. Command Allows you to change the Sysop security level. Any user with an access equal to or greater than this numeric value can read all messages (public and non-public), undelete messages, delete any message and overwrite existing files during uploading (if the filename already exists) as well as being able to perform other functions not available to users with a security level less than this numeric value. Command <C> Allows you to set the default security level for a new user. Command <D> Allows you to set the amount of time on the board for the new user's visit. (First day only) Command <E> Allows you to set 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.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command <F> Sets the amount of time per day a user is allowed on the board. Refer to the section on SPITFIRE FILE CLARIFICATION in this manual for more information on setting time limits. Command <G> Sets the amount of time per call, per user. Refer to the section on SPITFIRE FILE CLARIFICATION in this manual for more information on setting time limits. Command <H> Determines the amount of users you will allow to utilize your BBS. (i.e. - If you have this value set at 500 and you already have 500 users and a new user (501) tries to log-on, the system displays the file MAXUSERS.BBS and logs the user off.) Command This sets the limit of how many times a user can call your board per day. If this amount is exceeded, the system will display TOOMANY.BBS and log the user off. Command <J> This gives you the opportunity to set the number of callers. The reason for this is if you are already running an established board, you can enter the the current number of callers, so as not to start the BBS with Caller Number 1. Command <K> Sets the ratio of downloads to uploads. (i.e. - If a user's ratio exceed 1 upload for every "x" amount of files downloaded; after the download is completed, SPITFIRE sends SFRATIO.BBS unless DAILYLMT.DAT instructs SPITFIRE not to). SFRATIO.BBS is normally displayed to users to notify them that their upload/download ratio is not acceptable. Command <L> This sets the time compensation for time used during an upload. The default is 1.000. Should you wish to have the user rewarded with extra time for an upload, you can increase this numeric value. Command <M> Sets the password that is needed to drop to DOS from a remote location. The default is "Spitfire", but you should change this for the sake of security. Command <N> This provides an opportunity to set the starting date of your bulletin board. The reason for this is 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 that users will see credited as the Sysop of the BBS. Page 12 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command 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 here should be set to correspond to the appropriate node number. In other words, the second node should be set to 2, the third node set to 3, etc. Command <R> 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 that which the Sysop has set here, the display file, PRIVATE.BBS/CLR is displayed, if found, and the caller is logged off the BBS. Those using multi-node systems may 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. Command <T> This specifies the security level that a caller will be changed to if the upload/download ratio is violated and the following conditions are met: 1) The caller has exceeded the upload/download ratio of 1 upload to the amount specified at the ALT+Z configuration screen command <K> Upload/ Download Ratio Prompts plus 6. SPITFIRE adds the additional amount to ensure SFRATIO.BBS/CLR will be displayed to warn the caller of the possible change in status. 2) The caller's security level in the DAILYLMT.DAT file is set to display SFRATIO.BBS/CLR when the upload/download ratio is violated 3) The SPITFIRE Toggle Switch (ALT+T) option <M> Enforce Up/Download ratio is toggled to Yes. **NOTE** SPITFIRE will return the caller to their original security once the caller's upload/download ratio is again within the required ratio limits and provided: 1) The Enforce Up/Download Ratio switch is toggled On. Page 13 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 2) The caller's security level matches the U/D Ratio Violation Security. After setting your configuration for SPITFIRE enter <Q> to Quit and you are returned to the "Ready..." prompt. <7> Once this has been completed, you will need to press the ALT+T key strokes at the SPITFIRE ready prompt to continue your SPITFIRE configuration of setting the SPITFIRE toggle switches. A window will open up which allows to configure the following options: -----< Toggle SPITFIRE Switches >----- <A> US Phone Number Style..........: On Log On - Message Statistics....: On <C> Log On - New File Statistics...: On <D> Require New User Birthdate.....: Yes <E> New User Default Protocol......: Off <F> File Description Conversion....: On <G> Type Of BBS....................: Public BBS <H> Graphics.......................: Ansi Available Second Password................: One Password <J> Direct Screen Writes...........: Yes <K> Net-mail Message Base..........: Yes <L> Multi-Node System..............: Yes <M> Enforce Up/Download Ratio......: Yes <N> Scan All Msg Conferences.......: Yes <O> Comprehensive Upload Search....: On Enter Command <<Q>... Quit>: Command <A> This allows the Sysop to set whether the BBS will use a US phone number format (###-###-####) or allow for SPITFIRE to merely accept any 12 character string entered by the user. The SPITFIRE default is set for the US Phone Number Style. Command This feature allows 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 will be 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> This feature allows the Sysop to designate whether callers will be prompted with new file statistics Page 14 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- when logging on the BBS. If this is set to On and the caller opts to list for new files when logging on the BBS, all new files will be listed. In addition, SPITFIRE will inform the caller of the number of new files since last checked and the total downloadable files and bytes available on the system. SPITFIRE's default is On. Command <D> This feature allows the Sysop to designate whether a new user logging onto the BBS for the first time will be required to enter their birthdate. If toggled to Yes, the birthdate will be required and if toggled to No, the user will not be prompted to enter their birthdate. If Command , Second Password, is toggled to Second Password Required, and the Require New User Birthdate is changed to No, SPITFIRE will automatically change Command to One Password. **NOTE** SPITFIRE uses a caller's birthdate as the second password, when required. It is not possible to require a second password if the BBS does not require the caller to enter their birthdate. Command <E> This feature is used to determine if a new user logging on the BBS can select a default file transfer protocol after completing the new user questionnaire. If this is toggled to Yes, the new user will be presented with this option. If this feature is set Off, the new user will not automatically be 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> This feature allows the Sysop to set SPITFIRE's File Description Conversion on. When this is toggled On, SPITFIRE will automatically convert the first character of each word in the file description to uppercase. All other characters will be lower case. The exception to this being, any words the Sysop includes in SFUPCASE.DAT in the Work File Path will be converted to all uppercase characters, i.e., BBS, SPITFIRE, COMM, ZIP, etc. If this is toggled Off, SPITFIRE makes no attempt to alter the description entered by the caller. SPITFIRE's default is On. Page 15 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command <G> Toggles whether you are going to have a Private or a Public BBS. If you toggle this as a Private BBS, then the user attempting to log-on must be in the users file to be granted access. If you have the system toggled as a Private BBS and a caller tries to log-on as new user, then SPITFIRE will display NEWUSER.BBS /CLR (if found) and will then have the caller answer the new user questionnaire (if found). After the questionnaire is answered, then SPITFIRE will display PRIVATE.BBS/CLR (if found) and log the caller off. A note is left in HEYSYSOP.LOG advising that a new user attempted to log-on. Command <H> Toggles whether or not you wish to offer Ansi graphics. 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, you must have DEVICE=ANSI.SYS in your CONFIG.SYS file. Command Toggles password prompt. If toggled to One Password, the caller simply enters their password. If toggled to Second Password Required, then after entering the first password, the system prompts the user for their birth date. Should the user not know their birth date, the system will log them off. **NOTE** If the BBS is configured not to require a user 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 the users 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, you will want to set this to Yes because using direct screen writes increases the speed of the display. Command <K> Toggles whether your system will be supporting net- mail. If this is toggled on and that Message Conference has been configured to allow net-mail, when a user enters a message, SPITFIRE will prompt the user whether to "Send this Message via net-mail? [Y/n]", with Yes being the default response. If the Page 16 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- user responds with a Yes, then the caller can leave a message to someone who is not a user on the BBS and the message will be marked that it is a message for net-mail. If the caller responds to the prompt with an N then the message must be a person who is a user on the BBS. (This also applies to Carbon Copies). Command <L> Toggles whether you will be operating a multi-node BBS system. If you are operating a single node BBS, this should be toggled to No and if you are operating a multi-node system, this should be toggled to Yes. Command <M> Toggles whether the BBS will enforce the required upload/download ratio. If set to No, it will have no affect on caller. If set to Yes, and the following conditions are met: 1) The caller has exceeded the upload/download ratio of 1 upload to the amount specified at the ALT+Z configuration screen command <K> Upload/ Download Ratio Prompts plus 6. SPITFIRE adds the additional amount to ensure SFRATIO.BBS/CLR will be displayed to warn the caller of the possible change in status. 2) The caller's security level in the DAILYLMT.DAT file is set to display SFRATIO.BBS/CLR when the upload/download ratio is violated the callers security is changed to that specified in the ALT+Z 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 and provided: 1) The Enforce Up/Download Ratio switch is toggled On. 2) The caller's security level matches the U/D Ratio Violation Security. Command <N> This feature allows the Sysop 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 done by selecting <Y>...Your Message option from the Message Menu. Page 17 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <8> When setting up SPITFIRE for the first time, SPITFIRE will automatically create default file paths: --<SPITFIRE FILE PATHS>-- <A> External Transfer Protocols......: No Work Files Path..................: C:\SF\WORK <C> Message Files Path...............: C:\SF\MESSAGE <D> Display Files Path...............: C:\SF\DISPLAY <E> External Transfer Path...........: C:\SF\EXTNOD1 ENTER COMMAND < <Q>...Quit> : SPITFIRE will also place the files it creates in the appropriate file path. 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 which will be used in running SPITFIRE. An explanation of the commands are listed below: Command <A> Toggles whether you wish to implement the use of the external transfer protocol feature. Command Allows you to specify 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 which belong in the Work File Path are specified as such with a (WORK) in the file description in the section - SPITFIRE WORK FILES. Command <C> Allows you to specify the directory in which the SPITFIRE Message Files will reside. All files which belong in the Message File Path are specified as such with a (MESSAGE) in the file description in the section SPITFIRE MESSAGE FILES. Command <D> Allows you to specify 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 which belong in the Display File Path are specified as such with a (DISPLAY) in the file description in the section - SPITFIRE DISPLAY FILES. Page 18 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command <E> 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 will provide the Sysop 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. After you've completed that, you're ready to go! If you're having problems running SPITFIRE, and you're sure you've tried everything, gather together a report of your version number and all the information pertaining to the difficulties (such as System, Modem, Comm Port) you are experiencing and contact Buffalo Creek's BBS (515-225-8496) for registered 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. Further, if you had a problem that isn't covered by this manual and were able to work it out without registered 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. Page 19 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 4.0 SPITFIRE FILE PATHS ----------------------- SPITFIRE supports file 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 the files which are 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 user 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 user 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. 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 they 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 type is referred to as SYSTEM FILES. System Files are mandatory for SPITFIRE's operation and MUST reside in your main SPITFIRE directory from which you run SPITFIRE. Page 20 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 in 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 - Contains scheduled events information. (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) SFMAIN .BAT - Executes Sysop configurable command option available from the Main Menu. (SYSTEM) SFMESS .BAT - Executes Sysop configurable command option available from the Message Menu. (SYSTEM) SFFILE .BAT - Executes Sysop configurable command option available from the File Menu. (SYSTEM) SFDOOR .MNU - SPITFIRE Door Menu. (SYSTEM) SFORDER .MNU - SPITFIRE Questionnaire Menu. (SYSTEM) SFCHAT .CAP - Text file of chat captures. (SYSTEM) CALLERS .TMP - Temporary file used to record 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 each caller 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 whose security is equal to <X> of the SFSEC<X>. (SYSTEM) BADINIT .BAT - Batch file executed when modem initialization fails, i.e., SPITFIRE reports our modem is not responding properly. (SYSTEM) Page 21 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SPITFIRE.HLP - Help with all commands at all menus. This file can be modified via SFHELP.EXE. Consult the documentation accompanying SFHELP.EXE. NOTE: Systems using the Sysop configurable command option(s) will need to modify this help file with SFHELP.EXE 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 are kept 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 will be 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 will allow all nodes to share a common MESSAGE file path. 4.3 SPITFIRE WORK FILES ------------------------ The third type of file category 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 Page 22 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- of SPITFIRE's execution. In the event 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.) SFSYSTEM .DAT - Starting date, number of callers, etc. (WORK) SFUSERS .DAT - User data file. (WORK) SFUSERS .PTR - User data pointer file. (WORK) CALLERS .LOG - Record of the callers' activities. (WORK) HEYSYSOP .LOG - Record of special Sysop notification. (WORK) SFNEWU .QUE - New user questionnaire. (WORK) SFNEWU .ANS - Contains new user questionnaire answers. (WORK) SFMAIN<x>.QUE - Questionnaires at Main Menu for users. (WORK) SFMAIN<x>.ANS - Answers to 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 users purged from the BBS. Contains user'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 will allow all nodes to share a common WORK file path. 4.4 SPITFIRE DISPLAY FILES -------------------------- The following files are used as display files by SPITFIRE. 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 - Displayed to caller of user record #<x>. (DISPLAY) <x>SEC .BBS/CLR - Displayed to all callers of <x> security level. (DISPLAY) ALL .BBS CLR - The file that's displayed to all users upon log-on, unless their security allows for a quick log-on. (DISPLAY) Page 23 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- BULLETIN .BBS/CLR - Lists the bulletins available to the user. (DISPLAY) BULLET<x>.BBS/CLR - <x> file is displayed when <x> bulletin is selected. Maximum of <x> is 99. (DISPLAY) CHATDONE .BBS/CLR - Displayed to user upon completion of chat with the Sysop. (DISPLAY) DLMT .BBS/CLR - Displayed to user when downloads exceed daily limit. (DISPLAY) DORBUL<x>.BBS/CLR - <x> file displayed to the user when <x> bulletin is selected from the Door Bulletin Menu, where the maximum of <x> is 99. (DISPLAY) EVENTIME .BBS/CLR - Displayed to a user who logs on and has their log-on time adjusted to allow an on time event to be completed at a specified time. (DISPLAY) FILE<x> .BBS/CLR - Non-ansi and ansi created file menus for each of the corresponding security levels on the BBS. (DISPLAY) FILST<x> .BBS/CLR - Listing of available File Areas displayed to user with corresponding <x> security level. (DISPLAY) GOODBYE .BBS/CLR - Displayed to user when logging off. (DISPLAY) LOCKOUT .BBS/CLR - Displayed to a user who is 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 on the BBS. (DISPLAY) MAXUSERS .BBS/CLR - Contains message sent to new user when maximum amount of users has 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 - Message Menu displayed to user with corresponding <x> security level. (DISPLAY) NEEDSYS .BBS/CLR - Displayed to user prior to terminating connection when utilizing the ALT+F1 key. (DISPLAY) NEWUSER .BBS/CLR - Displayed to new user (normally rules of the BBS). (DISPLAY) PRIVATE .BBS/CLR - Contains message displayed to new user when logging on a private system after answering the new user questionnaire (if found). (DISPLAY) SF1STM .BBS/CLR - Displayed to the user when entering the Message Section the first time per log-on. (DISPLAY) SF1STF .BBS/CLR - Displayed to the user when entering the file section the first time per log-on. (DISPLAY) SF2SLOW .BBS - Displayed to a user 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 - Displayed to user 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) Page 24 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 - Displayed to a user on user's birthday. (DISPLAY) SFDOOR<x>.BBS/CLR - Displayed to user upon 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 - Displayed to user upon returning to SPITFIRE BBS after completing Door program. (DISPLAY) SFDORBUL .BBS/CLR - Lists the door bulletins available to the user from the SPITFIRE Door Menu. (DISPLAY) SFDOWN .BBS/CLR - Displayed to user 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 list of external download file transfer protocols available for use. (DISPLAY) SFEXTUP .BBS - Contains list of external upload file transfer protocols available for use. (DISPLAY) SFFILES .BBS - Display files which contain 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 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) SFFILE .<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 - Displayed to the user 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 ..Upload option from the File Menu. (DISPLAY) SFMAINT .BBS/CLR - Displayed 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 - Displayed to the user when selecting a specific message conference. <x> would correspond to the conference selected. (DISPLAY) SFMQDONE .BBS/CLR - Displayed to user who attempts to answer a main questionnaire a second time when it is configured to limit the user to one response. (DISPLAY) Page 25 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SFNODE .BBS/CLR - Displayed to the caller after the ALL.BBS/CLR and prior to the <X>SEC.BBS/CLR. (DISPLAY) SFNOTIME .BBS/CLR - Displayed to users 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 user with a corresponding <x> security level. (DISPLAY) SFPAGED .BBS/CLR - Displayed to screen if page goes unanswered or is toggled off. (DISPLAY) SFPRELOG .BBS - The first file displayed upon log-on. (DISPLAY) SFPROMSG .BBS/CLR - Displayed to the user prior to selecting a default file transfer. Sysops should use this display file to inform users that if a default transfer protocol is selected, External Transfer Protocols will not be available to them. (DISPLAY) SFRATIO .BBS/CLR - Displayed to user after a download if the user's download/upload ratio exceeds your setting. (DISPLAY) SFREMIND .BBS/CLR - Displayed to caller upon log-on if such caller was logged off during the previous session due to inactivity. (DISPLAY) SFTIMEUP .BBS/CLR - Displayed to a user whose log-on time has expired. (DISPLAY) SFUP .BBS/CLR - Displayed to user prior to an upload. (DISPLAY) SOP<x> .BBS/CLR - Non-ansi and ansi created Sysop menus for the specified security levels. <x> would correspond to the user's security level. (DISPLAY) TOOMANY .BBS/CLR - Displayed to user who exceeds daily limit of calls. (DISPLAY) SYSINIT .BBS/CLR - Displayed to the user upon entering chat if the Sysop initiated the chat. (DISPLAY) THOUGHTS .BBS - Contains thoughts created for SPITFIRE with THOUGHTS.EXE. (DISPLAY) USERINIT .BBS/CLR - Displayed to user upon entering chat with the Sysop if the user 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 user 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. Page 26 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SPITFIRE supports the use of Ansi/Graphics display files. The Ansi files use the file extension .CLR (color). In the event you have Ansi/Graphics 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 you create display files to be used with SPITFIRE, it is recommended that the line length not exceed 255 characters. Also, in the event, you make Ansi/Graphics available be sure to load the ansi driver (DEVICE=ANSI.SYS) from within your CONFIG.SYS file. NOTE: If you are making ANSI graphics available to your callers, you should duplicate all display <filename>.BBS files to ANSI files and call them <filename>.CLR. For an attractive BBS, you should 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 will automatically display 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 caller, that 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, a caller doesn'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 Page 27 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Knowing this, let's use the following example: B,.... Bulletins,,5,A ------------------------ The "B" is the Command Character. This will be the letter your caller must type to access this particular option. In this instance "B" is used to select Bulletins. ".... Bulletins" is your Command Description. This is how your file entry will be displayed in your menu on the screen. "5" is the minimum Security Level required for the caller to access this function...or even see it! "A" is the SPITFIRE Command Character Identifier and should NEVER be changed. The Command Character Identifier is constant in SPITFIRE programming. This character will be DIFFERENT for every command. Once you've explored 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 users. The SFFILE.MNU file that comes with the SPITFIRE package sets the <D>.... Download A File security at 10. While a user is on-line, hit F2 and change a user's security to 9 and the Download feature is gone for that user. 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. Page 28 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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) 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 advise so the information can be shared with other Sysops using SPITFIRE. 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 Page 29 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 The "x" represents the security level of the current caller. For example, if a caller with a security level of 10 called and selected Ansi/Graphics, then SPITFIRE would look 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 called and choose not to use Ansi Graphics, then SPITFIRE would look for files named MAIN10.BBS, FILE10.BBS, MSG10.BBS, SFDR10.BBS, etc. In the event these files are not found, then SPITFIRE will display the default menus. The reason for different color and Non-Ansi display menu files for each security level is to control what commands are shown to the user. For example, if it takes a security level of 10 to be able to download a file, then FILE10.CLR and FILE10.BBS would 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 users if you decide to have SPITFIRE display created menus rather than having SPITFIRE build 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.EXE. You can download it from Buffalo Creek's BBS at 515-225-8496. 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 display files are furnished with your SPITFIRE package. 4.6 SPITFIRE FILE CLARIFICATIONS --------------------------------- The following files are deserving of a more involved explanation: DAILYLMT.DAT - If you would like to set different DAILY time (SYSTEM) limits according to the user's security level, you want to use this file. Page 30 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- The syntax for each line in the DAILYLMT.DAT is: 10,60,,15,,,500000,,,,Y,QL,#OCA=5,TPNC=5 where: 10 represents the security level for which the subsequent parameters will apply and is followed by one comma 60 represents the daily time allowed for this security level and is followed by two commas 15 represents the number of downloads allowed each day for this security level and is followed by three commas 500000 represents the number of downloadable bytes allowed each day for this security level and is followed by four commas Y a Y or N is used after the number of downloadable bytes to indicate whether SFRATIO.BBS/CLR will be displayed if a user of this security file transfer ration in excess of the amount configured at the ALT+Z's Upload/Download Ratio Y indicates SFRATIO.BBS/CLR will be displayed and N indicates that SFRATIO.BBS/CLR will not be displayed QL will allow 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 user of this security is immediately displayed the Main Menu, avoiding the display of WELCOME2.BBS/CLR to WELCOME9.BBS/CLR, ALL.BBS/CLR, etc. To require a normal log-on, simply do not include QL on the line #OCA=5 is used to determine the Number Of Chats Allowed (node chats) each day on a multi-node system for this security level SPITFIRE defaults to 5. If you desire not to allow node chats for a particular security level, this can be done using #OCA=0. The #OCA=<x> is only applicable to multi-node systems. TPNC=5 is used to designate 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. Using the above example, all users with a security level of 10 would be allowed 60 minutes per day, 10 downloads per day, 500,000 bytes per day, SFRATIO.BBS/CLR would be displayed if the U/D ratio Page 31 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- was exceeded, allowed a remote quick log-on and be limited to 5 node chats per day where the maximum length of time per chat is 5 minutes. DAILYLMT.DAT should contain a line for each security level allowed on the BBS. SFRATIO .BBS/CLR - It's rare when a caller's uploads exceed their (DISPLAY) downloads. Some users 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 users' U/D ratio provided the DAILYLMT.DAT for the user's security level contains a Y. (This U/D ratio is set at the SPITFIRE CONFIGURATION MENU.) SFRATIO will then be displayed, showing your "friendly" words of advice to the user when this situation presents itself. If you are not concerned about a users' 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 Users 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 allows a user to be locked out or marked for deletion using ALT+A at the "Ready..." prompt or from the Sysop Menu. A caller may 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. Page 32 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 is displayed to callers when they (DISPLAY) request the <N>...Newsletter from the Main Menu. This file can be used to send a special message to the users 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 accepts simple usage of wildcards (i.e. *.GIF, TROJAN.*, etc.). You can create an ASCII file that has each name listed on a separate line, such as: TROJAN.* 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 - Used in each File Area for listing files available (DL FILE AREA) for download in 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. 1--------10--------20--------30--------40--------50--------60--------70 SF31-1.ZIP 325,000 06-24-91 SPITFIRE Bulletin Board System (V3.1) 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 is being displayed 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, that 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 whether the line is a file listing. Page 33 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SFUPCASE.DAT - A list of keywords that are converted to or left (WORK) 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 designed to be used with a carrier detect utility such as WATCHDOG. If connection is terminated while a user 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 used to invoke 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. SFMAIN .BAT - Batch file used to execute the Sysop configurable (SYSTEM) Main Menu option. SFFILE .BAT - Batch file used to execute the Sysop configurable (SYSTEM) File Menu option. SFMESS .BAT - Batch file used to execute the Sysop configurable (SYSTEM) Message Menu option. SFMSGPCK.BAT - Batch file executed immediately after packing the (WORK) 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 desired to pack all Message Conferences, except Message Conference #1, the following commands in the SFMSGPCK.BAT could be used: Page 34 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 executed, if it exists, after a caller (SYSTEM) hangs up and prior to the modem being initialized. This will allow utilities (such as creating a listing of the last 10 callers to the BBS) to be executed between callers to the BBS. SFPAGED .BBS/CLR - This file is displayed to the screen in the event (DISPLAY) a user has paged the Sysop and either the page was turned off or the Sysop doesn't answer. 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 message originates. SPITFIRE will tag this on the end of each net-mail message. SFSEC<x>.BAT - This batch file, if it exists, is executed after (SYSTEM) the 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 served as a hub for net-mail. All users who 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, is executed 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 is used to allow the Sysop to send a (DISPLAY) special notice to all users of a certain security level. This file is note automatically erased. Page 35 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- (x=The security level of the users 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 user. Once the user has received it, SPITFIRE automatically erases it. Example: John Doe is User 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. IMPORTANT NOTE: In the event you are using <x>.BBS to send special messages to users and you purge users from the users file by packing the users file, please note that the <x>.BBS may no longer match the user for whom you intended the message. 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 user's first name ^E - Enables the "More Prompt" if previously turned off by ^B ^F - Displays the user's city and state/province ^G - Transmits a beep over the user's PC speaker ^J - Displays the number of files uploaded by the user ^K - Displays the number of files downloaded by the user ^L - Will clear 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 Page 36 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Place these characters in your display file. When SPITFIRE sees a ^B when displaying a file to the screen, then the <More?> prompt will not interrupt the display. When SPITFIRE sees a ^C when displaying the file, then the user cannot abort the screen. A ^N nullifies the affect of a previous ^C and will allow 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 ^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. When SPITFIRE sees a ^D it will display the user's first name at that point in the display. In the same manner, when SPITFIRE sees a ^F, the caller's city and state/province is displayed, a ^H displays the K bytes uploaded by the caller, a ^I displays the K bytes downloaded by the caller, a ^J the number of files uploaded by the caller, a ^K the number of files downloaded by the caller and a ^O the original log-on date of the caller. The ^D, ^F, ^H, ^I, ^J, ^K and ^O should not be used inside a box. It causes characters to be inserted where the information is entered which throws 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 you perform Sysop maintenance like Packing the Message Base or Packing the Users file, SPITFIRE will first make "Backup" copies for Page 37 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- you. If disk space is a problem on your board you could copy the backups to disk or discard them. They are: 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 SFUSERS .$AT - Users Backup File SFMCONF .$$$ - Message Conferences Backup File SFFAREA .$$$ - File Areas Backup File 4.9 THOUGHTS.BBS ---------------- SPITFIRE will display a THOUGHT FOR THE DAY 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. Must be used 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 the /N parameter has no affect. /P - Sets the drive and directory used as the SPITFIRE Work File Path. /Tx - Used with frontend programs to set the amount of time allotted to the caller. This allows systems running under a frontend program to pass the Page 38 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- amount of time remaining before a frontend scheduled event. This only applies to the first caller on immediately after SPITFIRE is booted since SPITFIRE will terminate and return control to the frontend program when the caller logs off. This could also be used when running SPITFIRE as a door. (x indicates the amount of time in minutes the caller will be 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 you have set in the SF.BAT file. This is the reason the use of command line parameters is not recommended. 5.1 SF.BAT ----------- It is advisable to use batch files when running SPITFIRE. Here are some advantages: If an error occurs, and you're using the SF.BAT included with your SPITFIRE package, SPITFIRE will automatically reset with Page 39 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- the SF.BAT file. The SF.BAT file which is included with your SPITFIRE package is vital for running Scheduled Events and Door programs. You will find more information regarding Scheduled Events and Door programs in other Sections of this manual. If you have your AUTOEXEC.BAT file written to automatically boot SPITFIRE upon system startup and you have a power outage, then SPITFIRE will automatically reboot when power is restored. If you should want to configure your AUTOEXEC.BAT file to automatically boot SPITFIRE upon system startup then the last two commands in your 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 these system records in SPITFIRE. The first way is by using ALT key combinations at SPITFIRE's "Ready..." prompt. The second way is through the Sysop Menu which can be accessed from the Main, Message or File Menus. SPITFIRE will allow a total of 256 different Message Conferences and an unlimited amount of 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 be displayed on your screen: MESSAGE SYSTEM RECORD NUMBER 1 Of 1 Conference Description.. : "Untitled Message Conference" Conference Security..... : 5 Net-Mail Conference..... : No Msg Conference Access... : Equal To Or Greater Than User Security Public Msg Conference... : Non-Public Message Allowed User Message Deletion... : Allowed Purge Msgs Older Than... : 120 days Msg Pack Backup File.... : Yes Delete Old Thread Msg... : Yes Page 40 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- >>>> MESSAGE SYSTEM RECORD MENU <<<< <N>.......... Net-Mail Toggle <M>... Conference Description <S>...... Conference Security <#>........ Conference Access <R>............ Record Number <A>........... Add New Record .... Public Msg Conference ............ User Deletion .....Insert New Conference <D>........ Delete Conference <O>.........Old Message Purge ..............Backup Files <+>.......... Next Conference <->...... Previous Conference <T>.....Delete Old Thread Msg <Q>..................... Quit ENTER COMMAND - [N M S # R A P U I D + - T 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 will be allowed to leave messages to another person who is not a user on the BBS. If a message conference is not set up to allow net-mail a caller can only leave messages to other users 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". You will want to 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 user 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 user 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 User Security". Then only users with a security level equal to the security level of the Message Conference will be able to access this conference. Users with a security level greater than or less than the security level of this conference will not be able to access this conference except those users with Sysop security. Page 41 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command <R> - Record Number This option will allow you to enter a specific Message Conference record number. Upon entering the number, all current information for the record number you specified will be displayed. Command <A> - Add New Record By selecting the <A> option, a Sysop can add a new Message Conference to the Message Conference system records. 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 - Public Msg Conference The option is used to toggle whether the Message Conference will allow non-public messages. The default setting of SPITFIRE is to allow non-public messages. By selecting you can toggle this feature so that only messages marked as public are allowed. Command - User Deletion This option toggles whether a user of the BBS will be allowed to delete messages. If it is set at 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 has included this option 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 - Insert Msg Conference By selecting , a Sysop can insert a new Message Conference record between two existing Message Conference records. Upon selecting this option, you are prompted with "Insert before which conference?". A new Message System Record will be inserted preceding the Message System Record 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 42 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Message Conference. For example, let's assume you have five active Message Conferences. Then you insert a new Message Conference 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, you are prompted with "Delete which conference?". The number you enter 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 you have five active Message Conferences. Then you delete Message Conference #4. 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 This option allows you to specify how many days old a message within this individual conference should be prior to it being purged during SPITFIRE's internal message packing procedure. For instance, it this is set to 120 days, when SPITFIRE packs this particular message conference any messages older than 120 days will be purged. Command - Backup Files This option allows you to specify 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 Page 43 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- remain on the drive. If this is set to No, the backup files will be deleted following the completion of the message packing procedure. Command <+> - Next Conference This option is used to move forward from one Message System 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 Message System record. Command <-> - Previous Conference This option allows you to cycle through the the Message System records in reverse order. Pressing the "-" key will move you to the preceding record number. From the first Message System record if the "-" key is pressed you 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 <Q> - Quit Selecting this option will return you to the place in SPITFIRE from where the Message 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. 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 will be displayed on your screen: FILE SYSTEM RECORD NUMBER 1 Of 1 Download Path..... : C:\SF Upload Path....... : C:\SF Area Description.. : "Untitled File Area" Area Security..... : 5 Area Access....... : Equal To Or Greater Than User Security Preview Area...... : No CD Rom Area....... : No Page 44 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- >>>> FILE SYSTEM RECORD MENU <<<< <F>......... Area Description .............. Upload Path <D>............ Download Path <S>............ Area Security <&>.............. Area Access <R>............ Record Number <A>............. Add New Area .......... Insert New Area ............... Purge Area <T>...... Toggle Preview Area <+>................ Next Area <->............ Previous Area <C>...............CD Rom Area <Q>..................... Quit ENTER COMMAND - [F U D S & R A I P T + - C Q]? Command <F> - Area Description You will notice that the default File Area description is "Untitled File Area". You will want to change this to suit your needs. As an example, you may wish to change the description of this area to "Utilities". Select <F> to make this change. Command - Upload Path To change the upload path, you simply select 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. You can set 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 would send the uploads to a sub-directory called "UPLOADS" and allow the caller to download programs from a sub-directory called "GOODIES". (Note: SF is the parent directory.) Upload Path.......C:\SF\UPLOADS Download Path.....C:\SF\GOODIES The next example would send uploads to the same sub-directory where the files available for download exist: Upload Path.......C:\SF\GOODIES Download Path.....C:\SF\GOODIES If you're running on a floppy-based system with your uploads and download files on drive B, and not using sub-directories, you could do the following: Upload Path.......B:\ Download Path.....B:\ Page 45 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user 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 this File Area, then select <S> to change the security level of the area. Command <&> - Area Access You will note that SPITFIRE defaults the File Area Access to "Equal To Or Greater Than". What this means is that any user 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 User Security". Then only users with a security level equal to the security level of the File Area will be able to access this area. Users with a security level greater than or less than the security level of this area will not be able to access this area, except those users with Sysop security. Command <R> - Record Number This option will allow you to enter a specific File Area record number. Upon entering the number, all current information for the record number you specified will be 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. Page 46 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 - Insert New Area By selecting , a Sysop can insert a new File Area System Record records between two existing file area. 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 - 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 user with a security less than the required Area Security will be allowed to preview this file area. This means that the user 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 user can do everything except download from this file area. If this is toggled to No, users 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 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 File Area System record. Command <-> - Previous Area This option allows you to cycle through the the File Area System records in reverse order. Pressing the "-" key will move you to the preceding record number. From the first File Area System record if the "-" key is pressed you will cycle to the last File Area System record. Page 47 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command <C> - CD Rom Area The option allows you to specify 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. 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 user 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 be displayed to the user unless it begins with a special character. SPITFIRE uses established first characters to determine the type of response required by the user. These are: Page 48 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- : - If the first character in the line is a colon, SPITFIRE will pause for the user's input and the user 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 users input. But unlike the colon, the user is not required to respond to the question. The user 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 user to input a date in the format of MM-DD-YY. SPITFIRE will automatically insert the hyphens when the user responds. Once the user has entered the response, SPITFIRE will redisplay it to the user and ask whether the information is correct. # - If the first character in the line is the pound sign, SPITFIRE will pause for the user 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 user 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 user has entered the response, SPITFIRE will redisplay it to the user and ask whether the information is correct. ^# - If a line begins with a caret sign followed by a number, SPITFIRE will adjust the user'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. ~ - If the first character in a questionnaire line begins with a " ~ " 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. &# - 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. Page 49 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- ? - 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 user. This Yes/No question is used to branch to other special questions depending on the user'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 user 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 user who responded with an N should be contained between 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 user responds with a Y and the first plus sign will be ignored, just as any text or questions between where the user 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 user. The user's answer(s) is written to either SFNEWU.ANS or SFMAIN<x>.ANS, depending upon which questionnaire the user is replying to. In addition to the user's answers, the user's name, date and time of the response is recorded within the same file. In the new user questionnaire answer file, SPITFIRE will also note which node the user was logged on to when the questionnaire was answered. The SFNEWU.QUE is displayed to the user upon log-on. The SFMAIN<x>.QUE is displayed to the user 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: Page 50 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user 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 user will be allowed to answer the questionnaire multiple times. If an N is placed after the two commas, the user 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 users 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 users 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 user'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 user'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 user. As with other Ansi and Non-Ansi display menu files, a file should be created for each security level assigned to users 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 user's answers to the corresponding 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 user's answers are appended to the end of the appropriate answer file. If the file does not already exist, SPITFIRE will create it. 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. Page 51 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 8.1 AVAILABLE SPECIAL FUNCTION KEYS ------------------------------------ The special function keys available in SPITFIRE and a brief description of their usage include: F1 - Review Callers & Heysysop Logs & Purged User Listing/New Users Answers F2 - Change Security Level F3 - Toggle Sysop Page/Bell F4 - Toggle Printer F5 - Check Today's Statistics F6 - Take Five Minutes From User F7 - Give Five Minutes To User F8 - Toggle Full/Divided Screen F9 - Capture Chat To Disk F10 - Quit SPITFIRE ALT+F1 - Log User Off With Message ALT+F2 - Log User Off Without Message ALT+F3 - Remove Backup/Log Files ALT+A - Maintains Users File 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 8.2 SPECIAL FUNCTION KEY DEFINITIONS: -------------------------------------- Prior to each individual special function key definition, you will notice an <O>, <R> or . 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> - User must be ON-LINE to perform <R> - SPITFIRE must be at "Ready for Use" prompt to perform - Can be used BOTH when a user's on-line or from the SPITFIRE "Ready..." prompt. Page 52 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <R> F1 (View Log File Menu) Caller's, Heysysop Logs, Purged User List & New User's Answers ----------------------------------------------------------- This option 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 user listing or user responses to SPITFIRE's new user questionnaire. Upon selecting the desired log, you are then presented with the following options for reading the log file: <T>..Today's Date will begin displaying the CALLERS.LOG, HEYSYSOP.LOG SFPURGED.USR or SFNEWU.ANS from its first entry for the current day. ..Beginning Of File will display the CALLERS.LOG, HEYSYSOP.LOG or SFNEWU.ANS or SFPURGED.USR from the beginning of the file, starting with the first entry. <S>..Specify Date will prompt for a date to be entered and will begin 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. <O> F2 (Change Security Level) -------------------------------- If a user is ONLINE and you wish to change the user's security level, you can change it by pressing F2. The user is unable to see that you are changing the security level. 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 user selects for page, then the prompt bell will sound to notify you that a user 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 user pages you, then SFPAGED.BBS/CLR will be displayed to the user and CHAT REQUESTED will display Page 53 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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. 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 users' 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 display the name of the last caller, 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 User) ---------------------------------------- When a user is on-line, you can take 5 minutes from the user's log-on time by pressing F6. If you press F6 in multiples, then multiples of 5 minutes are taken from the user's time. <O> F7 (Give Five Minutes to a User) -------------------------------------- When a user is on-line, you can give 5 minutes to the users log-on time. If you press F7 in multiples, then multiples of 5 minutes are added to the user's time. F8 (Toggle Screen) ------------------------ This feature is used to toggle the split-screen/full-screen option. <O> F9 (Capture Chat To Disk) ------------------------------- 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. 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 Page 54 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 (user 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 user off. If a user is on-line 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 User Off Without Message) ------------------------------------------- If a user is on-line and you wish to disconnect this user, simply press the ALT+F2 keys simultaneously and the connection will be terminated. No message will be displayed to the user. <R> ALT+F3 (Remove Backup/Log Files) ------------------------------------- When selected, this option will display the following menu: >>> FILE REMOVAL MENU <<< <C>.... Erase CALLERS.LOG <H>... Erase HEYSYSOP.LOG <M>..... Erase SFMSG*.$?? .... 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. Page 55 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- ... Erase SFUSERS.$?? When this option is selected, the SPITFIRE user's backup files are erased. <R> ALT+A (Maintain Users File) --------------------------------- At the "Ready..." prompt, when you select ALT+A, you can maintain the user's file, rather than logging on and maintaining the users 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-90 User 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. : 07-01-90 Expert Mode... : Off Times On.. : 3 More Prompt... : On Uploads... : 0 Downloads..... : 3 Purge Allowed. : Yes SPITFIRE USER RECORD MENU (+) Next Record (-) Previous Record (D) Downloads (N) User Name (X) Expert (U) Uploads (A) User Address (&) Delete User (E) Last Msg Conference (P) User Password (L) Lock User Out (C) Last File Area (#) User Phone No (T) Times On (!) Time Left (R) Record Number (M) Subscription Date ($) More Prompt (F) Find User (S) Security Level (B) Birth Date (O) Original Log Date (@) Add New User (Z) Purge Allowed ENTER COMMAND - [+ - D N X U A & E P L C # T ! R M $ F S B O @ Z Q]? You will notice that when this option is selected, SPITFIRE will take you to the last user record. Usually the first record in the user's list is the Sysop's. Therefore, if the Sysop would do any maintenance on the user's file while others are nearby, displaying the last user's record prevents the Sysop's password from being readily visible. This is done to insure the security of your system. 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 user record to another. Pressing the "+" key will allow you Page 56 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user record. Command <-> - Previous Record This option allows you to cycle through the user records in reverse order. Pressing the "-" key will move you to the preceding record number. From the first user record if the "-" key is pressed you will cycle to the last user record. Command <D> - Downloads This option provides the opportunity to change the number of downloads the user is credited as having made on the BBS. This must be a numeric value ranging from 0-9999. Command <N> - User Name This option provides the opportunity to change or edit the user's name. Select "N" and you are prompted to enter the first name of the user and then the last name of the user. When prompted for the first name, you can also enter the first name, space and enter the last name. The information is automatically updated. SPITFIRE will allow up to 30 character spaces for the user'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 user on and off. If the Expert status is off, the user will receive a full menu display. If the Expert status is on, only the command line options will be displayed to the user. Command - Uploads This option provides the opportunity to change the number of uploads the user is credited as having made on the BBS. This must be a numeric value ranging from 0-9999. Command <A> - User Address This option provides the opportunity to change or edit the user's address. When <A> is selected, you are are prompted to enter the city and state/province for the current user 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. Page 57 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Command <&> - Delete User When you press the "&" key you toggle whether or not a user is marked for deletion from the SFUSERS.DAT file. If a user is marked to be deleted, the next time the SFUSERS.DAT file is packed the user will be removed from the SFUSERS.DAT file. You will notice that when a user is marked for deletion a "User Marked For Deletion!" will appear on the menu screen. Also, when marking a user for deletion, you are prompted as to whether to add the user's name to SPITFIRE's JOKER.DAT file Command <E> - Last Msg Conference This option will allow you to change the user'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 - User Password Provides an opportunity to change or edit the user's password. When selected, you will be prompted to enter the new password. SPITFIRE allows up to 14 characters 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 User Out This feature will toggle whether a user is locked out from the BBS. Any user who is locked out will be denied access to the BBS when he/she attempts to log-on. You will notice that when a user is locked out, the words "Locked Out!" are displayed on the menu. When locking out a user, you will be prompted as to whether the user's name should be added to SPITFIRE's JOKER.DAT file. Command <C> - Last File Area This option will allow you to change the user'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 <#> - User Phone No. Provides the opportunity to change or edit the user'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 Page 58 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- ###-###-#### 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 user 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 user 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. Command <R> - Record Number This option will allow you to enter a specific user record number. Upon entering the number, all current information for the record number you specified will be displayed. Command <M> - Subscription date This option will allow you to modify the Subscription Date. This option is included for Sysops who require users to subscribe to gain access to their system. When a new user logs on SPITFIRE will default to setting this as "N/A". If a Sysop wishes to use this option, the subscription date will need to be set. In the event, the Sysop would decide 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 user'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 Page 59 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 User When this option is chosen you are prompted to input the user's first name and then the user's last name of the user to be searched for. It is also possible to enter the entire name when prompted for the first name by separating the first and last name with a space. Once the name is entered SPITFIRE will inform you it is searching for the user whose name you have entered. If the user is located, that user's record becomes the current record being displayed. If no user is found that matches the name you entered, SPITFIRE will inform you it was unable to find a user with the name you have entered. You are then prompted as to whether you wish to continue searching using the first name and initial of the last name of user's name you entered. ***NOTE*** When inputting your search criteria you will notice that SPITFIRE is not case sensitive. Command <S> - Security Level Provides an opportunity to change or edit the security level of the current user record. You will be prompted to enter the number to represent the user'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 numerical values. Command - Birth Date Provides the opportunity to change or edit the user'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 user 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 Page 60 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- have been made, SPITFIRE will prompt you by displaying the new date entered and ask you if these changes are correct. Command <@> - Add New User This option provides you the opportunity to add a new user to the SFUSERS.DAT. Adding a new user locally, eliminates the necessity of the new user responding to the new user questionnaire when calling the BBS for the first time. You will be prompted to provide certain information about the user before they can be added. You will need to answer prompts regarding the user'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 user. The security level you assign will determine what features of the BBS the new user will have access to. Command <Z> - Purge Allowed This option allows you to toggle whether purging the user will be Allowed or Not Allowed. Normally, you 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 user file, the caller will be deleted. However, if the purge not allowed is toggled, the caller will not be deleted from the users 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 user. You can use this feature to answer a page or force a user into chat. When you answer a page, the caller's time on-line is still ticking away. However, when you force a user into chat, the user's time on-line counter is halted until the chat is finished and the user 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. Page 61 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <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 . ALT+J (Jump to DOS - Modem Stays On Hook) ----------------------------------------------- This feature allows you to jump to DOS when a user 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 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 while a locked out caller is logged on, 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 allows you to configure your modem initialization string, COMM port, baud rate, etc. You will also notice a toggle switch for use of 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 Page 62 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- transfer protocols will not be available to the user. (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 advise by calling Buffalo Creek's BBS (515-225-8496), so 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 opens a window which allows you to configure the File Paths you are using and set whether you are using the External File Transfer Protocols on your system. (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 user is on-line. Logging on 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 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 MESSAGE CONFERENCE RECORDS - of this manual for detailed information. 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 user is on-line. If you use this feature while a user is on-line, then when the user logs off, SPITFIRE will sound a audible signal to notify you the BBS is now available and you will be able to log-on immediately. Logging on with ALT+S will display the same initial log-on display files that are displayed to the remote users on the BBS, such as SFPRELOG.BBS, WELCOME1.BBS/CLR, through WELCOME9.BBS/CLR and ALL.BBS/CLR. Page 63 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <R> ALT+T (Toggle SPITFIRE Switches) -------------------------------------- This feature is used 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 is used to configure certain aspects of SPITFIRE. (Refer to the section - GETTING STARTED - of this manual for detailed information.) 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. 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 user 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 users 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 users. (i.e. - If the security level of the .... Bulletins command is set at 25 then a user 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: Page 64 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 9.1 MAIN MENU EXAMPLE ---------------------- >>>>>>>>> MAIN MENU <<<<<<<<< <M>.......... Message Section <F>.............. File Section <S>........... SPITFIRE Doors ................. Bulletins <C>......... Comment To Sysop <#>......... List Active Users <L>............ Locate A User *<W>............ Welcome Screen <Q>....... Questionnaire Menu <T>........ This System's Info <N>............... Newsletter ............ 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. 9.2 EXPLANATION OF MAIN MENU FEATURES -------------------------------------- <M>.... Message Section This feature takes a user from the MAIN Section of SPITFIRE to the MESSAGE Section. <F>.... Files Section This feature takes a user 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. .... Bulletins This feature allows a user to read the available bulletins. <C>.... Comment to Sysop Allows a user 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 Page 65 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <x> rather than Message Number <x>. In order for users to leave a comment to the Sysop, the Sysop must log onto the BBS using the name configured as the Sysop User 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 Users This feature will scroll the name and address of each user of this BBS. It also shows the last date each user logged on. <L>.... Locate a User This feature allows a user to see if a certain person is a user on this BBS. For example, if a user selects this feature, then the user will be asked for a name. After a user enters a name, SPITFIRE will check to see if that person is a user of this BBS. If found, SPITFIRE will inform the user that the person is a user of the BBS and display the date the person last called the BBS. If the last name cannot be matched with a current user, SPITFIRE provides the option of continuing to search for a user with the first name and last name initial corresponding to that which was entered. <W>.... Welcome Screen (Single Node SPITFIRE BBS) This feature allows a user 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 user 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 users. Individual questionnaire files (SFMAIN<x>.QUE) are used to present questions to your users. The user's 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 user certain information about the Page 66 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user. This can be used to keep the users updated with changes or news concerning your BBS. .... Page the Sysop This feature notifies the Sysop that a user has a question or problem to chat about. If the Sysop is not available to answer the page or has the page turned off, SFPAGED.BBS/CLR is displayed to the caller and the caller is prompted as to whether they would like to leave a comment to the Sysop. <G>.... Goodbye & Log Off This feature simply allows a user to log off the BBS. <X>.... Xpert Mode Toggle This feature changes a user's status from a novice to an expert or vice versa. If a user is set as a novice, then the menu descriptions will scroll by after each command. If a user is set as an expert, then only the command letters scroll by after each command. <Y>.... Your Statistics This feature displays certain user's statistics on this BBS and allows a user the opportunity to change some of them. For example, this is where a user can change the keystroke feature, toggle Ansi display on and off or select their default colors. <O>.... Other Bulletin Boards This feature will display SFBBSLST.DAT, a listing of names and phone numbers of other Bulletin Boards. <A>.... Add BBS Name & # This feature allows a user to add a name and phone number to the BBS list to display names and numbers of other bulletin boards described above. The BBS name and number is added to SFBBSLST.DAT. When this feature is used, 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 Page 67 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user from the MAIN Section to the SYSOP section. The BBS is maintained from the SYSOP Section. This feature is not normally available to most users. <?>.... HELP with Commands This feature will provide help for each command available from the MAIN MENU. 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 users. 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 ........... Browse Messages <N>.. Non-stop Message Capture <E>........... Enter A Message <Y>............. Your Messages <A>........Alter Message Queue <T>............... Text Search <F>.............. File Section ............ 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 @ ?>? Page 68 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 10.2 MESSAGE MENU EXPLANATION ------------------------------ <C>.... Change Message Conference This feature allows a user to change to a different Message Conference by entering the number of the Message Conference he/she wishes to change to. If a user selects <Q>uit, the user will remain in the current Message Conference. If a user presses the ENTER key, SPITFIRE will list the Message Conferences available to the user. If a MGLST<x>.BBS/CLR is found it will be displayed here. <R>.... Read Messages This feature allows the user to read public messages and non-public messages sent to and/or from the user in specified Message Conferences. The user 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 user's message queue and prompt the user as to whether to change the current queue. If the user 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 user to the Message Menu. During the process of reading messages, the user 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. Page 69 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <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 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 can not 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 user 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. Page 70 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <N>...Non-stop This feature will display all appropriate messages nonstop. <E>... Enter A Message This feature allows a user to enter a message. If the message the user enters is not to a specific person, then SPITFIRE addresses the message to "All Users". If the message is to a specific person and that person is not a user of this BBS, then SPITFIRE will not allow the user 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. Users are allowed to send carbon copies of a message to other users. There are a total of nine carbon copies available. SPITFIRE will automatically prevent duplicating carbon copy messages to users 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 user 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. Page 71 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <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 .......... Backward Read <E>.... Exit Message Thread <S>...Start Of Thread will take the user 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. ...Backward Read will cycle through the threaded messages in reverse order one message at a time. <E>...Exit Message Thread will return the user to the original message from where the Threaded Message Menu was activated. ... Public Allows a caller with Sysop security to toggle a public message to non-public or to toggle a non-public message to public. ...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. Using this option saves the message to a text file to 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. <Q>...Quit Returns the caller to the Message Menu. <H>.... Hurry Scan Messages This feature allows a user to scan messages in a specific Message Conference or in all Message Conferences. This scan Page 72 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- doesn't provide as much information regarding the messages as the rowse Messages feature. .... Browse Messages This feature allows a user to scan messages in a specific Message Conference or in all Message Conferences. This scan provides the user 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 user to enter a message. If the message the user enters is not to a specific person, then SPITFIRE addresses the message to "All Users". If the message is to a specific person and that person is not a user of this BBS, then SPITFIRE will not allow the user 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. Users are allowed to send carbon copies of a message to other users. There are a total of nine carbon copies available . SPITFIRE will automatically prevent duplicating carbon copy messages to users 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 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. Page 73 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <Y>.... Your Messages This feature will display the user's message statistics. The user 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 user has sent and the total number of messages available on the BBS. The user is then prompted if they would like to read their messages. *NOTE* If the user 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 user 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 <D>... Delete A Conference <C>.... Current Queue List <L>.. List Msg Conferences <S>.... Select Conferences <Q>.. Quit To Message Menu <A>...Add A Conference allows a user to enter a specific number corresponding to the Message Conference number the user wishes to have added to their message conference queue. <D>...Delete A Conference allows a user to enter a specific number corresponding to the Message Conference number the user wishes to have deleted from their message conference queue. <C>...Current Queue List will display to the user the message conferences currently contained in their message conference queue. <L>...List Msg Conferences will display all message conferences on the BBS to which the user has access. <S>...Select Conferences will individually display all message conferences on the BBS to which the user has access and prompt the user as to Page 74 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- whether to include the conference in their message conference queue. <Q>...Quit To Message Menu will return the user 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 user in a message conference that the user 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 users. <T>.... Text Search This feature allows a user to search for specific text in a message. This feature will only search the current Message Conference, for the messages sent to or from the user and public messages. <F>.... File Section This feature takes the user from the MESSAGE Section of SPITFIRE to the FILE Section. .... Page the Sysop This feature notifies the Sysop that a user has a question or problem to chat about. If the Sysop is not available to answer the page or has the page turned off, SFPAGED.BBS/CLR is displayed to the caller and the caller is prompted as to whether they would like to leave a comment to the Sysop. <Q>.... Quit To MAIN MENU This feature takes a user 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 user's status from novice to expert or vice versa. If a user is set as a novice, then the menu Page 75 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- descriptions will scroll by after each command. If a user 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 user to log off the BBS. <@>.... Sysop Utilities This feature takes a user 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. 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 users 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 ............ Upload A File <H>.. Help On Upload/Download ........... 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>? Page 76 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 11.2 FILE MENU EXPLANATION --------------------------- <C>.... Change File Area This feature allows a user to change to a different File Area. If the user selects <Q>uit, the user will remain in the current File Area. If the user presses the ENTER key, SPITFIRE will list the File Areas available to the user. <L>.... List Files In This Area This feature will display the files (SFFILES.BBS) in the current File Area that are available for the user to download. <E>.... Erase A File This feature allows a user the ability to erase a file from a File Area. Normally this feature is only available to users 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 will add the erased file's name to SFNOUP.DAT. <G>.... Goodbye & Log Off This feature simply allows a user to log off the BBS. <D>.... Download A File This feature simply allows a user the opportunity to download a file, provided the user hasn't exceeded the maximum daily download limit and provided the user has enough time left to make the download. The user does not have to be in any specific File Area to perform a download. 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. When the user is prompted for the name of the file to download, if the user inputs the filename and period, SPITFIRE will automatically add the ZIP extension. In other words, if SF31. is entered, SPITFIRE will initiate the download for SF31.ZIP. If the period is not added, SPITFIRE will 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 will be displayed. The ansi/non-ansi screen for this menu, SFIMPEXP.BBS/CLR, will be displayed if found. Otherwise, the following default SPITFIRE menu will display. Page 77 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- >>>> IMPORT/EXPORT MENU <<<< ...... 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 ... Import A File Allows a file to be added to copied from another drive and/or directory to a SPITFIRE file area. SPITFIRE will prompt the user to enter the path name of the file to be copied and also prompt for a description of the file being copied. The filename, size, date and description of the file being copied will be 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 user will be 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 user is prompted as to whether the file should be added to SFNOUP.DAT. <T>... Text Search Description Allows a user to search for certain text within a file description. The user 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 will be displayed. <F>... Find A File Allows a user to search a specific File Area or all File Areas for a specific file. Wildcards are allowed, with the exception of *.*. If a user 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 will be shown, provided the file is listed in the SFFILES.BBS. Page 78 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <L>... List Files (This Area) Will display the SFFILES.BBS for the current file area that are available for the user to download. <C>... Change File Area Allows a user to change to a different File Area. If the user selects <Q>uit, the user will remain in the current File Area. If the user presses the ENTER key, SPITFIRE will list the File Areas available to the user. <Q>... Quit To File Menu Allows the user to exit the IMPORT/EXPORT Menu and return to the File Menu. <G>... Goodbye & Log Off Allows the user to log off the BBS. .... Upload A File This feature simply allows a user the opportunity to upload a file. The user 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 will prompt the user to stand by while it checks to see if the file already exists. While checking for the file, SPITFIRE will check for the same file with a different extension. In other words, if a user attempted to upload SF31.PAK and SF31.ZIP was found, the user would be notified of the existing file and prompted whether to continue with the upload. Also, during the file check, SPITFIRE will remove any trailing digits from the file name. In other words, if a user attempted to upload SF30.ZIP and SF31.ZIP was found, the user would be notified of the existing file and prompted whether to continue with the upload. When the Upload A File option is selected by a caller who is logged on locally, the IMPORT/EXPORT Menu will be displayed. The ansi/non-ansi screen for this menu, SFIMPEXP.BBS/CLR, will be displayed if found. Otherwise, the following default SPITFIRE menu will display. Page 79 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- >>>> IMPORT/EXPORT MENU <<<< ...... 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 ... Import A File Allows a file to be added to copied from another drive and/or directory to a SPITFIRE file area. SPITFIRE will prompt the user to enter the path name of the file to be copied and also prompt for a description of the file being copied. The filename, size, date and description of the file being copied will be 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 user will be 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 user is prompted as to whether the file should be added to SFNOUP.DAT. <T>... Text Search Description Allows a user to search for certain text within a file description. The user 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 will be displayed. <F>... Find A File Allows a user 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 will be shown, provided the file is listed in the SFFILES.BBS. Page 80 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <L>... List Files (This Area) Will display the SFFILES.BBS for the current file area that are available for the user to download. <C>... Change File Area Allows a user to change to a different File Area. If the user selects <Q>uit, the user will remain in the current File Area. If the user presses the ENTER key, SPITFIRE will list the File Areas available to the user. <Q>... Quit To File Menu Allows the user to exit the IMPORT/EXPORT Menu and return to the File Menu. <G>... Goodbye & Log Off Allows the user to log off the BBS. <H>.... Help On Upload/Download This feature will describe the various file transfer protocols available to the user. The help information comes from SFPROTCO.HLP and may be edited with your favorite text editor, provided it saves in ASCII format. .... Page The Sysop This feature notifies the Sysop that a user has a question or problem to chat about. If the Sysop is not available to answer the page or has the page turned off, SFPAGED.BBS/CLR is displayed to the caller and the caller is prompted as to whether they would like to leave a comment to the Sysop. <M>.... Message Section This feature takes a user from the FILE Section of SPITFIRE to the MESSAGE Section. <Q>.... Quit To Main Menu This feature takes a user 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 user to search a specific File Area or all File Areas since a specific date or since the last Page 81 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- time the user searched for new files. In addition to listing the new files, a file statistics message will display to the user 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. <T>.... Text Search This feature allows a user to search for certain text within a file description. The user can search in a specific File Area or in all File Areas. Please note that this feature searches ONLY the file description and not the file name, date or size. These will be displayed, however, when matching text is located. <F>.... Find A File This feature allows a user 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 will be shown, provided the file is listed in the SFFILES.BBS. <X>.... Xpert Mode Toggle This feature changes a user's status from a novice to an expert or vice versa. If a user is set as a novice, then the menu descriptions will scroll by after each command. If a user is set as an expert, then only the command letters scroll by after each command. <?>.... HELP With Commands This feature will display 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 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 user from the FILE Section to the SYSOP Page 82 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Section. The BBS is maintained from the SYSOP Section. This feature is not normally available to most users. <V>.... View A File Archive This feature allows a user to view the contents of a ZIP file. The user will see the file name, file size and file date of each file within the compressed ZIP file. The user does not have to be in a specific file area to utilize this feature. <R>.... Read A Text File This feature allows a user to read a text file available for download. The user may want to use this feature and simply capture the text to save downloading the file. The user 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 <* Presently 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 will 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 Page 83 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- downloads. It is possible for a user to do a batch download without ever having the Batch Download Menu displayed to them. The Batch Download Menu will be displayed if after filling their batch queue the user responds "N" when prompted 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. The SPITFIRE default Download Batch Menu will look like this: >>>> BATCH DOWNLOAD MENU <<<< <A>...... Add To Batch Queue <W>... What's In Batch Queue <D>.... Download 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 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 will not allow the user to exceed their daily download limit or time limit. <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 will also inform 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 will automatically log the caller off after the download(s) are complete. <R>... Remove File From Queue In the event, the caller changes his/her mind about including a file in their batch queue, this feature will allow a caller to remove a file from the batch queue. <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. Page 84 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <L>... List Files (This Area) This feature will display 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 will be 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 will remain in the present File Area. If the caller presses the [ENTER] key, SPITFIRE will list the File Areas available to the caller. If a number corresponding to an available File Area is entered, SPITFIRE will make that File Area the current File Area. <Q>... Quit To File Menu This feature will take 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 will offer 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 have selected to upload a file from the File Menu and selected a file transfer protocol that is capable of doing batch file transfers. It is possible for a user to do a batch upload without ever having the Batch Upload Menu displayed to them. The Batch Upload Menu will be displayed if after filling their batch queue, the user responds "N" when prompted 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 will look like this: >>>>> BATCH UPLOAD MENU <<<<< <A>...... Add To Batch Queue <W>... What's In Batch Queue ...... 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]? Page 85 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <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 will prompt the caller to enter the file name and a description of the file to be uploaded. <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 will display 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 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 Yes, SPITFIRE will automatically log 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 of: "No Description Provided". <R>... Remove File From Queue This feature will allow a caller to remove a file from the batch queue, in the event, the caller changes his/her mind about including a file in their batch queue. <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 will display 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 will be 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 will remain in the present File Area. If the caller presses the [ENTER] key, SPITFIRE will list the File Areas available to the caller. If a number corresponding to an available File Area is entered, SPITFIRE will make that File Area the current File Area. <Q>... Quit To File Menu This feature will take 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. Page 86 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <?>... Help This feature will offer a brief description of the various commands available from the Batch Upload Menu. <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 .......... Pack Users File <J>........ Pack Message Base <R>.. Remove Backup/Log Files <M>...... Message Conferences ......... Print Users File <Q>........ Quit To MAIN MENU ............. Modify Users <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 will not allow the user 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 users, 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 Page 87 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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. <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 user 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. .... Pack Users File This feature allows you to pack SFUSERS.DAT. When using this feature, SPITFIRE will purge any user marked for deletion from the user's file. Also, SPITFIRE gives you the opportunity to purge inactive users. When you select this feature, SPITFIRE will ask if you wish to purge inactive users. If you answer "Y", then you will be asked to purge users that haven't called for <x> amount of days. The value of <x> is determined by you. Those users who haven't logged on for <x> amount of days will then be purged from the user's file. SPITFIRE allows you to toggle whether a purge will be allowed or not allowed for each user. If a user has been toggled to purge not allowed, the user will not be purged regardless, even if they have not called for the <x> amount of days specified here. If you are operating a multi-node system, SPITFIRE will not allow you to pack the users file while a caller is on any of the available nodes. Also, if you are packing the users 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 will be displayed here, if found. Page 88 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <J>.... Pack Message Base When you select this feature, you will be asked if you're sure you want to pack the message base. If you answer "y", SPITFIRE goes through the message files and purges all messages that have been marked as deleted. When configuring your Message Conference records you should have also specified a number of days old for purging messages from each message conference. Any messages older than the number of days you 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 you do this on a regular basis for a couple of reasons: <1> Disk space. <2> Speed (SPITFIRE works faster with fewer messages). If you are operating a multi-node system, SPITFIRE will not allow you to pack the message base while a caller is on any of the available nodes. Also, if you are packing the message base 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 screens, SFMAINT.BBS/CLR, which will be displayed here, if found. <R>.... Remove Backup/Log Files When selected, this option will display the following menu: >>> FILE REMOVAL MENU <<< <C>.... Erase CALLERS.LOG <H>... Erase HEYSYSOP.LOG <M>..... Erase SFMSG*.$?? .... 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. Page 89 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- ... Erase SFUSERS.$?? When this option is selected, the SPITFIRE user's backup files are erased. <M>.... Message Conferences This displays the Message Conference System Record's Menu. From this menu, you are able to configure or modify the Message Conference System Records. For more detailed information, refer to the section - CONFIGURING MESSAGE CONFERENCE RECORDS. .... Print Users File This feature prints out a hardcopy list of users' 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. .... Modify users 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 user and to manually add new users. For further information, refer to the section - SPECIAL FUNCTION KEY DEFINITIONS of this manual. <V>.... View Log Files This option allows you to view SPITFIRE's log files which include; 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 user listing or user responses to the new user questionnaire. Upon selecting the desired log, you are then presented with the following options for reading the log file: <T>..Today's Date will begin displaying the CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR or SFNEWU.ANS from its first entry for the current day. ..Beginning Of File will display the CALLERS.LOG, HEYSYSOP.LOG, SFNEWU.ANS or SFPURGED.USR from the beginning of the file, starting with the first entry. Page 90 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- <S>..Specify Date will prompt for a date to be entered and will begin displaying the CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR or SFNEWU.ANS with the first entry for the date that is 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 you to the Sysop Menu. <X>.... Xpert Mode Toggle This feature changes your status from a novice to an expert or vice versa. If you are set as a novice, then the menu descriptions will scroll by after each command. If you are set as an expert, then only the command letters scroll by after each command. 13.0 SPECIAL COMMANDS FOR SYSOP STATUS --------------------------------------- Definition of Sysop Status -------------------------- When we refer to Sysop Status in this manual, we refer to any user that has a security level equal to, or greater than, the Sysop security level set using the ALT+Z feature at the "Ready..." prompt. The Message section has a few "Special Commands" for users with Sysop Status. When a system is configured to allow a user the ability to delete messages, it's important to note that only the sender and receiver can delete messages, except for users with Sysop Status. Any user with Sysop status can read, delete, and un-delete any message. The rivate command is a toggle that can be used to make a non-public message public and a public message non-public. Last in the message arena is the 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. If you see a message which has been marked for deletion you may undelete it by using this command. Your callers will not be able to read deleted messages unless their access level is considered Sysop Status. When a message is Undeleted, changed from Non-public to Public or changed from Public to Non-public, the message will be re-displayed so Page 91 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- the change can be verified. When a message is changed from Non-public to Public, an option is given which will allow the message to be addressed to "All Users". If a user with Sysop Status attempts to upload a file that already exists, then that user is given the opportunity to overwrite the file. The user will be warned that the file already exists and given the option to overwrite it. SPITFIRE will not allow any other user 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 user name is whom SPITFIRE considers to be the Sysop of the BBS. It is to this user, that comments to Sysop are left by callers from the Main Menu. The Sysop has one feature available to them that no other users have, regardless of the user's security. When opting to read messages, if you have been recognized as the system Sysop, you will be prompted as to whether you wish to preview the messages. What this means is that you 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 you don't have time to respond to all your messages. You can still read the messages and respond to those you choose. Users will not see that you have received the message and feel slighted by the fact that you did not respond. You can later read messages and respond when you 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 92 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 14.1 EVENTS MENU EXPLANATION ----------------------------- <L>.... List An Event SPITFIRE supports 13 events <A..M>. When you select this feature, you will be asked which event <A..M> you wish to view. If the event you select is not configured, SPITFIRE will state that this event is not active. If the event you select is configured, then SPITFIRE will display 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. When you select this feature, you will be asked which event you wish to create. If you select one that is already active, SPITFIRE will notify you that the event selected is already active and then ask you if you wish to change it. If the requested event designation is not active, you will then be asked for the time of the event (use military time. Example: 22:00 = 10pm). Next you will be asked which day for the event. The format looks like this: 0=Sunday, 1=Monday, 2=Tuesday, etc....7=All! Next, you will be prompted as to whether the event should be marked as having been completed for the day. If you reply with N for No, and the event is configured to be executed at a time earlier than when it is created, the event will be executed upon exiting the Events Menu. If you reply with N for No, and the event is configured to be executed at a time later than when it is created, it will be executed at the next scheduled time. If you reply with Y, for Yes, the event will not be executed until the next designated scheduled time, after the day it is created. Lastly, you 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, then SPITFIRE reduces their amount of time on the BBS by that amount. For example, if a caller is allowed 60 minutes when logging Page 93 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user 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 user can withdraw stored online time. After you have selected the desired scheduled event and you have designated the time and day the event is to be performed, you will need to modify the SF.BAT file with your favorite text editor. For illustration purposes, let's assume you wish to execute Buffalo Creek Software's SFLOG.EXE to create a bulletin of the weekly activity on your BBS. SFLOG.EXE requires you 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, we will also assume all files are being run from the default directories, and the event you wish to create will be event A. First, you will need to select <E>.... Enable An Event from the Sysop Utilities Menu and then choose A as the event to be created. You are then prompted for the time the event will be performed. Let's assume you will enter 01:00. Next, you are prompted for the day the event will be performed. Let's assume you wish to run the event every Sunday, so enter 0. Next, when prompted whether to mark the event as being completed type Y. Lastly, you are prompted as to whether the event should be an on time event, so enter N Now, using your favorite text editor, 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.EXE program and enter those in place of the "REM Place Event Commands Here". A completed SF.BAT for Event A would appear as: Page 94 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- :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 user logs off since it has not been marked as an on time event), SFLOG would create a list of the BBS weekly activity. SFLOG must be located in the same directory as CALLERS.LOG (WORK). Therefore, we begin by changing to that directory. SFLOG is then executed and BULLET1.BBS/CLR are created. The bulletins must now be copied to the DISPLAY file directory and to conserve 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 you have configured. If the event is active, SPITFIRE will ask you if you are certain you want to disable it. In the event you answer "Yes", it will be disabled. <Q>.... Quit This feature takes the user 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. By pressing the "+" key you will progress from one event to the next in alphabetical order. When you reach the last event (Event M) and the "+" key is pressed you will cycle to the first event, Event A. <->.... Previous Area This option allows you to cycle through the Events in reverse order. Pressing the "-" key will move you to the preceding event. From Event A, if the "-" key is pressed you will cycle to Event M, the last event. 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 Page 95 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user 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 user 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 you 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 user is on-line when an event is scheduled to occur, SPITFIRE waits until the user logs off and then performs the scheduled event. In this fashion, the user 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 will shell to and execute the commands within the SFMSGPCK.BAT. This batch is intended to perform duties required by 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. Page 96 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 15.0 HARDWARE/SOFTWARE DATA FLOW CONTROL ---------------------------------------- When you select ALT+M to configure your modem, you will notice a Hardware Data Flow Control switch. This switch is turned on (Yes) when you are using a modem that automatically adjusts to the baud rate of the incoming call rather than depending on the software to reset the baud rate of the COMM port. If the switch is set to Yes, then SPITFIRE will not adjust the COMM port to the baud rate of the incoming call. If the switch is set to No, then SPITFIRE will adjust the COMM port to the baud rate of the incoming call. One case of having this switch set to YES is when you are using a USR HST modem at 19200 baud. In this case you need to use the modem initialization string mentioned earlier in this manual. If you are not sure if your modem adjusts to the baud rate of the incoming call, refer to your modem manual. 16.0 SCREEN SAVE FEATURE ------------------------- SPITFIRE contains its own Screen Save Feature to prevent screen-burn. If you are presently using a memory-resident screen-save utility, it is recommended that you 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 your SPITFIRE Bulletin Board System package and can be played on your 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 you with the door installation process. The following example assumes that you do not have any doors presently setup. It also assumes that you are running SPITFIRE on drive C in a directory named SF. In the event you 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. Page 97 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- A brief explanation of the SPITFIRE Door Menu structure will be beneficial to your understanding of installing a SPITFIRE door option. SPITFIRE will support 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 your system. Now let's configure your first door, step by step. The first thing to do is create the file named SFDOOR.MNU, using your favorite text editor. Place it in your system files directory. Since we are configuring door A, SFDOOR.MNU will have only 1 line. For demonstration purposes, let's write the line to look like this: Guess A Number,10 The name of the door (as you'll have it appear in the Door Menu) comes first in the line and is limited to 25 characters. You then enter 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. In the above example, the name of the door is "Guess A Number" and it requires a security level of 10 for a caller to be able to access it. When using SPITFIRE's default menus, this door will not display to any user with a security level less than 10. Next, create a sub-directory of your SF directory named DOOR_A and move the SFGUESS.EXE file into your DOOR_A directory. Consult your DOS manual if you do not understand how to create directories. Now load your SF.BAT file into your favorite text editor and find a line that reads :DOOR_A. You will place your door A commands (valid DOS commands, program execution, etc.) between :DOOR_A and GOTO LOOP. That portion of your 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 Once you have saved the changes in your SF.BAT file to disk, then boot SPITFIRE using your SF.BAT file. At the "SPITFIRE ready for..." prompt, log-on locally either using the ALT+S or ALT+Q Page 98 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- keystrokes. When you get to the Main Menu, select "<S>... SPITFIRE Doors" and your 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 you select <A> at this point, you will see a message SPITFIRE displays 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 user information for executing doors on a SPITFIRE BBS and DOOR.SYS is the universal accepted format containing user information by those attempting to standardize the door user information file. These files are created when a user enters a door and automatically erased when the caller returns to SPITFIRE.) SPITFIRE, after creating the SFDOORS.DAT and DOOR.SYS files, terminates, sending the appropriate ERROR CODE to your SF.BAT file. In the case of door A, SPITFIRE sends an ERROR CODE of 34 to SF.BAT which will cause the commands you have placed between :DOOR_A and GOTO LOOP to be executed. In the event you entered the correct commands between :DOOR_A and GOTO LOOP, you will see SFGUESS run. When you finish running SFGUESS, you will see SPITFIRE re-boot and you will be prompted for your password. If a caller enters a door while logged on SPITFIRE, there are three tests that must be passed for the caller to return to SPITFIRE after exiting the door program. First, SPITFIRE must find SFDOORS.DAT in the system files directory. Second, SPITFIRE must find a carrier detect. And third, the caller must enter the correct password when prompted for it. In the event a door is entered during a local log on, there are two tests that must be passed. SPITFIRE must find the SFDOORS.DAT file and 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. In the event you do not wish to run third party programs with SPITFIRE through the Door feature, simply set the security level of the SPITFIRE Door command in the SFMAIN.MNU, SFFILE.MNU and SFMSG.MNU files high enough so your users 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 Page 99 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 will use certain display files during the use of the Doors feature, if such files are found. It is important to note that SPITFIRE will work just fine 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 user. This is displayed to the user 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) SFDR<x> .BBS/CLR - Non-Ansi and Ansi door display menu file displayed to the user with a corresponding <x> security level. (DISPLAY) SFDOOR<x>.BBS/CLR - Non-Ansi and Ansi screen that is displayed to the user 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 user 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 will be supported by Buffalo Creek Software for registered users of SPITFIRE. Please keep Page 100 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- in mind once a user 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. If you should you have problems with the door program itself, please 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 users to select an external protocol as their default file transfer protocol. This is important for users to know, so SPITFIRE has provided a means to notify the caller that External Protocols exist. When a new user logs on for the first time and the Sysop has configured the BBS to require the New User 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 will display 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 a download external protocol, step by step. To start, an assumption is being made that you have a copy of DSZ.COM (Forsberg's ZModem). If you do not have a copy, you can download it from Buffalo Creek's BBS. You will need to use your Page 101 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 you will have available. For the purpose of setting up ZModem as your first download external protocol, your SFEXTDN.BBS file would have one line that would look something like this: <A> ZModem Now place SFEXTDN.BBS in the directory you have configured as your Display Files Path. Next, boot SPITFIRE. At the "SPITFIRE ready for use" prompt, simultaneously press your ALT+P keys. The SPITFIRE FILE PATHS window will open. If the External Transfer Protocols switch is set to "No", then toggle it to "Yes" by selecting <A>. Now, select <Q> to Quit to the "SPITFIRE ready for use" prompt and then select F10 to exit SPITFIRE. An assumption (for demonstration purposes) is being made here that you are running SPITFIRE on your C drive in a directory named SF and that the External Transfer path is C:\SF\EXTERNAL. The next step is to place DSZ.COM in the directory you set as your External Transfer Path (example... C:\SF\EXTERNAL). Next, using your favorite text editor, create a batch file named SFEXTDNA.BAT in the directory designated as your 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. Echo Off BRK OFF Echo Executing SPITFIRE'S External Protocol #1 CD\SF\EXTERNAL DSZ.COM %2 sz %3 ERASE %3 CD\SF BRK ON Now that SFEXTDNA.BAT, with the above listed commands, resides in the directory you set as your External Transfer Path, you have configured your first download External Protocol. The actual contents of the batch files you will use will depend on the specific protocols. The above is only a sample batch file that should work fine with DSZ.COM. Before the commands in the above described batch file are explained, it is important to note when a caller selects ... from the download protocol list, then SPITFIRE shells to a batch file Page 102 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 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 Now, an explanation of these batch files and what SPITFIRE does in preparation to use these batch files is appropriate and important for you 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 you have configured as your 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. Now, if all tests were passed and the file was successfully copied, then SPITFIRE switches to the directory you have configured as your 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 is going to require 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. Upon performing this shell, SPITFIRE is passing 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). In the event you're are not familiar with the use of the % command in batch files, refer to your 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 you have configured as your External Transfer Page 103 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Path for download. Last, SPITFIRE checks the amount of time that 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, then 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, then SPITFIRE assumes that the transfer was not successful and the callers data is not updated. You will notice the example batch file (above) has a command to change to the directory you have configured as your External Transfer Path. You will also notice there is a another command to change back to the SPITFIRE system files directory. Further, you will notice there is a command to erase the file that was copied to the directory for download. These commands do not have to be in the batch files you create because SPITFIRE automatically performs these chores. However, it is quite permissible for the commands to be in the batch file and can act as a safeguard. You will also 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. You will need this utility for the protection of your system. BRK.ZIP can be downloaded from Buffalo Creek's BBS. 18.2 EXTERNAL BATCH DOWNLOAD PROTOCOLS -------------------------------------- SPITFIRE will also allow 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 discussed in the section - EXTERNAL DOWNLOAD PROTOCOLS - also applies to the External Batch Download Protocols. However, there are some significant differences which warrant mentioning. When creating the SFEXTDN.BBS file, use your favorite text editor to list the name of the external batch file protocol you will have 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 Zmodem Batch,Batch The SFEXTDN.BBS must reside in the path assigned as your Display File Path. Page 104 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- The DSZ.COM must be placed in the directory you have configured as the External File path. The next thing to be done is using your favorite text editor, create a SFEXTDN<A..N>.BAT file which will contain the commands necessary to execute the batch download. For the above example, SFEXTDNB.BAT will need to be created to perform an 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\EXTERNAL DSZ.COM %2 sz %3 %4 %5 %6 %7 %8 %9 IF EXIST %3 ERASE %3 IF EXIST %4 ERASE %4 IF EXIST %5 ERASE %5 IF EXIST %6 ERASE %6 IF EXIST %7 ERASE %7 IF EXIST %8 ERASE %8 IF EXIST %9 ERASE %9 CD\SF BRK ON Note, 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 user may enter if the batch download external protocol is selected. SPITFIRE will allow up to seven files to be transferred during an external batch download. %3 through %9 represent the file names the user includes in the batch queue. As explained in the EXTERNAL DOWNLOAD PROTOCOL section of the manual, the commands to erase the files which have been selected for download and the command to change back to the SF directory are an added safety measure. SPITFIRE will automatically do this. 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 you have 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 will exceed the amount of available disk space or will exceed the number of daily allotted downloads for the user, an appropriate message will be displayed prior to downloading the files presently in the batch queue. Page 105 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 18.3 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 may be best at this point to go thru setting up an upload external protocol, step by step. To start, an assumption is being made you have a copy of DSZ.COM (Forsberg's ZModem). If you do not have a copy, you can download it from Buffalo Creek's BBS. Now, you will need to use your favorite text editor and create a display file named SFEXTUP.BBS, a simple text file which will contain the names of the external protocols you will have available. For the purpose of setting up ZModem as your first upload external protocol, your SFEXTUP.BBS file would have one line that would look something like this: <A> ZModem Now place SFEXTUP.BBS in the directory configured as your Display Files Path. Next, boot SPITFIRE. At the "SPITFIRE ready for caller" prompt, simultaneously press your ALT+P keys. The SPITFIRE FILE PATHS window will open. If the External Transfer Protocols switch is set to "No", then toggle it to "Yes" by selecting <A>. Now, select <Q> to Quit to the "SPITFIRE ready for use" prompt and then select F10 to exit SPITFIRE. An assumption (for demonstration purposes) is being made here that you are running SPITFIRE on your C drive in a directory named SF and that your External Transfer Path is C:\SF\EXTERNAL. The next step is to place DSZ.COM in the directory you set as your External Transfer Path (example... C:\SF\EXTERNAL). Next, using your favorite text editor, create a batch file named SFEXTUPA.BAT in the directory designated as your 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 users 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.COM %2 rz %3 MUV %3 %4 CD\SF BRK ON Page 106 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Now that SFEXTUPA.BAT, with the above listed commands, resides in the directory you set as your External Transfer Path, you have configured your first upload External Protocol. The actual contents of the batch files you will use will depend on the specific protocols. The above is only a sample batch file and should work fine with DSZ.COM. Before the commands in the above described batch file are explained, it is important to note when a caller selects ... from the upload protocol list, then SPITFIRE shells to a batch file named SFEXTUPB.BAT. As stated before, there are fourteen external protocols allowed and 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 for you 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 upload. If all tests were passed, then SPITFIRE changes to the directory you have configured as your 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), so 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 being 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). In the event you're are not familiar with the use of the % command in batch files, refer to your DOS manual for specific details. Page 107 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- When the external protocol file transfer program has finished its work, control is automatically returned to SPITFIRE. Once control is returned, then 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 then credited with the upload and other clean up chores are performed. In the event SPITFIRE does not find the file in the appropriate File Area, then SPITFIRE assumes the upload was aborted. You will notice that the example batch file (above) has a command to change to the directory you have configured as your External Transfer Path. You 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 you create because SPITFIRE automatically performs these chores. However, it is quite permissible for them to be in the batch file so they can act as a safeguard. You will also 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. You will need this utility for the protection of your system. BRK.ZIP can be downloaded from Buffalo Creek's BBS. Last but not least, you will notice a command MUV %3 %4. The file is uploaded to the directory you have configured as your External Transfer Path and you will remember SPITFIRE must find the file in the appropriate File Area in order for the caller to get credit for the upload and in order for the file to be added to SFFILES.BBS. Well, the MUV %3 %4 command will move the uploaded file to the appropriate file area. MUV is a shareware utility by Buffalo Creek Software that moves a file rather than copying it. MUV is available for download from Buffalo Creek's BBS. There are a number of other utilities that perform the same function as MUV. In the event you do not have MUV, then you can replace the MUV %3 %4 command with the below listed commands: COPY %3 %4 ERASE %3 Page 108 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 18.4 EXTERNAL BATCH UPLOAD PROTOCOLS ------------------------------------ SPITFIRE will also allow 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, use your favorite text editor to list the name of the external batch file protocol you will have 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 Zmodem Batch,Batch The SFEXTUP.BBS must reside in the path assigned as your Display File Path. The DSZ.COM must be placed in the directory you have configured as the External File path. The next thing to be done is using your favorite text editor, create a SFEXTUP<A..N>.BAT file which will contain the commands necessary to execute the batch upload. For the above example, SFEXTUPB.BAT will need to 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 rz IF EXIST %3 MUV %3 %4 IF EXIST %5 MUV %5 %4 IF EXIST %6 MUV %6 %4 IF EXIST %7 MUV %7 %4 IF EXIST %8 MUV %8 %4 IF EXIST %9 MUV %9 %4 CD\SF BRK ON Note, when using DSZ, do NOT list the % file and path parameters on the command line. If you list the % file parameter on the command line, it is possible that the uploaded files will end up with the Page 109 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- wrong names. For example, let's 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 your External Transfer Path just prior to shelling to the appropriate batch file. Then when control is returned to SPITFIRE, it checks the files in your External Transfer directory against the files listed in the previously created text file. If additional file(s) are found, then if such file does not already exist in a File Area, SPITFIRE will prompt 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 you have designated as your upload directory and %3, %5, %6, %7, %8, %9 are the file names. SPITFIRE will allow up to six files uploaded during an external batch upload. After selecting the batch transfer protocol the caller will be prompted to enter the name of the file to be uploaded and provide a brief description for each file to be uploaded. As explained in the section, EXTERNAL UPLOAD PROTOCOLS of this manual, the commands to erase the files which have been selected for upload and the command to change back to the SF directory are an added safety measure. SPITFIRE will automatically do this. 18.5 EXTERNAL PROTOCOL SUPPORT ------------------------------ Configuring the use of external file transfer protocols will be supported by Buffalo Creek Software for registered users of SPITFIRE. However, should you have problems with the external file transfer program itself, please read the documentation and then contact the author of the program. 19.0 SPITFIRE UTILIZES EMS (Expanded Memory) -------------------------------------------- Upon boot-up, SPITFIRE will automatically attempt to copy SPITFIRE.OVR to EMS. If there is adequate EMS available, then SPITFIRE will access it from there. This will increase the speed Page 110 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- at which SPITFIRE operates and save wear and tear on the drive. If this is done, SPITFIRE will upon boot-up display the message "EMS memory is used for SPITFIRE.OVR". 20.0 SPITFIRE NET-MAIL CAPABILITIES ------------------------------------ SPITFIRE will support net-mail in two basic formats. In the first format, SPITFIRE can be used in conjunction with a front-end type program where net-mail messages can be imported and made available to your users via the SPITFIRE door option. SPITFIRE also supports the PC Relay net-mail software which will directly import net-mail into SPITFIRE's existing 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. In the event you plan to run your copy of SPITFIRE with a front-end type program, then the front-end 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 your SPITFIRE package should be used even with a front-end program. Using the SF.BAT file, then 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, then 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. Certain features within SPITFIRE allow it to be compatible with specific net-mail drivers, such as Bob Browne's SFUTI<x> (which allows SPITFIRE to exchange PC Relay net-mail). Page 111 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user 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 will 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 would configure a SPITFIRE BBS system with a maximum baud rate of 0 (in which case, this node would only be accessible by local log-ons). 21.2 CONFIGURING SPITFIRE FOR MULTI-NODE OPERATION -------------------------------------------------- For the most part, 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, Page 112 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- there are several configuration options the Sysop must be sure to set correctly when installing or expanding to a multi-node system. First, press ALT+T to display the SPITFIRE configuration window. The <L> option must be toggled so the the Multi-Node System option is set to Yes. Then using the ALT+Z 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 will need to be appropriately configured for each node on the system. In addition, when operating SPITFIRE in a multi-node environment, the DOS SHARE command must be loaded. This can be accomplished by placing SHARE in your AUTOEXEC.BAT and SHARE will be loaded each time 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 user'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 will not allow a Sysop to use the internal SPITFIRE commands for packing the user 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 allowed to pack the user's file/message base while other nodes are busy." Depending on which activity is trying to be performed, either the text of user's file or message base will display in the above message. Page 113 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- If a caller attempts to log onto the system when SPITFIRE is packing the message base or user'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 will be shown the SFPRELOG.BBS and the WELCOME1.BBS/CLR but prior to entering their name and password the above message will be displayed. The Sysop may create their own screen for displaying the maintenance message if preferred. This screen, SFMAINT.BBS/CLR will display just prior to the caller entering their name, after the SFPRELOG.BBS and the WELCOME1.BBS/CLR is displayed. This replaces SPITFIRE's default message mentioned above. If configured as a multi-node system, when booted, SPITFIRE will check to determine whether maintenance is being performed (packing the users file and packing the message base). In the event SPITFIRE discovers that maintenance is being performed, then the following message will be displayed: ■ Report - Maintenance Being Performed. Pausing Until Maintenance Is Complete. Press Any Key To Return To DOS. SPITFIRE then goes into a loop and will continue to check the maintenance status indefinitely until the maintenance has been completed. When the maintenance is completed, SPITFIRE will continue the initialization and waits for a user. During the time while SPITFIRE is doing the continuous maintenance check loop, if a key is pressed SPITFIRE will terminate and return to DOS. In other words, when booting SPITFIRE, if it is discovered that maintenance is being performed by another node, SPITFIRE will loop until the maintenance status changes or until the Sysop presses a key to return to DOS. 21.4 NODE CHAT -------------- If you are running a multinode SPITFIRE 3.1 BBS, your 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 security level. The default values allow for five Node Chats of five minutes each per day. To set 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: Page 114 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- #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,0,,0,,,0,,,,Y,#OCA=0,TPNC=0 (Zero Permitted, Zero Minutes) 5,0,,0,,,0,,,,Y (Default Number And Time) 10,0,,0,,,0,,,,Y,#OCA=10,TPNC=20 (10 Chats Daily, 20 Minutes Each) 20,0,,0,,,0,,,,Y,TPNC=30 (Default Number, 30 Minutes Each) 30,90,,25,,,1000000,,,,Y,#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> " A <y>es response will then ask 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 will then see something like this: " (1st Caller) would like to chat! Would you like to chat with (1st Caller)? <y/n> " Page 115 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 will be 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 will send typed text to the other node and will word wrap 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 will present the "CHAT:" prompt to the other caller while the first caller will switch to the "WAIT:" prompt. At that time, the second caller may type. In order to terminate Node Chat and return to other activities, either caller may hit <ESC>. This will shortly end the Node Chat and return 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 Page 116 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- environment. In a multi-tasking environment multiple copies of SPITFIRE would 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 would be loaded on any number of computers that are networked together via such networking programs as LANtastic. The following sections will discuss the procedure for installing SPITFIRE in such environments. 22.1 SPITFIRE WITH WINDOWS 3.0 ------------------------------- In order to run SPITFIRE 3.1 under MS Windows 3.0, you will 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 you are running and describes the necessary memory and hardware requirements. A PIF file is required whether you are running a single node or a multi-node BBS. To create a PIF file, you 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. If you intend to drop to DOS from the SPITFIRE window, and you are running in Real or Standard Mode, you could increase the memory requirements. In 386 Enhanced Mode, a better way would be to open another DOS window. All other values are the Windows default PIF values. If you are running Windows 3.0 in 386 Enhanced Mode, click on ADVANCED options to examine additional parameters and settings. You will be unable to see these settings while running in Real or Standard Mode unless you pull down the Mode Option and select 386 Enhanced Mode. Enhanced options are meaningless when you are 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. Page 117 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Hardware Requirements: --------------------- To run multiple active SPITFIRE windows on the screen, you MUST be running in 386 Enhanced Mode. This REQUIRES a 386SX or 386DX CPU. 2MB of RAM is recommended, but the more the better! You MUST install the HIMEM.SYS driver that is included on the Windows 3.0 diskettes according to parameters applicable to your system. The popular QEMM386 program (Version 5.1 and greater) may be substituted for HIMEM.SYS with appropriate parameters. You 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 your BBS! If you are running your BBS on an 8086, 8088 or 80286, you 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. If you switch 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.1 in a DOS window, select Background and Windowed as options when you are creating your SPITFIRE PIF file. This will allow you to view 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 you are running a multi-node setup, it is suggested that you name your batch files and PIF files based upon their node number (SF1.BAT, SF1.PIF, etc.) In addition, there are Windows applications which will allow you to create custom Icons which can be unique for each node. To load Windows automatically and have it bring up your 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. Testing has demonstrated the DOS 4.01 has unique properties with regard to it's SHARE.EXE program and their relationship with Windows 3.0. If you are running MS-DOS 4.01 or PC-DOS 4.01 and intend to run more than one copy of Spitfire at a time, you must NOT load SHARE.EXE! Although this is contrary to what is in Page 118 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- the documentation that accompanies Windows 3.0, it is the only reliable way to run this combination of software. DOS 3.3 and the new DOS 5.0 do not suffer from this anomaly. SHARE.EXE can be loaded successfully on these systems without interfering with Windows 3.0 DOS windows. 22.2 RUNNING SPITFIRE 3.1 UNDER DESQVIEW 386 -------------------------------------------- In order to run SPITFIRE 3.1 under DESQview 386, you will 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 you're running and describes the necessary memory and hardware requirements. A DVP file is required whether you are running one or multiple nodes. To create a DVP file, select Open Window, then Add a Program from the popup DESQview menu that you get when you tap the ALT key. See below for further information. Memory Requirements: ------------------- SPITFIRE 3.1 requires 256K of RAM per node. If your setup includes programs that are run from DOS using SFMAIN.BAT, SFMESS.BAT or SFFILE.BAT, you will need to allocate more memory depending upon the size of the application that you are running. This is necessary because SPITFIRE will still be 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. Hardware Requirements: --------------------- A 386DX or 386SX 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 Page 119 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 your system for DESQview. Change A Program Program Name............:SPITFIRE 3.1 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.: ------------------------------------------------------------------ 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 ------------------------------------------------------------------ Page 120 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- Starting It All Up: ------------------ If ANSI Graphics are featured on your SPITFIRE BBS, you will need to load DVANSI.COM, a file that comes with the DESQview software, before you open 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 your 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 you would like this macro to be activated by. Make sure that 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 you use to start your "default" startup windows. When all your 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 you exit DESQview next, tell it to Save Scripts. Make sure to have your AUTOEXEC.BAT end with the line "XDV". This This will enable your system to boot DESQview which will in turn boot your SPITFIRE Setup in case of a power interruption. 22.3 RUNNING SPITFIRE 3.1 ON A LANTASTIC NETWORK ------------------------------------------------ Running SPITFIRE 3.1 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. Information discussed in this section while specific to the LANtastic Network should be 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 Page 121 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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, you must install the software. 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. 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. So, for example, if the Network has one Server and three Workstations associated with it, and all have SPITFIRE nodes set up on them, you would 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 Page 122 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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. Multitasking software such as MS Windows 3.0 or DESQview 386 can ONLY be used on Workstations! Running multitasking software on a 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 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 123 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 *) Page 124 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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; Extra : Array[0..81] 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 : Boolean; Extra : Array[1..88] Of Byte; End; Page 125 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- (* SFMCONF.DAT *) MsgSystem = Record MSec : Integer; NetMailConf : Boolean; MDesc : String[40]; MEqual, PublicMsgConf, AllowDelete, BackupNeeded : Boolean; DaysOld : Word; DelOldThdMsg : Boolean; Extra : Array[1..77] 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 126 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- ScrollBack, Xpert, LockedOut, Deleted : Boolean; Linelen, Pagelen, OnToday, Illegal, DLToday, ForeGround : Byte; ExtraWord : Word; DLBytes : LongInt; NewFCheck : String[8]; OrgSecurity, ChatsToday : Integer; Extra : Array[1..21] 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, DownsPerDay, D_URatio, MaxUsers, NotUsed : Word; DoorsAmt : Integer; Callernum : LongInt; LastDate : String[8]; StartDate : String[18]; DOSPassword : String[28]; SysopName, SysMsgName : String[30]; Page 127 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- USPhone, ConvertDesc, HeySysop, UseNetMail, MultiNode : Boolean; NumberOfNodes : Byte; ExtraInt : Integer; ScanAllMsg, OfferDefault : Boolean; ViolationSec : Integer; NUBirthDate : Boolean; ExtraBytes : Array[0..88] Of Byte; End; (* SFWHOSON.DAT *) NodesDat = Record UserNo : Integer; Mode : Char; DBytes : Array[1..3] Of Byte; End; (* SFNODE.DAT *) NodeSysRec = Record DirectScrn, ShowResult, Extran, 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; TimeComp : Real; LastDate : String[8]; Page 128 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- PrivateSec : Integer; HangUpDelay : Byte; UseHiSpeed EnforceRatio : Boolean; IRQ1, IRQ2, IRQ3, IRQ4, IRQ5, IRQ6, IRQ7, IRQ8 : Byte; ExtraBytes : Array[0..24] Of Byte; End; Page 129 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 24.0 COMMENT FROM THE AUTHOR ----------------------------- Undoubtedly there are features that can be added to SPITFIRE such as additional file transfer protocols, node chat abilities and so forth. Your suggestions and comments will certainly be appreciated and considered for future releases, however, you must realize that not all ideas will or can be implemented. It is believed that this version of 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.1 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 Mike Woltz, however, it would be remiss not to mention that the async routines were originally written by my good friend John Friel of the Forbin Project, Inc. (your support of QMODEM will be appreciated) and then modified by by myself for SPITFIRE. I would also be remiss if I didn't mention that Jacque Shipley, Doug Vangorp, Frank Lech, Ira Lichtenstein and Michael & Valli Redman were very instrumental in creating and maintaining this manual. It has taken over four 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 and father. I would also like to thank God for giving me the ability to write this program. SPITFIRE was first released nationally (internationally) some 40 months ago. Since that time, SPITFIRE has been registered over 950 times. 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 over four years of my life into SPITFIRE, I have attempted to keep the cost of this software as reasonable as Page 130 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ----------------------------------------------------------------------- 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. Page 131 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ----------------------------------------------------------------------- NOTES: 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> ATI 2400 ETC MNP1-5.........AT&Q5&C1&U1&D0&T5M0H0W1X5V1E0S2=1S0=0 <2> ATI 2400 ETC..................AT&F1&B0&C1&D0&T5M0H0V1E0X2S2=1S0=0 <3> Alpha Concord 1200.........................ATS0=0Q0E0M0V1H0S2=1X1 <4> Amstrad MC 2400......................ATS0=0Q0V1E0M0H0S2=1X2&C1&D0 Amstrad PPC Internal 2400............ATS0=0Q0V1E0M0H0S2=1X2&C1&D0 Anchor..(External 2400).............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0 <5> Anchor..(Internal 2400)....................ATS0=0Q0V1E0M0H0S2=1X4 Anchor..(Internal 2400).............AT&C1&D2&T5M0H0X4V1E0S2=1S0=0 <6> Avatex 1200 HC.............................ATS0=0Q0V1E0M0H0S2=1X1 Avatex 1200I........................ATX1E0M0H0V1S0=0S1=1S9=1S10=2 <7> Avatex 2400 External.............ATS0=0Q0V1E0L0M0&D0&C1X1H0S2=1&W <8> Avatex 2400II..............................ATS0=0Q0V1E0M0H0S2=1X1 <9> CMP 2400.....................................ATS0=0Q0E0M0H0S2=1X4 <10> CVI Internal 2400 Baud.....................ATS0=0Q0V1E0M0H0S2=1X1 <11> Capetronics MD 1207...1200 Baud..............ATE0V1Q0M0S2=1S0=0X1 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> Computer Peripherals 2400..................ATS0=0Q0V1E0M0H0S2=1X1 <16> Computer Peripherals Hook-up 2400s.......AT&FS0=0Q0V1E0M0H0S2=1X4 <17> Evercom 24E................AT&C1&D0&T5M0H0X1V1E0S2=1S0=0\N3\V1\C1 <18> Everex 24...(Internal 2400).........AT&C1&D0&T5M0H0X1V1E0S2=1S0=0 <19> Everex Internal 1200.......................ATS0=0Q0V1E0M0H0S2=1X1 Everex......(Internal 2400).........ATM0E0V1H0X1&D0&T5&L1S0=0S2=1 <20> Fastalk 2400..(External)...................ATS0=0Q0V1E0M0H0S2=1X1 <21> Fastcomm 9696.v32.............ATS0=0S2=1S10=2&H1&I1&M4V1M0X1#X1&W <22> Franklin FM-2400E..........................ATS0=0Q0V1E0M0H0S2=1X1 <23> GVC External 2400..............................ATS0=0V1E0M0S2=1X1 GVE Internal 2400................ATS0=0&C1&D2Q0V1E0M1L3H0S2=1X4&W <24> GoldStar GSM2400 (External).............ATS0=0Q0V1E0M0H0S2=1X1&C1 <25> Hayes 1200..(External).....................ATS0=0Q0V1E0M0H0S2=1X1 <26> Hayes 1200..(Internal).....................ATS0=0Q0V1E0M0H0S2=1X4 <27> Hayes 2400..(External)..............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0 Page 132 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ----------------------------------------------------------------------- <28> Hayes 2400..(Internal).....................ATS0=0Q0V1E0M0H0S2=1X4 <29> Hook-up 2400S..............................ATS0=0Q0V1E0M0H0S2=1X4 <30> IBM Model 5842 2400........................ATS0=0Q0V1E0M0H0S2=1X1 <31> Kyocera KM1200D............................ATS0=0Q0V1E0M0H0S2=1X1 <32> Leading Edge 2400...................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0 <33> Magitronic MB2450..(Internal)..........AT&C1&D2M0H0X1V1E0S2=1S0=0 <34> Megatronics - Internal 2400................ATS0=0Q0V1E0M0H0S2=1X4 <35> Mikon Super Modem...(2400 External)........ATS0=0Q0M0V1E0S2=1X1&W <36> MultiTECH V32.AT&E1&E4&E7&E12$BA0$MB9600$SB19200S0=0S2=1V1M0H0&Q1 <37> MultiTech MultiModem V32...............AT&C1&D2M0X1V1E0Q0S2=1S0=0 <38> Multitech 224EC (2400 Internal)............ATS0=0Q0V1E0M0H0S2=1X1 <39> NEC N2420/30HN.............................ATS0=0Q0V1E0M0H0S2=1X6 <40> Netcomm 1234SA Datalock 2400....AT&C1&D2E0V1M0S2=1S0=0S6=1S10=1X1 <41> Omnitel Encore 2400 HB...............AT&F&C1&D2M0H0X1V1E0S2=1S0=0 <42> Packard Bell 1200..........................ATS0=0Q0V1E0M0H0S2=1X1 <43> Packard Bell 2400 Internal.........ATS0=0&C1&D2Q0V1E0M0H0S2=1X4&W <44> Penril 2400 DataLink.......................ATS0=0Q0V1E0M0H0S2=1X1 <45> Practical Peripheral (Int 2400)...AT&C1&D2M0H0X1V1E0S7=30S2=1S0=0 <46> Practical Peripheral 1200 Baud.............ATS0=0Q0V1E0M0H0S2=1X1 <47> Prentice Popcomm 2400 (c200)........AT&C1&D2&T5M0V1E0Q0X1S2=1S0=0 <48> Prometheus ProModem 2400 B/2...............ATS0=0Q0V1E0M0H0S2=1X4 <49> Smart One..(Best Data Products of CA)......ATS0=0Q0V1E0M0H0S2=1X1 <50> SmartLink (2400 External)................ATE1X1V1Q0M0H0S0=0S2=1&W <51> SmartOne 2400........................ATS0=0Q0V1E0M0H0S2=1X1&C1&D2 <52> Smarteam.....................................ATS0=0V1E0M0H0S2=1X1 <53> Supra 2400 External..................ATS0=0&C1&D3L3M1V1S2=1E0H0&W <54> SupraModem2400 I...........................ATS0=0Q0V1E0M0H0S2=1X4 <55> US Robotics Courier 2400...................ATS0=0Q0V1E0M0H0S2=1X1 <56> US Robotics HST 9600......(9600 Baud)......ATS0=0Q0V1E0M0H0S2=1X1 <57> US Robotics Sportster...............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0 <58> USR HST 9600..(19200 Baud).....ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6 <59> US Robotics Dual Standard (v32bis/v42bis) ATS0=0&B1&H1&K3&N0&R2&Y3B0Q0V1E0M0H0S2=1X6 <60> VIVA 2400m External MNP5....ATH0Q0V1E0M0S0=0S2=1X1&C1&D2\N3\Q3\V1 <61> Zoom 2400 Internal Modem...................ATS0=0Q0V1E0M0H0S2=1X4 <62> Zoom 2400..............................AT&C1&D2M0H0X1V1E0S2=1S0=0 <63> Zuckerboard Model ZCom24/AT 2400....AT&C1&D2&T5M0V1E0Q0X1S2=1S0=0 <64> Hayes Ultra 9600..ATS0=0S95=2N1W2X4&C1&D2&K3&Q5&R0V1Q0L2S2=1S36=7 Page 133 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- APPENDIX B ---------- SPITFIRE QUESTIONS AND ANSWERS ------------------------------ QUESTION: Why is the "Do You Want ANSI Graphics? <y/N>" displayed each time a user logs on the BBS? ANSWER: Some BBS software stores in the users file whether a caller uses ANSI, and if so, then each time the user logs on, ANSI graphics are automatically displayed. When creating SPITFIRE it was decided to provide the user with the opportunity to select the display preferred at each log-on. There are two basic reasons for including this prompt to each user upon log on. First, some users may call the BBS from different locations. For instance, many users 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 user may sometimes choose Ansi graphics and other times not. This may be due to the amount of time a user 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 user 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 134 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 user information required for door operation. These files are SFDOORS.DAT, required by SPITFIRE, and DOOR.SYS, a universal format door user information file. These are only used during door operation and once the caller returns to SPITFIRE, these files are 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 user 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 135 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 users 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 136 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 users 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 user 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 user. Once the user 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 137 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- QUESTION: I recently registered a door program and was requested by the author to add him to the user'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 user to the users file? ANSWER: A user may be added to the SFUSERS.DAT file by selecting ALT+A at the SPITFIRE "Ready For Use..." prompt. A user may also be added by using the ... Modify Users 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. 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. QUESTION: Why must callers enter their password when returning to SPITFIRE from a door program? ANSWER: There are three tests that must be passed for a caller to be able to return to SPITFIRE from a door program. Those three test are: 1) SPITFIRE must find SFDOORS.DAT 2) There must be a carrier detect 3) Callers must enter their password This is the reason the password is required... it is possible that a caller could disconnect while in a door program. That Page 138 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- would mean that SPITFIRE would re-boot and wait for the next caller. However, it is possible that a new call could come in before SPITFIRE was re-booted. In that case, SPITFIRE would find a carrier detect and prompt for the password. When the new caller is not able to enter the correct password, the caller is logged off. However, if SPITFIRE did not prompt for a password, then the new caller would be logged on and SPITFIRE would think that the previous caller was still on. 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 user with Sysop status. In other words, any user 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 user of the BBS. The name the Sysop uses to log onto the BBS must be the same as the Sysop User Name configured using the ALT+Z configuration window. If a Sysop enters Sysop as the Sysop User 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 in not a user of the BBS. In this example, the Sysop would need to change the Sysop User 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 user 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 139 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- 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 140 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- NOTES: Page 141 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 1 <X>.BBS/CLR 22 <X>SEC.BBS/CLR 22 19200 5, 6, 8, 96 38400 5, 38 1K-XMODEM 82 <<<<<< A >>>>>> ALL.BBS/CLR 25, 30, 62 ALLOWDELETE 125 ALT+A 31, 51, 55, 89, 137 ALT+C 51, 53, 60 ALT+D 51, 60, 86 ALT+E 51, 61 ALT+F 18, 23, 43, 51, 61 ALT+F1 23, 51, 54 ALT+F2 51, 54 ALT+F3 51, 54 ALT+J 51, 61, 86, 134 ALT+L 31, 51, 61 ALT+M 5, 6, 7, 38, 51, 61, 96 ALT+P 17, 19, 38, 51, 62, 101, 105 ALT+Q 51, 62, 97 ALT+R 18, 39, 51, 62 ALT+S 7, 51, 62, 97 ALT+T 12, 13, 48, 51, 57, 63, 112 ALT+Z 10, 12, 16, 23, 30, 51, 63, 65, 86, 90, 91, 95, 111, 112, 138 ANSI 3, 13, 15, 23, 24, 25, 26, 28, 29, 32, 50, 66, 76, 78, 87, 88, 99, 117, 120, 123, 133, 135 ANSI.SYS 3, 15, 26, 117 APPENDIX A 4, 5, 131 APPENDIX B 133 APPENDIX ARC 82 ARQ 4, 8 ASCII 6, 21, 25, 28, 31, 32, 36, 47, 80, 82, 87, 88, 102, 106, 133 AUTOEXEC.BAT 33, 39, 112, 117, 120, 121, 134 <<<<<>>>>> BACKUP FILES 36, 40, 42, 43, 54, 88, 95 BADINIT.BAT 21 BATCH 20, 22, 24, 28, 29, 33, 34, 37, 38, 82, 83, 84, 85, 86, 95, 101, 102, 103, 104, 105, 106, 107, 108, 109, 117, 120, 137 BATCH DOWNLOAD 24, 28, 82, 83, 84, 103, 104, 137 BATCH UPLOAD 24, 28, 84, 85, 86, 108, 109, 137 BAUD RATE 4, 8, 9, 23, 37, 38, 61, 96, 102, 106, 110, 111, 123, 133 BBSNAME.DAT 22, 34 BEEP 35, 36 Page 142 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 2 BINKLEYTERM 110 BRK 3, 4 BRK OFF 101, 103, 104, 105, 107, 108 BRK ON 101, 103, 104, 105, 107, 108 BRK.DRV 3 BRK.ZIP 103, 107 BUFFALO CREEK'S BBS 18, 29, 34, 37, 62, 81, 98, 99, 100, 103, 105, 107, 122, 134 BUFFERS 3, 121 BULLETIN.BBS/CLR 23 BULLETINS 23, 24, 27, 58, 63, 64, 94, 98, 99, 138, 139 BULLET<X>.BBS/CLR 23 <<<<<< C >>>>>> CALLERS.TMP 20 CALLERS.LOG 9, 20, 52, 53, 54, 88, 89, 90, 94, 134, 135, 136 CAPTURE CHAT TO DISK 51 CD-ROM 24 CHAT 20, 23, 25, 30, 31, 51, 52, 53, 54, 60, 65, 66, 74, 80, 113, 114, 115, 126, 129 CHATDONE.BBS/CLR 23 CHECK TODAY'S STATISTICS 51 COMMAND LINE PARAMETERS 5, 6, 37, 38 COMMAND.COM 4, 102, 106, 134 CONFERENCE 13, 15, 16, 18, 20, 21, 24, 33, 37, 39, 40, 41, 42, 43, 45, 51, 54, 55, 57, 62, 64, 67, 68, 69, 70, 71, 72, 73, 74, 86, 87, 88, 89, 95, 111, 123, 124 CONFIGURE 4, 5, 6, 9, 10, 13, 15, 18, 23, 24, 30, 37, 39, 40, 43, 47, 48, 51, 57, 60, 61, 62, 63, 65, 66, 69, 70, 72, 75, 81, 86, 87, 89, 90, 92, 93, 94, 95, 96, 97, 100, 101, 102, 103, 104, 105, 106, 107, 108, 111, 112, 113, 115, 121, 123, 138 CONFIG.SYS 3, 4, 15, 26, 117, 121, 137 CRC 82, 124, 136 <<<<<< D >>>>>> DAILYLMT.DAT 11, 12, 16, 20, 21, 29, 30, 31, 113, 114 DELETE 10, 39, 40, 41, 42, 43, 46, 55, 57, 60, 69, 71, 73, 74, 88, 90, 94, 124, 125, 126 DESQVIEW 3, 116, 118, 119, 120, 122 DEVICE 3, 15, 26 DISCONNECT DELAY 9 DISPLAY 8, 9, 11, 12, 15, 16, 17, 19, 20, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 34, 35, 36, 37, 39, 41, 43, 45, 47, 48, 49, 50, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80 DISPLAY FILE CONTROL CHARACTER 35, 36 DISPLAY FILE PATHS 111 Page 143 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 3 DLMT.BBS/CLR 23 DOORS 3, 28, 33, 64, 67, 74, 75, 80, 96, 97, 98, 99, 122, 126, 134, 137 DORBUL<X>.BBS/CLR 23, 99 DOS 1, 3, 4, 5, 10, 11, 20, 33, 37, 38, 44, 45, 51, 54, 60, 61, 86, 93, 97, 102, 106, 112, 113, 116, 117, 118, 121, 122, 126, 134, 136, 137 DOWNLOAD 2, 10, 11, 12, 13, 14, 16, 20, 21, 23, 24, 25, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 43, 44, 45, 46, 55, 56, 75, 76, 78, 80, 81, 82, 83, 84, 98, 99, 100, 101, 102, 103, 104, 105, 107, 123, 125, 134, 135, 137 DSZ 3, 100, 101, 103, 104, 105, 106, 108, 109 DVANSI.COM 120 DVP 118, 120 <<<<<< E >>>>>> EDLIN 28 EMS 109, 110 ERASE 32, 34, 35, 41, 54, 55, 75, 76, 77, 79, 88, 89, 94, 97, 98, 101, 102, 103, 104, 107, 109, 122, 134, 135, 136, 139 ETHERNET 121 EVENTIME.BBS/CLR 23 EVENTS 20, 33, 39, 51, 55, 61, 86, 87, 91, 92, 94, 110, 126 EXIT 51, 60, 61, 71, 78, 80, 92, 98, 101, 105, 118, 119, 120 EXTERNAL PROTOCOLS 18, 100, 101, 103, 105, 106, 108 <<<<<< F >>>>>> F1 23, 51, 52, 54, 101, 105, 117, 119, 120, 131, 135 F2 7, 9, 23, 26, 27, 51, 52, 54, 117 F3 51, 52, 54 F4 51, 53 F5 51, 53 F6 51, 53 F7 51, 53 F8 51, 53 F9 51, 53 F10 51, 54, 101, 105 FILE AREA 18, 20, 23, 24, 32, 37, 39, 43, 44, 45, 46, 47, 51, 55, 57, 61, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 107, 109, 123, 135 FILE<X>.BBS/CLR 23, 28, 29 FILST<X>.BBS/CLR 23 FRONTDOOR 110 <<<<<< G >>>>>> GOODBYE.BBS/CLR 32 Page 144 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 4 <<<<<< H >>>>>> HARDWARE 3, 8, 96, 116, 117, 118, 120, 121 HEYSYSOP.LOG 15, 48, 52, 54, 78, 88, 89, 90, 134, 135, 136 HIGH SPEED ASYNC ROUTINES 8 HIMEM.SYS 117 <<<<<>>>>> INITIALIZATION STRING 4, 5, 7, 8, 37, 38, 62, 96, 131, 133 <<<<<< J >>>>>> JOKER.DAT 23, 31, 32, 57 <<<<<< L >>>>>> LANTASTIC 3, 5, 116, 120, 121, 122 LOCKOUT.BBS/CLR 32 LOOP 93, 94, 97, 98, 113 <<<<<< M >>>>>> MAIN MENU 7, 14, 20, 22, 23, 25, 28, 30, 32, 33, 47, 49, 58, 62, 63, 64, 66, 67, 74, 75, 80, 86, 89, 91, 97, 98, 112, 113 MAIN<X>.BBS/CLR 23, 28, 29 MAINTENANCE 24, 36, 55, 86, 87, 88, 113, 139 MAXUSERS.BBS MAXUSERS.BBS/CLR 11, 23 MESSAGE CONFERENCE 16, 18, 20, 21, 24, 33, 37, 39, 40, 41, 42, 51 54, 57, 62, 64, 68, 69, 70, 71, 72, 73, 74, 86, 87, 88, 89, 95, 111 MESSAGE FILES PATH 17 MGLST<X>.BBS/CLR 23, 68 MKSFMENU.EXE 29 MODEM 3, 4, 5, 6, 7, 8, 9, 18, 20, 34, 37, 38, 51, 60, 61, 62, 82, 96, 111, 131, 132, 133 MOVE 7, 43, 55, 56, 94, 97, 107, 109, 135 MSG<X>.BBS/CLR 23, 24, 28, 29 MULTI-TASKING 15, 111, 115, 116, 136 MULTI-NODE 12, 13, 16, 21, 22, 25, 30, 64, 65, 87, 88, 111, 112, 113, 115, 116, 117, 120, 136 MUV 3, 105, 107, 108 <<<<<< N >>>>>> NEEDSYS.BBS/CLR 23, 54 NETWORK 111, 115, 116, 120, 121, 122, 136 NET-MAIL 13, 15, 16, 22, 33, 34, 38, 39, 40, 70, 72, 95, 110, 111, 121 NEWSLETTER 25, 64, 66 NEWUSER.BBS/CLR 15, 23 NODE CHAT 20, 30, 31, 65, 113, 114, 115, 129 NOVELL 120 Page 145 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 5 <<<<<< O >>>>>> OLD MESSAGE PURGE 42 OS/2 122 <<<<<>>>>> PACK 6, 19, 22, 27, 35, 36, 39, 42, 43, 57, 60, 69, 86, 87, 88, 95, 112, 113 PACK MESSAGE 86, 88 PACK USERS 86, 87 PAK 78, 82 PASSWORD 7, 10, 11, 13, 14, 15, 25, 35, 55, 57, 60, 62, 86, 87, 88, 98, 113, 123, 125, 126, 127, 137, 138 PATHS 17, 18, 19, 44, 51, 62, 101, 105, 111 PIF FILES 117 PREVIEW AREA 43, 44, 46 PRIVATE.BBS/CLR 12, 15, 23 PROTOCOLS 3, 4, 17, 18, 19, 24, 25, 37, 62, 80, 82, 100, 101, 102, 103, 104, 105, 106, 108, 109, 129 PURGE ALLOWED 55, 60 <<<<<< Q >>>>>> QEMM 117 QUESTIONNAIRES 22, 28, 47, 65 QUEUE 16, 67, 68, 73, 74, 83, 84, 85, 104, 125 QUICK LOG 20, 22, 30, 31, 62 <<<<<< R >>>>>> RATIO 1, 6, 7, 8, 10, 11, 12, 13, 16, 18, 19, 20, 21, 25, 30, 31, 37, 38, 57, 65, 91, 93, 95, 97, 100, 101, 102, 105, 106, 111, 112, 113, 126, 129, 130, 134, 136, 138, 139 REGISTRATION 1, 130 RESULT MESSAGE 8 <<<<<< S >>>>>> SEALINK 3, 82 SERVER 120, 121, 122 SF.BAT 5, 6, 21, 33, 38, 39, 93, 96, 97, 98, 100, 110 SF1STF.BBS/CLR 23 SF1STM.BBS/CLR 23 SF2SLOW.BBS/CLR 9, 23, 26 SFASLEEP.BBS/CLR 23 SFBATCHD.BBS/CLR 24, 28, 29 SFBATCHU.BBS/CLR 24, 28, 29 SFBBSLST.DAT 66 SFBDAY.BBS/CLR 24 SFBDAY 24 SFCHAT.CAP 53, 54 Page 146 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 6 SFDOOR.MNU 20, 21, 28, 97 SFDOORS.DAT 97, 98, 122, 134, 137 SFDORBAK.BBS/CLR 24, 99 SFDORBUL.BBS/CLR 24, 99 SFDOWN.BBS/CLR 24 SFDR<X>.BBS/CLR 24, 28, 29, 99 SFEVENTS.DAT 20 SFEXTDN.BBS 24, 26, 101, 103 SFEXTDN<?>.BAT 101, 102, 104 SFEXTUP.BBS 24, 26, 105, 108 SFEXTUP<?>.BAT 106, 108 SFFAREA.DAT 7, 20 SFFILE.BAT 21, 118 SFFILE.MNU 26, 27, 75, 98 SFFILES.BBS 24, 26, 32, 45, 76, 77, 78, 79, 80, 81, 107, 109, 135, 136 SFFILE.DAT 122, 134 SFFILE.MNU 20, 26, 27, 28, 75, 98 SFIMPEXP.BBS/CLR 24, 28, 29, 76, 78 SFINIT.BAT 4, 20, 21, 34 SFLOGON.BAT 20, 21 SFLOG.EXE 93 SFMAIN.BAT 20, 21, 33, 66, 118 SFMAIN.MNU 20, 26, 28, 98, SFMAINT.BBS/CLR 24, 87, 88, 113 SFMAIN.DAT 122, 134 SFMAIN<X>.ANS 22, 47, 49, 50, 65 SFMAIN<X>.QUE 22, 47, 49, 50, 65 SFMCONF.DAT 7, 20 SFMESS.BAT 20, 21, 33, 75, 81, 118 SFMESS.DAT 122, 134 SFMQDONE.BBS/CLR 24 SFMSG.MNU 20, 26, 28, 98 SFMSGPCK.BAT 4, 22, 33, 95 SFNEWU.ANS 22, 47, 49, 52, 89, 90 SFNEWU.QUE 22, 47, 48, 49 SFNODE.BBS/CLR 25, SFNODE.DAT 6, 20, 135 SFNOTIME.BBS/CLR 25 SFNOUP.DAT 22, 32, 76, 77, 138 SFNWSLTR.BBS 25, 26, 32, 66 SFORDER.MNU 20, 21, 28, 49 SFORD<x>.BBS/CLR 25, 28, 29, 50 SFPAGED.BBS/CLR 25, 34, 52, 53, 66, 74, 80 SFPRELOG.BBS 25, 26, 62, 113 SFPROMSG.BBS/CLR 25, 100 SFPROTCO.HLP 21, 80 Page 147 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 7 SFRATIO 11, 12, 16, 25, 30, 31 SFREMIND.BBS/CLR 25 SFREMOTE.BAT 20, 21, 33, 86, 134 SFSEC<X>.BAT 20, 21, 34 SFSYSOP.MNU 20, 26, 28 SFSYSTEM.DAT 6, 22 SFTIMEUP.BBS/CLR 25 SFUP.BBS/CLR 25 SFUPCASE.DAT 14, 22, 33 SFUSERS.DAT 6, 7, 22, 57, 60, 87, 137 SFUSERS.PTR 22 SFWHOSON.DAT 22, 112, 139 SF.BAT 5, 6, 20, 33, 38, 39, 93, 96, 97, 98, 100, 110 SMARTDRV 117 SOP<X>.BBS/CLR 25, 28, 29 SPITFIRE.HLP 21, 67, 75, 81 SPITFIRE.OVR 20, 109, 110, 136 SYSINIT.BBS/CLR 25 SYSOP UTILITIES 64, 67, 75, 81, 86, 93, 94 <<<<<< T >>>>>> TELINK 82 THIS SYSTEM'S INFO 64, 65 THOUGHTS.BBS 25, 26, 37 TOOMANY.BBS/CLR 11, 25 <<<<<>>>>> UNDELETE 10, 71, 90 UPLOAD 10, 11, 12, 16, 21, 22, 24, 25, 28, 30, 31, 32, 35, 36, 43, 44, 53, 55, 56, 75, 78, 80, 82, 84, 85, 86, 91, 93, 95, 105, 106, 107, 108, 109, 123, 124, 125, 134, 135, 136, 137, 138 USER DELETION 40, 41 USERINIT.BBS/CLR 25, 52 UTILITIES 34, 44, 64, 67, 75, 81, 86, 93, 94, 107, 111, 122, 130 <<<<<< W >>>>>> WATCHDOG 33 WELCOME1.BBS/CLR 24, 25, 62, 113 WELCOME<X>.BBS/CLR 25 WILDCARDS 32, 77, 79, 81 WILDFIRE 3, 99 WINDOWS 3, 116, 117, 118, 120, 122 WORK FILES PATH 17, 19 WORKSTATION 121, 122 <<<<<< X >>>>>> XMODEM 82 XPERT 55, 56, 64, 66, 67, 74, 75, 81, 86, 90, 126 Page 148 ---------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ---------------------------------------------------------------------- SUBJECT INDEX - Page 8 <<<<<< Y >>>>>> YMODEM 37, 61, 82 YMODEM-G 37, 61, 82 <<<<<< Z >>>>>> ZIP 14, 32, 76, 78, 82, 103, 107, 109, 136 ZMODEM 100, 101, 103, 104, 105, 108 Page 149 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ----------------------------------------------------------------------- NOTES: Page 150 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.1 - June 24, 1991 +- ----------------------------------------------------------------------- NOTES: