ftp.wwiv.com

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

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / MISC / SF36-2.ZIP / SPITFIRE.DOC < prev next >

Wrap

Text File | 1999-08-20 | 586KB | 10,457 lines

_________________________________________________________________________ ___________________ ___________________ ________________ S P I T F I R E ________________ _____________ ------------------------- _____________ __________ Bulletin Board System __________ _______ for MS/PC DOS _______ ____ Personal Computers ____ _______________________________ ____ ____ _____ Version 3.6 ____ ___________________ Copyright (C) 1987-1999 by Mike Woltz ------------------------------------- Buffalo Creek Software 913 39th Street West Des Moines, Iowa 50265 Data Phone (515) 225-8496 ------------------------------------------ >>> Release Date August 20, 1999 <<< ------------------------------------------ TABLE OF CONTENTS --------------------- # Section Title Page # +--+------------------------------------------------+------+ Introduction........................................ 1 <1> 1.0 Important Notice.............................. 1 1.1 Copyright & Registered Trademark Notice....... 2 1.2 SPITFIRE Support.............................. 3 <2> 2.0 SPITFIRE Hardware Requirements................ 4 2.1 Modems........................................ 5 2.2 Modem Initialization.......................... 5 <3> 3.0 Getting Started............................... 8 3.1 SPITFIRE Async Configuration.................. 9 3.2 SPITFIRE Configuration........................ 14 3.3 Toggle SPITFIRE Switches...................... 19 3.4 Configuring SPITFIRE File Paths............... 24 <4> 4.0 Setting Up the System Records................. 26 4.1 Configuring Message Conference Records........ 26 4.2 Configuring File Area Records................. 32 <5> 5.0 SPITFIRE File Paths........................... 39 5.1 SPITFIRE System Files......................... 40 5.2 SPITFIRE Message Files........................ 43 5.3 SPITFIRE Work Files........................... 43 5.4 SPITFIRE Display Files........................ 44 5.5 SPITFIRE Menu Files........................... 50 5.6 SPITFIRE File Clarifications.................. 54 5.7 About SPITFIRE Display Files.................. 64 5.8 Backup Files.................................. 66 5.9 THOUGHTS.BBS.................................. 66 <6> 6.0 Command Line Parameters....................... 66 6.1 SF.BAT........................................ 67 <7> 7.0 SPITFIRE Questionnaires....................... 68 <8> 8.0 Special Function Keys......................... 72 8.1 Available Special Function Keys............... 72 8.2 Special Function Key Definitions.............. 73 <9> 9.0 Main Section Explained........................ 87 9.1 Main Menu Example............................. 88 9.2 Explanation of Main Menu Features............. 88 <10> 10.0 Message Section Explained..................... 93 10.1 Message Menu Example.......................... 94 10.2 Message Menu Explanation...................... 94 <11> 11.0 File Section Explained........................ 109 11.1 File Menu Example............................. 109 11.2 File Menu Explanation......................... 109 11.3 Upload/Download Protocols..................... 119 11.4 Batch Download Menu........................... 119 11.5 Batch Upload Menu............................. 121 <12> 12.0 Sysop Section Explained....................... 123 12.1 Sysop Menu Explanation........................ 123 TABLE OF CONTENTS (cont) ------------------------ # Section Title Page # +--+------------------------------------------------+------+ <13> 13.0 Special Commands for Sysop Status............. 128 13.1 Special Commands for Sysop.................... 129 <14> 14.0 Events Menu Example........................... 130 14.1 Events Menu Explanation....................... 130 <15> 15.0 SPITFIRE Doors Section........................ 134 15.1 SPITFIRE Doors Display Files.................. 137 15.2 SPITFIRE Doors Support........................ 138 <16> 16.0 External File Transfer Protocols.............. 138 16.1 External Download Protocols................... 139 16.2 External Batch Download Protocols............. 141 16.3 Text File External Batch Download Protocols... 142 16.4 External Upload Protocols..................... 144 16.5 External Batch Upload Protocols............... 146 16.6 Bi-Directional Protocol File Transfers........ 148 16.7 External Protocol Support..................... 150 <17> 17.0 Hardware/Software Data Flow Control........... 150 <18> 18.0 Additional SPITFIRE Features.................. 151 18.1 Screen Save Features.......................... 151 18.2 SPITFIRE Utilizes EMS......................... 151 18.3 SPITFIRE Records CALLER ID Information........ 151 <19> 19.0 SPITFIRE Net-Mail Capabilities................ 152 19.1 Exchanging Mail With A Front-End Program...... 152 19.2 Exchanging Mail Using A UTI Driver............ 152 19.3 Exchanging Mail Using QWK Packets............. 153 <20> 20.0 Operating A Multi-Node SPITFIRE............... 153 20.1 Multi-Node BBS Requirements................... 154 20.2 Configuring SPITFIRE For Multi-Node Operation. 154 20.3 Features Unique To Multi-Node Operation....... 154 20.4 Node Chat..................................... 156 <21> 21.0 SPITFIRE Multi-Tasking/Network Environment.... 158 <22> 22.0 Receiving FAX Calls With SPITFIRE............. 158 22.1 Configuring Your System To Receive Fax Calls.. 159 22.2 SFFAX.BAT..................................... 160 <23> 23.0 SPITFIRE Technical Reference Information ..... 161 <24> 24.0 SPITFIRE Companion Programs .................. 161 24.1 DAILYLMT...................................... 162 24.2 SFDOOR........................................ 162 24.3 SFSENDIT...................................... 162 24.4 LAKOTA........................................ 163 24.5 SFPCKUSR...................................... 164 24.6 SFPCKMSG...................................... 164 <25> 25.0 Comment from the Author....................... 165 Appendix A SPITFIRE Questions and Answers................ 168 Subject Index............................................. 177 Page 1 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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! ----------------------- 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. 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" diskettes. If not specified, 3 1/2" 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 additional $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. Considering that SPITFIRE is shareware and that an adequate evaluation trial period is allowed, the registration fee is non-refundable. |--------------------------------------------------------------------| | 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.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Mike Woltz and/or Buffalo Creek Software shall in no way be held responsible for any damage incurred while operating SPITFIRE. All responsibility rests 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 callers 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. There are a number of very good bulletin board software packages available and your selection of SPITFIRE is truly appreciated. Once again, thank you very much for your support of SPITFIRE. 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-1999 by Mike Woltz Page 3 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- "SPITFIRE" is a registered trademark of Buffalo Creek Software. "Turbo Pascal" is a registered trademark of Borland International Corp. "BRK" is Copyright (C) 1985, by Solid Systems "WILDFIRE" is Copyright (C) 1988-1995 by Stephen L. Cox "LAKOTA" is Copyright (C) 1992, 1996 by Buffalo Creek Software "KOLDBOOT" is Copyright (C) 1989-1996 by Buffalo Creek Software "SHILOH" is Copyright (C) 1989-1996 by Buffalo Creek Software "GSZ" is Copyright (C) 1991-1995 by Omen Technology, Inc. "WINDOWS 3.1" / "Windows 95" is Copyright (C) 1990-1995 by Microsoft "DESQview 386" is Copyright (C) 1990-1995 by Quarterdeck Office Systems "OS/2" is Copyright (C) by IBM Corporation "LANtastic" is Copyright (C) 1991-1995 by Artisoft "Doorway" is Copyright (C) 1987-1995 by Marshall Dudley "Remdoor" is Copyright (C) 1989-1995 by Ken Brown "HS/Link" is Copyright (C) 1992-1995 by Samuel H. Smith "RIP" is Copyright (C) 1992-1995 by TeleGrafix Communications, Inc. "BGFAX" is Copyright (C) 1993-1995 by B. J. Guillot 1.2 - SPITFIRE SUPPORT ----------------------- If you encounter problems running SPITFIRE, begin by referring to Appendix B, SPITFIRE Questions and Answers. Many of the most common SPITFIRE questions are addressed in that section of the manual. If you are unable to solve your problem after reading the SPITFIRE Question and Answer section and you are sure you've followed the steps outlined in the documentation, gather together a report of your version number along with information pertaining to the difficulties you are experiencing (such as System, Modem, Com Port) and contact Buffalo Creek's BBS at (515-225-8496) for support. Be as thorough as possible so an accurate determination of the cause of your problem(s) can be made. Every effort will be made to determine and to correct the Page 4 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- problem! Please keep in mind that it is difficult at best to provide help if you simply leave a message that says something like, "I can't make external protocols work. What am I doing wrong?". You need to provide specific information regarding the problem. Furthermore, if you've had a problem which isn't covered by this manual and were able to work it out without support, please contact Buffalo Creek's BBS so the information you have discovered can be shared with other users of SPITFIRE. Also, please report any unique configurations you may discover so everyone will benefit from your ideas. 2.0 - SPITFIRE HARDWARE REQUIREMENTS ------------------------------------ The following are considered the minimum equipment requirements for running SPITFIRE: <1> MS-DOS/IBM compatible personal computer <2> At least 256K memory <3> DOS version 3.0 or higher <4> Fixed disk (preferable) <5> Modem SPITFIRE requires several files being open at the same time. For this reason, you will need to have the following files and buffers set in your system's CONFIG.SYS file, located in your root directory. SPITFIRE may not work properly if this is not done! CONFIG.SYS should have the following settings: FILES=25 BUFFERS=30 DEVICE=ANSI.SYS DEVICE=BRK.DRV The "DEVICE=BRK.DRV" is optional, however, if your system supports the use of SPITFIRE Doors, External File Transfer Protocols, or any of the Sysop Configurable commands from the Main, File, Message or Sysop Menus, the use of BRK (or some similar utility) is certainly recommended. More information regarding the use of BRK is provided in the EXTERNAL FILE PROTOCOLS section of this manual. If you are unfamiliar with how CONFIG.SYS works, consult your DOS manual. If you do not configure your system to allow at least 25 files to be open at once, you may have a problem with SPITFIRE aborting and displaying a message of Runtime error 004. Page 5 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SPITFIRE supports a number of features which cause it to search the PATH for COMMAND.COM. To work properly, SPITFIRE must be able to find COMMAND.COM residing in a directory set up in your path statement. These features are the ability to jump to DOS, the Sysop configurable features from each menu, execution of the SFINIT.BAT or the SFMSGPCK.BAT and external file transfer drivers. In the event you are unfamiliar with setting a PATH, please refer to your DOS manual. 2.1 - MODEMS ------------ SPITFIRE automatically determines your incoming callers' baud rate. In order for this to work, your modem must be able to send verbose result codes. Appendix A contains a list of modems and their corresponding initialization strings which have been reported to work with SPITFIRE. SPITFIRE determines the baud rate of incoming calls by receiving the verbose result code from your modem when the modem establishes carrier detect. Listed below are examples of verbose result messages returned by most modems. Non-Error Correction Modems Error Correction Modems --------------------------- ----------------------- 300 Baud - CONNECT 1200 Baud - CONNECT 1200 1200 Baud - CONNECT 1200/ARQ 2400 Baud - CONNECT 2400 2400 Baud - CONNECT 2400/ARQ 7200 Baud - CONNECT 7200 7200 Baud - CONNECT 7200/ARQ 9600 Baud - CONNECT 9600 9600 Baud - CONNECT 9600/ARQ 14400 Baud - CONNECT 14400 14400 Baud - CONNECT 14400/ARQ 16800 Baud - CONNECT 16800 16800 Baud - CONNECT 16800/ARQ 28800 Baud - CONNECT 28800 28800 Baud - CONNECT 28800/ARQ SPITFIRE's default modem initialization string seems to work with many modems. Some modems, however, may require a unique initialization string. There are three modem register settings that MUST exist in your modem initialization string for SPITFIRE to work properly. They are S0=0, V1 and S2=1. There are a number of firms (modem manufacturers, etc) who graciously provided evaluation products for testing with SPITFIRE. Mike Woltz and Buffalo Creek Software would like to express much appreciation to these firms for their help and support. These firms are not listed for fear that we would omit a name. 2.2 - MODEM INITIALIZATION -------------------------- When SPITFIRE is booted, it sends the Pre-Initialization string the Sysop configures at the ALT+M SPITFIRE Async Configuration window, waits for modem response and then sends the configured modem Page 6 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- initialization string to the modem after each caller. This procedure seems to work fine with most modems. In the event you are using a USR HST Dual Standard and wish to run your BBS at 38400 baud in V.32 mode, the initialization string listed below works: ATS0=0B0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X6^M Should you need to change the modem initialization string, you select ALT+M at the "SPITFIRE ready for use" prompt. Appendix A contains a listing of modems and corresponding initialization strings which have been reported to work with SPITFIRE. The modem initialization string can also be altered at the DOS prompt by entering the following command line parameters: SPITFIRE /M ATS0=0Q0V1E0M0H0S2=1X1^M (Your Initialization String) Using the same command line parameters, the modem initialization string can be included within the SF.BAT file. Please note, however, the command line parameters set in SF.BAT will always override those set by using ALT+M at the "SPITFIRE ready for use" prompt. The configuration of SPITFIRE in conjunction with most modems is relatively simple. One of the first things which you need to be concerned with is whether your modem is configured to report a carrier even when there is not a carrier. Many (most) modems, by factory default, are configured to constantly report a carrier even when there is not an actual carrier. When initializing the modem, SPITFIRE will provide the error message "Modem Reporting Carrier" when the modem is configured to falsely report a carrier. In such case, it is recommended that you change the factory defaults using the below listed procedure: 1) Load your favorite terminal program (QMODEM, TELIX or whatever). 2) At the OK prompt, enter AT&C1&D2&W ... You should then see another OK prompt. 3) Return to DOS and then boot SPITFIRE. SPITFIRE should no longer provide the error message "Modem Reporting Carrier". In the event you are using a 2400 baud modem or slower (non-high speed FAX modem), then the below listed configuration should work: Baud Rate: 2400 Pre-Init String: ATZ^M Page 7 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 1st Choice Init String: ATS0=0V1Q0E0H0M0S2=1X1^M 2nd Choice Init String: AT&F1S0=0V1&C1&D2Q0E0H0M0S2=1X1^M 3rd Choice Init String: AT&FS0=0V1&C1&D2Q0E0H0M0S2=1X1^M 4th Choice Init String: AT&FS0=0V1Q0E0H0M0S2=1X1^M Off Hook String: ATM0H1 Hardware Data Flow Control: Yes DTR Hangup: Yes In the event you are using a high speed FAX modem, then the below listed configuration should work: Baud Rate: 19200 for 14400 bps modem Baud Rate: 38400 for 28800 bps modem Baud Rate: 57600 for high speed modem if you are using a 16550 UART chip Pre-Init String: ATZ^M 1st Choice Init String: AT&F1S0=0V1&C1&D2Q0E0H0M0W2S95=3S2=1X4^M 2nd Choice Init String: AT&FS0=0V1&C1&D2Q0E0H0M0W2S95=3S2=1X4^M 3rd Choice Init String: AT&FS0=0V1Q0E0H0M0S2=1X4^M Off Hook String: ATM0H1 Hardware Data Flow Control: Yes DTR Hangup: Yes In the event the above information doesn't work correctly with your modem, then please feel free to contact Buffalo Creek Software for help. The 'Pre-Init String Failure' error message is for informational purposes. Your system may work just fine even though you see this informational error message. Such informational error message simply means that your modem did not return an OK after the configured pre-initialization string was sent to it. Page 8 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 3.0 - GETTING STARTED --------------------- If you're like most computer users, you're probably not thrilled with the prospect of reading the entire documentation of SPITFIRE. Most folks are going to boot this program and try to run SPITFIRE without reading further. So here are some quick guidelines regarding your initial setup of SPITFIRE. <1> Create a directory named SF on the drive on which you intend to run SPITFIRE. Copy all SYSTEM FILES into your newly created SF directory. (Listed in the SPITFIRE SYSTEM FILES section of this manual.) <2> Included in the SPITFIRE package is a file named SF.BAT. You may use any text editor (as long as it saves in ASCII format) to modify this file. Examine the default values (such as target and source drives) and configure them to comply with your setup. (Example: The default drive specification is C: and if you're running SPITFIRE on drive D, then you'll need to change this to D: ). After finishing that, look for the line that contains SPITFIRE /C1. "/C1" indicates the COM port you are using. In the event you are using COM port 2, you need to change the string to read "SPITFIRE /C2". After you've made these changes, be certain to save your modified file to disk. ** NOTE ** The default command line parameters are used for booting SPITFIRE on your system for the first time. After setting these parameters in SPITFIRE by using the ALT+M modem configuration window, any unnecessary command line parameters (i.e., SPITFIRE /C1, etc.) should be removed from your SF.BAT file. <3> Now you are ready to boot SPITFIRE by using your SF.BAT file. When first booting SPITFIRE, you will get the prompt "SFSYSTEM.DAT not found! Do you wish to create it? <Y/n>". SPITFIRE defaults to "Y" and by pressing <ENTER> or entering "Y" for yes, SPITFIRE creates the required SFSYSTEM.DAT file. Subsequently, SPITFIRE provides similar prompts for other required files. These include: SFNODE.DAT SFUSERS.DAT SFFAREA.DAT SFMCONF.DAT By pressing <ENTER> or "Y" at each prompt, SPITFIRE will automatically create the file and place it in the appropriate directory. Page 9 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- The first thing to be concerned with is not properly assigning the correct COM port. In the event you have the wrong COM port configured, it is possible that SPITFIRE will lock up at this point. In such case, refer to step number 2 in this section. If the COM Port is properly assigned, you will then be prompted for the Sysop's Name. The name you enter here is the name that the callers will see credited as being the Sysop of the system. You will most likely want to enter your real full name. Next, SPITFIRE will ask you for a Sysop Caller Name. It is recommended you answer this prompt with "Sysop". (The name you enter here, should be the name that you use to log on the BBS.) SPITFIRE addresses all comments left for the Sysop to this configured name. SPITFIRE will next prompt you to input a password, phone number, city, state/province and date of birth. SPITFIRE uses the responses entered here to automatically add you as the first caller in the SFUSERS.DAT file. If your modem is malfunctioning, disconnected or turned off, SPITFIRE will display the message "Your modem is not responding properly! Do you wish to continue? <y/n>". Answer "Y" and SPITFIRE will progress to the "SPITFIRE ready for use..." prompt. Press ALT+M to modify the modem's initialization string to one which will work properly with your modem. (Refer to the section, SPITFIRE ASYNC CONFIGURATION for configuring SPITFIRE for your modem.) <4> At the "SPITFIRE ready for use..." prompt, press ALT+S to log on locally as Sysop. When asked for your name, you must enter the same name as you entered as the Sysop Caller Name when configuring SPITFIRE. (If you use the name "Sysop", the system will ask for a last name. Simply press <ENTER> and continue.) Next enter the password you previously selected. At the Main Menu, press F2 and set your security level to 999. Now move from menu to menu and view the various features. After viewing, and experimenting with the various features, log off by pressing G for Goodbye, and next press Y to answer Yes to the "Are you sure you want to logoff?" prompt. SPITFIRE will reset, and the "SPITFIRE ready for use" prompt will appear at this point. 3.1 - SPITFIRE ASYNC CONFIGURATION ---------------------------------- The SPITFIRE Async Configuration is used to view or modify your modem configurations such as serial port, initialization strings, baud Page 10 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- rate, etc. AT the "SPITFIRE ready for use..." prompt, press the ALT key, and while holding it down, next press the M key. This keystroke combination opens the SPITFIRE Async Configuration window. The commands that you will see are listed below: --< SPITFIRE NODE 1 ASYNC CONFIGURATION >-- Initialization String............ : ATS0=0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X1^M <A> Answer String.................. : ATA <F> Fax Connection Result Msg...... : FAX <1> Line COM1.. : IRQ4 Pre-Initialization String...... : ATZ^M <2> Line COM2.. : IRQ3 <O> Offhook String................. : ATH1 <3> Line COM3.. : IRQ4 <S> Serial Port No................. : 1 <4> Line COM4.. : IRQ3 System Baud Rate............... : 19200 <5> Line COM5.. : IRQ0 <E> Error Correction Message....... : ARQ <6> Line COM6.. : IRQ0 <H> DTE Locked..................... : Yes <7> Line COM7.. : IRQ0 <N> Number Of Rings................ : 1 <8> Line COM8.. : IRQ0 <D> Display Result Messages........ : On <F1> Base COM1.. : 03F8 <C> Disconnect Delay............... : 28 <F2> Base COM2.. : 02F8 Use High Speed Async Routines.. : Yes <F3> Base COM3.. : 03F8 <R> Baud Rate Requirement.......... : 1200 <F4> Base COM4.. : 02F8 <L> Break Length..(1000=1 Second).. : 100 <F5> Base COM5.. : 0000 <M> DTR Hangup..................... : Yes <F6> Base COM6.. : 0000 <F7> Base COM7.. : 0000 <F8> Base COM8.. : 0000 Enter Command or <Q>uit - Command Sets the modem initialization string appropriate for your modem. In most cases, a carriage return (a ^M) should be placed at the end of your initialization string. However, some modems do not require the carriage return. If this is the case with your modem, simply do not include the ^M at the end of your initialization string. ** NOTE ** The caret sign (^) is entered by pressing the shift key, in combination with the numeric 6 key and should not to be confused with the caret sign which is used to indicate a control character when creating SPITFIRE Display Files. Command <A> Allows the Sysop to configure the answer string that is required by the modem in order for the modem to receive both Fax and data calls. In the event you do not have your system configured to receive Fax calls, this option should be set to ATA. If the system is configured to receive Fax calls, then you should use the answer string supported by your particular modem. Page 11 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <F> Specifies the FAX Connection Result Message which allows SPITFIRE to distinguish that the incoming call is a Fax call. Enter the Fax Connection Result Message that is appropriate for your particular modem. For example, the USR Courier HST Dual Standard with Fax uses +FCO. SPITFIRE defaults to +FCO as the FAX Connection Result Message. Command Specifies the pre-initialization string sent to the modem prior to initializing the modem. ATZ^M should be used in most instances. However, some modems do not require the carriage return (^M). If this is the case with your modem, simply use ATZ here. ** NOTE ** The caret sign (^) is entered by pressing the shift key, in combination with the numeric 6 key and should not to be confused with the caret sign which is used to indicate a control character when creating SPITFIRE Display Files. Command <O> Defines the off hook string required by your modem. Most modems use the standard ATH1 to set the modem off hook. However, some newer modems, due to a change in FCC regulations, will only leave the modem off hook for 30 seconds when the ATH1 command is used. The off hook string allows the Sysop to enter the string which will allow the modem to remain off hook for an extended period of time. For example, the Zoom 28.8 uses ATX1D; as its extended off hook string. Command <S> Specifies the COM Port being utilized by this node. Command Defines the maximum baud rate allowed by this node. The maximum COM port speed in SPITFIRE is 115200. Command <E> Specifies the Error Correction Message for your particular modem if an error correction modem is being used. For instance, US Robotics uses ARQ. Please refer to your modem manual to determine the error correction message used by your modem, providing it has error checking capabilities. Some of the newer model modems use different result codes when an error correction connection is detected. SPITFIRE is hard coded to automatically search for the ARQ, MNP and REL result codes which indicate an error correction connection has been made. In addition to these, SPITFIRE will search for the error correction control message the Sysop configures here. Page 12 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <H> Specifies whether the BBS is being configured to operate at a locked baud rate. If toggled to Yes, and the BBS is configured to a maximum baud rate of 57600, when an incoming call is received SPITFIRE leaves the COM port open at 57600 regardless of the speed of the incoming call. In other words, when set to Yes, it is the modem's responsibility to control the flow of data. This is equivalent to hardware flow control. If toggled to No, and the BBS is configured to a maximum baud rate of 57600, when an incoming call is received, SPITFIRE adjusts the COM port speed to match that of the incoming call. Or, SPITFIRE assumes responsibility to control the flow of data. This is equivalent to software flow control. Command <N> Specifies on what ring number SPITFIRE will answer incoming calls. For instance, with 1, SPITFIRE answers the incoming call on the first ring. Most often, you will want this set to 1. Command <D> Toggles On or Off SPITFIRE's display of the modem's verbose message. For instance, when toggled On, and a caller logs on at 2400 baud, CONNECT 2400 is displayed to the screen, and is also recorded in the CALLERS.LOG. If this is toggled Off, the CONNECT message will not be written to the screen or recorded in the CALLERS.LOG. Command <C> Specifies the disconnect delay. This feature is for modems utilizing a data buffer. The Sysop may use this option to configure the amount of time to delay the disconnect, allowing the data contained in the modem buffer to be displayed to the caller. SPITFIRE defaults to 28, which is adequate for the 5k buffer in the US Robotics HST. Command This switch should be set to On provided your system operates properly using high speed routines. If your display files are not properly shown to the remote caller, then turn this switch Off. Command <R> This switch sets the minimum baud rate required to access your BBS. For instance, if set at 1200, a caller must connect at a baud rate between 1200 and the maximum baud rate of your BBS. Callers connecting at baud rates less than the rate configured here will be shown SF2SLOW.BBS and the caller will be logged off the system. This is a variable option, and can be set to disallow callers with a baud rate of 65535 or less. Page 13 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <L> Sets the break length for each tilde found in the modem initialization string. If the break length is set at 500, each time SPITFIRE finds a tilde symbol in the modem initialization string, it will pause for 1/2 second. Command <M> When this option is toggled to Yes, SPITFIRE will disconnect the caller and place the modem in command state by lowering the DTR. When set to No, SPITFIRE places the modem in command state by sending the escape code (ASCII 001) three times to the modem, requiring the modem's S2 register to be set to 1. It is recommended that this toggle be set to Yes. Command <1> Allows the Sysop to configure the IRQ SPITFIRE will use for COM port 1. IRQ4 is standard for COM1. Valid options are 1 through 15. Command <2> Allows the Sysop to configure the IRQ SPITFIRE will use for COM port 2. IRQ3 is standard for COM2. Valid options are 1 through 15. Command <3> Allows the Sysop to configure the IRQ SPITFIRE will use for COM port 3. IRQ4 is standard for COM3. Valid options are 1 through 15. Command <4> Allows the Sysop to configure the IRQ SPITFIRE will use for COM port 4. IRQ3 is standard for COM4. Valid options are 1 through 15. Command <5> Allows the Sysop to configure the IRQ SPITFIRE will use for COM Port 5. Valid options are 1 through 15. Command <6> Allows the Sysop to configure the IRQ SPITFIRE will use for COM Port 6. Valid options are 1 through 15. Command <7> Allows the Sysop to configure the IRQ SPITFIRE will use for COM Port 7. Valid options are 1 through 15. Command <8> Allows the Sysop to configure the IRQ SPITFIRE will use for COM Port 8. Valid options are 1 through 15. Command <F1> Allows the Sysop to configure the base address SPITFIRE will use for COM port 1. 03F8 is standard for COM1. Command <F2> Allows the Sysop to configure the base address SPITFIRE will use for COM port 2. 02F8 is standard for COM2. Command <F3> Allows the Sysop to configure the base address SPITFIRE will use for COM port 3. 03F8 is standard for COM3. Page 14 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <F4> Allows the Sysop to configure the base address SPITFIRE will use for COM port 4. 02F8 is standard for COM4. Command <F5> Allows the Sysop to configure the base address SPITFIRE will use for COM port 5. Command <F6> Allows the Sysop to configure the base address SPITFIRE will use for COM port 6. Command <F7> Allows the Sysop to configure the base address SPITFIRE will use for COM port 7. Command <F8> Allows the Sysop to configure the base address SPITFIRE will use for COM port 8. 3.2 - SPITFIRE CONFIGURATION ---------------------------- The SPITFIRE Configuration Window allows the Sysop to configure a variety of system options for their BBS. At the "SPITFIRE ready for use" prompt, press ALT+Z. The ALT+Z keystroke combination opens the SPITFIRE Configuration window. The commands that you will see are listed below: --< SPITFIRE CONFIGURATION >-- <A> Sysop Caller Name............ : Sysop Sysop Name................... : John Doe <C> Drop to DOS Password......... : *********************** <D> BBS Starting Date............ : July 15, 1995 <E> Daily Time Limit............. : 60 <F> Log On Time Limit............ : 60 <G> Maximum Callers In Database.. : 500 <H> Maximum Caller Daily Access.. : 10 # Of Callers................. : 1 <J> # Of File Description Lines.. : 20 <K> Upload Time Compensation..... : 1.000 <1> Expired Security... : 0 <L> New Caller Security.......... : 10 <2> Expiration Warning. : 0 <M> New Caller Log On Time....... : 45 <3> Sysop Security..... : 50 <N> No Activity Time Limit....... : 3 <4> Node Chat Drive.... : E <O> Node Number.................. : 2 <5> Default ANSI Color. : 32 Private BBS Security Level... : 0 <R> Total Number Of Nodes........ : 3 <S> U/D Ratio Violation Security. : 25 <T> Upload Disk Space Requirement : 100K ENTER COMMAND [<Q>... Quit]: Command <A> Use this command to enter or change the Sysop Caller Name. Page 15 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command Allows you to change the Sysop name. This is the name callers will see credited as the Sysop of the BBS. Command <C> Sets the password that is needed to drop to DOS from a remote location. The default is a blank line. To use this feature, 'a drop to DOS' password must be configured. The configured password is disguised by asterisks, and is never visible. Should you forget the drop to DOS password, it can be reconfigured. Command <D> This command sets the starting date of your bulletin board. If you are already running an established board, you can enter the original starting date of your BBS rather than the date of your conversion to SPITFIRE. Command <E> Sets the amount of time per day a caller is allowed on the board. Refer to the section on SPITFIRE FILE CLARIFICATION in this manual for more information on setting daily time limits in SPITFIRE's DAILYLMT.DAT. Command <F> Sets the amount of time allowed per call for each caller. Refer to the section on SPITFIRE FILE CLARIFICATION in this manual for more information on setting daily time limits in SPITFIRE's DAILYLMT.DAT. Command <G> Determines the number of callers you will allow to utilize your BBS. (i.e. - If this value is set at 500 and you already have 500 callers and a new caller (501) tries to log on, the system displays the file MAXUSERS.[BCR], if it exists, and logs the caller off the BBS.) Command <H> This option limits how many times a caller can call the board each day. If this number is exceeded, the system will display TOOMANY.[BCR], if it exists, and log the caller off the BBS. Command This allows the Sysop to set the number of callers. The purpose of this command is to allow Sysops already running an established board to enter their current number of callers, so as not to start the BBS with Caller Number 1. Command <J> Sets the number of descriptive lines callers can input when uploading files to the BBS. Valid options are 1 through 20. If set to 1, only single-line descriptions are allowed. Using 2 through 20 allows multi-line file descriptions. If this option is set to allow multi- Page 16 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- line file descriptions, and a caller uploads a file the entire multi-line description entered by the caller is written to the CALLERS.LOG. Also, if the file is uploaded for Sysop Only, the entire multi-line description entered by the caller is written in the HEYSYSOP.LOG. If the ALT+T option, Uploaded By Description, is set to Yes it will add 1 line to the description crediting the caller who uploaded the file. So even if this option is set to 1, if the ALT+T's Uploaded By Description is set to Yes multi-line file descriptions will result. ** NOTE ** If any SPITFIRE utility, such as SFCHKUP, uses the file description contained in the file's FILE_ID.DIZ to replace the description entered by the caller then there is no limit to the number of descriptive lines allowed by SPITFIRE. Command <K> Sets the ratio for the amount of time a caller is compensated in relation to the amount of time spent uploading. SPITFIRE defaults to 1.000. If you wish to reward the caller with additional time for uploads, increase this numeric value. For instance, if this is set at 2.000 and a caller spends 10 minutes uploading, the caller is compensated 20 minutes after the upload is completed. Command <L> Sets the default security level for a new caller. Command <M> Sets the amount of time a new caller is allowed on the BBS. (First day only) Command <N> Sets the amount of time a caller can remain inactive (no keyboard input) before being automatically logged off the BBS. Command <O> Sets the Node Number for this particular node of the BBS. If you are not operating a multi-node system, this should be set to 1. If you are operating a multi-node BBS, the node number entered here should correspond to the appropriate node number. In other words, the second node should be set to 2, the third node to 3, etc. SPITFIRE supports up to 255 nodes. Command This command sets the security required to access the BBS if the BBS has been toggled to be a private BBS. If a caller attempts to log on the BBS and does not have a security equal to or greater than what the Page 17 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Sysop has set here, the display file, PRIVATE.[BCR], if it exists, is displayed to the caller, and the caller is logged off the BBS. Multi-node systems should set this option for each individual node. Command <R> Sets the total number of nodes available on your system. For single node systems, a 1 is entered, and for multi-node systems, it would be equivalent to the total number of nodes supported in your system setup. SPITFIRE supports up to 255 nodes. Command <S> Specifies the security level that a caller will be changed to if the upload/download ratio is violated. SPITFIRE's DAILYLMT.DAT file defines parameters for determining if and when a caller's security is adjusted for violating the upload/download ratio. The DAILYLMT.DAT file must define a VWR (Violation Warning Ratio) and a VER (Violation Enforcement Ratio). The VWR and VER should be defined for each security level on the BBS for which the Sysop desires to monitor upload/download requirements. (Refer to the section - SPITFIRE FILE CLARIFICATIONS - for further information on SPITFIRE's DAILYLMT.DAT.) If SPITFIRE finds the VWR and VER is defined for the security level of the caller, each time a file is downloaded, SPITFIRE performs the following calculations to determine if a caller has violated the upload/download ratio requirement: The number of files downloaded by a caller is divided by the number of files uploaded AND the number of kilobytes downloaded by the caller is divided by the number of kilobytes uploaded by the caller. SPITFIRE must verify that both the file ratio, and the kilobyte ratio have been violated. If the results of both the file, and kilobyte calculation are greater than the value defined for the VER (Violation Enforcement Ratio), SPITFIRE will then alter the caller's security level to that configured here at the U/D Ratio Violation Security. ** NOTE ** SPITFIRE will return the caller to their original security once the caller's upload/download ratio is again within the required ratio limits. SPITFIRE's SFUSERS.DAT file contains a field which stores information regarding the caller's original security level. When a caller uploads a file to the BBS, SPITFIRE first checks to see if the caller's current Page 18 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- security level is less than their original security. If so, SPITFIRE performs the same computations as described above. If the results of the file or kilobyte calculation is less than the VER (Violation Enforcement Ratio), the caller's original security level is restored. Keep in mind, for this to work properly, the VER (Violation Enforcement Ratio) must be configured the same for both security levels, the security that is being monitored and the U/D Ratio Violation Security entered here. Command <T> Allows the Sysop to configure the amount of disk space which must be available on the upload drive before a caller will be allowed to perform an upload. The default is 100K. Command <1> Defines the security level a caller will be returned to in the event their subscription to the BBS should expire. When a caller logs on and the caller's subscription has expired, then SPITFIRE will display SFSUBCHG.[BCR] and will alter the caller's security level to this pre-determined level. At the time a caller's security level is altered, SPITFIRE records the event in the CALLERS.LOG. If you do not intend to use the subscription features of SPITFIRE, simply set this value to 0. Command <2> Allows the Sysop to configure the number of days prior to a caller's subscription expiring that the caller will be warned. SPITFIRE uses the number of days entered here in conjunction with the subscription date (date the subscription will expire which is maintained in the caller's record) to warn the caller of the impending subscription expiration. SPITFIRE displays SUBWARN.[BCR] to warn the caller of the approaching subscription expiration. SPITFIRE also records that the warning was issued to the caller in the CALLERS.LOG. If you do not intend to use the subscription features of SPITFIRE, simply set this value to 0. Command <3> Sets the Sysop security level. Any caller with an access equal to or greater than this value can read all messages (public and non-public), undelete messages, delete any message, copy a message and overwrite existing files when uploading (the filename already exists) as well as being able to perform other functions not available to callers with a security level less than what is configured here. Page 19 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <4> Specifies the drive letter which will be used to read and write the node chat file. Due to the constant access required of this file during the process of a node chat, it is highly recommended that a RAM drive be created for use as the node chat drive. DOS comes with the necessary software to create a RAM drive. Refer to your DOS manual for instructions on creating a RAM drive. Command <5> This option allows the Sysop to set the default ANSI color that will be used for new callers to the BBS. Valid options are 31 through 36. The colors associated with the numeric value are 31 Red, 32 Green, 33 Yellow, 34 Blue, 35 Magenta, 36 Cyan, and 37 White. After completing your SPITFIRE Configuration, enter <Q> to Quit and the "Ready..." prompt is displayed. 3.3 - TOGGLE SPITFIRE SWITCHES ------------------------------ The Toggle SPITFIRE Switches allows the Sysop to toggle the availability of specific SPITFIRE features when configuring their BBS. The Toggle SPITFIRE Switches window is opened by pressing ALT+T at the SPITFIRE ready prompt. A window opens up to display the following configuration options: -----< Toggle SPITFIRE Switches >----- <A> US Phone Number Style......... : On <1> Mandatory Msg Scan..... : On Log On - Message Statistics... : On <2> Use RIP Command Lines.. : No <C> Log On - New File Statistics.. : On <D> Require New Caller Birthdate.. : Yes <E> New Caller Default Protocol... : Yes <F> File Description Conversion... : On <G> Type Of BBS................... : Public BBS <H> ANSI Graphics................. : Ansi Available Second Password............... : One Password <J> Direct Screen Writes.......... : Yes <K> Uploaded By Description....... : Yes <L> Password Failure Comment...... : No <M> Require Door Return Password.. : No <N> Scan All Msg Conferences...... : Yes <O> Comprehensive Upload Search... : On Color Monitor................. : Yes <R> RIP Graphics.................. : Yes <S> Search CD Rom Area SFFILES.... : No <T> Test Files Upon Boot.......... : Yes Use International Characters.. : No Enter Command <<Q>... Quit>: Page 20 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <A> Allows the Sysop to configure whether the BBS will use the US phone number format (###-###-####) or allow SPITFIRE to accept any 12 character string entered by the caller. SPITFIRE defaults to the US Phone Number Style set to On. Command This feature enables the Sysop to determine whether callers will be prompted with their message statistics when logging on the BBS. If this is set On, the caller is notified upon log on of any new messages, number of received messages, messages sent by the caller and total number of messages on the BBS. SPITFIRE's default is On. Command <C> Allows the Sysop to designate whether callers are prompted with new file statistics when logging on. If this is set to On and the caller elects to view new files, a list of all new files will be displayed to the caller. Additionally, SPITFIRE informs callers of the number of new files since last checked, as well as the total downloadable files and bytes available on the system. SPITFIRE's default is On. SPITFIRE will not check for new files or report file statistics on a file area that is configured as a CD-ROM file area. When toggled On, the caller may tag files from the new files listing for download. After the list has finished displaying, and if the caller has tagged files for download, SPITFIRE will prompt the caller as to whether to begin the file download process. If the caller responds with a "Y", SPITFIRE will then prompt the caller as to whether he/she would like to be logged off after the download is completed. If the caller responds with a "Y", when the download is completed, the caller is automatically logged off the BBS. In such an instance, it is possible for a caller to log on the BBS, perform a file download and log off the BBS without ever reaching the Main Menu of the BBS. Command <D> Designates whether a new caller logging onto the BBS for the first time is required to enter their date of birth. If toggled to Yes, the birthdate is required. If toggled to No, the caller is not prompted to enter their date of birth. If Second Password option is toggled to Second Password Required, and the Require New Caller Page 21 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Birthdate is changed to No, SPITFIRE will automatically change the Second Password option to One Password. **NOTE** SPITFIRE uses a caller's date of birth as the second password, when required. It is not possible to require a second password if the BBS does not require the caller to enter their date of birth. Command <E> This feature determines if a new caller logging onto the BBS is allowed to select a default file transfer protocol after answering the new caller questionnaire. If toggled to Yes, the new caller is automatically presented with this option. If this feature is set to Off, the new caller is not automatically presented with this option, but may still select a default file transfer protocol from the <Y>our Statistics option of the Main Menu. Command <F> Toggles SPITFIRE's File Description Conversion On and Off. When toggled On, SPITFIRE automatically converts the first character of each word in the file description entered by the caller to upper case. All other characters will be lower case. The exception to this would be any words which SPITFIRE finds in SFUPCASE.DAT (in the Work File Path). Any words the Sysop places in SFUPCASE.DAT are converted to all upper case characters, i.e., BBS, SPITFIRE, COM, ZIP, etc. If toggled Off, SPITFIRE makes no attempt to alter the description entered by the caller. SPITFIRE defaults to setting this On. *** NOTE *** When using SFCHKUP or similar utilities to replace the file description entered by the caller with the FILE_ID.DIZ text, regardless of the File Description Conversion toggle, SPITFIRE will not alter the imported FILE_ID.DIZ description. Command <G> Toggles the BBS as a Private or Public system. If you toggle this as a Private BBS, then the caller's name must be found in the callers file and the caller's security must be equal to or greater than that configured for option <R> Private BBS Security Level at the ALT+Z configuration screen prior to the caller being granted access. If the caller's name is found in the caller data base but the caller's security is not equal to or greater Page 22 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- than the configured Private BBS Security Level, then PRIVATE.[BCR], if it exists, is displayed to the caller and the caller is logged off the BBS. Command <H> Toggles ANSI graphics On or Off. If you wish to offer ANSI graphics, you must create .CLR files to match the display .BBS files you have, (i.e., ALL.BBS {non-ANSI} and ALL.CLR {ANSI Graphics}). In order for you to see the ANSI Graphics locally, DEVICE=ANSI.SYS must exist in your CONFIG.SYS file. Command Toggles password prompt. If toggled to One Password, the caller simply enters their password. If toggled to Second Password Required, after entering the first password, the system prompts the caller for their birth date. Should the caller not know their birth date, the system logs them off. **NOTE** If the BBS is configured not to require a caller to enter their date of birth when logging onto the BBS the first time, SPITFIRE automatically sets this option to One Password, if it is not already. The Second Password Required is only available when callers are required to enter their birth date. Command <J> Toggles the Direct Screen Write feature on and off. If you are running SPITFIRE in a multi-tasking environment, you will want to set this to No to disable direct screen writing. Otherwise, set this to Yes because using direct screen writes increases the speed of the display. Command <K> Toggles whether a line is added to the file description crediting the caller who uploaded the file. The line, "Uploaded By <Caller's Name>" will appear as the last line of the file description if this is set to Yes. If set to No, no information referencing the uploader will appear in the file description. Command <L> Toggles whether a caller who is unable to enter their password may leave a Comment To The Sysop. If toggled to "No", the caller is not prompted for a comment. When toggled to "Yes", the caller is given the option of leaving a comment to the Sysop before being logged off the BBS. Command <M> Toggles whether the BBS requires a caller to enter their passwords when returning to SPITFIRE from the Page 23 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- door section of the BBS. If toggled to No, entering their password is not required when returning from a door. Command <N> This feature allows Sysops to designate the message scan parameters. When set to Yes, all message conferences are included in the scan. When set to No, only messages in the caller's queued conferences are scanned. This affects both the log on message scan and the scan performed when selecting <Y>...Your Messages option from the Message Menu. Command <O> This feature provides Sysops the option of configuring whether the system will take advantage of SPITFIRE's comprehensive file search when a caller attempts an upload. If toggled Off, SPITFIRE searches for exact matches. If a match is found, the caller is informed that the file already exists on the BBS. When toggled On, SPITFIRE trims any trailing digits from the file name during the search, replacing the numeric values with the '*' wildcard. For instance, if a caller attempts to upload SF35.ZIP, SPITFIRE would search for SF*.ZIP. SPITFIRE will report individually each SF*.ZIP file it finds on the BBS and prompt the caller as to whether they still wish to continue with the upload. **NOTE** The Comprehensive Upload Search does not prevent callers from uploading the file. This feature is meant only to make the callers aware that another version of this file already exists on the BBS. Hopefully the majority of callers are responsible enough not to upload older versions of existing files, but rather only the more current, updated versions. Command This feature allows the Sysop to toggle whether or not the monitor used for the BBS is a color monitor. Command <R> Allows the Sysop to configure whether RIP Graphics will be made available to callers of the BBS. If toggled to Yes, when a caller logs on the BBS, SPITFIRE will test to determine if the caller is using a RIP terminal program. If the caller is not using a RIP terminal communications program the caller is prompted with: "Do You Want ANSI Graphics? <y/N>". If the caller is using a RIP terminal program, the caller is prompted to select one of the following graphic formats: <A>nsi, <R>ip, or <N>one. If RIP Graphics is selected, *.RIP display files will be displayed to the caller, if found. Page 24 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <S> Toggles whether a File Area configured as a CD-Rom Area (refer to the section, Configuring File Area Records) will search SFFILES.<x> during file searches rather than the CD-Rom drive. This option provides the Sysop the capability of configuring SPITFIRE to work with a CD-Rom in the most efficient manner. If it is faster to search the CD-Rom drive, then toggle this option to No. However, if it is faster to search the SFFILES.<x>, then toggle this option to Yes. Command <T> Toggles whether SPITFIRE tests the various message base files to assure that the files are in working condition. If toggled On, when SPITFIRE is booted the message base files are tested. If toggled Off, no tests are performed. Sysops with numerous message conferences may wish to toggle this Off to speed the boot process. SPITFIRE defaults to On and this setting is recommended to ensure file integrity. Command Allows the Sysop to configure whether to allow keyboard input of non-English characters, with an ASCII value of 128 to 175. These characters are used in countries outside the United States. Command <1> Allows the Sysop to configure whether SPITFIRE will perform the message base scan when a caller logs on the BBS. When toggled On SPITFIRE will automatically scan the message base for new messages the first time a caller logs onto the BBS each day. If the caller makes additional calls to the BBS that day, then the message base scan will be optional. If toggled Off, the caller will be prompted as to whether he/she would like to review the BBS message statistics. Command <2> Toggles whether the SPITFIRE command lines will be displayed to callers logging onto the BBS using the RIP Graphic format. If toggled to Yes, SPITFIRE will display the menu command lines after the RIP menus are displayed. If toggled to No, SPITFIRE's menu command lines will not be displayed after the RIP menus are displayed. 3.4 - CONFIGURING SPITFIRE FILE PATHS ------------------------------------- When setting up a SPITFIRE BBS for the first time, SPITFIRE automatically creates the default file paths. SPITFIRE will place any file which it creates in the appropriate file path. If you wish to Page 25 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- modify these settings, you may do so by pressing ALT+P at the SPITFIRE "Ready..." prompt. Pressing ALT+P opens the SPITFIRE File Path window which allows the Sysop to configure the file paths that will be used when running SPITFIRE. --<SPITFIRE FILE PATHS>-- <A> Work Files Path..................: C:\SF\WORK Message Files Path...............: C:\SF\MESSAGE <C> Display Files Path...............: C:\SF\DISPLAY <D> External Transfer Path...........: C:\SF\EXTNOD1 ENTER COMMAND < <Q>...Quit> : An explanation of each command is listed below: Command <A> Specifies the directory in which the SPITFIRE Work Files reside. (For more information on this refer to the section FILE PATHS in this manual.) All files belonging in the Work File Path are specified as such with a (WORK) in the file description in the section - SPITFIRE WORK FILES. Command Allows you to specify the directory in which the SPITFIRE Message Files will reside. All files belonging in the Message File Path are specified as such with a (MESSAGE) in the file description in the section - SPITFIRE MESSAGE FILES. Command <C> Specifies the directory in which the SPITFIRE Display Files reside. All files with a BBS, CLR or RIP extension are Display Files and should reside in the directory you designate here. (For more information refer to the section on FILE PATHS in this manual.) All files belonging in the Display File Path are specified as such with a (DISPLAY) in the file description in the section - SPITFIRE DISPLAY FILES. Command <D> Allows you to specify the directory from which you opt to run the SPITFIRE External Transfer Protocols. All files which you are using to run the External Transfer Protocols must reside in the directory you designate here. (For more information refer to the section - EXTERNAL FILE TRANSFER PROTOCOLS of this manual.) Establishing specified file paths provides Sysops with more manageable directories. However, if the Sysop prefers, all files can be accessed from the SF directory. Simply enter C:\SF in response to each of the above file path questions. Page 26 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- After you've configured SPITFIRE to meet your specifications, Quit and return to the "SPITFIRE ready for use..." prompt. The next thing to be concerned about when setting up a SPITFIRE BBS is configuring your system records. 4.0 - SETTING UP THE SYSTEM RECORDS ------------------------------------ Message Conference records and File Area records comprise your SPITFIRE system records. There are two ways to set up the system records in SPITFIRE. The first is by using ALT key combinations at the SPITFIRE "Ready..." prompt. The second is through the Sysop Menu which is accessed from the Main, Message or File Menus. SPITFIRE will allow 784 different Message Conferences and 65535 File Areas. 4.1 CONFIGURING MESSAGE CONFERENCE RECORDS ------------------------------------------- Message Conference records are configured by pressing ALT+R at the "Ready" prompt or by selecting option <M> from the Sysop Menu. When this is done the following will display to the screen: Conference Description.. : "Untitled Message Conference" Msg Conference Access... : Equal To Or Greater Than Caller Security Public Messages Only.... : No Message Entry Security.. : 25 Conference Security..... : 5 Net-Mail Conference..... : No Maximum Msg Length...... : 99 Purge Msgs Older Than... : 120 days Caller Message Deletion. : Yes Purge Unreceived Msg.... : No Delete Old Thread Msg... : Yes Net ID Name............. : UNTITLED MSG Allow Message Routing... : No Privileged Securities... : 0;0;0;0;0 >>>> RECORD [1 Of 10] MESSAGE SYSTEM RECORD MENU <<<< <N>.......... Net-Mail Toggle <M>... Conference Description <S>...... Conference Security <@>........ Conference Access <#>............ Record Number <A>........... Add New Record ..... Public Messages Only <C>...... Caller Msg Deletion .....Insert New Conference <D>........ Delete Conference <O>.........Old Message Purge ......Unreceived Msg Purge <+>.......... Next Conference <->...... Previous Conference <T>..... Purge Old Thread Msg <L>........Maximum Msg Length <R>.... Allow Message Routing <E>....Message Entry Security <!>...............Net ID Name <&>.... Privileged Securities ENTER COMMAND - [N M S @ # A P C I D O U + - T L R E ! & <Q>uit ]? Command <N> - Net-Mail Toggle Allows the Sysop to configure whether an individual message conference will allow net-mail. If a message Page 27 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- conference is set up to allow net-mail, callers are allowed to leave messages to a person who is not a caller on the BBS. If a message conference is not configured to allow net-mail a caller can only leave messages to other callers of the BBS. (This also applies to Carbon Copy messages.) Command <M> - Conference Description You will notice that the default Message Conference description is "Untitled Message Conference". Change this to suit your needs. As an example, you may wish to change the description of this conference to "Public Messages". Command <S> - Conference Security This allows you to set the security level for this Message Conference. You will notice that the default security level is 5, which means that any caller with a security of 5 or greater will be able to read messages in this conference. If you wish to set a different security level for this Message Conference, then select <S> to change the security level of the conference. Command <@> - Conference Access You will note that SPITFIRE defaults the Message Conference Access to "Equal To Or Greater Than". What this means is that any caller with a security level equal to or greater than the security level of this Message Conference can access it. If you select <@>, SPITFIRE will toggle this feature to "Equal To Caller Security" and only callers with a security level equal to the security level of the Message Conference will be able to access this conference. Callers with a security level greater than or less than the security level of this conference will not be able to access this conference (unless the caller has Sysop security or whose security is equal to a specified Privileged Security). Command <#> - Record Number Allows you to enter a specific Message Conference record number. After entering the number, the information for the record number you specified is displayed. Command <A> - Add New Record Allows the Sysop to add a new Message Conference to the Message base. The new record will be added after the last existing Message Conference record. For instance, if your system has 25 Message Conferences and the <A> option is selected, a Message System Record Number 26 will be added. Page 28 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command - Public Messages Only Toggles 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 <C> - Caller Msg Deletion Toggles whether a caller of the BBS is allowed to delete messages. If set to Yes, the caller will be able to delete messages either sent to or sent by them. If this is toggled to No, a caller will not be allowed to delete 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 offers the Caller Deletion option which the Sysop can use to configure whether a caller is allowed to delete messages in 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 New Conference Inserts a new Message Conference record between two existing Message Conference records. Upon selecting this option, SPITFIRE displays the prompt "Insert before which conference?". A new Message System Record is inserted preceding the Message System Record number that is 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 Message Conference. For example, assume the BBS has five active Message Conferences and a new Message Conference is inserted prior to Message Conference #4. The new Message Conference becomes Message Conference #4. The previous Message Conference #5 now becomes Message Conference #6 and the SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX and SFMSG05.LMR are appropriately renamed to SFMSG06.DAT, SFMSG06.PTR, SFMSG06.IDX and SFMSG06.LMR. The previous Message Conference #4 now becomes Message Conference #5, and the SFMSG04.DAT, SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR are appropriately renamed to SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX and SFMSG05.PTR. Page 29 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SPITFIRE will also rename any SFMSG<x>.BBS/CLR/RIP when a Message Conference is inserted. For example, let's assume there are 25 Message Conferences on the BBS. If a Message Conference is nserted before Message Conference #23, SFMSG25.BBS/CLR/RIP would be renamed to SFMSG26.BBS/CLR/RIP, SFMSG24.BBS/CLR/RIP would be renamed to SFMSG25.BBS/CLR/RIP, and SFMSG23.BBS/CLR/RIP would be renamed to SFMSG24.BBS/CLR/RIP. Command <D> - Delete Conference This option allows an existing Message System Record to be deleted. Upon selecting this option SPITFIRE displays the prompt "Delete which conference?". The number entered here will cause that Message Conference to be removed. ***IMPORTANT NOTE*** When deleting an existing Message Conference the SFMSG<x>.DAT, SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR files are automatically reset to correspond to the appropriate Message Conference. For example, let's again assume the BBS has five active Message Conferences and Message Conference #4 is deleted. The pre-existing SFMSG04.DAT, SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR files are deleted when Message Conference #4 is deleted. The previous Message Conference #5 now becomes Message Conference #4. The SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX and SFMSG05.LMR are appropriately renamed to SFMSG04.DAT, SFMSG04.PTR, SFMSG04.IDX and SFMSG04.PTR. SPITFIRE will also rename any SFMSG<x>.BBS/CLR/RIP when a Message Conference is deleted. For example, let's assume there are 25 Message Conferences on the BBS. If a Message Conference #23 is <D>eleted, SPITFIRE would rename SFMSG24.BBS/CLR/RIP to SFMSG23.BBS/CLR/RIP and SFMSG25.BBS/CLR/RIP would be renamed to SFMSG24.BBS/CLR/RIP. Command <O> - Old Message Purge Specifies how many days old a message in this particular conference must be prior to it being purged during SPITFIRE's message packing procedure. For instance, if this is set to 120 days, when SPITFIRE packs this message conference any messages older than 120 days will be purged. Command - Unreceived Msg Purge Specifies whether messages which are unreceived are allowed to be purged from the Message Conference. If Page 30 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- set to Yes, when packing the message base any messages older than the days set with the <O>..Old Message Purge option will be purged even if they have not yet been received. If set to No, unreceived messages will not be purged. Command <+> - Next Conference This option is used to move forward from one Message System record to another. Pressing the "+" key initiates the progression from one Message Conference record to the next in sequential order. Upon reaching the last record, if the "+" key is pressed, SPITFIRE will cycle to the first Message System record. Command <-> - Previous Conference This option is used to cycle through the Message System records in reverse order. Pressing the "-" key causes the previous conference number to be displayed. From the first Message System record, if the "-" key is pressed, SPITFIRE will cycle to the last Message System record. Command <T> - Purge Old Thread Msg This option allows the Sysop to designate whether threaded messages will be deleted when using SPITFIRE's SFPCKMSG message packer. If this is toggled to Yes, when the message base is packed, threaded messages older than the days set with the <O>..Old Message Purge will be deleted. If toggled to No, threaded messages will not be deleted from the message base. Command <L> - Maximum Msg Length The option allows the Sysop to configure the maximum lines that will be allowed per message in this message conference. Valid options range from 25 lines to 99 lines. For instance, if 50 is entered, the maximum length for all messages in this conference would be 50 lines. Command <R> - Allow Message Routing The Routing option is only applicable if the message conference has been configured as a net-mail conference. When set to Yes (and you are using BCSUTI Version 1.0 or greater or responding to a message imported through Buffalo Creek's SHILOH netmail system) SPITFIRE will automatically default the message routing information for you. Otherwise, you will need to manually enter the message routing information. Page 31 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- The Routing feature also works with carbon copy messages. So it is possible to send the same message to 10 different people, routing it to 10 different locations. When entering a routed message, SPITFIRE allows the caller to specify whether the message should be sent as public or non-public. SPITFIRE allows a caller to enter a routed, non-public message even though the conference has been configured to allow public messages only. Command <E> - Message Entry Security This option allows the Sysop to configure the security level required before a caller is allowed to enter a a message in this Message Conference. A caller whose security is equal to or greater than the security entered here will be allowed to enter messages in this Message Conference. A caller whose security is less than the security configured here will not be allowed to enter a message in this Message Conference. To configure a Message Conference as read-only, simply configure this option at a value equal to or greater than the highest security level of any caller. It should be noted that if a caller receives a message in a Message Conference where the caller's security is less than the configured Message Entry Security, the caller will not be allowed to reply to the message. Also, if a caller's security is equal to a configured privileged security, the caller will be allowed to enter messages in the conference even though the caller's security might be less than the configured Message Entry Security. Command <!> - Net ID Name When this feature is selected, the Sysop can configure the Net ID Name for this conference. The Net ID Name is a shortened conference description name used by LAKOTA, (SPITFIRE's QWK Mail System), SHILOH (Buffalo Creek's Netmail System) and BCSUTI (Buffalo Creek's UTI utility) If the Sysop does not configure this, the Net ID Name defaults to the first 15 characters from the Message Conference description. (LAKOTA uses the first 13 characters of the Net ID Name while BCSUTI and other mail exchange programs may use the full 15 characters.) Command <&> - Privileged Securities This feature allows the Sysop to configure up to five privileged security levels per Message Conference. If a caller logs on and has a security level equal to a security assigned here, the caller will have access to this Message Conference regardless of how the Message Page 32 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Conference Security and the Message Conference Access options have been configured. In other words, the privileged security will always override the Security and the Access configuration for the Message Conference. A caller with a privileged security may also enter messages in the conference even though the caller's security might be less than the configured Message Entry Security. As an example, assume a Message Conference has been configured only to allow callers with a security level greater than or equal to 50. Also, assume that 30 is configured as a privileged security. If a caller with a security of 30 logs onto the BBS, the caller will have full access to that particular Message Conference. Command <Q> - Quit Upon selecting this option, SPITFIRE will return to the place from which the Message System Record Menu was initiated. In other words, if invoked from the Sysop Menu, SPITFIRE will return to the Sysop Menu. If initiated from the "Ready..." prompt, SPITFIRE will return to the "Ready..." prompt. 4.2 - CONFIGURING FILE AREA RECORDS ----------------------------------- File Area records are configured by pressing ALT+F at the "Ready" prompt or by selecting option <F> from the Sysop Menu. When this is done the following is displayed to the screen: Download Path..... : C:\SF Upload Path....... : C:\SF Area Description.. : "Untitled File Area" Area Access....... : Equal To Or Greater Than Caller Security Area Security..... : 5 No Charge (FREE) Area.. : No Preview Area...... : No Privileged Securities.. : 0;0;0;0;0 CD Rom Area....... : No Search File Area.. : Yes >>>> RECORD [1 Of 10] 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 <$>......... Search File Area (N>.....No Charge (FREE) Area <&>.... Privileged Securities ENTER COMMAND - [F U D S @ R A I P T + - C $ N & <Q>uit ]? Page 33 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <F> - Area Description Notice that the default File Area description is "Untitled File Area". Change the area description so it appropriately describes the types of files stored in this particular file area. For example, if the files in this area could be categorized as system utilities, a suitable description for this area might be "Utilities". Select <F> to make this change. Command - Upload Path To change the upload path, simply select from the menu. The Upload and Download paths are any legal DOS path names telling SPITFIRE where it can find the files associated with the File Area. It is possible to configure uploads to go into a single "Recent Uploads" File Area, or to different areas which you could specify by subject. Here are a few examples of upload/download paths: The following example sends uploads to a sub-directory called "UPLOADS" and allows the caller to download programs from a sub-directory called "UTILITIES". (Note: SF is the parent directory.) Download Path.....C:\SF\UTILITIES Upload Path.......C:\SF\UPLOADS In the following example, uploads are sent to the same sub-directory where the files available for downloading exist: Download Path.....C:\SF\UTILITIES Upload Path.......C:\SF\UTILITIES If you're running the BBS on a floppy-based system with upload and download files on drive B, and not using sub-directories, you could do the following: Download Path.....B:\ Upload Path.......B:\ Command <D> - Download Path You will notice that SPITFIRE sets the default download path to the directory where SPITFIRE resides. To change this DOS file path, select <D> to set the path for this File Area. In the event that the file path 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 Page 34 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 available for download) in that directory. The SFFILES.BBS file must also reside in that directory. (The utility, SFFILESA, which creates your SFFILES.BBS for each file directory, is available for download from Buffalo Creek's BBS - 515-225-8496.) If the File Area is configured as a CD Rom File Area, a SFFILES.<x>, where <x> represents the File Area number, will need to be created and placed the directory that is configured as the Display file path. SFFILES.<x>, like SFFILES.BBS, is a text file listing the files available for download for that file area. To use SPITFIRE's extended download directory feature, create an FA<x>.TXT, where <x> is equal the File Area number, and place it in the SPITFIRE home directory. FA<x>.TXT is a simple text file which can be created using your favorite text editor, as long as it saves in ASCII text. Each line of FA<x>.TXT should contain the drive and directory of any extended download directories for the File Area. For instance, if File Area 5 was configured for Games, the contents of the FA5.TXT in the SPITFIRE Home directory might look like this: F:\GAMES G:\NEWGAMES If SPITFIRE does not find the file to download, read, view, etc. in the configured download directory (the primary download directory) it will then look for the appropriate FA<x>.TXT in the SPITFIRE Home directory. The number of extended download directories can be configured using FA<x>.TXT is unlimited. However, the SFFILES.BBS in the primary download directory (or the SFFILE.<x> for areas configured as CD Rom file areas) should list all files available for downloading from all download paths, including any extended download directories. The FA<x>.TXT, extended download directory feature, provides additional CD Rom support. However, the Sysop should be aware when using this feature that if the File Area is not configured as a CD Rom File Area and the file Page 35 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- to be downloaded exists on a CD Rom disc, the file is directly transferred to the caller from the CD Rom drive rather than being copied to the disk drive. Secondly, if the File Area is configured as a CD Rom File Area and the ALT+T's Search CD Rom Area SFFILES.BBS is toggled to Yes, SPITFIRE will search the SFFILES.<x>, rather than the drive. Therefore, the file must be listed in the SFFILES.<x> in order for SPITFIRE to find the file. Command <S> - Area Security This allows you to set the security level for this File Area. You will notice that the default security level is 5, which means that any caller with a security of 5 or greater will be able to access this File Area. If you wish to set a different security level for the File Area, then select <S> to change the security level of the area. Command <@> - Area Access Note that SPITFIRE defaults to the File Area Access of "Equal To Or Greater Than". This means that callers with a security level equal to or greater than the security level of this File Area can access it. If you select <@>, SPITFIRE will toggle this feature to "Equal To Caller Security". Then only callers with a security level equal to the security level of the File Area will be able to access this area. Callers with a security level greater than or less than the area security level will be unable to access it, except those callers with Sysop security or a security equal to a configured privileged security. Command <R> - Record Number This option allows you to enter a specific File Area record number. Upon entering the number, all current information for the record number you specified is displayed. Command <A> - Add New Area By selecting the <A> option, a Sysop can add a new File Area Conference to the File Area System Records. The new record will be added after the last existing File Area System Record. For instance, if your system has 25 File Areas and the <A> option is selected, a File Area Record Number 26 will be added. SPITFIRE will allow up to 65,535 File Areas. Command - Insert New Area By selecting , a Sysop can insert a new File Area System Record between two existing file areas. Upon Page 36 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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. *** IMPORTANT NOTE *** SPITFIRE will rename any SFFILES.<x> or FA<x>.TXT file area listings which are affected by inserting a new file area record. For instance, let's assume that a BBS is configured as having 25 file areas, and File Area #24 and File Area #25 are CD-Rom file areas which use SFFILES.24 and SFFILES.25 to list files available in those areas. Next assume a file area is inserted before File Area #24. SPITFIRE will automatically rename SFFILES.25 to SFFILES.26 and SFFILES.24 to SFFILES.25 when it inserts the new file area. Similarly, if in the same scenario, the BBS utilized a FA24.TXT and a FA25.TXT, FA25.TXT would be renamed to FA26.TXT and FA24.TXT would be renamed to FA25.TXT when the new file area is inserted. SPITFIRE will also rename any SFIL<x>.BBS/CLR/RIP when a new File Area is inserted. For example, let's assume there are 25 File Areas on the BBS. If a new File Area nserted before File Area #23, SFIL25.BBS/CLR/RIP would be renamed to SFIL26.BBS/CLR/RIP, SFFIL24.BBS/CLR/RIP would be renamed to SFIL25.BBS/CLR/RIP, and SFIL23.BBS/CLR/RIP would be renamed SFMSG24.BBS/CLR/RIP. 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. When a File Area is purged, the subsequent File Area system records are appropriately reset in sequential order. For instance, if there are 15 File Areas on a system and File Area 12 is purged, File Area record 13 becomes 12, File Area record 14 becomes 13 and File Area record 15 becomes 14. *** IMPORTANT NOTE *** SPITFIRE will rename any SFFILES.<x> or FA<x>.TXT file area listings which are affected by deleting an existing file area record. For instance, let's assume that a BBS is configured as having 25 file areas, and File Area #24 and File Area #25 are CD-Rom file areas which use SFFILES.24 and SFFILES.25 to list files available in those areas. Next, assume that File Area #23 is deleted. SPITFIRE will automatically rename SFFILES.24 to Page 37 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFFILES.23 and SFFILES.25 to SFFILES.24 when it deletes the existing file area. Similarly, if in the same scenario, the BBS utilized a FA24.TXT and a FA25.TXT, FA24.TXT would be renamed to FA23.TXT and FA25.TXT would be renamed to FA24.TXT when the file area is purged. SPITFIRE will also rename any SFIL<x>.BBS/CLR/RIP when a File Area is purged. For example, let's assume there are 25 File Areas on the BBS. If File Area #23 is purged, SFIL24.BBS/CLR/RIP would be renamed to SFIL23.BBS/CLR/RIP and SFFIL25.BBS/CLR/RIP would be renamed to SFIL24.BBS/CLR/RIP. Command <T> - Toggle Preview Area The "T" option will toggle a File Area's Preview Area option between Yes and No. If Preview Area is toggled to Yes, a caller with a security less than the required Area Security will be allowed limited access to preview this file area. This means that the caller can access this file area, list files, read text files, view file archives, etc. but will not be allowed to download any files from this area. In other words, the caller can do everything except download from this file area. If this is toggled to No, callers with a security less than the specified Area Security will not be allowed access to this File Area. Command <+> - Next Area This option is used to move forward from one File Area System record to another. Pressing the <+> key will progress forward from one record to the next in numerical order. When reaching the last record and the <+> key is pressed, SPITFIRE will cycle to the first File Area System record. Command <-> - Previous Area This option cycles through the File Area System records in reverse order. Pressing the <-> key will display the preceding record number. From the first File Area System record if the <-> key is pressed SPITFIRE will cycle to the last File Area System record. Command <C> - CD Rom Area The option specifies the file area as a CD Rom Area. If this is toggled on, then SPITFIRE searches the Display File Path for a SFFILES.<x> for the file listing of this CD Rom Area. The <x> should correspond with the number of the file area. For instance, if File Area 15 is configured as a CD Rom Area then the file listing would Page 38 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- need to be named SFFILES.15. If SPITFIRE finds any file areas configured as CD Rom Areas it does not report file statistics for the BBS when listing <N>ew Files at log on or from the File Menu. When a caller elects to download a file from a CD Rom File Area, SPITFIRE copies the file from the CD Rom to the disk drive. SPITFIRE creates a sub-directory off the configured Work directory and names the sub-directory it creates CDROM<node number>. For example, if the configured Work directory of node 2 is C:\SF2\WORK, then the sub-directory created by SPITFIRE would be C:\SF2\WORK\CDROM2. The file which is copied to this directory is erased, however, the sub-directory is not removed. Command <$> - Search File Area Allows Sysops to configure whether the download path for the File Area will be searched for duplicate files when a caller attempts an upload. If this is toggled to Yes, the download path will be searched and if this is toggled to No, the download path will not be searched. As an example, Sysops using a CD Rom file area may wish to skip the search for these areas due to the time that is required to scan these areas. ** NOTE ** For a File Area configured as a CD Rom File Area, if the Search CD Rom Area SFFILES has been toggled to Yes from the Toggle SPITFIRE Switches configuration window and the File Area's record Search File Area option is configured to Yes, then the SFFILES.<x> is searched for duplicate files rather than the drive/directory listing. Command <N> - No Charge (FREE) Area Allows the Sysop to configure whether a File Area will be a free File Area. If this option is toggled to Yes, a caller may download files from this area and the caller's statistics (number of files downloaded and kilobytes downloaded) will not be updated. When toggled to No, files downloaded from this area will update the caller's statistics, increasing the number of files and the kilobytes downloaded for each file that is downloaded from this area. Files may be downloaded from a File Area configured as a No Charge (FREE) Area even if the download would cause the caller to exceed the daily file and/or daily byte limit configured by the Sysop in DAILYLMT.DAT. Page 39 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <&> - Privileged Securities This feature allows the Sysop to configure up to five privileged security levels per File Area. If a caller logs on and has a security level equal to a security assigned here, the caller will have access to this File Area regardless of how the File Area Security and the File Area Access options have been configured. In other words, the privileged security will always override the Security and the Access configuration for the File Area. As an example, assume a File Area has been configured only to allow callers with a security level greater than or equal to 50. Also, assume that 30 is configured as a privileged security. If a caller with a security level of 30 logs onto the BBS, the caller will be granted access to that particular File Area. Command <Q> - Quit Selecting this option will return you to the place in SPITFIRE from where the File System Record Menu was called. In other words, you will be returned either to the Sysop Menu or the "Ready..." prompt. SPITFIRE will automatically save your newly configured System Record. 5.0 - SPITFIRE FILE PATHS ------------------------- SPITFIRE supports paths for the files which are accessed in the process of its execution. Using the individual file paths created by SPITFIRE (SYSTEM, WORK, MESSAGE, DISPLAY and EXTERNAL), your directories are more manageable. The SYSTEM files path is the directory in which you have set up SPITFIRE (usually C:\SF) and contains files required for the execution of SPITFIRE. The WORK files path contains files which SPITFIRE accesses and writes to periodically in the process of program execution. The DISPLAY files path contains all files which are displayed to the caller while logged on the BBS. The MESSAGE files path contains all files used by the message section of SPITFIRE. The EXTERNAL files path includes the files necessary to provide the caller with optional transfer protocols other than those provided in 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 in most instances display a default message if a display file is not found. The DISPLAY files merely provide an additional means by which the Sysop can create unique screens to personalize their BBS system. Page 40 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- The system files that were created when setting up SPITFIRE MUST reside in the main SPITFIRE directory (also referred to as the SPITFIRE Home 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 - CONFIGURING SPITFIRE FILE PATHS of the SPITFIRE manual.) The following sections discuss, individually, files used by SPITFIRE. After the file description, a (SYSTEM), (WORK), (MESSAGE) or (DISPLAY) is included to help you determine in which directory the file should be placed. No files which will be used in your External Protocol Path will be found. These are not included in the SPITFIRE package because these are separate programs written by other programmers. 5.1 - SPITFIRE SYSTEM FILES --------------------------- There are five file types that comprise SPITFIRE and allow it to function - System, Work, Message, Display and External Protocol. The first is SYSTEM FILES. System Files are mandatory for SPITFIRE's operation and MUST reside in your main (also referred to as HOME) SPITFIRE directory from which you run SPITFIRE. SPITFIRE.EXE - Main System Program. (SYSTEM) SPITFIRE.OVR - SPITFIRE Overlay File. (SYSTEM) SFMAIN.MNU - SPITFIRE Main Menu. (SYSTEM) SFMSG.MNU - SPITFIRE Message Menu. (SYSTEM) SFFILE.MNU - SPITFIRE File Menu. (SYSTEM) SFSYSOP.MNU - SPITFIRE Sysop Menu. (SYSTEM) The above-mentioned files MUST be present for SPITFIRE to run. SPITFIRE will halt if these files are not found in the directory from which you are running your system. The following system files will be created by SPITFIRE if they are not already present. SFNODE.DAT - Configuration information for this node. (SYSTEM) SFFAREA.DAT - File Area system information. (SYSTEM) SFMCONF.DAT - Message Conference system information. (SYSTEM) SFEVENTS.DAT - Stores information regarding scheduled events.(SYSTEM) Other system files which will need to reside in the SPITFIRE home directory include: SFREMOTE.BAT - Used for remote Drop to DOS. (SYSTEM) SF.BAT - Batch file for invoking SPITFIRE. (SYSTEM) Page 41 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFMAIN.BAT - Executes Sysop configurable command option available from the Main Menu. (SYSTEM) SFMAIN.DAT - File created that contains caller information. SPITFIRE creates this file when a caller uses the Main Menu Sysop Configurable Command to execute a third party program. This file is automatically erased when the caller returns to SPITFIRE. (SYSTEM) SFMESS.BAT - Executes Sysop configurable command option available from the Message Menu. (SYSTEM) SFMESS.DAT - File created that contains caller information. SPITFIRE creates this file when a caller uses the Message Menu Sysop Configurable Command to execute a third party program. This file is automatically erased when the caller returns to SPITFIRE. (SYSTEM) SFFILE.BAT - Executes Sysop configurable command option available from the File Menu. (SYSTEM) SFFILE.DAT - File created that contains caller information. SPITFIRE creates this file when a caller uses the File Menu Sysop Configurable Command to execute a third party program. This file is automatically erased when the caller returns to SPITFIRE. (SYSTEM) SFSYSOP.BAT - Executes the Sysop Configurable Command option that is available from the Sysop Menu. (SYSTEM) SFSYSOP.DAT - File created that contains caller information. SPITFIRE creates this file when a caller uses the Sysop Menu Configurable Command option. This file is automatically erased when the caller returns to SPITFIRE. (SYSTEM) SFDOOR.MNU - SPITFIRE Door Menu. (SYSTEM) SFDOORS.DAT - File created that contains caller information. SPITFIRE creates this when a caller uses the SPITFIRE door feature and erases it when the caller returns to SPITFIRE. (SYSTEM) DOOR.SYS - Universal door file that contains caller information. SPITFIRE creates this when a caller uses the SPITFIRE door feature. (SYSTEM) SFORDER.MNU - SPITFIRE Questionnaire/Order Menu. (SYSTEM) SFCHAT.CAP - Text file of chat captures. (SYSTEM) CALLERS.TMP - Temporary file for recording callers' activity. This file is later appended to CALLERS.LOG file in the WORK file path and erased. (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 the caller logs off and prior to initializing the modem. (SYSTEM) Page 42 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFLOGON.BAT - Batch file, if found, is executed when a caller logs onto the BBS and after the system information is displayed. (SYSTEM) SFSEC<X>.BAT - Batch file, if found, is executed after a caller logs onto the BBS provided the caller's security is equal to <X> of the SFSEC<X>. (SYSTEM) BADINIT.BAT - Batch file executed when modem initialization fails, i.e., SPITFIRE reports the modem is not responding properly. (SYSTEM) SFFAX.BAT - Batch file executed after SPITFIRE answers the phone and testing establishes the incoming call is a fax connection. (SYSTEM) SPITFIRE.HLP - Help with all commands for all menus. This file can be modified using SFHELP. Consult the documentation accompanying SFHELP. NOTE: Systems using the Sysop Configurable Command option(s) will need to modify this help file with SFHELP to include an explanation of the added feature(s). (SYSTEM) SFPROTCO.HLP - Extra help with Uploads/Downloads. This is a simple text file that you can modify with your favorite text editor, provided it saves in ASCII format. (SYSTEM) LAKOTA.COM - SPITFIRE companion utility which allows messages to be downloaded and uploaded in QWK format. (SYSTEM) SFPCKMSG.COM - SPITFIRE companion utility which purges old messages from the message base. SPITFIRE shells to SFPCKMSG.COM when packing messages, either as Event M or from the Sysop Menu. (SYSTEM) SFPCKUSR.COM - SPITFIRE companion utility that purges inactive callers and/or callers that are marked for deletion from SPITFIRE's caller database, SFUSERS.DAT. (SYSTEM) FA<x>.TXT - Text file which contains the drive and directory of extended download directories for the appropriate File Area. <x> represents the File Area number. (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, SFSYSOP.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. Page 43 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 5.2 - SPITFIRE MESSAGE FILES ---------------------------- All files relating to message conferences reside in the MESSAGE file path. SPITFIRE supports up to 784 message conferences and for each message conference on the system a SFMSG<X>.DAT, SFMSG<X>.PTR, SFMSG<X>.LMR and SFMSG<X>.IDX file is created. (<X> refers to the number of the corresponding message conference and will range from 1 to 784.) SFMSG<x>.DAT - All messages are contained here. (MESSAGE) SFMSG<x>.PTR - Message data pointer file. (MESSAGE) SFMSG<x>.IDX - Message index file. (MESSAGE) SFMSG<x>.LMR - Last message read pointer file. (MESSAGE) * NOTE * Any Sysop operating a multi-node system should be aware that SPITFIRE allows all nodes to share a common MESSAGE file path. 5.3 - SPITFIRE WORK FILES ------------------------- The third file type is WORK FILES. Although not all of these files are required to run SPITFIRE, you will, no doubt, find them invaluable in the operation of your BBS system. These files are accessed routinely and are periodically written to during the course of SPITFIRE's execution. If the REQUIRED work files are not found, SPITFIRE will create them, with the exception of SFCALLOG.DAT. The SFCALLOG.DAT is not created, but included in the SPITFIRE distribution package and must be copied over to the directory configured as the WORK FILE PATH. (SFNEWU.QUE, SFORDER<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 - Caller data file. (WORK) SFUSERS.PTR - Caller data pointer file. (WORK) SFUSERS.LST - Text file created when caller's data file is printed to disk from the Sysop Menu (WORK) CALLERS.LOG - Record of the BBS callers' activities. (WORK) SFCALLOG.DAT - Stores information used to write CALLERS.LOG. (WORK) HEYSYSOP.LOG - Record of special Sysop notification. (WORK) SFNEWU.QUE - New caller questionnaire. (WORK) SFNEWU.REP - Contains new caller questionnaire replies. (WORK) SFORDER<x>.QUE - Questionnaires/Order Forms available to callers from the Main Menu. (WORK) SFORDER<x>.REP - Contains callers' responses to the Main Menu Questionnaires/Order Forms. (WORK) JOKER.DAT - List of undesirable caller names. (WORK) Page 44 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFBBSLST.DAT - Contains list of other boards to call. (WORK) SFILEREQ.LOG - Log file of caller's file requests for files that are stored OFFLINE or which are included in the SFFILES.BBS list but can not be found in the download directory. (WORK) SFUPCASE.DAT - Keywords in a file description that will be converted to upper case. (WORK) SFNOUP.DAT - List of files the Sysop does not want uploaded to the BBS. (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 - List of callers purged from the BBS. Contains caller's name, address and security level at the time of the purge. (WORK) SFWHOSON.DAT - Contains information regarding who is logged onto each node. (WORK) BBSNAME.DAT - Net-mail tag line data. (WORK) ** NOTE ** Any Sysop operating a multi-node system should be aware that SPITFIRE allows all nodes to share a common WORK file path. 5.4 - SPITFIRE DISPLAY FILES ---------------------------- SPITFIRE display files must be placed in the directory which the Sysop has configured as the DISPLAY FILE PATH. SPITFIRE display files use three graphic formats. Files with an extension of .BBS use the ASCII (non-color) format. Files with an extension of .CLR use the ANSI (color) format. Files using a .RIP extension use the Remote Imaging Protocol, commonly referred to as RIP graphics format. If the display files are not found, SPITFIRE will run just the same and in many instances display a default message to the caller. Display files can be created using your favorite text editor or screen generating program. Below is the list of display files available in SPITFIRE. In this listing, as well as throughout the remainder of the manual, if the display file name is followed by the code characters [BCR], it can be created using each of the three graphic formats, using the appropriate extension of .BBS (ASCII), .CLR (ANSI) or .RIP (RIP). If the display file name is followed by the code characters of [BC ], it can be created using the graphic format with the appropriate extension of .BBS (ASCII) or .CLR (ANSI). If the display file uses a specific graphic format, the appropriate extension will follow the display file name. Page 45 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- For instance, .BBS would indicate the file must be created using the ASCII format only. The display file a caller sees will depend on the Graphic mode the caller selects when logging onto the BBS. <x>.[BCR] - Displays to the caller at log on if the caller record number equals <x>. (DISPLAY) <x>SEC.[BCR] - Displays to all callers with a security level equal to <x>. (DISPLAY) ALL.[BCR] - Displays to all callers upon log on, unless their security allows for a quick log on. (DISPLAY) BULLETIN.[BCR] - Menu listing of bulletins (BULLET<x> files) available to the caller. (DISPLAY) BULLET<x>.[BCR] - Displays to the caller when <x> bulletin is selected from the Bulletin Menu where <x> can equal 1 to 99. (DISPLAY) CHATDONE.[BC ] - Displays to callers after completing a chat with the Sysop. (DISPLAY) DLMT.[BCR] - Displays to callers when downloads exceed the daily limit. (DISPLAY) DORBUL<x>.[BCR] - This file displays to callers when <x> bulletin is selected from the Door Bulletin Menu, where <x> can equal 1 to 99. (DISPLAY) EVENTIME.[BCR] - Displays to a caller who logs on and has their log on-time adjusted so an on-time event can be completed at a specified time. (DISPLAY) FILECTRL.RIP - RIP graphic display file which can be used as a control panel while the caller is in the File section of the BBS. (DISPLAY) FILE<x>.[BCR] - File menu that is displayed to callers whose security level is equal to <x>. (DISPLAY) FILST<x>.[BCR] - Listing of available File Areas to callers whose security level is equal to <x>. (DISPLAY) GOODBYE.[BCR] - Displays to callers when logging off the BBS. (DISPLAY) LOCKOUT.[BCR] - Displays to a caller at log on if the caller is marked as locked out or is found in JOKER.DAT. (DISPLAY) MAINCTRL.RIP - RIP graphic display file which can be used as a control panel while the caller is in the Main section of the BBS. (DISPLAY) MAIN<x>.[BCR] - Main menu that is displayed to callers whose security level is equal to <x>. (DISPLAY) MAXUSERS.[BCR] - Displays to new callers when the maximum number of callers have been reached. (DISPLAY) MSGCTRL.RIP - RIP graphic display file which can be used as a control panel while the caller is in the Message section of the BBS. (DISPLAY) MSG<x>.[BCR] - Message menu that is displayed to callers whose security level is equal to <x>. (DISPLAY) Page 46 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- MGLST<x>.[BCR] - Listing of available Message Conferences displayed to callers whose security level is equal to <x>. (DISPLAY) NEEDSYS.[BC ] - Displays to callers prior to the connection being terminated using the ALT+F1 key. (DISPLAY) NEWUSER.[BCR] - Displays to new callers (normally rules of the BBS). (DISPLAY) NOSPACE.[BCR] - Displays to a caller attempting to upload when the disk space available is less than what the Sysop has configured at the ALT+Z Upload Disk Space Requirement option. (DISPLAY) PRIVATE.[BCR] - Contains message displayed to callers logging onto a private system if they exist in the caller database but their security is not equal to or greater than the ALT+Z's Private Security Level option. (DISPLAY) SF1STM.[BCR] - Displays to the caller when entering the Message Section the first time per log on. (DISPLAY) SF1STF.[BCR] - Displays to the caller when entering the file section the first time per log on. (DISPLAY) SF2SLOW.BBS - Displays to a caller who connects at a baud rate lower than what the Sysop has configured as the minimum baud rate allowed on the BBS. (DISPLAY) SFASLEEP.[BC ] - Displays to a caller who has not entered a keystroke for the amount of time configured by the Sysop at the ALT+Z's No Activity Time Limit, prior to logging them off the BBS. (DISPLAY) SFBATCHD.[BCR] - Display file of the Batch Download Menu. (DISPLAY) SFBATCHU.[BCR] - Display file of the Batch Upload Menu. (DISPLAY) SFBDAY.[BCR] - Displays to a caller on their birthday. (DISPLAY) SFDOOR<x>.[BCR] - Displays to callers entering the corresponding SPITFIRE Door program. <x> can be an alphabetical character A through Z, with the exception of G and Q, which are reserved for use by SPITFIRE. (DISPLAY) SFDORBAK.[BCR] - Displays to a caller upon returning to the SPITFIRE BBS after completing a door program if the Sysop has configured the BBS to require a password when returning from a door. Normally used to prompt the caller for his/her password. (DISPLAY) SFDORBUL.[BCR] - Lists the door bulletins available to the caller from the SPITFIRE Door Menu. (DISPLAY) SFDOWN.[BCR] - Displays to callers prior to a download. (DISPLAY) SFDR<x>.[BCR] - Door menus for each of the corresponding security levels available on the BBS. (DISPLAY) SFEXTDN.BBS - Contains a list of external download file transfer protocols available on the BBS. (DISPLAY) SFEXTUP.BBS - Contains a list of external upload file transfer protocols available on the BBS. (DISPLAY) SFFILES.BBS - Display file containing the names of files available for downloading in each of the file areas on the BBS. Page 47 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- This is the only exception to the rule of placing a Display File in the Display File Path. A SFFILES.BBS should be placed in each download directory; listing the files available for download from that particular File Area. (DOWNLOAD DIRECTORIES) SFFILES.<x> - ASCII text listing of files available for download from a CD Rom file area. <x> represents the number of the File Area. (DISPLAY) SFIL<x>.[BCR] - Displays to callers when selecting a specific file area. <x> would correspond to the file area selected. (DISPLAY) SFIMPEXP.[BCR] - 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.[BCR] - Displays to the caller after WELCOME1.[BCR] and prior to the caller entering their name if system maintenance is being performed. After this file displays, the caller is logged off the BBS. (DISPLAY) SFMSG<x>.[BCR] - Displays to callers when selecting a specific message conference. <x> would correspond to the conference selected. (DISPLAY) SFMQDONE.[BCR] - Displays to a caller attempting to answer a Main questionnaire/order form a second time when it is configured to limit callers to one response. (DISPLAY) SFNOD<x>.[BCR] - Displays to callers after the ALL.[BCR] and prior to the <X>SEC.[BCR]. <x> would correspond to the BBS node number. (DISPLAY) SFNOTIME.[BCR] - Displays to callers who attempt to log on after using their daily allotted time. (DISPLAY) SFNWSLTR.[BCR] - Sysop's newsletter available from the Main Menu. (DISPLAY) SFONFAIL.[BCR] - Displayed to a caller who logs on the BBS and fails to enter the correct password. This could be used to inform the caller that someone with the same name already accesses the BBS and they should attempt to log on using a nickname or their middle initial. (DISPLAY) SFORD<x>.[BCR] - Questionnaire/Order Form Menu displayed to caller with a corresponding <x> security level. (DISPLAY) SFPAGED.[BCR] - Displays if the Sysop has the page on and a caller attempts to page the Sysop again when the Sysop has not answered the first page. (DISPLAY) SFPGOFF.[BCR] - Displays to callers paging the Sysop when the Sysop has the page feature turned off. (DISPLAY) SFPRELOG.BBS - The first file displayed upon log on. (DISPLAY) SFPROMSG.[BCR] - Displays to the caller prior to selecting a default file transfer protocol. Sysops should use this Page 48 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- display file to inform callers that if a default transfer protocol is selected, External Transfer Protocols will not be available to them. (DISPLAY) SFRATIO.[BCR] - Displays to callers after a download if their download/upload ratio exceeds configured settings and a VWR (Violation Warning Ratio) exists for the caller's security level in DAILYLMT.DAT. (DISPLAY) SFREMIND.[BCR] - Displays to callers upon log on if the caller was logged off during the previous session due to inactivity. (DISPLAY) SFSUBCHG.[BCR] - Displays to the caller when the callers subscription has expired. When this file is displayed to the caller, SPITFIRE will change the caller's security to the Expired Security (configured by the Sysop in SPITFIRE's ALT+Z configuration window.) (DISPLAY) SFTIMEUP.[BC ] - Displays to a caller whose log on-time has expired. (DISPLAY) SFUNANS.[BCR] - Displays to a caller when the Sysop has the page turned on and the Sysop does not answer the page. If SFPAGED.[BCR] is found in the display file directory, SPITFIRE will not allow additional pages if the first page remains unanswered. (DISPLAY) SFUP.[BCR] - Displays to callers prior to an upload. (DISPLAY) SOP<x>.[BCR] - Sysop Menu display files created for specific security levels where <x> would correspond to the caller's security level. (DISPLAY) SUBWARN.[BCR] - Displays to warn a caller that his/her subscription is nearing expiration. The Sysop configures the Expiration Warning days from SPITFIRE's ALT+Z configuration window. This screen will begin displaying to the caller this number of days prior to the subscription expiration. (DISPLAY) THOUGHTS.BBS - Contains thoughts created for SPITFIRE with THOUGHTS.EXE. (DISPLAY) TOOMANY.[BCR] - Displays to callers who exceeds the daily limit of calls. (DISPLAY) SYSINIT.[BC ] - Displays to the caller upon entering chat if the Sysop initiated the chat. (DISPLAY) USERINIT.[BC ] - Displays to caller upon entering chat with the Sysop if the caller paged the Sysop and requested the chat. (DISPLAY) WELCOME1.[BCR] - The second file displayed upon log on. (DISPLAY) WELCOME<x>.[BCR]- WELCOME2.BBS/CLR/RIP through WELCOME9.BBS/CLR/RIP are displayed in numerical order after a caller enters their 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 49 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SPITFIRE supports the use of ANSI and RIP Graphics display files. The Sysop must use the ALT+T (Toggle SPITFIRE Switches) window to configure the BBS to support ANSI Graphics and/or to support RIP Graphics. The ANSI files use the file extension .CLR (color) and the RIP files use the file extension of .RIP. Provided the BBS is configured to make RIP Graphics available, when a caller logs onto the BBS, SPITFIRE tests to verify whether the caller is calling with a RIP terminal program. If the caller is using a RIP terminal communications program, the caller is prompted to select one of the following graphic formats: <A>nsi, <R>ip, or <N>one. If RIP Graphics is selected, the display files with an extension of .RIP are displayed to the caller, if found. If the BBS does not make RIP Graphics available but is configured to support ANSI Graphics, or if SPITFIRE determines that the caller is not calling with a RIP terminal program, then the caller is prompted with: "Do You Want ANSI Graphics? <y/N>". If the caller selects ANSI Graphics, display files with an extension of .CLR will be displayed to the caller, if found. If the BBS is not configured to support ANSI or RIP Graphics or if the caller elects not to use color graphics, ASCII display files with an extension of .BBS will be displayed to the caller, if found. Provided the caller is using a RIP terminal program and SPITFIRE is configured to allow RIP Graphics, if SPITFIRE does not find the appropriate .RIP file to display, then the appropriate .CLR file will be displayed. In the event ANSI Graphics are available and SPITFIRE does not find the appropriate .CLR file to display, then SPITFIRE will display the appropriate .BBS file. If the appropriate .RIP, .CLR, or .BBS display files are not found, SPITFIRE will, in most cases, display a default message. IMPORTANT: In the event, ANSI/Graphics are available be sure to load the ANSI driver (DEVICE=ANSI.SYS) from within your CONFIG.SYS. NOTE: When making ANSI graphics available to callers, duplicate all display <filename>.BBS files to ANSI files and call them <filename>.CLR. Similarly, when making RIP graphics available to callers, duplicate all display <filename>.BBS files to RIP files and call them <filename>.RIP. For an attractive BBS, display files should be created for each of the available Graphic formats. Display files which are available within SPITFIRE using only the RIP Graphic format are: MAINCTRL.RIP FILECTRL.RIP MSGCTRL.RIP Page 50 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Display files which use only the ASCII (.BBS) and ANSI (.CLR) graphic format include: SFASLEEP.BBS/CLR SFTIMEUP.BBS/CLR USERINIT.BBS/CLR SYSINIT.BBS/CLR CHATDONE.BBS/CLR NEEDSYS.BBS/CLR The display files listed below are only available within SPITFIRE as ASCII (extension of .BBS) files: THOUGHTS.BBS SFEXTDN.BBS SFEXTUP.BBS SFFILES.BBS SFPRELOG.BBS SF2SLOW.BBS SPITFIRE automatically displays SFFILES.BBS in color if the caller selected ANSI or RIP color graphics when logging on the BBS. In the event a file line is not colored like the others, but rather uses the caller's default color, it is because the comma in the file size is either not located properly or does not exist. SPITFIRE utilizes the comma in the file size to determine the coloring of the SFFILES.BBS listings. SPITFIRE's display files may be created using special control codes. These special control codes allow specific information to be displayed within the display file or will perform a specific task when encountered within a display file. The control codes are valid for each of the graphic formats (.BBS, .CLR, and .RIP). For additional information on the display file control codes, refer to section, ABOUT SPITFIRE DISPLAY FILES of this manual. 5.5 - SPITFIRE MENU FILES ------------------------- Menu files contain all the information needed for SPITFIRE to dynamically build each caller's menus, dependent on the caller's security level. SPITFIRE displays a feature only if a caller's security level is high enough to access it. Therefore, callers do not necessarily see every possible choice in a given menu. This places the Sysop in control and allows the BBS to be tailored to meet their individual needs. The format used for the SFMAIN.MNU, SFSYSOP.MNU, SFMSG.MNU and SFFILE.MNU is: Command Character,Command Description,,Security Level,Command Identifier Knowing this, let's use the following example: B,.... Bulletins,,5,A Page 51 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- The "B" is the Command Character. This is the letter the caller must type to access this particular option. In this instance "B" is used to select Bulletins. ".... Bulletins" is the Command Description and represents how the file entry appears in SPITFIRE's default menu on the screen. "5" is the minimum Security Level required for the caller to access this function or, for that matter, 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 is DIFFERENT for every command. After exploring a bit, you'll find that SPITFIRE allows the Sysop to design menus which suit their personal taste, as well as control what commands are available to what callers. The SFFILE.MNU file that comes with the SPITFIRE package sets the <D>.... Download A File security at 10. While a caller is on-line, hit F2 to change the caller's security to 9 and notice that the Download feature is no longer available for that caller. THERE ARE THREE RULES CONCERNING MENU LINES! 1) You CANNOT change the Command Character Identifier from what it is in the original distribution package menu! 2) You CANNOT assign the same Command Letter to two commands in the same menu! 3) You CANNOT make the total length of the line more than 40 characters long! Therefore, it is possible to change the Bulletins option described above to read: A,<A>.... Announcements,,5,A Just remember: NEVER change the Command Character Identifier (the last character on each entry line), and NEVER use a Command Letter more than once in each menu. SPITFIRE uses the following Menu Files: SFMAIN.MNU - Main Menu (SYSTEM) SFMSG.MNU - Message Menu (SYSTEM) SFFILE.MNU - File Menu (SYSTEM) Page 52 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFSYSOP.MNU - Sysop Menu (SYSTEM) SFDOOR.MNU - Door Menu (SYSTEM) SFORDER.MNU - Questionnaire Menu (SYSTEM) 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 the DOS EDIT program or any text editor that is capable of saving in ASCII format to edit the *.MNU files. Should you edit these menu files and come up with some very nice looking menus, please share the information so other Sysops using SPITFIRE may benefit from your discovery. SPITFIRE uses the following display menu files: MAIN<x>.BBS - Non-ANSI Main Menu (DISPLAY) MAIN<x>.CLR - Color Main Menu (DISPLAY) MAIN<x>.RIP - RIP Graphic Main Menu (DISPLAY) FILE<x>.BBS - Non-ANSI File Menu (DISPLAY) FILE<x>.CLR - Color File Menu (DISPLAY) FILE<x>.RIP - RIP Graphic File Menu (DISPLAY) MSG<x>.BBS - Non-ANSI Message Menu (DISPLAY) MSG<x>.CLR - Color Message Menu (DISPLAY) MSG<x>.RIP - RIP Graphic Message Menu (DISPLAY) SOP<x>.BBS - Non-ANSI Sysop Menu (DISPLAY) SOP<x>.CLR - Color Sysop Menu (DISPLAY) SOP<x>.RIP - RIP Graphic Sysop Menu (DISPLAY) SFDR<x>.BBS - Non-ANSI Doors Menu (DISPLAY) SFDR<x>.CLR - Color Doors Menu (DISPLAY) SFDR<x>.RIP - RIP Graphic Doors Menu (DISPLAY) SFORD<x>.BBS - Non-ANSI Questionnaire Menu (DISPLAY) SFORD<x>.CLR - Color Questionnaire Menu (DISPLAY) SFORD<x>.RIP - RIP Graphic Questionnaire Menu (DISPLAY) SFBATCHU.BBS - Non-ANSI Batch Upload Menu (DISPLAY) SFBATCHU.CLR - Color Batch Upload Menu (DISPLAY) SFBATCHU.RIP - RIP Graphic Batch Upload Menu (DISPLAY) SFBATCHD.BBS - Non-ANSI Batch Download Menu (DISPLAY) SFBATCHD.CLR - Color Batch Download Menu (DISPLAY) SFBATCHD.RIP - RIP Graphic Batch Download Menu (DISPLAY) SFIMPEXP.CLR - Color Local Log-on Import/Export Menu (DISPLAY) SFIMPEXP.BBS - Non-ANSI Local Log-on Import/Export Menu (DISPLAY) SFIMPEXP.RIP - RIP Graphic Local Log-on Import/Export Menu (DISPLAY) Page 53 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Each of the Menu display files listed below are supported in SPITFIRE using the ASCII text (.BBS extension), ANSI graphics (.CLR extension) and/or RIP graphics (.RIP extension). MAIN<x> FILE<x> MSG<x> SFDR<x> SOP<x> SFORD<x> SFBATCHU SFBATCHD SFIMPEXP "x" represents the security level of the current caller. For example, if a caller with a security level of 10 calls using a RIP terminal program and selects RIP graphics, then SPITFIRE searches for files named MAIN10.RIP, MSG10.RIP, FILE10.RIP, SFDR10.RIP, etc. If a caller with a security level of 10 calls and opts to use ANSI Graphics, then SPITFIRE searches for files named MAIN10.CLR, MSG10.CLR, FILE10.CLR, SFDR10.CLR, etc. to display as the color menus. Similarly, if a caller with a security level of 10 calls and chooses not to use RIP graphics or ANSI Graphics, then SPITFIRE searches for files named MAIN10.BBS, MSG10.BBS, FILE10.BBS, SFDR10.BBS, etc. In the event these files are not found, then SPITFIRE displays the default menus. The reason for different RIP, ANSI and Non-ANSI display menu files for each security level is to control what commands are shown to the caller. For example, if the BBS requires a security level of 10 to be able to download a file, then FILE10.RIP, FILE10.CLR and FILE10.BBS must be created to show the <D>... Download A File command while FILE9.RIP, FILE9.CLR and FILE9.BBS would not show the command. Display file menus using RIP, ANSI, or non-Ansi graphics will need to be created for each security level assigned to callers on the BBS if you decide to use SPITFIRE display file menus rather than using SPITFIRE's default menus and you have also configured your BBS to support ANSI and/or RIP graphics. The exception to the security defined Non-ANSI, ANSI, and RIP menus are the menus used for the batch file transfer and the local log on import/export menu. The batch file transfer menus are simply named SFBATCHU and SFBATCHD with the appropriate extension of BBS, CLR, or RIP. The import/export menu which displays when logged on locally is named SFIMPEXP.[BCR]. Buffalo Creek Software provides a utility to create the RIP, ANSI, and non-ANSI menu files. The name of this utility is MKSFMENU. You can download it from Buffalo Creek's BBS at 515-225-8496. Your SPITFIRE distribution package includes sample MAIN10, MSG10 FILE10, SFBATCHU, SFBATCHD, SFIMPEXP, and SOP999 display menu files in each of the available graphic formats (non-ANSI using the .BBS extension, ANSI graphics using the .CLR extension, and RIP graphics using the .RIP extension). Page 54 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 5.6 - SPITFIRE FILE CLARIFICATIONS ---------------------------------- The following files deserve a more in-depth explanation: SFFILES.BBS - Resides in each File Area and lists files available (DL FILE AREA) for download from that area. This file can be created using any text editor as long as it saves in ASCII format. Here are the guidelines required in creating an SFFILES.BBS that will work properly with SPITFIRE. 1--------10--------20--------30--------40--------50--------60--------70 SF36-1.ZIP 325,000 08-20-99 SPITFIRE Bulletin Board System V3.6 The FILENAME must begin at column 1 The FILE SIZE must end at column 21 The FILE DATE must end at column 31 The FILE DESCRIPTION must start at column 34 When the SFFILES.BBS displays to a caller who is using either RIP or ANSI Color Graphics and a file line is not colored like the others, but rather uses the caller's default color, it is because the comma in the file size is either not located properly or does not exist. SPITFIRE uses the comma in the file size to determine whether the line is a file listing or part of the file area header. DAILYLMT.DAT - This file controls, per security level, the amount (SYSTEM) of time a caller has each day, each call, kilobytes allowed to be downloaded per day, files allowed to be downloaded per day, node chats allowed, time allowed per node chat, quick log on access, when and if a caller will be warned of file ratio violation, and when/if the file ratio violation will be enforced. Below is a list of abbreviations used in DAILYLMT.DAT and what each abbreviation represents: MPC - Minutes Per Call MPD - Minutes Per Day QL - Quick Log-on DLPD - Downloads Per Day KB - Kilobytes (allowed to be downloaded per day) #OCA - Number Of Chats Allowed TPNC - Time In Minutes Per Node Chat VWR - Violation Warning Ratio VER - Violation Enforcement Ratio Page 55 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- A line should be created in DAILYLMT.DAT for each security level you allow on your BBS. Each line should begin with the numeric value of the security level whose parameters are being defined. The syntax for each line in the DAILYLMT.DAT is: 10,MPC=45,MPD=60,QL,DLPD=15,KB=2000,#OCA=5,TPNC=5,VWR=15,VER=25 where: 10 represents the security level for which the subsequent parameters apply. MPC=45 represents the maximum time in minutes a caller with this security level is allowed for each call to the BBS. This overrides the Log On Time Limit defined at SPITFIRE's ALT+Z configuration. MPD=60 represents the total daily time limit in minutes a caller of this security level is allowed. This overrides the Daily Time Limit defined at the ALT+Z SPITFIRE configuration screen. QL allows a remote caller with this security level to quickly log on the BBS. This remote quick log on is similar to a local quick log. After the initial log on, a caller with this security is immediately displayed the Main Menu, avoiding the display of WELCOME2.[BCR] to WELCOME9.[BCR], ALL.[BCR], etc. It should be noted, <x>SEC.[BCR] and <x>.[BCR] will display to callers with quick log on capability. To require a normal log on, simply omit the QL from the DAILYLMT.DAT line. DLPD=15 represents the maximum number of files a caller with this security will be allowed to download each day. KB=2000 represents the maximum number of kilobytes a caller with this security level will be allowed to download each day. #OCA=5 sets the maximum Number Of Chats Allowed (node chats) each day on a multi-node system for this security level. The SPITFIRE default is 5. To disable node chats for a particular security level, set this parameter to #OCA=0. The #OCA=<x> is only applicable to multi-node systems. TPNC=5 designates the Time (in minutes) Per Node Chat allowed for this security level. SPITFIRE defaults to 5 minutes per node chat. The TPNC=<x> is only applicable to multi-node systems. VWR=15 represents the Violation Warning Ratio for this security level. When the upload/download ratio exceeds 1 upload for each VWR Page 56 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- value downloaded, SFRATIO.[BCR], if found, is displayed to the caller. Both the number of files AND the kilobytes downloaded must exceed the ratio before SFRATIO.[BCR] is displayed to the caller. If you do not wish to warn the caller, simply do not include the VWR parameter in the DAILYLMT.DAT for this security level. VER=25 represents the Violation Enforcement Ratio for this security level. When the upload/download ratio exceeds 1 upload for each VER value downloaded, SPITFIRE alters the caller's security to what the Sysop has configured at the U/D Ratio Violation Security in the ALT+Z configuration screen. Both the number of files AND the kilobytes downloaded must exceed the ratio before the caller's security is altered. If you do not wish to enforce the ratio violation for this security level, simply do not include the VER parameter in the DAILYLMT.DAT for this security level. **NOTE** A warning should be displayed prior to enforcing the upload/ download ratio which would alter the caller's security level. It is highly recommended that the difference between the violation warning and the violation enforcement should be greater than the amount of files the caller may download in a batch download. Using the word Batch at the end of a line in SFEXTDN.BBS limits downloads per batch to 6, so a difference of at least 6 is recommended. Using the word Usefile, at the end of a line in SFEXTDN.BBS limits downloads per batch to 99, so a difference of 99 is recommended. (Refer to the section - EXTERNAL BATCH DOWNLOAD PROTOCOLS - of this manual for a full explanation.) If the difference between the violation warning and the violation enforcement is not equal to or greater than the amount of files a caller can download in a single batch, it is possible during a batch download for a caller to have their security altered without ever being warned of the impending status change. If SPITFIRE finds the VWR and VER are defined for the security level of the caller, each time a file is downloaded, SPITFIRE performs the following calculations to determine if a caller has violated the upload/download ratio requirement: The number of files downloaded by a caller is divided by the number of files uploaded AND the number of kilobytes downloaded by the caller is divided by the number of kilobytes uploaded by the caller. SPITFIRE must verify that both the file ratio and the kilobyte ratio have been violated. If the results of both the file and kilobyte calculation are greater than the value defined for the VER (Violation Enforcement Ratio), SPITFIRE will then alter the caller's security level to that configured at the U/D Ratio Violation Security. Page 57 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SPITFIRE will return the caller to their original security once the caller's upload/download ratio is again within the required ratio limits. The SFUSERS.DAT file contains a field which stores information regarding the caller's original security level. When a caller uploads a file to the BBS, SPITFIRE first checks to see if the caller's current security level is less than the original security level. If so, SPITFIRE performs the same computations as described above. If the results of the file or kilobyte calculation is less than the VER (Violation Enforcement Ratio), the caller's original security level is restored. Keep in mind, for this to work properly, the VER (Violation Enforcement Ratio) must be configured the same for both security levels, the security that is being monitored and the U/D Ratio Violation Security. Using the sample DAILYLMT.DAT from above, all callers with a security level of 10 are allowed 45 minutes per call, 60 minutes per day, 15 downloads per day with a limit of 2,000 kilobytes per day, 5 node chats of up to 5 minutes per node chat, will be displayed SFRATIO.[BCR], if it exists, when the upload/download ratio of 1 to 15 is exceeded, and will have their security altered when the upload/download ratio of 1 to 25 is exceeded. DAILYLMT.ZIP is included in the SPITFIRE distribution package or can be downloaded from Buffalo Creek's BBS. DAILYLMT.COM is a menu driven program that is used to create and maintain DAILYLMT.DAT. SFRATIO.[BCR] - It's rare when a caller's uploads exceed their (DISPLAY) downloads. Some callers get in the habit of taking and never give much consideration toward uploading. This file is displayed after a download is completed that causes the caller's U/D ratio to violate the warning ratio (VWR) configured in DAILYLMT.DAT (provided the DAILYLMT.DAT for the caller's security level contains a VWR - Violation Warning Ratio). SFRATIO.[BCR] will then be displayed to the caller showing your "friendly" words of advice whenever this situation presents itself. If you are not concerned about a caller's U/D ratio, simply do not include this file in the display file directory. JOKER.DAT - JOKER.DAT contains a list of all names you don't (WORK) want to allow on your board. It may be used to list names like: Dr. Phreak, Micro Muck, Lord Havoc, Killer, etc.. Also, if any line in JOKER.DAT is preceded with an @ followed by text, no one with that portion of the text in any part of their name will be allowed to log on to the BBS. These feature is primarily intended to scrutinize those who Page 58 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- attempt to log on a BBS using profane words. The '@<text>' feature should be used with caution since it would be quite easy to unintentionally deny someone access. JOKER.DAT is an ASCII file that has each name listed on a separate line, such as: Dr. Phreak Micro Muck Lord Havoc @damn All Callers When locking a caller out of a 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 caller to be locked out or marked for deletion using ALT+A at the "Ready..." prompt or from the Sysop Menu. A caller may also be locked out by pressing ALT+L while the caller is logged on the BBS. A caller may be added to JOKER.DAT using any of these features. LOCKOUT.[BCR] - 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.[BCR] is displayed to the caller and the caller is logged off the BBS! LAKOTA.COM - If LAKOTA.COM exists in the SPITFIRE home directory, (SYSTEM) callers may download messages in QWK format, using an offline mail reader to read/reply to messages, and upload reply packets into SPITFIRE's message base. LAKOTA, a SPITFIRE QWK Mail System, is available using Option L of the Message Menu. If you do not wish to have this option available to callers, the security in SFMSG.MNU for this feature should be set high enough so the caller is not able to access it. For more information refer to the documentation that accompanies LAKOTA.COM. FA<x>.TXT - To use SPITFIRE's extended download directory feature, (SYSTEM) create a FA<x>.TXT, where <x> is equal the File Area number, and place it in the SPITFIRE home directory. FA<x>.TXT is a simple text file which can be created using your favorite text editor, as long as it saves in ASCII text. Each line of FA<x>.TXT should contain the drive and directory of any extended download directories for the File Area. For instance, if File Page 59 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Area 5 was configured for Games, the contents of the FA5.TXT in the SPITFIRE Home directory might look like this: F:\GAMES G:\NEWGAMES If SPITFIRE does not find the file to download, read, view, etc. in the configured download directory (the primary download directory) it will then look for the appropriate FA<x>.TXT in the SPITFIRE Home directory. The number of extended download directories that can be configured using FA<x>.TXT is unlimited. However, the SFFILES.BBS in the primary download directory (or the SFFILE.<x> for areas configured as a CD Rom file area) should list all files available for downloading from all download paths, including any of the extended download directories. The FA<x>.TXT, extended download directory feature, provides additional CD Rom support. However, the Sysop should be aware when using this feature that if the File Area is not configured as a CD Rom File Area and the file to be downloaded exists on a CD Rom disc, the file is directly transferred to the caller from the CD Rom drive rather than being copied to the disk drive. Secondly, if the File Area is configured as a CD Rom File Area and the ALT+T's Search CD Rom Area SFFILES.BBS is toggled to Yes, SPITFIRE will search the SFFILES.<x>, rather than the drive. Therefore, the file must be listed in the SFFILES.<x> in order for SPITFIRE to find the file. SFNWSLTR.[BCR] - File which displays to the caller when they request (DISPLAY) the <N>...Newsletter from the Main Menu. SPITFIRE will also notify the caller if this file has been updated since they last logged on the BBS. This file can be used to send special informational messages to callers regarding the system. SFNOUP.DAT - SFNOUP.DAT contains a list of files which the (WORK) Sysop does not wish to have uploaded to the BBS. SFNOUP.DAT will allow complete use of DOS's wildcard feature. Simply create an ASCII file that has each name listed on a separate line, such as: NUCALLER.* WIN*.* PERVERT.COM *.GIF Page 60 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- When erasing a file from the file menu, SPITFIRE prompts you as to whether you wish to have the file added to SFNOUP.DAT. Responding with a Y for Yes, will add the erased file's name to SFNOUP.DAT. NUCALLER.* - SPITFIRE will flag this file for download when a (FILE AREA #1) new caller logs onto the BBS. After completing the new caller questionnaire, the new caller is given the opportunity to download the file named NUCALLER. The Sysop may select the desired extension for NUCALLER, i.e., .TXT, .ZIP, .ARJ, etc. Suggested uses for NUCALLER.* might be to include any rules for participating on the BBS, subscription applications, RIP icons specific to the BBS, etc. NUCALLER.* must be placed in the first file area on the BBS. To disable this feature, simply do not place a NUCALLER.* in File Area #1. Sysops should be aware, however, that if there is more than one NUCALLER.* file (i.e., NUCALLER.TXT and NUCALLER.ZIP) in the first file area, SPITFIRE will send the first NUCALLER.* file it finds. It is therefore recommended that NUCALLER.* be added to SFNOUP.DAT to prevent callers from uploading any NUCALLER.* files and eliminating the possibility of having the wrong NUCALLER.* file sent to new callers. SFFAX.BAT - After SPITFIRE answers the incoming call, it then (SYSTEM) tests the modem result message for the configured FAX Connection Result Message (configured by the Sysop at SPITFIRE's ALT+M configuration window). If the modem result message matches the Fax Connection Result Message, then SPITFIRE shells to a batch file in the SPITFIRE home directory named SFFAX.BAT. The SFFAX.BAT needs to be written so that it contains the commands necessary to execute the Fax software so that the Fax can be properly received. SFILEREQ.LOG - SPITFIRE will allow a caller to make file requests when certain conditions exist. The Sysop can mark a file OFFLINE by replacing the file size in the file description of SFFILES.BBS with the word OFFLINE. The word OFFLINE must start at column 15. For example: 1--------10----5---20--------30--------40--------50--------60--------70 SF36-1.ZIP OFFLINE 08-20-99 SPITFIRE Bulletin Board System V3.6 Page 61 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SPITFIRE also treats a file listed in SFFILES.BBS but which is not located in the download directory as a file request. When a file marked as OFFLINE is tagged for download, or when SPITFIRE is unable to locate a tagged file in the download directory, SPITFIRE treats these as file requests. SPITFIRE records all file requests to the SFILEREQ.LOG file located in the SPITFIRE Work directory. If the SFILEREQ.LOG does not exist, SPITFIRE will create it when a file request is made. If the SFILEREQ.LOG does exist, SPITFIRE will append any new file requests to the existing log. SPITFIRE records the name of the caller requesting the file, the name of the file, the date and time of the file request to SFILEREQ.LOG. SFPCKMSG.COM - SPITFIRE shells to SFPCKMSG.COM for purging (SYSTEM) messages either as Event M or when selected from the SPITFIRE Sysop Menu. Criteria for packing messages is determined according to how the Sysop has configured the Message Conference record. The purge criteria is set independently for each conference available on the BBS. SFPCKUSR.COM - SPITFIRE shells to SFPCKUSR when the Sysop selects (SYSTEM) the Pack User File option from the SPITFIRE Sysop Menu. SFPCKUSR is used to purge callers marked for deletion and/or inactive callers. A caller is considered inactive if they have not called the BBS in <x> amount of days. The Sysop determines the value of <x>. SFPCKUSR may also be set up to run as a scheduled event in SPITFIRE. Refer to the section - EVENT MENU EXPLANATION - for additional information on scheduled events. SFUPCASE.DAT - A list of keywords that are converted to or left (WORK) in upper case when converting file descriptions. This is a simple text file that lists these keywords, one per line. SFREMOTE.BAT - This batch file is used with the remote Drop to (SYSTEM) DOS feature and should be used with a carrier detect utility such as WATCHDOG, RemDoor or Doorway. If connection is terminated while a caller is at the DOS level the system is reset provided such a utility is used. If you have included SF.BAT in the Page 62 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- AUTOEXEC.BAT, SPITFIRE will automatically boot on system start up. Using such a utility is highly recommended, but none are included in the SPITFIRE distribution package since these programs are written by other authors. However, these utilities 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 COM port. SF.BAT - Batch file which invokes SPITFIRE. This file (SYSTEM) contains the necessary data for the scheduled events feature within SPITFIRE to work properly. Refer to section - EVENT MENU EXPLANATION - of this manual for more information on Scheduled Events. It also contains the data necessary to execute programs using the SPITFIRE Door feature. Refer to the section - SPITFIRE DOORS SECTION - of this manual for more information on SPITFIRE Doors. SFMAIN.BAT - Batch file which executes the Sysop configurable (SYSTEM) Main Menu option. SFFILE.BAT - Batch file which executes the Sysop configurable (SYSTEM) File Menu option. SFMESS.BAT - Batch file which executes the Sysop configurable (SYSTEM) Message Menu option. SFSYSOP.BAT - Batch file which executes the Sysop configurable (SYSTEM) Sysop Menu option. SFMSGPCK.BAT - Batch file that executes immediately after packing (WORK) the message base. SFMSGPCK.BAT might be used to create a file archive of the SPITFIRE message base after it is packed. SFMSGPCK.BAT may be used by some net-mail drivers to perform some necessary duties required after packing the message base. SFINIT.BAT - Batch file executes, if it exists, after a caller (SYSTEM) hangs up and prior to the modem being initialized. This allows utilities (such as a last 10 caller listing or checking the integrity of uploaded files) to be executed between callers to the BBS. SFPGOFF.[BCR] - This file displays to the caller in the event (DISPLAY) the caller pages the Sysop and the Sysop has the page feature turned off. Page 63 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFUNANS.[BCR] - This file displayed to the screen in the event a (DISPLAY) caller has paged the Sysop and the Sysop does not answer the page. SFPAGED.[BCR] - This file displays to the caller in the event (DISPLAY) the Sysop has the page turned on and the caller attempts to page the Sysop again when the first page remains unanswered. If this file exists in the display file directory, the Sysop will only receive the first page. Any additional pages will cause SFPAGED.[BCR] to display to the caller. If you wish to receive multiple pages, simply do not include the SFPAGED.[BCR] files in the display file directory. BBSNAME.DAT - Simple one line text file that is placed in the (WORK) Work file directory and contains information about the BBS from which the net-mail message originates. SPITFIRE will tag this on the end of each net-mail message. SFSEC<x>.BAT - This batch file, if it exists, executes after the (SYSTEM) caller logs on the BBS, provided the caller's security is equal to <x> in the batch file name. One example for utilizing this would be if your BBS serves as a hub for net-mail. All callers who use your BBS for mail could be assigned a set security level. Upon logging on the BBS, the SFSEC<x>.BAT could contain commands that would allow the caller to immediately initiate the mail transfer process. BADINIT.BAT - This batch file, if it exists, executes in the (SYSTEM) event the modem fails to respond when initialized between callers. Commands could be placed in the batch file to issue modem commands to reset your modem or to reboot your system with Buffalo Creek Software's KOLDBOOT utility. (KOLDBOOT may be downloaded from Buffalo Creek's BBS.) <x>SEC.[BCR] - This feature allows the Sysop to send a special (DISPLAY) notice to all callers of a certain security level. This file is not automatically erased. (<x> equals the security level of the callers to whom you wish to send the special message.) <x>.[BCR] - This feature allows the Sysop to send a special (DISPLAY) message to a specific caller, where <x> equals the caller's record number. Once the caller has received it, SPITFIRE automatically erases it. Page 64 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Example: John Doe is Caller Record # 95 on your system. If you have a file named "95.BBS", SPITFIRE will display this file when John Doe logs on and then erase it after it has been received. Your callers log will have a notation that the special message was sent. **NOTE** In the event you use <x>.[BCR] to send special messages to callers and you purge callers from the caller data base by packing SFUSERS.DAT, please note that the <x>.[BCR] may no longer match the caller for whom the message was intended. 5.7 - ABOUT SPITFIRE DISPLAY FILES ---------------------------------- SPITFIRE provides complete flexibility when it comes to creating display files. The Sysop can use this flexibility to make their BBS as unique and personalized as he/she desires. In addition, SPITFIRE will recognizes both display file control characters or display file control strings which can be built into the non-ANSI (.BBS), ANSI (.CLR), and/or RIP (.RIP) display files for even more flexibility. The display file control characters and control strings SPITFIRE uses are: Ctrl Ctrl Ctrl Character / Ctrl String Char String Feature Description ---------------------------------------------------------------------- ^B @PROMPTOFF@ Inhibits the display of the "More Prompt". When this is placed in a display file, then the <More?> prompt will not interrupt the display of the file. ^C @NOABORT@ When placed in a display file, it prevents the caller from interrupting and/or aborting the screen display. ^D @FNAME@ Displays caller's first name. ^E @SUBDATE@ Displays the number of subscription days a caller has remaining before his/her subscription will expire, provided the subscription date for the caller is configured. ^F @CITYSTATE@ Displays the caller's city and state/province. ^G @BEEP@ Transmits a beep over the caller's PC speaker. ^J @UPLOADS@ Displays the number of files uploaded by the caller. ^K @DOWNLOADS@ Displays the number of files downloaded by the caller. ^L @CLS@ Clears the display screen for the remote caller. ^N @ABORTON@ Allows caller to interrupt the screen display. This will nullify the affect of a previous ^C or @NOABORT@ in the display screen. Page 65 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- ^O @ORGLOG@ Displays the caller's original log on date. ^P @PROMPT@ Exhibits a "More Prompt" in the display. When SPITFIRE finds a ^P or @PROMPT@, the <More?> prompt is displayed to the screen. It should be mentioned that if a ^P or @PROMPT@ is preceded by a ^B or @PROMPTOFF@ (disables the display of the "More Prompt"), the ^P or @PROMPT will nullify the affect of the ^B or @PROMPTOFF@ control code/string. It should also be noted that when a ^P or @PROMPT@ is used in a .RIP display file, it will only be functional to the remote caller. On the local monitor, the screen will display as if no ^P or @PROMPT@ existed within the display file. ^Q @LOGTIME@ Displays the number of minutes allowed this log on. ^R @PHONENUM@ Displays the caller's phone number. ^S @LASTCALL@ Displays the date of the caller's last call. ^T @PASSWORD@ Displays the caller's password. ^U @BIRTHDATE@ Displays the caller's date of birth. ^V @NAME@ Displays the caller's full name. ^W @UPK@ Displays the number of K uploaded. ^X @DOWNK@ Displays the number of K downloaded. ^Y @SLEVEL@ Displays the caller's security level. Some planning is required when using display control characters or strings. For instance, do not use control characters or strings that write information to the screen (such as ^D, @FNAME@, ^F, @CITYSTATE@, ^J, @UPLOADS@, ^K, @DOWNLOADS@, etc.) inside of a box. The characters inserted will throw the box completely out of line. Below is the list of control characters used in SPITFIRE display files and their extended ASCII value: ^B - extended ASCII value of 002 ^P - extended ASCII value of 016 ^C - extended ASCII value of 003 ^Q - extended ASCII value of 017 ^D - extended ASCII value of 004 ^R - extended ASCII value of 018 ^E - extended ASCII value of 005 ^S - extended ASCII value of 019 ^F - extended ASCII value of 006 ^T - extended ASCII value of 020 ^G - extended ASCII value of 007 ^U - extended ASCII value of 021 ^J - extended ASCII value of 010 ^V - extended ASCII value of 022 ^K - extended ASCII value of 011 ^W - extended ASCII value of 023 ^L - extended ASCII value of 012 ^X - extended ASCII value of 024 ^N - extended ASCII value of 014 ^Y - extended ASCII value of 025 ^O - extended ASCII value of 015 Page 66 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 5.8 - BACKUP FILES ------------------ When performing Sysop maintenance such as modifying Message Conferences or modifying File Areas, SPITFIRE makes "Backup" copies for you. If disk space is a problem on your board copy the backup files to disk or delete them. SPITFIRE backup files include: SFMCONF.$$$ - Message Conferences Backup File SFFAREA.$$$ - File Areas Backup File 5.9 - THOUGHTS.BBS ------------------ SPITFIRE displays a thought to callers if a file named THOUGHTS.BBS is found in the directory configured as your display file path. The program to create THOUGHTS.BBS can be downloaded from Buffalo Creek's BBS at 515-225-8496 or you can optionally download a ready-made THOUGHTS.BBS file. 6.0 - COMMAND LINE PARAMETERS ----------------------------- Command Line Parameters can be used to make SPITFIRE start-up with a different configuration. Command Line Parameters are what you type at the DOS prompt (or send to the program from a batch file) when you boot SPITFIRE. /Cx - Sets which COM port to use (<x> represents the number of the COM port). /E - Used with front end programs for detecting error correction modem connections, making the Ymodem-g file transfer protocols available. This /E must be used in conjunction with baud rate parameter. /M - Sets the initialization string used with your modem. /N - Allows SPITFIRE to be terminated without hanging up the phone or re-initializing the modem. This allows a second copy of SPITFIRE to be run as a door. NOTE: A baud rate parameter must be specified prior to the /N or it has no affect. /P - Sets the drive and directory used as the SPITFIRE Work File Path. /Tx - Used with frontend programs and sets the amount of time allotted to the caller. This allows systems running under a frontend program to pass the amount of time remaining before a frontend scheduled Page 67 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- event. This only applies to the first caller on immediately after SPITFIRE is booted since SPITFIRE will terminate and return control to the frontend program when the caller logs off. This could also be used when running SPITFIRE as a door. (x indicates the amount of time in minutes the caller is allowed.) (baud rate) - This represents the numerical value for the highest possible baud rate of your system. This allows SPITFIRE to be booted without initializing the modem so it can be used in conjunction with some net mail software programs. Refer to the section - SPITFIRE NET-MAIL CAPABILITIES - of this manual for further information. The range of allowable baud rates for SPITFIRE are 0 (allows local log on only) to 115200. The use of these Command Line Parameters is not usually necessary. An exception might be when you are originally booting SPITFIRE for the very first time or if your configuration has changed. When originally booting SPITFIRE you should only use Command Line Parameters if you are using a COM port other than COM 1. In other words, SPITFIRE is written to default to COM port 1 so you will not have to use Command Line Parameters unless these defaults are different from what you plan to use while running SPITFIRE. SPITFIRE /C2 The above example would boot SPITFIRE utilizing COM port #2. It should also be mentioned that any Command Line Parameters assigned from the DOS prompt or included in the SF.BAT file will override those set by using ALT+M or ALT+P at the SPITFIRE "Ready Prompt". Anytime a change is made in the COM port assignment, work path, or modem initialization string, you MUST also change the specifications set in the SF.BAT file. It is for this reason that the use of command line parameters in SF.BAT is not recommended. 6.1 - SF.BAT ------------ It is advisable to use the SF.BAT to boot SPITFIRE. Some of the advantages for using a batch file to invoke SPITFIRE are listed below: If an error occurs, and you're using the SF.BAT included with your SPITFIRE package, SPITFIRE will automatically reset with the SF.BAT file. The SF.BAT file, included with your SPITFIRE package, is vital for running Scheduled Events and Door programs. More Page 68 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- information regarding Scheduled Events and Door programs may be found in other sections of this manual. If you have the AUTOEXEC.BAT file written to automatically boot SPITFIRE upon system startup and there is a power outage, then SPITFIRE will automatically reboot when power is restored. To configure the AUTOEXEC.BAT file to automatically boot SPITFIRE upon system startup, the last two commands in the AUTOEXEC.BAT file should resemble this: CD\SF SF The above example assumes you are running SPITFIRE on the drive you are booting from, you are running SPITFIRE in a directory named SF and you are using the SF.BAT file to invoke SPITFIRE. 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 Questionnaire which uses: SFNEWU.QUE - The new caller questionnaire file. SFNEWU.REP - The new caller reply file. SFNEWU.QUE is automatically utilized ONLY when a new caller logs on. There is also, the ORDER Questionnaire which uses: SFORDER<x>.QUE - The order/questionnaire files. SFORDER<x>.REP - The order/questionnaire replies. SFORDER<x>.QUE is utilized only from the MAIN MENU when the caller selects the <Q>.. Questionnaire Menu option. SPITFIRE will allow up to 24 different questionnaire files to be accessed from the Main Menu. The files which contain the questions are SFORDER<x>.QUE. The replies are stored in the corresponding SFORDER<x>.REP. <x> represents an alpha character ranging from A to Z (with the exception of G and Q which are reserved by SPITFIRE for Goodbye and Quit). For example: Page 69 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SFORDERA.QUE SFORDERA.REP SFORDERB.QUE SFORDERB.REP SFORDERC.QUE SFORDERC.REP The caller's answers are appended to the end of the appropriate reply file. If the file does not already exist, SPITFIRE will create it. SPITFIRE uses a very basic process for utilizing Questionnaires on the BBS. 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 caller unless it begins with a special character. SPITFIRE uses established first characters (one code per questionnaire line) to determine the type of response required by the caller. These are: : - If the first character in the line is a colon, SPITFIRE pauses for the caller's input. The caller must respond to the question before SPITFIRE will continue with the questionnaire. ; - If the first character in the line is a semicolon, SPITFIRE will pause for the callers input. But unlike the colon, the caller is not required to respond to the question. The caller can simply hit the Enter key and SPITFIRE will continue with the questionnaire. @ - If the first character in the line is an "at" sign, SPITFIRE will pause for the caller to input a date in the format of MM-DD-YY. SPITFIRE will automatically insert the hyphens when the caller responds. Once the caller has entered the response, SPITFIRE will redisplay it to the caller and ask whether the information is correct. # - If the first character in the line is the pound sign, SPITFIRE will pause for the caller to input a phone number. The format will depend on how the Sysop has the system configured. If the Sysop has used the ALT+T to configure the phone number to US format, then SPITFIRE will require the following format: ###-###-####. Again, SPITFIRE will automatically insert the hyphens when the caller responds. If the Sysop does not have the system configured to US format, SPITFIRE will accept any input up to 12 characters in length. Once the caller has entered the response, SPITFIRE will redisplay it to the caller and ask whether the information is correct. $<x>$ - If the first and last character of a questionnaire line is a dollar sign and the <x> character between the dollar signs is a value ranging from 1 to 32767, then SPITFIRE will set the Page 70 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- caller's subscription date to the number of days which is represented by the value between the dollar signs. For instance, if you wished to grant a 30 days subscription then the line, $30$ would need to be included within the questionnaire. At the time the subscription date is updated, SPITFIRE will record the change to the CALLERS.LOG. No other text should appear on this line. ^# - If a line begins with a caret sign followed by a number, SPITFIRE will adjust the caller's security level equal to the number following the caret sign provided the number is less than the configured Sysop security. If the number used here is equal to or greater than configured Sysop security level, the caller's security level will not be changed. The number should be a valid security level available on your system. SPITFIRE writes a note in HEYSYSOP.LOG to advise you that the callers security level was changed. No other text should appear on this line. ~ - If the first character in a questionnaire line begins with a tilde character, the caller will be disconnected from the BBS. This could be used by Sysops in the SFNEWU.QUE so callers could be verified before they are allowed access to the BBS. No other text should appear on this line. &<#> - 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. No other text should appear on this line. ? - If the first character in the line is a question mark, SPITFIRE will prompt the line and automatically add a "[y/n]?". SPITFIRE will then only accept a Y or N response from the caller. This Yes/No question is used to branch to other special questions depending on the caller's response. For instance, when SPITFIRE receives a Y response to a question beginning with a question mark, it will continue on through the questionnaire until a plus sign, "+", is found. The text or additional questions you would like to present to the caller who has responded with a Y should start immediately after the plus sign. This Y series of lines is ended with a second plus sign, "+". When the second plus sign "+" is encountered, SPITFIRE will continue on with the questionnaire normally. Similarly, when SPITFIRE receives a N response to a question beginning with a question mark, it will continue on through the questionnaire until a minus sign, "-", is found. Any text or additional questions you would like to present to the caller who responded with a N should be contained between two minus signs, "-". When the second minus sign "-" is encountered, SPITFIRE will continue on with the questionnaire normally. It should be mentioned that any text or questions between where the caller responds with a Y and the first plus Page 71 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- sign will be ignored, just as any text or questions between where the caller responds with an N and the first minus sign will be ignored. Each line that starts with a question mark must be followed by a set of plus signs and a set of minus signs. For example: ?Are you the Sysop of a SPITFIRE Bulletin Board + You have made a wise choice! + - You really should consider running SPITFIRE! - If none of the above described characters are found at the beginning of the line, the line is simply displayed to the caller. The caller's answers are either written to SFNEWU.REP or to SFORDER<x>.REP, depending upon which questionnaire the caller is responding to. In addition to the caller's answers, the caller's name, date and time of the response is recorded within the reply file. In the new caller questionnaire reply file, SPITFIRE will also note which node the caller was logged on to when the questionnaire was answered. The SFNEWU.QUE is displayed to the caller upon log on. The SFORDER<x>.QUE displays to the caller if the Questionnaire Menu is selected from the Main Menu. The Questionnaire Menu file name is SFORDER.MNU. The SFORDER.MNU file can be created using your favorite text editor and following the format: <Title of the Questionnaire>,SEC>=x,ONETIME,PRINT 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. The Questionnaire Topic is followed by a comma. Next the security required to access the questionnaire is defined with SEC<=x or SEC>=x or SEC=x. x represents a numerical value that should coincide within the framework of security levels which apply to the BBS. For example, let's assume x = 10. SEC<=10 would allow callers with a security less than or equal to 10 to access the questionnaire. SEC>=10 would allow callers with a security greater than or equal to 10 to access the questionnaire. SEC=10 would only allow callers with a security of 10 to access the questionnaire. (Any caller with Sysop security may access a questionnaire regardless of how SEC is defined.) Page 72 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- The ONETIME variable will only allow the caller to answer the questionnaire one time. If ONETIME does not appear, the questionnaire can be answered multiple times. PRINT will send the caller's questionnaire responses to the printer. If PRINT is used, the caller's responses are sent to the printer as well as being saved to the appropriate SFORDER<x>.REP file. However, 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. If PRINT is not included on the line, no attempt is made to send the questionnaire answers to the printer. When sending replies to the printer, SPITFIRE notes which questionnaire the reply is in response to. If the ONETIME and/or PRINT options are used, be sure to include a comma to separate them from the previous parameter. Optional RIP, ANSI and Non-ANSI display menu files may be created using the SFORD[x].[BCR] file name. The [x] will correspond to the security level of the caller. As with other RIP, ANSI and Non-ANSI display menu files, a file should be created for each security level assigned to callers on your BBS system. 8.0 - SPECIAL FUNCTION KEYS --------------------------- SPITFIRE uses the ALT key in combination with various letter keys 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 section lists the special function keys used with SPITFIRE, explains from where within SPITFIRE these commands can be activated and the functions they perform. 8.1 - AVAILABLE SPECIAL FUNCTION KEYS ------------------------------------- The special function keys available in SPITFIRE and a brief description of their usage include: F1 - Review Log Files F2 - Change Security Level F3 - Toggle Sysop Page/Bell F4 - Toggle Printer F5 - Check Today's Statistics F6 - Take Five Minutes From Caller Page 73 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- F7 - Give Five Minutes To Caller F8 - Toggle Full/Divided Screen F9 - Capture Chat To Disk F10 - Quit SPITFIRE ALT+F1 - Log Caller Off With Message ALT+F2 - Log Caller Off Without Message ALT+F3 - Remove Backup/Log Files ALT+A - Maintains Callers Database ALT+C - Enter/Exit Chat Mode ALT+D - Jump to DOS - Off Hook ALT+E - Configure Events ALT+F - Configure File Areas ALT+J - Jump to DOS - On Hook ALT+L - Lock Caller Out ALT+M - Configure Modem ALT+P - Configure Paths ALT+Q - Quick Local Log On ALT+R - Configure Msg 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 within SPITFIRE each particular function key can be utilized. Listed below is a guide that explains what these letters represent: <O> - Caller must be ON-LINE to perform. <R> - SPITFIRE must be at the "Ready for Use" prompt to perform. - Can be used BOTH when a caller's on-line or from the SPITFIRE "Ready..." prompt. <R> F1 (View Log File Menu) ---------------------------- This option sets the modem off hook and presents you with the following menu: >> View Log File Menu << <C>..........CALLERS.LOG <H>.........HEYSYSOP.LOG <N>...........SFNEWU.REP <O>.......SFORDER<x>.REP <R>.........SFILEREQ.LOG <S>.........SFPURGED.USR <Q>.................QUIT Page 74 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- which allows you to view SPITFIRE's log files from the "Ready..." prompt without having to log onto the BBS to access this feature from the Sysop Menu. Appropriate to your selection, you are able to review the caller's activity log, Sysop notification log, replies to the new user questionnaire, responses to the Main Menu questionnaire/order files, file request logs or the purged caller listing. If <O> is selected for viewing the questionnaire/order file replies, you are prompted to enter the letter corresponding to which SFORDER<x>.REP file you wish to have displayed. Upon selecting the desired log, you are then presented with the following options for reading the log file: <T>..Today's Date displays the selected log file starting with the first entry for the current day. ..Beginning Of File displays the selected log file from the beginning of the file, starting with the first entry. <S>..Specify Date will prompt for a date to be entered and begins displaying the selected log file with the first entry of the date entered. If the date specified here cannot 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 caller is ONLINE and you wish to change the caller's security level, you can change it by pressing F2. The caller is unable to see that you are changing the security level. F3 (Toggle Sysop Page) ---------------------------- By toggling this parameter <ON or OFF> the Sysop can designate whether or not to be paged. If the PAGE is ON, the words "PAGE ON" will appear on the top of your screen, provided you are using the split screen. If the page is turned on and a caller selects for page, then the prompt bell will sound to notify you that a caller wishes to chat with you. USERINIT.[BC ], if found, will be displayed to the screen when you respond to the page. If the PAGE is turned off and a caller pages you, then SFPAGED.[BCR], if Page 75 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- found, will be displayed to the caller and CHAT REQUESTED will display if you are using the divided screen. After SFPAGED.[BCR] is displayed, the caller will be prompted as to whether they 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 themselves. 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 is toggled on. This is useful if you wish to retain a hard copy of your callers' activities while on-line. Keep in mind that your printer must be turned on and ready for use. SPITFIRE checks to determine if your printer is properly connected and ready for use and responds accordingly. <R> F5 (Check Today's Statistics) ----------------------------------- While at the "SPITFIRE ready for use prompt...", if you press F5, SPITFIRE will set the modem off hook and display the total number of calls to the BBS, the number of calls for the day, number of uploads and downloads for today, daily door usage for today, the number of new callers which logged onto the BBS today and the number of messages entered today. <O> F6 (Take Five Minutes from a Caller) ---------------------------------------- When a caller is on-line, you can take 5 minutes from the caller's log on-time by pressing F6. If you press F6 in multiples, then multiples of 5 minutes are taken from the caller's time. <O> F7 (Give Five Minutes to a Caller) -------------------------------------- When a caller is on-line, you can give 5 minutes to the caller's log on-time. If you press F7 in multiples, then multiples of 5 minutes are added to the caller's time. F8 (Toggle Screen) ------------------------ This feature is used to toggle the split-screen/full-screen option. If a caller is on-line and the split-screen is toggled on, SPITFIRE defaults to display the following information for the current caller: Page 76 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Name: John Doe #117 Security: 10 Time On : 12 From: Peoria, IL Times On: 5 Time Left: 48 Last On: 08-20 07:29 BPS: 19200 Uploads: 4 Downloads: 148 [PAGE OFF]=[HOME FOR HELP]=[RIP Used]=[01-21-54]=[555-151-5555] At a glance, the Sysop can readily view pertinent information regarding the current caller. The Sysop can also press the HOME key while a caller is online and a summary of the available function key features will be displayed on the split-screen. <O> F9 (Capture Chat To Disk/Printer) --------------------------------------- Either when responding to a caller who has paged you or when initiating a chat, pressing F9 will capture the conversation and save it to a file called SFCHAT.CAP in the main SPITFIRE directory. In the event SPITFIRE finds a printer attached and ready, the Sysop is given the option of sending the capture to the printer. There are two ways to activate the chat capture. You can begin the chat using F9 (rather than ALT+C). This will begin the chat and immediately save the chat to SFCHAT.CAP. Or the F9 can be pressed any time during a chat, at which time it will save the remaining chat to the SFCHAT.CAP file. If SFCHAT.CAP does not exist, it will be created. If it does exist, the chat will be appended to the existing SFCHAT.CAP file. Chats will be differentiated in the SFCHAT.CAP file by beginning with "Chat started with (caller name) at (date/time)" and ending with "Chat ended at (date/time)". <R> F10 (Terminate SPITFIRE) ----------------------------- Pressing F10 will terminate SPITFIRE and return you to DOS. <O> ALT+F1 (Log Caller Off With Message) ------------------------------------------ Displays NEEDSYS.[BC ] and logs caller off. If a caller is online and you need to access your system, pressing ALT+F1 displays your message using the NEEDSYS.[BC ] screen and terminates the connection. <O> ALT+F2 (Log Caller Off Without Message) --------------------------------------------- If a caller is online and you wish to disconnect this caller, simply press the ALT+F2 keys simultaneously and the connection will be terminated. No message will be displayed to the caller when using this method to severe the connection, <R> ALT+F3 (Remove Backup/Log Files) ------------------------------------- When selected, this option sets the modem off hook and displays the following menu: Page 77 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- >>> FILE REMOVAL MENU <<< <C>.... Erase CALLERS.LOG <H>... Erase HEYSYSOP.LOG <R>... Erase SFILEREQ.LOG <S>... Erase SFPURGED.USR .... Erase SFUSERS.$?? <Q>................. Quit FILE REMOVAL MENU - [C H S 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 causes the existing HEYSYSOP.LOG file to be erased. SPITFIRE will automatically create a new HEYSYSOP.LOG file. <R>... Erase SFILEREQ.LOG Selecting this option causes the existing SFILEREQ.LOG, SPITFIRE's file request log, to be erased. SPITFIRE will automatically create a new SFILEREQ.LOG when the next file request is made. <S>... Erase SFPURGED.USR If this option is selected, SFPURGED.USR will be erased. SPITFIRE will automatically create a new SFPURGED.USR file the next time the SFUSERS.DAT file is packed. ... Erase SFUSERS.$?? When this option is selected, the SPITFIRE caller's backup files are erased. <R> ALT+A (Maintain Callers File) ----------------------------------- At the "Ready..." prompt, when selecting ALT+A, SPITFIRE sets the modem off hook and allows maintenance to be performed on the caller's file, rather than logging on and maintaining the caller's file from the Sysop Menu. When this option is selected, the following screen will be displayed: Page 78 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Name...... : John Doe Subscription.. : N/A Address... : Peoria, IL Last File Area : 1 Password.. : **** Msg Conference : 1 Phone No.. : 555-151-5555 Security Level : 10 Birth date : 01-20-54 K Uploaded.... : 27 Time Left. : 25 K Downloaded.. : 122 Last Call. : 08-20-93 08:08 Expert Mode... : Off Times On.. : 3 More Prompt... : Off Uploads... : 1 Downloads..... : 3 Msgs Left. : 2 Original Log.. : 07-15-91 Purge Allowed. : Yes >>>> RECORD [117 Of 233] SPITFIRE CALLER RECORD MENU <<<< (+) Next Record (-) Previous Record (D) Downloads (N) Caller Name (X) Expert (U) Uploads (A) Caller Address (&) Delete Caller (M) Change Msg Data (P) Caller Password (L) Lock Caller Out (C) Last File Area (#) Caller Phone No (T) Times On (!) Time Left (R) Record Number (E) Enter Subscription Date ($) More Prompt (F) Find Caller (S) Security Level (B) Birth Date (O) Original Log Date (@) Add New Caller (Z) Purge Allowed ENTER COMMAND [+ - D N X U A & E P L C # T ! R M $ F S B O @ Z <Q>uit ]? Notice that when this option is selected, SPITFIRE displays the last caller record. Usually the first record in the caller's list is the Sysop's. Therefore, if the Sysop were to do any maintenance on the caller's file while others are nearby, displaying the last caller's record prevents information from the Sysop's record from being readily visible. This is done to ensure the security of the BBS. (When accessed online from the Sysop Menu, SPITFIRE displays the record for the current caller.) Although, most of the command line options are self explanatory, a description of each feature is discussed more fully below: Command <+> - Next Record This option is used to move forward from one caller record to another. Pressing the "+" key will allow you to progress from one record to the next in numerical order. When reaching the last record and the "+" key is pressed you will cycle to the first caller record. Command <-> - Previous Record This option allows you to cycle through the caller records in reverse order. Pressing the "-" key will move you to the preceding record number. From the first caller record if the "-" key is pressed you will cycle to the last caller record. Page 79 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <D> - Downloads Upon choosing this option, the following menu appears: <N>umber Of Files, ytes, <Q>uit? <N>umber Of Files allows you to update the statistics regarding the number of downloads the caller has made on the BBS. This must be a numeric value ranging from 0-9999. ytes allows you to update the statistics regarding the total kilobytes the caller has downloaded from the BBS. This must be a numeric value ranging from 0-9999. <Q>uit returns you to the SPITFIRE Record User Menu. Command <N> - Caller Name This option allows editing of the caller's name. Select "N" and you are prompted to enter the first and last name of the caller. When prompted for the first name, you can also enter the first name, space and enter the last name. The information is automatically updated. SPITFIRE will allow up to 30 character spaces for the caller's first and last name to be entered. Command <X> - Expert By selecting this command line option you will toggle the Expert status of the caller on and off. If the Expert status is off, the caller will receive a full menu display. If the Expert status is on, only the command line options will be displayed to the caller. Command - Uploads Upon choosing this option, the following menu appears: <N>umber Of Files, ytes, <Q>uit? <N>umber Of Files allows you to update the statistics regarding the number of uploads the caller is credited with having made to the BBS. This must be a numeric value ranging from 0-9999. ytes allows updating caller statistics regarding the total kilobytes the caller is credited with having uploaded to the BBS. This must be a numeric value ranging from 0-9999. <Q>uit returns you to the SPITFIRE Record User Menu. Page 80 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <A> - Caller Address This option provides the opportunity for editing the caller's address. When <A> is selected, you are prompted to enter the city and state/province for the current caller record. SPITFIRE allows up to 30 character spaces for this information. Once the corrections are made, you will be prompted to verify whether the new information is correct. Command <&> - Delete Caller When you press the "&" key you toggle whether or not a caller is marked for deletion from the SFUSERS.DAT file. If a caller is marked to be deleted, the next time the SFUSERS.DAT file is packed the caller will be purged from the caller data base file. You will notice that when a caller is marked for deletion a "Caller Marked For Deletion!" message will appear on the menu screen. Also, when marking a caller for deletion, you are prompted as to whether the caller's name should be added to the JOKER.DAT file. Command <M> - Change Msg Data Upon choosing this option, the following menu appears: <N>umber Of Msgs, <C>onference, <Q>uit? <N>umber of Msgs allows you to modify the number of messages entered by the caller. This must be a numeric value ranging from 0-9999. <C>onference allows you to change the caller's last message conference number. <Q>uit returns you to the SPITFIRE User Record Menu. Command - Caller Password Provides an opportunity to view or change the caller's password. When selected, you will be prompted with: <V>iew, <C>hange, <Q>uit. If V is selected, the caller's password is displayed. If C is selected, a new password can be entered for the caller. 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. If <Q> is selected, the screen with the caller information is again displayed. Command <L> - Lock Caller Out Toggles whether a caller is locked out from the BBS. Any caller who is locked out will be denied access to the BBS Page 81 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- when he/she attempts to log on. Notice that when a caller is locked out, the words "Locked Out!" are displayed on the menu. When locking out a caller, SPITFIRE provides the option of adding the caller's name to JOKER.DAT. Command <C> - Last File Area This option will allow you to change the caller's last file area number. SPITFIRE allows up to 65535 file areas and you can enter any number from 1 to the number of the last available file area. Command <#> - Caller Phone No Provides the opportunity for editing the caller's phone number. Upon selecting this option, you are prompted to enter the new number. A sample format is also displayed. The format displayed will depend on how you have configured the US Phone format option from the ALT+T configuration window. If the US format is toggled to Yes, the format will be ###-###-#### and the dashes will automatically be inserted when entering the new number. If the US Phone format option is toggled to No, the format will be [ ] and any 12 character input will be accepted. Regardless, of the format, after the new phone number is entered, you will be asked to verify whether the information is correct. Command <T> - Times On This option will allow you to change or edit the number of times the caller has logged on the BBS. This number may range from -999 to 9999. Normally you will only use the range from 1 to 9999 but Sysops or co-Sysops who do not wish to have their names included in top caller bulletins may wish to use negative numbers here. Command <!> - Time Left This option will allow you to enter the daily time remaining in minutes. This number may range from -999 to 9999 minutes remaining. Command <R> - Record Number This option will allow you to enter a specific caller record number. Upon entering the number, all current information for the record number you specified will be displayed. Command <E> - Enter Subscription Date This option allows the Subscription Date to be edited. This option is included for Sysops who require callers Page 82 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- to subscribe in order to gain access to their system. SPITFIRE's default setting is "N/A". If a Sysop wishes to use this option, the subscription date will need to be set. In the event, the Sysop decides to change the Subscription Date back to "N/A", this can be done by entering 01-01-80 as the Subscription Date. The Subscription Date may be automatically maintained using a SPITFIRE Questionnaire. If the first and last character in a Questionnaire line is a dollar sign ($) and a value ranging from 1 to 32767 is placed between the dollar signs, then the numerical value between the dollar signs is used to set the callers subscription date. When SPITFIRE encounters such a questionnaire line, the callers subscription date is adjusted by the number of days which is represented by the value between the dollar signs. At the time the subscription date is updated, SPITFIRE will record the change to the CALLERS.LOG. The Subscription Date is used in conjunction with the configured ALT+Z's Expiration Warning to determine when SUBWARN.[BCR] is displayed to the caller, notifying the caller their subscription is nearing expiration. The Subscription Date is also used along with the configured ALT+Z's Expired Security to determine when SFSUBCHG.[BCR] is displayed to the caller, notifying the caller their subscription has expired and altering the caller's security level to the configured Expired Security level. SPITFIRE will record the subscription expiration warning and a subscription security change in the CALLERS.LOG. Command <$> - More Prompt Selecting the "$" More Prompt option from the command line will toggle the More Prompt On and Off. If the More Prompt is toggled On, each time a complete screen display is received the "More, Continue" prompt is sent and the display is paused until a keystroke is entered signaling the display to continue. The number of lines of text which are displayed between the "More, Continue" prompt is determined by the caller's screen display setting set from <Y>our Statistics of SPITFIRE's Main Menu. For instance, if the screen display is set at 80X23, after every 23 lines the "More, Continue" prompt will be displayed. If the More Prompt is toggled Off, the "More, Continue" prompt will not display and information will continue to scroll without being paused. Page 83 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Command <F> - Find Caller When this option is chosen you are prompted to input the full or partial name of the caller you are attempting to find. SPITFIRE will search for any string matching what is entered. When a match is found, SPITFIRE will report the find and prompt you as to whether this is the caller you were searching for. If you respond with a Y for Yes, SPITFIRE will display that caller's record information. If you respond with an N for No, SPITFIRE will continue to search the caller data base, informing you of any match found, prompting whether the match is the caller you are searching for. In the event, no match is found, SPITFIRE will inform you no match could be found. ***NOTE*** When inputting your search criteria you will notice that SPITFIRE is not case sensitive. Command <S> - Security Level Provides an opportunity to edit the security level of the current caller record. You will be prompted to enter the caller's new security level when this option is selected. SPITFIRE allows up to a four digit figure for the new security level and will only accept numeric values. Command - Birth Date Provides the opportunity to edit the caller's birth date. When selected, you are prompted to enter the new birth date. The format for entering the correction is the numerical representation for MM-DD-YY. SPITFIRE will automatically insert the dash between the month, the day and the year. Once the corrections have been made, SPITFIRE will prompt you by displaying the new birth date entered and ask you to verify if the changes are correct. Command <O> - Original Log Date Provides the opportunity to change or edit the date the caller logged onto the BBS for the first time (original date). When selected, you are prompted to enter the new date of the original log on. The format for entering the correction is the numerical representation for MM-DD-YY. SPITFIRE will automatically insert the hyphens between the month, the day and the year. Once the corrections have been made, SPITFIRE will prompt you by displaying the new date entered and ask you to verify that these changes are correct. Command <@> - Add New Caller This option provides you the opportunity to add a new caller to the SFUSERS.DAT. Adding a new caller locally, Page 84 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- eliminates the necessity of the new caller responding to the new caller questionnaire when calling the BBS for the first time. You will be prompted to provide certain information about the caller before the new caller record will be added. You will need to answer prompts regarding the caller's name, address, password, birthdate (if required on your BBS) and phone number. Once this information is entered, you will be prompted for the security level you wish to assign to the new caller. The security level you assign will determine what features of the BBS the new caller will have access to. Command <Z> - Purge Allowed This option allows you to toggle whether purging the caller will be Allowed or Not Allowed. Normally, you will want this toggled to Yes. If set to allow the purge and the caller has not logged on the BBS for the number of days configured by the Sysop, when packing the callers file, the caller will be deleted. However, if toggled to not allow the purge, the caller will not be deleted from the caller's data base file during packing regardless of how many days it has been since the caller last logged on. SPITFIRE defaults to Yes. <O> ALT+C (Enter/Exit Chat Mode) ---------------------------------- This feature is for entering and exiting chat with a caller. You can use this feature to answer a page or force a caller into chat. When you answer a page, the caller's time on-line continues to be reduced. However, when you force a caller into chat, the caller's time on-line counter is halted until the chat is finished and the caller is returned to the system. <R> ALT+D (Jump to DOS - Off Hook) ------------------------------------ This feature allows you to jump to DOS at the "Ready..." prompt and places the modem offhook so callers attempting to phone the BBS will get a busy signal. When you wish to go back to SPITFIRE, type EXIT. If you are not in the proper directory when you EXIT, SPITFIRE will automatically take you back to the directory in which SPITFIRE resides. <R> ALT+E (Configure Events) ------------------------------ This feature causes the Events Menu to be displayed. The Events Menu is used to cycle through the active events in a forward or backward direction, list events, enable an event or disable an Page 85 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 - On Hook) ----------------------------------- This feature allows you to jump to DOS when a caller is on-line and also when you are at the "Ready..." prompt. When you wish to go back to SPITFIRE, type EXIT. If you are not in the proper 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 Out Of BBS) ----------------------------------- ALT+L can be utilized to lock a caller out of your BBS while they are on-line. Once the ALT+L is pressed to lock the caller out, the Sysop is prompted as to whether the caller should be locked out. If the Sysop responds with a "Y" for Yes, the Sysop is then asked if the caller should be logged off. If ALT+L is pressed a second time, SPITFIRE displays a message informing you the caller is locked out and prompts you as to whether you wish to reverse the lockout. In other words, the ALT+L is used to toggle whether a caller is to be locked out from the BBS. <R> ALT+M (Configure Modem) ----------------------------- This feature sets the modem off hook and opens a window which allows you to configure the modem initialization string, COM port, baud rate, etc. (Refer to the section - SPITFIRE ASYNC CONFIGURATION - of this manual for detailed information.) In the event your modem requires an initialization string different than those listed in this manual, please forward the information to Buffalo Creek's BBS (515-225-8496), so that the information can be passed on to other Sysops. <R> ALT+P (Configure File Paths) --------------------------------- Pressing the ALT+P at the "SPITFIRE ready for use..." prompt sets the modem off hook and opens a window which allows you to Page 86 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- configure the File Paths. (For more information on this, refer to the section - CONFIGURING SPITFIRE FILE PATHS and the section - SPITFIRE FILE PATHS of this manual.) ALT+Q (Sysop Quick Log-On/Sysop Next) ------------------------------------------- This feature is used to log on SPITFIRE locally. It can be used at the "Ready..." prompt or while a caller is on-line. Logging on 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. If you use this feature while a caller is on-line, then when the caller logs off, SPITFIRE will sound an audible signal notifying you that the BBS is now available. You will then be able to log on immediately. <R> ALT+R (Configure Msg Conferences) --------------------------------------- While SPITFIRE is at the "SPITFIRE ready for use.." prompt, you can select ALT+R to configure your Message Conference records. This feature sets the modem off hook and allows you to configure your Message Conferences without having to go through the motions of logging on and using the Sysop Menu to make these changes. Refer to the section - CONFIGURING MESSAGE CONFERENCE RECORDS - of this manual for detailed information. ALT+S (Log On Locally/Sysop Next) -------------------------------------- This feature is used to log on to SPITFIRE locally. It can be used at the "Ready..." prompt or while a caller is on-line. If you use this feature while a caller is on-line, then when the caller logs off, SPITFIRE will sound an audible signal to notify when you the BBS is available. You will then be able to log on immediately. Logging on with ALT+S will display all the initial display files available on the system, such as SFPRELOG.BBS, WELCOME1.[BCR], through WELCOME9.[BCR] and ALL.[BCR]. <R> ALT+T (Toggle SPITFIRE Switches) -------------------------------------- This feature sets the modem off hook and allows you to set the various toggle switches contained within SPITFIRE. (For more information on this, refer to the section - TOGGLE SPITFIRE SWITCHES - of this manual.) <R> ALT+Z (Configure SPITFIRE) -------------------------------- This feature sets the modem off hook and allows you to configure certain aspects of SPITFIRE. (Refer to the section - SPITFIRE CONFIGURATION - of this manual for detailed information.) Page 87 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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, as all other sections of the BBS may be accessed from the Main Menu. However, it is important to note that a caller does not have to return to the Main Menu from the Message Section to go to the File Section (and vice- versa). In the event there is a command on the Main Menu that you do not wish to have functional, simply set the security level for that command high enough so callers cannot access it or see it. As the Main Menu is described and the features explained, please keep in mind that you control which callers can access these features by changing the security level of the commands in the SFMAIN.MNU file. In other words, you control which commands are available to which callers. For instance, if the security level of the .... Bulletins command is set at 25 then a caller with a security level of 24 or less would not see the command or be able to use the command. (Refer to the section - SPITFIRE Menu Files - for further information regarding setting security levels for accessing each menu feature.) 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 our explanation, each menu displayed will be as if the Sysop (with the highest security level and capable of accessing each menu feature) were viewing it, thus looking like this: Page 88 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 9.1 - MAIN MENU EXAMPLE ----------------------- >>>>>>>>> MAIN MENU <<<<<<<<< <M>.......... Message Section <F>.............. File Section <D>............. Door Section ................. Bulletins <C>......... Comment To Sysop <#>....... List Active Callers <L>.......... Locate A Caller *<W>............ Welcome Screen <Q>....... Questionnaire Menu <T>........ This System's Info <N>...... SPITFIRE 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 caller from the MAIN Section of SPITFIRE to the MESSAGE Section. <F>.... File Section This feature takes a caller from the MAIN Section of SPITFIRE to the FILE Section. <D>.... Door Section 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 caller to view the available bulletins. <C>.... Comment to Sysop Allows a caller to enter a non-public message to the Sysop. All comments are automatically saved to Message Conference #1. However, these are marked and listed as Comment Number <x> rather than Message Number <x>. In order for callers to leave a comment to the Sysop, the Sysop must log onto the BBS using the name configured as the Sysop Caller Name in the Page 89 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- ALT+Z configuration window. If the Sysop does not use the name configured there for logging onto the BBS, callers will not be able to leave a comment to the Sysop. <#>.... List Active Callers This feature displays the name and address of each caller of this BBS. It also shows the date each caller last logged on. <L>.... Locate a Caller This feature allows a caller to see if a another person is a caller on this BBS. When a caller selects this feature, the caller is prompted to enter either the full or partial name of the person he/she is attempting to locate. SPITFIRE will search for any string matching what is entered. When a match is found, SPITFIRE will report the find and ask the caller as to whether this is the person he/she is attempting to locate. If the caller responds with a Y for Yes, SPITFIRE will notify the caller when that person last logged onto the BBS. If the caller responds with an N for No, SPITFIRE will continue to search the caller data base, informing the caller of any match found, prompting whether the match is the person they are attempting to locate. In the event no match is found, SPITFIRE will inform the caller no match could be found. <W>.... Welcome Screen (Single Node SPITFIRE BBS) This feature allows a caller to review the opening screen. This feature is only available on single node SPITFIRE BBS systems. On multi-node SPITFIRE systems this option is replaced with <W>........ Who's On/Node Chat. <W>.... Who's On/Node Chat (Multi-node SPITFIRE BBS) This feature will display information regarding what other callers are currently logged on the other available nodes and provide an option for entering into a node chat with a caller on another node. (Refer to the section - NODE CHAT for a more detailed explanation of node chat). This feature is only available on multi-node SPITFIRE BBS systems. On single node SPITFIRE systems this option is replaced with the <W>...Welcome Screen. <Q>.... Questionnaire Menu This feature presents the Questionnaire Menu to your callers. Individual questionnaire/order files (SFORDER<x>.QUE) are used to present questions to your callers. The caller's responses are then stored in the corresponding answer file, SFORDER<x>.REP. (For more information, please refer to the section - SPITFIRE Questionnaires - of this manual.) Page 90 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <T>.... This System's Info This feature displays to the caller certain information about the BBS, such as the Sysop's name, starting date of the BBS, total number of calls received on the BBS, etc. <N>.... SPITFIRE Newsletter This feature displays SFNWSLTR.[BCR] (the BBS newsletter) to the caller. This can be used to keep the callers updated with changes or news concerning your BBS. .... Page the Sysop This feature notifies the Sysop that a caller has a question or problem to chat about. If the Sysop is not available to answer the page, SFUNANS.[BCR] is displayed to the caller. If a caller attempts to page the Sysop a second time, and SFPAGED.[BCR] is found, SFPAGED.[BCR] is displayed to the caller and the Sysop is not paged a second time. If SFPAGED.[BCR] is not found, the caller may page the Sysop multiple times. If the Sysop has the page feature turned off and a caller attempts to page the Sysop, SFPGOFF.[BCR] is displayed to the caller. <G>.... Goodbye & Log Off This feature simply allows a caller to log off the BBS. <X>.... Xpert Mode Toggle This feature changes a caller's status from a novice to an expert or vice versa. If a caller is set as a novice, then the menu descriptions will scroll by after each command. If a caller is set as an expert, then only the command letters scroll by after each command. <Y>.... Your Statistics This feature displays certain statistics for the caller on the BBS and provides a menu which gives the caller the opportunity to change some information pertaining to them. The screen and the information that can be changed are explained below: >>>>>> JUST FOR YOUR INFORMATION <<<<<< Your Name : John Doe Security Level : 10 Last Time On : 12-22-95 13:04 Number Of Times On : 127 Birthdate : 01-20-54 Times On Today : 1 Files Uploaded : 19 Files Downloaded : 53 K Uploaded : 122 K Downloaded : 2631 Original Log On : 05-23-90 Subscription Date : N/A Node Chats Left : 5 Messages Entered : 22 Page 91 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- >>>>>>>> THINGS YOU CAN CHANGE <<<<<<<< <W> Address : Peoria, IL <H> Hot Key : On <#> Phone Number : 555-151-5555 <D> Display Size : 80X24 <S> Scroll Prompt : On <G> Graphics : On <F> File Transfer : 1k-Xmodem <M> More Prompt : On Password : ********** <C> Change Color : 36 CHANGE MENU - [W S # H C G D M P F <Q>uit ] ? Command <W> - Provides the caller with an opportunity to change their address. The caller is prompted to enter both the city and state. SPITFIRE will then redisplay what they have entered to verify the changes before saving the new information. Command <S> - Allows the caller to toggle SPITFIRE's Scroll Back option On and Off. The scroll back feature is used in connection with the display of the "< ENTER >"/"More, Continue" prompts. If the scroll back feature is toggled on, when the prompt is displayed and the caller enters a keystroke to continue, the message will scroll back and disappear from the screen. If the scroll back feature is off, the "< ENTER >" or "More, Continue" prompt remains displayed on the screen. Command <#> - Allows the caller to change their phone number. Command <H> - This feature allows the caller to toggle the Hot Key within SPITFIRE. If toggled On, when entering the command character of a menu, a return is entered automatically and the command is immediately executed. When toggled off, the caller is required to press the <ENTER> key before the command is executed. Command <C> - Allows the caller to select their default color settings. The caller may select 31 through 36. The colors associated with the numeric value are as follows: 31 - Red 32 - Green 33 - Yellow 34 - Blue 35 - Magenta 36 - Cyan 37 - White Command <G> - Allows the caller to toggle the color graphics on or off. When toggled Off, ANSI and RIP graphic modes are turned off and ASCII is used. Display files with the extension of .BBS are displayed to the caller, if found. When toggled On, SPITFIRE loads ANSI graphics and then tests to determine if the caller is using a RIP terminal program. If a RIP terminal program is not detected, ANSI graphics are used and display files with the extension of Page 92 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- .CLR are displayed to the caller, if found. If a RIP terminal program is detected, the caller is then asked to select from the following Graphic options: <N>one, <A>nsi or <R>ip. If RIP is selected, display files with the extension of .RIP will be displayed to the caller, if found. Command <D> - Allows the caller to set the screen display size. When this feature is selected, the caller is prompted to enter a new line length. Acceptable values for the line length range from 40 to 144. Next, the caller is prompted to enter a new page length. Acceptable values for the page length range from 10 to 24. The page length determines when the "More, Continue" prompt will display. For example, if the page length is 24, the prompt will display after every 24 lines. Command <M> - This toggles the More Prompt On and Off. When toggled On, each time a complete screen display is received, either the "< ENTER >" or "More, Continue" prompt is sent and the display is paused until a keystroke is entered signaling the display to continue. If the More Prompt is toggled Off, the "< ENTER >"/"More, Continue" prompt will not display and information will continue to scroll without being paused. Command - For security control a caller's password is not visible and only asterisks will appear. The caller is provided with the following choices when selecting this option: <V>iew - allows the caller to view his/her password. <C>hange - allows the caller to change his/her password. Only asterisks will display and the caller is prompted to enter the password a second time for verification. <Q>uit - returns the caller to the information screen. Command <F> - Allows the caller to select their default file transfer protocol. The caller may select from: <1> Ascii <2> Xmodem Checksum <3> Xmodem CRC <4> 1K-Xmodem <5> Ymodem (Batch) <6> Zmodem (Batch) <T> Telink <S> Select at time of transfer Enter the protocol of your choice - [1 2 3 4 5 6 T S]? Page 93 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Selecting any option other than <S>, Select at time of transfer, causes the external protocol options to be unavailable to the caller. SPITFIRE's display file, SFPROMSG.[BCR], is used to inform the caller of this when selecting a default file transfer. Command <Q> - Returns the caller to the Main Menu <O>.... Other Bulletin Boards This feature displays SFBBSLST.DAT which is a listing of names, bps rate and phone numbers of other Bulletin Boards. <A>.... Add BBS Name & # This feature allows a caller to add the name, bps rate and phone number of other bulletin board systems to the BBS list, SFBBSLST.DAT. When adding a BBS to SFBBSLST.DAT, the number is recorded in the caller's log to provide the Sysop a means of tracing who entered the listing. <K>.... Main Menu Extension This command can be set to run a third party program configured by the Sysop. It is set up using the necessary commands to execute the desired option within the SFMAIN.BAT file. It should be noted that Sysops will need to use the SFHELP.EXE utility to modify the SPITFIRE.HLP file so it properly explains the added option. When this option is selected, SPITFIRE creates the file SFMAIN.DAT and places it in the SPITFIRE home directory. SFMAIN.DAT contains caller information which is often required by the third party program. SPITFIRE then shells from memory during the execution of the third party program. When the caller exits the third party program and control is returned to SPITFIRE, SFMAIN.DAT is automatically erased. <@>.... Sysop Utilities This feature takes a caller from the MAIN Section to the SYSOP section. The BBS is maintained from the SYSOP Section. This feature is not normally available to most callers. <?>.... HELP with Commands This option provides 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 using the <M>...Message Section command option. Page 94 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 the SFMSG.MNU file. In other words, you can control what commands are available to what callers. (Refer to the section - SPITFIRE Menu Files - for further information regarding setting security levels for accessing each menu feature.) For the purpose of discussion, however, each menu displayed will be as if the Sysop (with the highest security level and capable of accessing each menu feature) were viewing it. In this case the Message Menu would look like this. 10.1 - MESSAGE MENU EXAMPLE --------------------------- >>>>>>>> MESSAGE MENU <<<<<<<< <L>.... LAKOTA QWK Mail System <C>..... Change Msg Conference <R>............. Read Messages ........... Browse Messages <S>...Specific Caller Messages <E>........... Enter A Message <Y>............. Your Messages <A>.... Alter Conference Queue <T>............... Text Search <F>.............. File Section ............ Page The Sysop <Q>......... Quit To Main Menu <G>......... Goodbye & Log Off <X>......... Xpert Mode Toggle <K>.... Message Menu Extension <@>........... Sysop Utilities <?>........ HELP With Commands MESSAGE MENU - <L C R B S E Y A T F P Q G X K @ ?>? 10.2 - MESSAGE MENU EXPLANATION ------------------------------- <L>.... LAKOTA QWK Mail System When this option is selected, SPITFIRE shells to LAKOTA.COM, SPITFIRE's Mail System and the following menu is displayed: <D>............. Download Messages (QWK Format) ............... Upload Messages (QWK Format) <S>............. Set Last Read Message Pointers <Q>....................................... Quit Selecting <D> displays the Download Message Menu: >>>> Download Message Menu <<<< <N>............... New Messages <T>..................... To You <Q>....................... Quit This menu defines the selection criteria of the messages to be downloaded using SPITFIRE's Mail System. Once the Page 95 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- caller chooses between downloading new messages or messages addressed to them, the conference menu is displayed: >>>> Message Conference Menu <<<< <A>.............. All Conferences .......... Select A Conference <C>...... Your Queued Conferences <Q>......................... Quit This menu allows the caller to define what conferences messages will be extracted from during the message download process. The caller is then asked whether the last message read pointers should be updated. If the caller is logged on locally the message packet will be placed in SPITFIRE's home directory. If the caller is logged on remotely a menu will display from which the caller can select the file transfer protocol to be used for the message download. Selecting from SPITFIRE's Mail System Menu allows the caller to upload replies in QWK format which are imported into SPITFIRE's message base. Prior to the upload, LAKOTA verifies that the amount of available disk space is greater than that which the Sysop has configured at the ALT+Z Upload Disk Space Requirement option. If the caller is logged on locally, the following prompt appears: File must be in .ZIP format! Enter name of the file to import: The first character entered should be the drive letter where the file to be uploaded is located. LAKOTA automatically inserts the colon and the backslash after this letter is entered. (In other words, if you input the letter C, LAKOTA will place the :\ after this character to make it "C:\".) Next enter the path and name of the file to be imported. LAKOTA will import messages from the reply file directly into SPITFIRE's message base. If the caller is logged on remotely a menu will display from which the caller can select the file transfer protocol to be used to upload the message reply packet. Once the file is received, it is imported into the SPITFIRE message base. Selecting <Q> returns the caller to SPITFIRE Message Menu. Page 96 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- For more information on LAKOTA, SPITFIRE's QWK Mail System, refer to the documentation, LAKOTA.DOC. <C>.... Change Msg Conference This feature allows a caller to change to a different Message Conference by entering the number of the Message Conference he/she wishes to change to. If a caller selects <Q>uit, the caller will remain in the current Message Conference. If a caller presses the ENTER key, SPITFIRE will list the Message Conferences available to the caller. If a MGLST<x>.[BCR] is found it will be displayed here. After changing to a new Message Conference, SPITFIRE will prompt the caller as to whether he/she would like to read messages in the conference they have changed to. <R>.... Read Messages This feature allows the caller to read public messages and non-public messages sent to and/or from the caller in the specified Message Conferences. The caller is presented with five options and may elect to read: <T>...This Message Conference This option allows the caller to read available messages in the current Message Conference. <A>...All Message Conferences This option allows the caller to read available messages in all Message Conferences to which the caller has access. <O>...Only Queued Conferences This option allows the callers to read available messages in the Message Conferences the callers have selected to be included in their Message Queue. <A>...Alter Conference Queue When this option is selected, SPITFIRE will display a list of all conferences contained in the caller's message queue and prompt the caller as to whether to change the current queue. If the caller selects to change the queued message conferences, the Message Queue Menu is displayed. For more information on the Message Queue Menu, refer to Command <A>..Alter Message Queue discussed below. <Q>...Quit This option will return the caller to the Message Menu. Page 97 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- During the process of reading messages, the caller will have the following commands available to them, provided the command is a viable option at the time. If it is not a viable option, the command will not be shown to the caller. <R>...Reply Allows the caller to reply to an existing message provided the caller's security is equal to or greater than the Message Entry Security configured by the Sysop for the current Message Conference. 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. If the caller is replying to a message in a conference which allows non-public messages the caller will be prompted as to whether the reply should be public or non-public. SPITFIRE will default according to how the original message was entered. In other words, if the original message was public, SPITFIRE defaults to making the reply public. When the prompt is displayed the caller may override the default or simply hit Enter to accept the default. If the message being replied to is a net-mail message, the caller will be prompted as to whether the message reply should also be sent net-mail. If so, the caller is also asked whether the reply message should be routed. In the event the caller chooses to route the reply, he/she will be asked to enter the routing number or name. If the BBS is using Buffalo Creek's BCSUTI or SHILOH net-mail software, the reply is automatically routed to the originating BBS. Other net-mail programs or UTI programs may require the message to be routed in the normal fashion. ***NOTE*** When routing a message, SPITFIRE will prompt the caller as to whether the message should be sent public or non-public. SPITFIRE allows a message to be entered as non-public when the message is being routed, even if the Message Conference where the message is being replied to has been configured to only allow public messages. Page 98 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- When replying to a message the caller will have the following commands available to them: CTRL+Q Allows the caller 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 wishes to quote. This range is then included in their reply message with the initials of the sender of the original message preceding each line. For example: MW> SPITFIRE is the best BBS software available! A quoted portion of a reply cannot be edited. CTRL+F Allows a person replying to the message, when logged on locally, the ability to import an an existing text file into the message reply. When the CTRL+F - Import File! feature is selected, SPITFIRE will prompt the caller for the path and file name of the file to be imported. In the event a file name is not entered, SPITFIRE will look in the Work directory for a file named SFMSG.TXT and import this, if found. If after pressing the CTRL+F keys the caller decides not to import a file, entering a non-existent path at the prompt will abort the process. If the <ENTER> key is pressed when replying to a message, the following options become available to the caller who is replying to the message: <S>ave will save the reply. <E>dit allows the caller to edit the message text. <A>bort will end any message entry without saving the message. <C>ontinue will resume entry/reply of message from the point where the <ENTER> key was pressed. egin will clear the existing text and allow the Again caller to begin entering the message anew. <R>eplace allows the caller to replace a line within Line the text of the message. <L>ist allows the caller to display the text of the message which is being entered. nsert allows a blank line to be added within the Line text of the message. Page 99 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <D>elete allows the caller to delete a line or range Line of lines from the existing message text. <D>...Delete This option will be available only if 1) the caller has Sysop security or 2) the Message Conference has been configured to allow the caller the ability to delete messages and the message is either being sent to or entered 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. <E>...Enter A Message This feature allows a caller to enter a message while reading messages, provided the caller's security is equal to or greater than what the Sysop has configured as the Message Conference's Message Entry Security. If the message the caller enters is not addressed to a specific person, then SPITFIRE addresses the message to "All Callers". SPITFIRE will allow the entry of a partial name when entering a local message (message in a conference that is not configured to allow net-mail). Each time a partial name match is found, SPITFIRE will quiz the caller to determine if the current match is the caller for whom the message is intended. If no match can be found, SPITFIRE notifies the caller that no match was found and prompts the caller with "Try Again? [Y/n]". This allows the caller to re-enter the full or partial name of the person for whom the message is intended or to abort the message. SPITFIRE will not allow a caller to enter messages addressed to a specific person if that person cannot be found in the caller's data base unless the Message Conference in which the message is being entered is configured as a net-mail conference and the message is marked to be sent via net-mail. When entering a message in a net-mail conference, you will be prompted as to whether to send the message via net-mail. If the Message Conference is configured to allow Message Routing, the caller is also prompted as to whether the message should be routed. If the caller responds with a Y, he/she will then be asked to enter the routing number or name. ***NOTE*** When routing a message, SPITFIRE will prompt the caller as to whether the message should be sent public or Page 100 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- non-public. SPITFIRE allows a message to be entered as non-public when the message is being routed, even if the Message Conference where the message is being entered has been configured to only allow public messages. Callers are allowed to send carbon copies of a message to other callers. SPITFIRE allows a total of nine carbon copies per message and automatically prevents duplicating carbon copy messages to callers already receiving the message. Using carbon copies in conjunction with the routing feature will allow the caller to send the same message to ten different callers, routing it to ten different locations. SPITFIRE allows a total of 99 lines per message but the Sysop can configure, per message conference, the maximum number of lines per message that will be allowed. When entering (or responding) to a message, SPITFIRE can display the Message Conferences available to the caller and whether the specified Message Conference allows public or public and non-public messages. Pressing ENTER twice when prompted for the message subject will abort the message. When logged on locally and entering a message, another option, the CTRL+F will allow an existing text file to be imported into the message. When the CTRL+F - Import File! feature is selected, SPITFIRE will prompt the caller for the path and file name of the file to be imported. In the event, a file name 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. If the <ENTER> key is pressed while entering a message, the following options become available to the caller who is entering to the message: <S>ave will save the message. <E>dit allows the caller to edit the message text. <A>bort will end any message entry without saving the message. <C>ontinue will resume entry of the message from the point where the <ENTER> key was pressed. egin will clear the existing text and allow the Again caller to begin entering the message anew. Page 101 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <R>eplace allows the caller to replace a line within Line the text of the message anew. <L>ist allows the caller to display the text of the message which has been entered. nsert allows a blank line to be added within the Line text of the message. <D>elete allows the caller to delete a line or range Line of lines from the existing message text. <ENTER>...Next Message Pressing the enter key will cycle the caller to the next available message to be read. <->...Previous Message Allows the caller to return to the previous message in the current conference. <#>...Number Of An Existing Message In This Conference Entering a number of a specific message that is available in the conference will display that message. <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 caller to the first message containing the common message subject which threads the messages together. <F>...Forward Read will cycle through the threaded messages in forward order, one message at a time. ...Backward Read will cycle through the threaded messages in reverse order, one message at a time. <E>...Exit Message Thread will return the caller to the original message from where the Threaded Message Menu was activated. Page 102 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- ...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. When selected, SPITFIRE checks to see if a printer is attached and ready for printing. If so, SPITFIRE provides the option of exporting the message to the printer or saving it to a text file on disk. If no printer is attached or it is not ready for printing, the message is saved as a text file in the directory designated as the Message file path. The default format for the file name to which it is saved is: MSG+message#.conference#. In other words, if message number 15 in conference 3 was Xported, it would be saved as MSG15.3. SPITFIRE will display the default file name of the saved message which the caller can modify by backspacing out the default and entering in the preferred file name. <C>...Copy This feature is only available to a caller with Sysop security. This feature actually serves two purposes. First, it allows the caller to move the message to another message conference or copy the message to the current conference. SPITFIRE will informs the caller regarding to whom the message is currently addressed and prompt the caller as to whether this should be changed, therefore, also allowing the message to be forwarded to another caller. When copying a message to a conference which has been configured as a net-mail conference, the caller is prompted as to whether the message should be marked as a net-mail message. <Q>...Quit End the read message feature and returns the caller to the Message Menu. .... Browse Messages This feature allows a caller to scan messages in a specific Message Conference or in all Message Conferences. This scan provides the caller information on to whom the message Page 103 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- is addressed, whom the message is from and the subject of the message. At the end of each screen the caller is prompted with: <ENTER>=Continue, <Q>uit or Read Msg #: at which time the caller may choose the continue browsing through the message conference, quit to the Message Menu or read a specific message number. If the caller elects to read a message, after the message has finished displaying, the caller simply presses <ENTER> to return to browsing messages. If the caller's security is equal to or greater than the Message Entry Security level, the caller may also be presented with the option of Replying to the message. <S>.... Specific Caller Messages This feature allows the caller to search for messages either to or from a specific caller. When this option is selected, the caller presented a menu which allows them to define what conferences will be used in the search. The Conference Scan looks like this: >>>> CONFERENCE SCAN MENU <<<< <T>.... This Message Conference <A>.... All Message Conferences <Q>.... Only Queued Conferences <Q>........................Quit Next, the caller is prompted to enter the name of the caller to be used in the search. SPITFIRE then prompts the caller to select whether it will search messages that are From, To or both To and From the specified caller. When a message is found, SPITFIRE will display the message to the caller provided it is a public message and it has not been marked for deletion. SPITFIRE will continue to display messages until the search is aborted or the last message to/from the specific caller is displayed. When ended, a message is displayed which informs the caller of the number of messages found to/from the specific caller. *** NOTE *** SPITFIRE displays such a message, if found, to a caller with Sysop security regardless of whether the message has been marked for deletion or entered as a non-public message. <E>.... Enter A Message This feature allows a caller to enter a message, provided the caller's security is equal to or greater than the Message Entry Security for the conference the caller selects to enter Page 104 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- a message to. If the message the caller enters is not addressed to a specific person, then SPITFIRE addresses the message to "All Callers". SPITFIRE will allow the entry of a partial name when entering a local message (message in a conference that is not configured to allow net-mail). SPITFIRE will then quiz the caller to determine who exactly the message is intended for each time a partial name match is found. If no match can be found, SPITFIRE notifies the caller that no match was found and prompts the caller with "Try Again? [Y/n]". This allows the caller to re-enter the full or partial name of the person for whom the message is intended or to abort the message. SPITFIRE will not allow a caller to enter messages addressed to a specific person if that person cannot be found in the caller's data base unless the Message Conference in which the message is being entered is configured as a net-mail conference and the message is marked to be sent via net-mail. When entering a message in a net-mail conference, you will be prompted as to whether to send the message via net-mail. If the conference is configured to allow Message Routing, the caller is will be prompted as to whether the message should be routed. If the caller responds with a Y, he/she will be asked to enter the routing number or name. ***NOTE*** When routing a message, SPITFIRE will prompt the caller as to whether the message should be sent public or non-public. SPITFIRE allows a message to be entered as non-public when the message is being routed, even if the Message Conference where the message is being entered has been configured to only allow public messages. Callers are allowed to send carbon copies of a message to other callers. There are a total of nine carbon copies available. SPITFIRE will automatically prevent duplicating carbon copy messages to callers already receiving the message. Using the carbon copies in conjunction with the routing feature will allow the caller to send the same message to ten different callers, routing it to ten different locations. SPITFIRE allows a total of 99 lines per message but the Sysop can configure, per message conference, the maximum number of lines per message that will be allowed. When entering (or responding) to a message, SPITFIRE will display the Message Conferences available to the caller and whether the specific Message Conference allows public or public and non-public messages. Pressing ENTER twice when prompted for the message subject will abort the message. Page 105 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 the caller for the path and file name of the file to be imported. In the event, a file name 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. If the <ENTER> key is pressed while entering a message, the following options become available to the caller who is entering to the message: <S>ave will save the message. <E>dit allows the caller to edit the message text. <A>bort will end any message entry without saving the message. <C>ontinue will resume entry of the message from the point where the <ENTER> key was pressed. egin will clear the existing text and allow the Again caller to begin entering the message anew. <R>eplace allows the caller to replace a line within Line the text of the message anew. <L>ist allows the caller to display the text of the message which has been entered. nsert allows a blank line to be added within the Line text of the message. <D>elete allows the caller to delete a line or range Line of lines from the existing message text. <Y>.... Your Messages This feature will display the caller's message statistics. The caller receives a report on the number of new messages they have waiting to be read, the number of messages they have already received, the number of messages the caller has sent and the total number of messages available on the BBS. The caller is then prompted as to whether he/she would like to read their messages. *NOTE* If the caller is recognized as the Sysop of the BBS, he/she will also be prompted as to whether he/she would like to preview messages. If the Sysop replies with a Yes, SPITFIRE allows the messages to be read, but does not mark the message as being received. (For more information on the Message Preview feature, refer to section SPECIAL COMMANDS FOR SYSOP of this manual.) Page 106 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <A>.... Alter Conference Queue This feature allows a caller to include specific message conferences in his/her message conference queue. Conferences not included in the caller's message queue will be ignored. When a caller selects the <A>...Alter Message Queue option, the caller is presented with the following sub-menu: >>>> MESSAGE QUEUE MENU <<<< <A>...... Add A Conference <C>....... Current Queue List <D>... Delete A Conference .. Include All Conferences <L>.. List Msg Conferences <R>... Remove All Conferences <S>.... Select Conferences <Q>..... Quit To Message Menu <A>...Add A Conference allows a caller to enter a specific number corresponding to the Message Conference number the caller wishes to have added to their message conference queue. <D>...Delete A Conference allows a caller to enter a specific number corresponding to the Message Conference number the caller wishes to have deleted from their message conference queue. <L>...List Msg Conferences will display all message conferences on the BBS to which the caller has access. <S>...Select Conferences will display, one screen at a time, all conferences available on the BBS. A tag letter precedes the conference number and conference description. To remove a conference from your message conference queue, enter a minus sign and the respective tag character(s). To add a conference enter the respective tag characters. For instance, -BE would remove the second and fifth conferences listed from the callers conference queue and AC would add the first and third conferences listed to the callers conference queue. Only conferences to which the caller has access will be included in the list for selection. <C>...Current Queue List will display to the caller the message conferences currently contained in their message conference queue. ...Include All Conferences will place all available message conferences in the caller's message queue. Page 107 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <R>...Remove All Conferences will remove all message conferences from the caller's message queue with the exception of the first Message Conference. SPITFIRE requires that all callers have Message Conference 1 in their queue. <Q>...Quit To Message Menu will return the caller to the Message Menu. ** SPECIAL NOTES ABOUT QUEUED CONFERENCES ** Conferences not included in the caller's queue will not be scanned when SPITFIRE scans for new messages. For this reason, when a caller attempts to leave a message to another caller in a message conference that the caller does not have selected in their queue, SPITFIRE will not allow the caller to send the message. Also, a caller may delete any message conference from their message queue, except for the first message conference. The first message conference will remain active to all callers. <T>.... Text Search This feature allows a caller to search for specific text in a message. When selected, the text search option displays the following menu to allow the caller to define what message conference(s) will be included in the search: <T>.... This Message Conference <A>.... All Message Conferences <Q>.... Only Queued Conferences <Q>........................Quit SPITFIRE supports a multi-word text search of up to six key words at one time. The caller is prompted to enter the key word(s) to be used in the search. SPITFIRE then searches for any message containing the keywords in the conference option selected by the caller. When any matching text is found in a message, SPITFIRE will display the message and prompt the caller as to whether they wish to continue with the search. When the search is ended, a message displays notifying the caller of the number of times any matching text was found. <F>.... File Section This feature takes the caller from the MESSAGE Section of SPITFIRE to the FILE Section. .... Page The Sysop This feature notifies the Sysop that a caller has a question or problem to chat about. If the Sysop is not available to Page 108 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- answer the page, SFUNANS.[BCR] is displayed to the caller. If a caller attempts to page the Sysop a second time, and SFPAGED.[BCR] is found, SFPAGED.[BCR] is displayed to the caller and the Sysop is not paged a second time. If SFPAGED.[BCR] is not found, the caller may page the Sysop multiple times. If the Sysop has the page feature turned off and a caller attempts to page the Sysop, SFPGOFF.[BCR] is displayed to the caller. <Q>.... Quit To Main Menu This feature takes a caller from the MESSAGE Section of SPITFIRE to the MAIN Section. <G>.... Goodbye & Log Off This feature simply allows a caller to log off the BBS. <X>.... Xpert Mode Toggle This feature changes a caller's status from novice to expert or vice versa. If a caller is set as a novice, then the menu descriptions will scroll by after each command. If a caller is set as expert, then only the command letters scroll by after each command. <K>.... Message Menu Extension This command can be used to run third party programs which are configured by the Sysop. It is set up by including the necessary commands to execute the desired option within the SFMESS.BAT file. It should be noted that Sysops will need to use the SFHELP.EXE utility to modify the SPITFIRE.HLP file so it properly explains the added option. When this option is selected, SPITFIRE creates the file, SFMESS.DAT and places it in the SPITFIRE home directory. SFMESS.DAT contains caller information which is often required by the third party program. SPITFIRE then shells from memory during the execution of the third party program. When the caller exits the third party program and control is returned to SPITFIRE, SFMESS.DAT is automatically erased. <@>.... Sysop Utilities This feature takes a caller from the MESSAGE Section to the SYSOP Section. The BBS is maintained from the SYSOP Section. <?>.... HELP With Commands This feature will provide help for each command available from the MESSAGE MENU. Page 109 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 11.0 - FILE SECTION EXPLAINED ----------------------------- It is from the File Menu that all file related activity is accessed. The File Menu may be selected from either the Main Menu or the Message Menu with the <F>...File Section command option. The Sysop has the ability to control which features are available to the callers by adjusting the security level within the SFFILE.MNU. (Refer to the section - SPITFIRE Menu Files - for further information regarding setting security levels for accessing each menu feature.) For the purpose of discussion, each menu displayed will be as if the Sysop (with the highest security level and access to each menu feature) 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>............ Shuffle Files <N>................ New Files <T>.. Text Search Description <F>.............. Find A File <X>........ Xpert Mode Toggle <?>....... HELP With Commands <K>..... File Menu Extension <@>.......... Sysop Utilities <V>...... View A File Archive <R>......... Read A Text File FILE MENU - <C L E G D U H P M Q S N T F X ? K @ V R>? 11.2 - FILE MENU EXPLANATION ---------------------------- <C>.... Change File Area This feature allows a caller to change to a different File Area. If <Q>uit is selected, the caller remains in the current File Area. If the ENTER key is pressed, SPITFIRE will list the File Areas available to the caller. <L>.... List Files In This Area This displays the file listing (SFFILES.BBS) in the current File Area that are available for the caller to download. When listing files, SPITFIRE offers file tagging for ease of downloading. SPITFIRE precedes each file in the list Page 110 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- with a tag character. As each screen completes displaying, the caller is prompted to enter the tag character(s) that are associated with the file(s) to be downloaded. When the file download transfer process begins, SPITFIRE will automatically insert the name of the file(s) tagged for downloading. When a file is marked as OFFLINE in the SFFILES.BBS or if the file can not be found in the download directory, SPITFIRE will treat any such tagged files as file requests. File requests are recorded to the SFILEREQ.LOG in the SPITFIRE Work File Path. Refer to the section - SPITFIRE FILE CLARIFICATIONS - of this manual for additional information regarding SPITFIRE's file request feature. <E>.... Erase A File This feature allows callers to erase a file from a File Area. Normally this feature is only available to callers with Sysop security. When erasing a file from the file menu, SPITFIRE prompts you as to whether the file should be added to SFNOUP.DAT. Responding with a Y for Yes adds the erased file's name to SFNOUP.DAT. SPITFIRE's file tagging feature can be used when erasing a file(s). If no files have been tagged, you must enter the name of the file to be erased. Before the file is deleted you will be asked to verify that the file is to be erased. If files have been tagged for erasing, the name will default in automatically but SPITFIRE still prompts you to verify each file before it is erased. This process will continue until all tagged files are processed. When erasing a file, information regarding the file is removed from SFFILES.BBS. <G>.... Goodbye & Log Off This feature simply allows a caller to log off the BBS. <D>.... Download A File This feature allows a caller to download a file, provided the caller hasn't exceeded the maximum daily download limit and the caller has enough time left to perform the download. The caller does not have to be in any specific File Area to perform a download. If the caller starts a download while in a File Area marked as a CD-ROM File Area and the file to be downloaded isn't found in that area, SPITFIRE asks the caller whether to search the other File Areas. On a single file transfer, 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. On a batch file transfer, the caller is prompted as to whether SPITFIRE should automatically log the caller off the BBS when the file Page 111 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- transfer is completed. After completing the download, SPITFIRE notifies the caller of the number of downloads he/she has remaining for the day. When the caller is prompted for the name of the file to download, if the file name and period is input, SPITFIRE automatically adds the ZIP extension. If, for example, SF35. is entered, SPITFIRE initiates the download of SF35.ZIP. If the period is not added, SPITFIRE does not add the file extension. Prior to starting the download, SPITFIRE displays to the caller a list of the files selected for downloaded and the number of bytes which will be sent. When using SPITFIRE's internal transfer protocols and a file transfer is initiated, a window opens on the screen, allowing the Sysop to monitor the progress of the download. The information displayed in the window includes: the transfer protocol selected, file name, total bytes to be sent, bytes sent, bytes that remain to be sent, consecutive errors, total errors, a last message field which SPITFIRE uses to display the calculated characters per second transfer rate when there is no other message, and a graph depicting the progress of the transfer. When the Download a File option is selected by a caller who is logged on locally, the IMPORT/EXPORT Menu is displayed. The RIP/ANSI/non-ANSI screen for this menu, SFIMPEXP.[BCR], is displayed if found. Otherwise, the following default SPITFIRE menu is displayed: >>>> 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 by copying it from another drive and/or directory to the configured upload path for the current SPITFIRE file area. SPITFIRE prompts the caller to enter the path name of the file to be copied and also prompts for a description of the file being copied. The file name, size, date, as well as Page 112 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- the description of the file being copied is added to the SFFILES.BBS in the upload directory of the File Area in which file is being copied to. <E>... Export A File Allows a file from a SPITFIRE file area to be copied to a drive and/or directory not set up as a SPITFIRE file area. The caller is prompted for the name of the file to be copied and the path to which the file will be copied to. <R>... Remove A File Allows a file to be erased from the SPITFIRE file area and removed from the appropriate SFFILES.BBS. When a file is removed, the caller is prompted as to whether the file should be added to SFNOUP.DAT. <T>... Text Search Description Allows a caller to search for certain text within a file description. The caller can search in a specific File Area or in all File Areas. This feature ONLY searches the file description and not the file name, date or size. However, when the matching text is located, these are displayed. If the caller is logged on in ANSI or RIP graphics, and the matching text is found, it is highlighted when it is displayed to the caller. <F>... Find A File Allows a caller to search a specific File Area or all File Areas for a specific file. Wildcards are allowed, with the exception of *.*. If a caller enters a file name without the file extension, SPITFIRE automatically adds a ".*" to the file name. If there is a match, the file name, size, date and description are shown, provided the file is listed in the SFFILES.BBS. <L>... List Files (This Area) Displays the SFFILES.BBS for the current File Area, listing files that are available for the caller to download. When listing files, SPITFIRE offers file tagging for ease of downloading. SPITFIRE precedes each file in the list with an alphabetical character. As each screen completes displaying, the caller is prompted to enter the alpha character(s) associated with a file(s) to be downloaded. When the caller begins the file download process, SPITFIRE will automatically insert the name of the file(s) the caller has tagged for downloading. Page 113 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <C>... Change File Area Allows a caller to change to a different File Area. If the caller selects <Q>uit, the caller remains in the current File Area. If the caller presses the ENTER key, SPITFIRE lists the File Areas that are available to the caller. <Q>... Quit To File Menu Allows the caller to exit the IMPORT/EXPORT Menu and return to the File Menu. <G>... Goodbye & Log Off Allows the caller to log off the BBS. .... Upload A File This feature provides the caller the opportunity to upload a file. The caller can be compensated additional time on the BBS for the upload. The amount of the additional time is set by the Sysop. SPITFIRE allows the caller to automatically log off after the completion of the upload by placing a backslash, "\", after the name of the file to be uploaded. By using a forward slash, "/", at the beginning of the file description, a caller can upload a file for Sysop only. When a file is uploaded for Sysop only, it is not added to the SFFILES.BBS but the Sysop is notified in the HEYSYSOP.LOG. After the name of the file to be uploaded is entered, SPITFIRE prompts the caller to stand by while it checks to see if the file already exists. While checking for the file, SPITFIRE checks for the same file with a different extension. For example, if a caller attempts to upload SF351.ARJ and SF351.ZIP is found, the caller is notified of the existing file and is questioned as to whether the upload should be continued. If the Sysop has toggled the Comprehensive Upload Search to On (ALT+T configuration), during the search, SPITFIRE removes any trailing digits from the file name. If a caller attempts to upload SF34.ZIP and SF351.ZIP was found, the caller is notified of the existing file and questioned as to whether the upload should continue. When using SPITFIRE's internal transfer protocols and a file transfer is initiated, a window opens on the screen, allowing the Sysop to monitor the progress of the upload. Information displayed in the window includes: transfer protocol selected, file name, total bytes to be sent, bytes sent, bytes that remain to be sent, consecutive errors, total errors, a last message field which SPITFIRE uses to display the calculated characters per second transfer rate when there is no other message, and a graph depicting the progress of the transfer. Page 114 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- When a caller uploads a file which was not expected (no file name or description was provided by the caller), at the conclusion of the upload when the file is found, SPITFIRE checks to see if the file already exists. File Areas with the Search File Area option set to No will not be searched. If the file is not found, SPITFIRE then prompts the caller to enter a description of the file. When the Upload A File option is selected by a caller who is logged on locally, the IMPORT/EXPORT Menu is displayed. The RIP/ANSI/non-ANSI screen for this menu, SFIMPEXP.[BCR], is displayed if found. Otherwise, the following default SPITFIRE menu is displayed: >>>> 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 by copying it from another drive and/or directory to the configured upload path for the current SPITFIRE file area. SPITFIRE prompts the caller to enter the path name of the file to be copied and also prompts for a description of the file being copied. The file name, size, date, as well as the description of the file being copied is added to the SFFILES.BBS in the upload directory of the File Area in which file is being copied to. <E>... Export A File Allows a file from a SPITFIRE file area to be copied to a drive and/or directory not set up as a SPITFIRE file area. The caller is prompted for the name of the file to be copied and the path to which the file will be copied to. <R>... Remove A File Allows a file to be erased from the SPITFIRE file area and removed from the appropriate SFFILES.BBS. When a file is removed, the caller is prompted as to whether the file should be added to SFNOUP.DAT. Page 115 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <T>... Text Search Description Allows a caller to search for certain text within a file description. The caller can search in a specific File Area or in all File Areas. This feature ONLY searches the file description and not the file name, date or size. However, when the matching text is located, these are displayed. If the caller is logged on in ANSI or RIP graphics, and the matching text is found, it is highlighted when it is displayed to the caller. <F>... Find A File Allows a caller to search a specific File Area or all File Areas for a specific file. Wildcards are allowed, with the exception of *.*. If a caller enters a file name without the file extension, SPITFIRE automatically adds a ".*" to the file name. If there is a match, the file name, size, date and description are shown, provided the file is listed in the SFFILES.BBS. <L>... List Files (This Area) Displays the SFFILES.BBS for the current File Area, listing files that are available for the caller to download. When listing files, SPITFIRE offers file tagging for ease of downloading. SPITFIRE precedes each file in the list with an alphabetical character. As each screen completes displaying, the caller is prompted to enter the alpha character(s) associated with a file(s) to be downloaded. When the caller begins the file download process, SPITFIRE will automatically insert the name of the file(s) the caller has tagged for downloading. <C>... Change File Area Allows a caller to change to a different File Area. If the caller selects <Q>uit, the caller remains in the current File Area. If the caller presses the ENTER key, SPITFIRE lists the File Areas that are available to the caller. <Q>... Quit To File Menu Allows the caller to exit the IMPORT/EXPORT Menu and return to the File Menu. <G>... Goodbye & Log Off Allows the caller to log off the BBS. Page 116 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <H>.... Help On Upload/Download This feature describes the various file transfer protocols available to the caller. The help information comes from SFPROTCO.HLP and may be edited using your favorite text editor, provided it saves in ASCII format. .... Page The Sysop This feature notifies the Sysop that a caller has a question or problem to chat about. If the Sysop is not available to answer the page, SFUNANS.[BCR] is displayed to the caller. If a caller attempts to page the Sysop a second time, and SFPAGED.[BCR] is found, SFPAGED.[BCR] is displayed to the caller and the Sysop is not paged a second time. If SFPAGED.[BCR] is not found, the caller may page the Sysop multiple times. If the Sysop has the page feature turned off and a caller attempts to page the Sysop, SFPGOFF.[BCR] is displayed to the caller. <M>.... Message Section This feature takes a caller from the FILE Section of SPITFIRE to the MESSAGE Section. <Q>.... Quit To Main Menu This feature takes a caller from the FILE Section of SPITFIRE to the MAIN Section. <S>.... Shuffle Files This feature allows files to be moved from one File Area to another. Security should be set for this option so it is not available to most callers. When a file is moved, the file name, file size, file date and file description from the original SFFILES.BBS is moved and appended to the SFFILES.BBS of the File Area to which the file is being moved. Files may be tagged for shuffling from one File Area to another. Upon selecting this feature, you are prompted to enter the name(s) of the file(s) you wish to move. If you have tagged files prior to selecting this feature, when prompted for the file name, it will default in automatically. SPITFIRE then prompts for the File Area you wish to move the file to. Pressing Enter will list the file areas or you may opt to quit. This continues until all tagged files are processed and no file name is entered for moving. If no files have been tagged and you select the Shuffle Files option, you will be prompted to enter the file name. Next, you will be asked to enter the File Area to which you wish to Page 117 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- move the file. Pressing enter will list the available file areas or you may opt to Quit. This process will continue until no file name is entered for moving. When Shuffling files, SPITFIRE tests to see if the file to be moved exists in the target File Area and if it exists, then the operation is aborted with a message. <N>.... New Files This feature allows a caller to search a specific File Area or all File Areas since a specific date or since the last time the caller searched for new files. In addition to listing the new files, a file statistics message is displayed to the caller with the number of new files received since last checked, the total number of files available for download on the BBS and the number of bytes of downloadable files which exist on the BBS. If any File Area is configured as a CD Rom File Area, SPITFIRE will not report statistics on the number of files and bytes available for download since the statistics are not accurate due to omitting CD ROM File Area(s) in the search for new files. When listing new files, SPITFIRE offers file tagging for ease of downloading. SPITFIRE precedes each file in the list with a tag character (with the exception of S which is used to Stop the file display). As each screen completes displaying, the caller is prompted to enter the tag character(s) that are associated with a file(s) to be downloaded. When the caller begins the file transfer process, SPITFIRE automatically inserts the name of the file(s) the caller has tagged for downloading. <T>.... Text Search Description This feature allows a caller to search for certain text within a file description. SPITFIRE supports multi-word text searches and allows up to 6 key words to be searched for at one time. The caller can search a specific File Area or all File Areas. Please note that this feature searches ONLY the file description and not the file name, date or size. These are displayed, however, when the matching text is located. If the caller is logged on in ANSI or RIP graphics, when matching text is found, it will be highlighted when it is displayed to the caller. <F>.... Find A File This feature allows a caller to search a specific File Area or all File Areas for a certain file. Wildcards are allowed, with the exception of *.*. If a caller enters a file name without the file extension, SPITFIRE automatically adds a Page 118 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- ".*" to the file name. If there is a match, the file name, size, date and description are shown, provided the file is listed in the SFFILES.BBS. <X>.... Xpert Mode Toggle This feature changes a caller's status from a novice to an expert or vice versa. If a caller is set as a novice, then the menu descriptions scroll by after each command. If a caller is set as an expert, then only the command letters scroll by after each command. <?>.... HELP With Commands This feature displays help for each command available from the FILE MENU. This feature is augmented with SFHELP.EXE, which creates separate help screens for each individual command. For more information on SFHELP.EXE, consult the documentation accompanying it. This program is available for download on Buffalo Creek's BBS. <K>.... File Menu Extension This command can be used to run third party programs which are configured by the Sysop. It is set up by including the necessary commands to execute the desired option within the SFFILE.BAT file. It should be noted that Sysops need to use the SFHELP.EXE utility to modify the SPITFIRE.HLP file so it properly explains the added option. When this option is selected, SPITFIRE creates the file, SFFILE.DAT and places it in the SPITFIRE home directory. SFFILE.DAT contains caller information which is often required by the third party program. SPITFIRE then shells from memory during the execution of the third party program. When the caller exits the third party program and control is returned to SPITFIRE, SFFILE.DAT is automatically erased. <@>.... Sysop Utilities This feature takes a caller from the FILE Section to the SYSOP Section. The BBS is maintained from the SYSOP Section. This feature is not normally available to most callers. <V>.... View A File Archive This feature allows a caller to view the contents of a ZIP file. The caller sees the file name, file size and file date of each file within the compressed ZIP file. The caller does not have to be in a specific file area to utilize this feature. <R>.... Read A Text File This feature allows a caller to read a text file available for download. The caller may want to use this feature and Page 119 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- simply capture the text rather than download the file. The caller does not have to be in a specific File Area to utilize this feature. 11.3 - UPLOAD/DOWNLOAD PROTOCOLS -------------------------------- The following is a list of Upload and Download protocols available within SPITFIRE: 1) Ascii 2) Xmodem Checksum 3) Xmodem CRC 4) 1K-Xmodem 5) Ymodem (Batch) 6) Zmodem (Batch) 7) 1K-Xmodem-g 8) Ymodem-g (Batch) 9) Telink SPITFIRE does not allow a caller to download files with a .COM, .EXE, .ARC, .ARJ, ZIP, or PAK extension when using the ASCII transfer protocol. Batch transfers using the External Protocol drivers are supported by SPITFIRE. (For more information refer to the section - EXTERNAL FILE TRANSFER PROTOCOLS - of this manual.) 11.4 - BATCH DOWNLOAD MENU -------------------------- In order for the Batch Download Menu to be displayed, the caller must have selected to download a file from the File Menu and then selected a file transfer protocol that is capable of doing batch downloads. It is possible for a caller to do a batch download without ever having the Batch Download Menu displayed to them. The Batch Download Menu is displayed if, after filling their batch queue, the caller responds with a "N" when prompted as to whether to begin the batch transfer now or if the batch queue is empty and the caller presses the Enter key when asked to enter the name of the file to be downloaded. The SPITFIRE default Download Batch Menu looks like this: Page 120 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- >>>> BATCH DOWNLOAD MENU <<<< <A>...... Add To Batch Queue <V>..View Tagged/Queued List ..... Begin File Transfer <R>... Remove File From List <S>... Start New Batch Queue <L>.. List Files (This Area) <C>........ Change File Area <Q>....... Quit To File Menu <?>.................... Help <G>....... Goodbye & Log Off BATCH MENU - [A V D R S L C Q ? G]? <A>... Add To Batch Queue This feature allows the caller to enter the name of the files(s) to be added to the batch queue. SPITFIRE does not allow the caller to exceed their daily download limit or time limit. <V>... View Tagged/Queued List This feature allows the caller to review the file(s) they have tagged or added to the batch queue. SPITFIRE also informs the caller of the approximate time required for the file transfer of each file, as well as the total approximate time to transfer the entire batch queue. ... Begin File Transfer This feature simply starts the batch download provided the caller has files to download listed in the batch queue. Before the download(s) is started, the caller is prompted as to whether they wish to log off when the transfer is finished. If the answer is Yes, SPITFIRE automatically logs the caller off after the download(s) is completed. <R>... Remove File From List If the caller changes his/her mind about including a file in their list of files to download, this feature allows the caller to remove a file from the list. <S>... Start New Batch Queue In the event the caller decides to start over, this feature allows the caller to clear all file names currently contained in the batch queue. <L>... List Files (This Area) This feature displays the files in the current File Area which are available for the caller to download. The file's name, file size, file date and a brief description of the file are displayed to the caller. <C>... Change File Area This feature allows the caller to change to a different File Area. If the caller selects <Q>uit, the caller remains in Page 121 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- the present File Area. If the caller presses the [ENTER] key, SPITFIRE lists the File Areas available to the caller. If a number corresponding to an available File Area is entered, SPITFIRE makes that File Area the current File Area. <Q>... Quit To File Menu This feature takes the caller from the Batch Section of SPITFIRE to the File Section of SPITFIRE. If this is selected, the caller's batch queue is cleared. <?>... Help This feature offers a brief description of the various commands available from the Batch Download Menu. <G>... Goodbye & Log Off This feature simply allows the caller to log off the BBS. 11.5 - BATCH UPLOAD MENU ------------------------ For the Batch Upload Menu to be displayed, the caller must select to upload a file from the File Menu and select a file transfer protocol that is capable of doing batch file transfers. It is possible for a caller to do a batch upload without ever having the Batch Upload Menu displayed to them. The Batch Upload Menu is displayed if, after filling their batch queue, the caller responds with a "N" when prompted as to whether to begin the batch transfer or if the batch queue is empty and the caller presses the Enter key when asked to enter the name of the file to be uploaded. SPITFIRE's default Upload Batch Menu looks like this: >>>>> BATCH UPLOAD MENU <<<<< <A>...... Add To Batch Queue <W>... What's In Batch Queue ..... Begin File Transfer <R>.. Remove File From Queue <S>... Start New Batch Queue <L>.. List Files (This Area) <C>........ Change File Area <Q>....... Quit To File Menu <?>.................... Help <G>....... Goodbye & Log Off BATCH MENU - [A W U R S L C Q ? G]? <A>... Add To Batch Queue This feature allows the caller to enter the name of the files(s) to be added to the batch queue. SPITFIRE prompts the caller to enter the file name and a description of the file(s) to be uploaded. Page 122 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <W>... What's In Batch Queue This feature allows the caller to review the file(s) that have been added to the batch queue. SPITFIRE displays the file name(s) and a brief description of the file(s) currently contained in the batch queue. ... Begin File Transfer This feature simply starts the batch upload provided that the caller has files to upload listed in the batch queue. Before the upload(s) is started, the caller is prompted as to whether they wish to log off when the transfer is finished. If he/she responds with a <Y>es, SPITFIRE automatically logs the caller off after the upload(s) is completed. If the caller fails to provide a description for a file in a batch upload, SPITFIRE provides a default description: "No Description Provided". <R>... Remove File From Queue This feature allows a caller to remove a file from the batch queue if the caller changes his/her mind as to whether a file should be included. <S>... Start New Batch Queue In the event the caller decides to start over, this feature allows the caller to clear all file names currently contained in the batch queue. <L>... List Files (This Area) This feature displays the files in the current File Area which are available to the caller. The file's name, file size, file date and a brief description of the file are displayed to the caller. <C>... Change File Area This feature allows the caller to change to a different File Area. If the caller selects <Q>uit, the caller remains in the present File Area. If the caller presses the Enter key, SPITFIRE lists the File Areas available to the caller. If a number corresponding to an available File Area is entered, SPITFIRE makes that File Area the current File Area. <Q>... Quit To File Menu This feature takes the caller from the Batch Section of SPITFIRE to the File Section of SPITFIRE. If this is selected, the caller's batch queue is cleared. <?>... Help This feature offers a brief description of the various commands available from the Batch Upload Menu. Page 123 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <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). SPITFIRE's default Sysop Menu looks like this: >>>>>>>> SYSOP MENU <<<<<<<< <D>.............. Drop To DOS <E>................. Event Menu <F>............... File Areas <G>.......... Goodbye & Log Off <K>..... Sysop Menu Extension ....... Pack Caller Database <J>........ Pack Message Base <R>.... Remove Backup/Log Files <M>...... Message Conferences ...... Print Caller Database <Q>........ Quit To Main Menu ............. Update Callers <V>........... View Log Files <X>......... Expert Mode Toggle SYSOP MENU [D E F G K I J R M P Q U V X]? 12.1 - SYSOP MENU EXPLANATION ----------------------------- <D>.... Drop to DOS This feature allows the caller to drop to DOS from a remote location. You need to use the ALT+J feature or ALT+D feature to drop to DOS locally. When this feature is used from a remote location, SPITFIRE does not allow the caller to drop to DOS unless the drop-to-DOS password is properly entered. This password is configured using the ALT+Z command at the "Ready..." prompt. It is recommended that this feature be made available to only trusted callers (if made available at all). When this feature is utilized, SPITFIRE shells to SFREMOTE.BAT and sends a parameter which indicates the COM port being used. <E>.... Event Menu This option is used for maintaining events used on the BBS. It is used to List Events, Enable An Event and to Disable An Event. For more detailed information, refer to the EVENTS MENU EXPLANATION section of this manual. Page 124 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <F>.... File Areas This displays the File Area System Record's Menu. From this menu, you are able to configure or modify the File Area System Records. For more detailed information, refer to the section - CONFIGURING FILE AREA RECORDS of this manual. <G>.... Goodbye & Log Off This feature simply allows the caller to log off the BBS. <K>.... Sysop Menu Extension This option allows the Sysop to configure another program or utility (independent of SPITFIRE) to be run from this Sysop configurable command. The Menu Extension option is set up with the necessary commands for executing the program or utility using the SFSYSOP.BAT. The SFSYSOP.BAT needs to reside in the SPITFIRE home directory. When this option is selected, SPITFIRE creates the files, SFSYSOP.DAT (the equivalent of SFDOORS.DAT) and DOOR.SYS in the SPITFIRE home directory. During the execution of the menu extension, SPITFIRE shells from memory. When the caller exits the configured program and control is returned to SPITFIRE, the SFSYSOP.DAT file is automatically erased. .... Pack Caller Database This feature allows you to pack SFUSERS.DAT. When selected, SPITFIRE shells to SFPCKUSR.COM. SFPCKUSR.COM must reside in the SPITFIRE home directory. When you select this feature, SPITFIRE asks if you wish to purge inactive callers. If you answer "Y", you will then be asked whether to purge callers that haven't called for <x> amount of days. The value of <x> is determined by you. After responding to these prompts, SPITFIRE shells to SFPCKUSR and passes to it the purge criteria you have defined. SFPCKUSR will purge from the caller's data base any callers which have been marked for deletion. If you have opted to purge inactive callers, any caller who has not called for the amount of days you specified will also be purged. Once SFPCKUSR has completed packing the caller's data base, information regarding the purged callers is written to SFPURGED.USR (or appended to the existing file) in the WORK directory and control is returned to SPITFIRE. SPITFIRE allows you to toggle whether a purge will be allowed or not allowed for each caller. If a caller has Page 125 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- been toggled as "purge not allowed," SFPCKUSR will not purge the caller (even if the caller has not called for the <x> amount of days specified.) If you are operating a multi-node system, SPITFIRE does not allow you to pack the callers file while a caller is on any of the available nodes. Also, if you are packing the callers file and a caller attempts to log on, after entering their name and password, SPITFIRE notifies the caller that system maintenance is being performed, asks the caller to call back later and then logs the caller off the BBS. The Sysop may create their own ASCII/ANSI/RIP display screen, SFMAINT.[BCR], which will be displayed here, if found. It should be noted that if you select this option and are calling remotely, once you have answered the prompts supplied by SPITFIRE you will not be able to view the progress of SFPCKUSR. No remote display is provided by SFPCKUSR. Display will return when control is returned to SPITFIRE. <J>.... Pack Message Base When this feature is selected, Sysops are asked if they are sure they want to pack the message base. A "Y" response causes SPITFIRE to shell to SFPCKMSG.COM which goes through the message files, purging all messages that have been marked for deletion. When configuring Message Conference records the Sysop specifies how old a message must be (in number of days) for purging with the Purge Messages Older Than option. From the Message Conference record, the Sysop also configures whether threaded and unreceived messages are to be purged when packing the message base. This criteria, defined individually for each Message Conference, determines the messages selected for purging when the message base is packed. It is recommended that the message base be packed on a regular basis for a the following reasons: <1> Disk space. <2> Speed (SPITFIRE works faster with fewer messages). On multi-node systems, SPITFIRE will not permit packing of the message base while a caller is on any of the available nodes. Also, if while packing the message base a caller attempts to log on, after entering their name and password, SPITFIRE notifies the caller that system maintenance is being performed, and asks them to call back later. It then logs the caller off the BBS. The Sysop may create their own ASCII/ANSI/RIP display screens, SFMAINT.[BCR], which are displayed here, if found. Page 126 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <R>.... Remove Backup/Log Files When selected, this option displays the following menu: >>> FILE REMOVAL MENU <<< <C>.... Erase CALLERS.LOG <H>... Erase HEYSYSOP.LOG <R>... Erase SFILEREQ.LOG <S>... Erase SFPURGED.USR .... Erase SFUSERS.$?? <Q>................. Quit FILE REMOVAL MENU - [C H S U Q]? <C>... Erase CALLERS.LOG Selecting this option causes the existing CALLERS.LOG file to be erased. SPITFIRE will automatically create a new CALLERS.LOG file. <H>... Erase HEYSYSOP.LOG Selecting this option causes the existing HEYSYSOP.LOG file to be erased. SPITFIRE will automatically create a new HEYSYSOP.LOG file. <R>... Erase SFILEREQ.LOG When this option is selected, the existing SFILEREQ.LOG is erased. SPITFIRE will automatically create a new SFILEREQ.LOG file the next time a caller makes a file request. <S>... Erase SFPURGED.USR When this option is selected, SFPURGED.USR is erased. SPITFIRE will automatically create a new SFPURGED.USR file the next time the SFUSERS.DAT file is packed. ... Erase SFUSERS.$?? When this option is selected, the SPITFIRE erases the backup files of the caller data base records. <M>.... Message Conferences This displays the Message Conference System Record's Menu. From this menu, Sysops can configure or modify the Message Conference System Records. For more detailed information, refer to the section - CONFIGURING MESSAGE CONFERENCE RECORDS. .... Print Caller Database If the printer is turned on and ready for use and this feature is selected, the Sysop is prompted to select one of the following options: Print to <D>isk, rinter, <Q>uit?. If the printer is not turned on and ready, Page 127 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- only the options: Print to <D>isk, Quit will be displayed Print to <D>isk creates a text file named SFUSERS.LST in the WORK file directory. SFUSERS.LST contains such information as caller name, city/province, and phone number for each caller in the database. rint will send the information to the printer for each caller in the database. <Q>uit returns you to the Sysop Menu. <Q>.... Quit to Main Menu This feature takes you from the Sysop Utility Section of SPITFIRE to the MAIN MENU. .... Update Callers This feature is the same as selecting ALT+A at the "Ready..." prompt and is used to modify statistics on any BBS caller or to manually add new callers. For further information, refer to the section - SPECIAL FUNCTION KEY DEFINITIONS of this manual. <V>.... View Log Files Selecting this option causes the following sub-menu to be displayed: >> View Log File Menu << <C>..........CALLERS.LOG <H>.........HEYSYSOP.LOG <N>...........SFNEWU.REP <O>.......SFORDER<x>.REP <R>.........SFILEREQ.LOG <S>.........SFPURGED.USR <Q>.................QUIT This feature is the same as pressing F1 from the SPITFIRE "Ready..." prompt and is used to view the various BBS log files that are listed in the menu. For further information, refer to the section - SPECIAL FUNCTION KEY DEFINITIONS of this manual. <X>.... Expert Mode Toggle This feature changes caller status from novice to expert or vice versa. If set as novice, the menu descriptions scroll by after each command. If set as expert, only the command letters scroll by after each command. Page 128 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 13.0 - SPECIAL COMMANDS FOR SYSOP STATUS ---------------------------------------- Definition of Sysop Status -------------------------- A caller with Sysop Status is defined as any caller that has a security level equal to or greater than the Sysop security level set using SPITFIRE's ALT+Z configuration window at the "Ready..." prompt. The Message section has a few "Special Commands" for callers with Sysop Status. When a Message Conference is configured to allow the caller the ability to delete messages, it is important to note that only the sender and receiver can delete messages, with the exception of callers with Sysop Status. Any caller with Sysop status can read, delete, and un-delete any message. Any caller with Sysop Status may enter messages into all Message Conferences even though the caller's security may not be equal to or greater than the Message Entry Security configured by the Sysop. The rivate command is a toggle that is available to callers with Sysop security and can be used to toggle a non-public message to public or a public message to non-public. The <C>opy command will allow a caller with Sysop security to move a message to another Message Conference or copy a message within the same conference and forward the message to another caller other than the original recipient of the message. 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 base, even if the message has been deleted. Those who see a message which has been marked for deletion may undelete it by using this command. Callers are not able to read deleted messages unless their access level is equal to or greater than Sysop Status. When a message is Undeleted, changed from Non-public to Public or changed from Public to Non-public, the message is re-displayed so the change can be verified. When a message is changed from Non-public to Public, an option is given which allows the message to be addressed to "All Callers". In the File Area, if a caller with Sysop Status attempts to upload a file that already exists, that caller is given the opportunity to overwrite the file. The caller is warned that the file already exists and is given the option to overwrite it. SPITFIRE does not allow any callers without Sysop Status this privilege. Page 129 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 13.1 - SPECIAL COMMANDS FOR SYSOP --------------------------------- The Sysop is determined within the ALT+Z configuration window. The name entered as Sysop Caller Name is used by SPITFIRE to determine the name of the Sysop. Messages left using the <C>omment to Sysop feature from the Main Menu feature are displayed to the person logging on under this name. The Sysop has some features available to them that no other callers have, regardless of the caller's security. When selecting the option to read messages, if recognized as the Sysop, the caller is prompted as to whether he/she wishes to preview messages. This feature allows the Sysop to read messages without the messages being marked as having been received. A handy use for this feature may be when Sysops don't have time to respond to all their messages. They can still read messages and respond to those they choose. Callers will not see that the Sysop has received the message and feel slighted by the fact that there is no response. Sysops can re-read messages later and respond when they have more time to devote to responding to messages. Also, those with Sysop-Level security have an "unlimited" number of daily node chats of "unlimited" duration. The Sysop of the BBS can enter a message to SFCALLER and SPITFIRE handles this as a message which is addressed to every caller on the board. So, when a caller logs on and performs a message scan, SPITFIRE will consider all messages addressed to SFCALLER as a message addressed to the current caller. Additionally, the Sysop of the BBS can enter a message addressed to SFCALLER<x>, where <x> is equal to a valid security level on the BBS. SPITFIRE will handle this as a message addressed to every caller of the board with the specified security level. In other words, when a caller with a security level of 10 logs on and performs a message scan, SPITFIRE will consider any messages addressed to SFCALLER10 as a message addressed to the current caller. It is important to know how SPITFIRE handles the SFCALLER and the SFCALLER<x> messages entered by the Sysop. For obvious reasons, the caller is not allowed to delete any message received by them and which is addressed to SFCALLER or SFCALLER<x>. Secondly, the date the caller last logged on to the BBS is compared to the date of the SFCALLER/SFCALLER<x> message to determine if the message should be displayed to the caller. If the date of the message is more recent than the date the caller last logged on, the message will be reported as an unreceived message to the caller when SPITFIRE performs a message scan. Page 130 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- When using this feature, the Sysop will need to assume some responsibility in regard to deletion of the message. Only the Sysop can mark a SFCALLER/SFCALLER<x> message for deletion. If such a message is entered in a conference that allows unreceived messages to be purged, it will purge when the message pack is performed and the message is older than the configured Purge Msgs Older Than value for that message conference. However, if the SFCALLER/SFCALLER<x> message is saved to a message conference that is configured to not purge unreceived messages, the Sysop must mark the message for deletion or it will never purge. SFCALLER/SFCALLER<x> MESSAGE TIP! The ability to enter a message that will never purge can actually work to the Sysop's advantage. For instance, if the Sysop would like to keep certain messages on their BBS indefinitely the SFCALLER messages provide the tools by which to accomplish this. Simply enter a SFCALLER/SFCALLER<x> message into a message conference that is configured to not allow unreceived messages to be purged. One example that comes to mind, is a general message to all callers that explains how to disable call waiting prior to calling the BBS. 14.0 - EVENTS MENU EXAMPLE -------------------------- It is possible for a Sysop to 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 + -]? 14.1 - EVENTS MENU EXPLANATION ------------------------------ <L>.... List An Event SPITFIRE supports 13 events <A..M>. Sysops who select this feature are asked which event <A..M> they wish to view. If the event selected is not configured, SPITFIRE states that this event is not active. If the event selected is configured, then SPITFIRE displays the time of the event, the day of the event, whether the event is active and whether it has been completed that day. Page 131 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <E>.... Enable An Event This feature is used to activate one of the 13 scheduled events available. Sysops who select this feature are asked which event they wish to enable. If they select one that is already active, SPITFIRE notifies them that the event selected is already active and they are asked whether they wish to change it. If the designated event is not active, Sysops are prompted to enter the time the event is to be activated (expressed in 24 hour format. Example: 22:00 = 10pm). Next they are asked on what day the event should be scheduled to take place. The format looks like this: 0=Sunday, 1=Monday, 2=Tuesday, etc....7=All! Sysops are then prompted as to whether the event should be marked as having been completed for the day. If they reply with N for No, and the event is configured to be executed at a time earlier than when it is created, the event is executed upon exiting the Events Menu. If they reply with N for No, and the event is configured to be executed at a time later than when it is created, it is executed at the next scheduled time. If they reply with Y, for Yes, the event is not executed until the next designated scheduled time after the day it is created. Finally, Sysops are prompted as to whether the event should be marked as an on-time event. For additional information regarding on-time events, refer to the following section, Important Note Regarding Scheduled Events of this manual. After having selected the desired scheduled event and establishing the time and day the event is to be performed, Sysops need to modify the SF.BAT file with their favorite text editor. For illustration purposes, let's assume Sysops wish to execute Buffalo Creek Software's SFLOG to create a bulletin of the weekly activity on their BBS. The SFLOG utility requires Sysops to specify the bulletin file name that the information will be written to by adding a "/BULLET<x>" parameter to the command line. Our example will use the file BULLET1. To simplify this explanation, assume all files are being run from the default directories, and the event will be event A. The Sysop will need to select <E>.... Enable An Event from the Sysop Utilities Menu and then choose A as the event to be created. They are then prompted for the time the event Page 132 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- will be performed. Let's assume a time of 01:00. Next, the Sysop is prompted for the day the event will be performed. Let's assume they wish to run the event every Sunday, so 0 is entered. When prompted whether to mark the event as being completed today, type Y. Finally, Sysops are prompted as to whether the event should be an on-time event and N is entered. The SF.BAT file for Event A will look like this: :EVENT_A REM Place Event Commands Here GOTO LOOP What is required next is to include all necessary DOS commands which are needed to run the SFLOG program and enter those in place of the "REM Place Event Commands Here". A completed SF.BAT for Event A appears as: :EVENT_A CD\SF\WORK SFLOG /BULLET1 COPY BULLET1.* \SF\DISPLAY ERASE BULLET1.* CD\SF GOTO LOOP With the event set up as described, every Sunday morning at 1:00 am (or immediately after a caller logs off since it has not been marked as an on-time event), SFLOG creates a bulletin of the BBS weekly activity. SFLOG must be located in the same directory as the CALLERS.LOG (WORK). Therefore, the batch begins by changing to that directory. SFLOG is then executed and the BULLET1.BBS/CLR display files are created. Next, the bulletins are copied to the DISPLAY file directory and to conserve disk space, the BULLET1.BBS/CLR files in the WORK directory are deleted. <D>.... Disable An Event This feature is used to disable an event that has been previously configured. If the event is currently active, SPITFIRE asks the Sysop whether they are certain they want to disable it. Responding with "Yes" disables the scheduled event. <Q>.... Quit This feature takes the caller from the Events Menu and returns them to where SPITFIRE was prior to calling up Page 133 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- the Events Menu, either the "SPITFIRE ready..." prompt or the Sysop Utilities Menu. <+>.... Next Event This option is used to move forward from one Event to another. Pressing the "+" key progresses from one event to the next in alphabetical order. When the last event is reached (Event M) and the "+" key is pressed SPITFIRE cycles to the first event, Event A. <->.... Previous Area This option enables Sysops to cycle through the Events in reverse order. Pressing the "-" key moves to the preceding event. From Event A, if the "-" key is pressed SPITFIRE will cycle to Event M, the last event. IMPORTANT NOTE REGARDING SCHEDULED EVENTS! ------------------------------------------ SPITFIRE has the capability of marking an event as an "on-time" event, which causes the event to be executed at the exact time for which it has been set up. If 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 time the caller has remaining, then SPITFIRE reduces the amount of the caller has 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 reduced to 25 minutes. **NOTE** Even though an event is marked as an on-time event, it is possible that a caller could gain additional time on the BBS preventing the event from being executed on-time. For example, the BBS could be configured to allow additional time for file uploads (i.e. 2 to 1 time compensation for uploads) or offer time bank programs where the caller can withdraw stored online time. Marking an event as on-time event might be necessary for running programs that require a specific time to be executed. Such an instance might be importing daily net-mail packets where Sysops are given a designated amount of time for connecting with their net-mail hub. Usually configuring an event to activate "on-time" is not necessary. When an event is not marked as an on-time event, unlike most other Bulletin Board Systems, if a caller is on-line when an event is Page 134 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- scheduled to occur, SPITFIRE waits until the caller logs off and then performs the scheduled event. In this fashion, the caller is not interrupted or subjected to a forced log-off. Please note that 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. In addition to messages marked for deletion, messages are purged based on how the Sysop has configured the Message Conference Record. The options which determine which messages will be purged include Purge Msgs Older Than, Purge Unreceived Msg, and Purge Old Thread Msg. Purge criteria is configured individually for each Message Conference that is available on the BBS. Refer to the section - CONFIGURING MESSAGE CONFERENCE RECORDS for more information regarding these options. Immediately after completing the scheduled event M, SPITFIRE looks for SFMSGPCK.BAT in the work file directory. If it exists, SPITFIRE shells to and executes the commands within the SFMSGPCK.BAT. This batch is intended to perform duties required by some net-mail utility drivers. If SFMSGPCK.BAT is not found or once it has been completed, SPITFIRE returns to the "Ready..." prompt. Packing the message base should be done routinely to conserve disk space. 15.0 - 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. SFGUESS is included in the SPITFIRE Bulletin Board System distribution package and can be played on a SPITFIRE BBS after it has been installed. What follows is a step-by-step set up procedure for SFGUESS. This is provided to demonstrate the process and assist Sysops in future door installations. A brief explanation of the SPITFIRE Door Menu structure is beneficial to understanding the installation of a SPITFIRE door. SPITFIRE supports up to 24 doors. Alphabetical characters are used to initiate the door commands, A through Z, with two exceptions. The G (Goodbye) is used to log the caller off the BBS and Q (Quit) returns the caller to the Main Menu. Therefore, the SFDOOR.MNU file can have a maximum of 24 lines, one for each door program available on the system. For this example, it is assumed that there are not any doors presently set up. It is also assumed that SPITFIRE is being run on Page 135 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- drive C in a directory named SF. In the event Sysops are running SPITFIRE on a different drive and/or in a different directory than C:\SF, then the SF.BAT file example (listed below) will have to be altered to reflect the correct drive and directories appropriate to your system configuration. What follows is a step-by-step description of the procedure utilized to configure a SPITFIRE Door. The first thing to do is create the file named SFDOOR.MNU, using a text editor that saves in ASCII text. When created, SFDOOR.MNU is placed in the system files directory. When configuring only door A, SFDOOR.MNU will have only 1 line. For demonstration purposes, this line can look like any of these: Guess A Number,SEC>=10 Guess A Number,SEC=10 Guess A Number,SEC<10 The name of the door (as it appears in the Door Menu) comes first in the line and is limited to 25 characters. This is followed by a comma, which is used to tell SPITFIRE where to end the name of the door and where to start reading the security level required to access the door. The Sysop controls access to the door through the security function. Using SEC>=[x], where [x] is the numeric value of the security level, any caller with a security equal to or greater than [x] can access the door. If SEC=[x] is used, a caller with a security level of [x] can access the door and if SEC<[x] is used only a caller with a security level less than [x] can access the door. For our example, Guess A Number,SEC>=10 will be used. Therefore, this door does not display to any caller with a security level less than 10. Buffalo Creek Software provides a menu driven utility that easily creates and/or modifies the SFDOOR.MNU file. SFDOOR.ZIP is included in the SPITFIRE package and can be downloaded from Buffalo Creek's BBS. The next step in setting up the door is to create a sub-directory of the SF directory named DOOR_A and move the SFGUESS.EXE file into the DOOR_A directory. The DOS manual can be referred to for information on how to create directories. Edit the SF.BAT file with your favorite text editor. At the point where the SF.BAT file reads :DOOR_A place the commands needed to run the door (these must be valid DOS commands) between the :DOOR_A and the GOTO LOOP statements. For SFGUESS, that portion of the SF.BAT file should be changed to read as listed below: Page 136 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- :DOOR_A COPY SFDOORS.DAT C:\SF\DOOR_A CD\SF\DOOR_A SFGUESS ERASE SFDOORS.DAT CD\SF GOTO LOOP :DOOR_B After saving the changes in the SF.BAT file to disk, boot SPITFIRE using the SF.BAT file. At the "SPITFIRE ready for..." prompt, log on locally either using the ALT+S or ALT+Q keystrokes. At the Main Menu, select "<S>... SPITFIRE Doors". The Door Menu should appear something like this: >>>>>>>>> DOOR MENU <<<<<<<<< <A>... Guess A Number <?>... Door Bulletins <Q>... Quit <G>... Goodbye DOOR MENU - <A ? Q G>? If <A> is selected from the menu, SPITFIRE displays a message that states "Executing Door A... Please stand by!". At this point, SPITFIRE writes a text file named SFDOORS.DAT and a file named DOOR.SYS to the drive. (SFDOORS.DAT contains necessary caller information for executing doors on a SPITFIRE BBS and DOOR.SYS is the universally accepted format containing caller information by those attempting to standardize the door caller information file. These files are created when a caller enters a door and SFDOORS.DAT is automatically erased when the caller returns to SPITFIRE.) SPITFIRE, after creating the SFDOORS.DAT and DOOR.SYS files, terminates, sending the appropriate DOS ERRORLEVEL to the SF.BAT file. In the case of door A, SPITFIRE sends an ERRORLEVEL of 34 to SF.BAT which causes the commands placed between :DOOR_A and GOTO LOOP to be executed. In the event the correct commands were entered between :DOOR_A and GOTO LOOP, SFGUESS will run. When the door is finished running, control is returned to SPITFIRE. If the Sysop has the BBS configured to require a password when returning from a door, the caller is prompted to enter their password and the caller is returned to the Door Menu of the BBS. If a caller enters a door while logged on SPITFIRE, there are up to three tests SPITFIRE performs when a caller returns to SPITFIRE, after exiting the door program. First, SPITFIRE must find SFDOORS.DAT in the system files directory. Second, SPITFIRE must find a carrier detect. And third, if the Sysop has configured the BBS to require a password when returning from a door, the caller must enter the correct password when prompted for it. In the event a door is entered during a local log on, SPITFIRE will perform the following test(s): SPITFIRE Page 137 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- must find the SFDOORS.DAT file and, if the Sysop has configured the BBS to require a password when returning from a door, the correct password must be entered. There are numerous door programs, usually Shareware products, available for download from Buffalo Creek's BBS as well as most other bulletin boards. Sysops who do not wish to run third party programs through SPITFIRE Door feature, should set the security level of the SPITFIRE Door command in the SFMAIN.MNU file high enough so that callers cannot access it. SPITFIRE Doors can be accessed by a caller from the Main 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 available that will expand this to hundreds of doors. An example of such a program is WILDFIRE, which is a Shareware program by Steve Cox. The newest release of WILDFIRE can be downloaded from Buffalo Creek's BBS and Flite-Line BBS at (402) 421-2434. 15.1 - SPITFIRE DOORS DISPLAY FILES ----------------------------------- SPITFIRE uses certain display files during the execution of the Doors feature, if such files are found. However, it is important to note that SPITFIRE works perfectly without these display files. Listed below are the display files that can be used in conjunction with the SPITFIRE door feature: SFDORBUL .[BCR] - Non-ANSI/ANSI/RIP list of door bulletins which are available to the caller. This is displayed to the caller just prior to the door menu (if available) or when selecting the <?> command from the door menu. (DISPLAY) DORBUL<x>.[BCR] - Non-ANSI/ANSI/RIP bulletin file that is displayed when the corresponding <x> is selected from the SPITFIRE door bulletin list. These files are often used to display top score bulletins created by many of the available door game programs. (DISPLAY) SFDR<x> .[BCR] - Non-ANSI/ANSI/RIP door display menu file displayed to the caller with a corresponding <x> security level. (DISPLAY) SFDOOR<x>.[BCR] - Non-ANSI/ANSI/RIP screen that is displayed to the caller after selecting the corresponding <x> door Page 138 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- option and prior to the <x> door being executed. This file might be used to send callers a special message about the door. (DISPLAY) SFDORBAK .[BCR] - Non-ANSI/ANSI/RIP screen displayed to the caller after quitting the door program and prior to returning to SPITFIRE. This is normally used simply to welcome the caller back to SPITFIRE. (DISPLAY) 15.2 - SPITFIRE DOORS SUPPORT ------------------------------ Configuring the use of doors with SPITFIRE is supported by Buffalo Creek Software for registered users of SPITFIRE. Please keep in mind once a caller executes a door, SPITFIRE is totally terminated from memory and control is passed to the SF.BAT where the commands configured by the Sysop are executed. Sysops who have problems with the door program itself should read the documentation and then contact the author of the program. Once a caller has entered a door, SPITFIRE is completely out of memory and has NO responsibility for the operation of the door program! 16.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. For instance, JModem, HS/Link and GSZ (Graphical ZModem) are just a few of transfer protocols which are available. There are no External Protocols distributed with SPITFIRE because they are usually Shareware products written by other programmers. Buffalo Creek Software most likely has no right to distribute them with the SPITFIRE program. However, there are many available for download from Buffalo Creek's BBS, as well as most other bulletin boards. It should be noted that SPITFIRE does not allow callers to select an external protocol as their default file transfer protocol. This is important for callers to know, so SPITFIRE has provided a means to notify the caller that External Protocols exist. When a new caller logs on for the first time and SPITFIRE is configured to require the New Caller Default Protocol option to display or when callers use the "<Y>... Your Statistics" from the Main Menu to change their default file transfer protocol, SPITFIRE displays SFPROMSG.[BCR] just before a default file transfer protocol selection is made. The SFPROMSG.[BCR] message should be used to inform callers Page 139 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- that if a default file transfer protocol is selected, the external protocol option will not be available to them. Callers wishing to utilize external protocols should set their default to <S>.. Select At Time Of Transfer. 16.1 - EXTERNAL DOWNLOAD PROTOCOLS ---------------------------------- SPITFIRE allows up to 14 external protocols <A..N> to be utilized for downloads. It may be best at this point to go through setting up an external download protocol, step by step. To start, an assumption is being made that Sysops have a copy of JModem. Those without a copy may download it from Buffalo Creek's BBS. Sysops will need to use their favorite text editor to create a display file named SFEXTDN.BBS. This is a simple text file which will contain the names of the external protocols that are available to callers. For the purpose of setting up JModem as the first external download protocol, the SFEXTDN.BBS file has only one line and looks something like this: <A> JModem Sysops need to place SFEXTDN.BBS in the directory configured as the Display Files Path. To verify, or modify, the EXTERNAL TRANSFER FILE PATH, press ALT+P at the SPITFIRE "Ready..." prompt. Selecting option D allows modification of SPITFIRE's default setting. An assumption (for demonstration purposes) is being made here that SPITFIRE is run on the C drive in a directory named SF and that the External Transfer path is C:\SF\EXTNOD1. The next step is to place JModem in the directory set up as the External Transfer Path (for our example, C:\SF\EXTNOD1). Next, using your favorite text editor, a batch file is created and named SFEXTDNA.BAT. SFEXTDNA.BAT must be placed in the directory designated as the External Transfer Path. SPITFIRE shells to this batch file whenever 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\EXTNOD1 JMODEM S%2 %3 CD\SF BRK ON Page 140 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Now that SFEXTDNA.BAT, with the above listed commands, resides in the directory set up as the External Transfer Path, the first External Download Protocol has been configured. The actual contents of the batch files in use depends upon the specific protocols. The above is only a sample batch file that should work well with JModem. 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 (SFEXTDN.BBS), SPITFIRE shells to the batch file named SFEXTDNB.BAT. As stated before, there are fourteen external protocols allowed and are denoted by command letters "A" thru "N". These command letters are used to shell from SPITFIRE to the corresponding batch files. A = SFEXTDNA.BAT B = SFEXTDNB.BAT C = SFEXTDNC.BAT D = SFEXTDND.BAT E = SFEXTDNE.BAT F = SFEXTDNF.BAT G = SFEXTDNG.BAT H = SFEXTDNH.BAT I = SFEXTDNI.BAT J = SFEXTDNJ.BAT K = SFEXTDNK.BAT L = SFEXTDNL.BAT M = SFEXTDNM.BAT N = SFEXTDNN.BAT An explanation of these batch files and what SPITFIRE does in preparation to use these batch files is appropriate and important for Sysops to understand. When an External Protocol is selected, SPITFIRE does all the normal tests to be sure it is permissible for the caller to perform the download. If allowable, then SPITFIRE copies the selected file to the directory configured as the External Transfer Path. PLEASE NOTE THAT SPITFIRE COPIES THE SELECTED FILE. THIS MEANS THERE MUST BE ENOUGH DISK SPACE AVAILABLE FOR THE FILE TO BE COPIED. If all tests are passed and the file is successfully copied, SPITFIRE switches to the directory configured as the External Transfer Path and stays in memory but shells to the appropriate batch file (as described above). Keep in mind that SPITFIRE is resident in memory, as well as a second copy of the command processor (COMMAND.COM) so the external file transfer protocol requires some memory. Therefore, the minimum memory requirement of 256K, stated earlier in the manual, may be insufficient for systems including the external protocol file transfer options. Upon performing this shell, SPITFIRE passes at least three parameters to the appropriate batch file. The first parameter is the baud rate. The second parameter being passed is the number of the COM 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 file name is passed in ASCII text as %3. The baud rate passed as %1 is a number representing baud rate of the caller, such as 2400. The COM Page 141 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- port, %2, is the number of the COM port in use (1 through 8). Those who are not familiar with the use of the % command in batch files, should refer to the DOS manual for specific details. When the external protocol file transfer program has finished its work, control is automatically returned to SPITFIRE. Once control is returned, SPITFIRE switches back to the directory in which the SPITFIRE system files reside. Next, SPITFIRE erases the file that was copied to the directory configured as the External Transfer Path for download. Finally, SPITFIRE checks the amount of time that has passed during the shell to the external protocol batch file. In the event SPITFIRE discovers that the time spent in the shell was at least 30% of the estimated transfer time, the number of downloads, K downloaded, etc. of the caller is updated. In the event the time spent in the shell was less than 30% of the estimated transfer time, then SPITFIRE assumes that the transfer was not successful and the caller's data is not updated. Sysops will notice the example batch file (above) has a command to change to the directory configured as the External Transfer Path. They will also notice there is a another command to change back to the SPITFIRE system files directory. These commands do not have to be in the batch files created because SPITFIRE will automatically perform these chores. However, it is quite permissible for the commands to be in the batch file where they can act as a safeguard. Sysops will finally notice a command BRK OFF at the beginning of the batch file example, as well as a BRK ON at the end. BRK is a Shareware utility distributed by Solid Systems of Newport News, Virginia. It is used to disable and enable the CTRL+BREAK, which can be used to terminate a batch file. Sysops may need this utility for the protection of their systems. BRK.ZIP can be downloaded from Buffalo Creek's BBS. 16.2 - EXTERNAL BATCH DOWNLOAD PROTOCOLS ---------------------------------------- SPITFIRE also allows for batch downloads to be transferred with the use of external protocols, provided the external protocol is written to include batch transfers. Much of the information discussed in the section - EXTERNAL DOWNLOAD PROTOCOLS - also applies to the External Batch Download Protocols. However, there are some significant differences which warrant mentioning. The SFEXTDN.BBS file is created using your favorite text editor. It lists the names of the external batch file protocols that are available. On the same line, the protocol description is followed by a comma and the word BATCH. For the batch protocol example, GSZ will be used and the SFEXTDN.BBS file might now look like this: Page 142 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- <A> JModem GSZ Graphic ZModem Batch,Batch The SFEXTDN.BBS must reside in the path defined as the Display File Path. The GSZ.EXE must be placed in the directory configured as the External File path. Again, using the text editor, create a SFEXTDN<A..N>.BAT file which contains the commands necessary to execute the batch download. Using the above example, SFEXTDNB.BAT needs to be created to perform external Graphic ZModem batch downloads from SPITFIRE. The commands for the SFEXTDNB.BAT file should look like this: BRK OFF ECHO OFF ECHO EXECUTING EXTERNAL PROTOCOL # 2 CD\SF\EXTNOD1 GSZ %2 sz %3 %4 %5 %6 %7 %8 %9 CD\SF BRK ON The commands used for GSZ , Graphic ZModem batch, pass the same command line parameters (explained above in the EXTERNAL DOWNLOAD PROTOCOLS section) as the single file ZModem transfer with the addition of %4, %5, %6, %7, %8, %9. The %3 through %9 are the file names the caller enters if the batch download external protocol is selected. SPITFIRE allows up to seven files to be transferred during an external batch download. %3 through %9 represent the file names the caller includes in the batch queue. When an External Protocol is selected, SPITFIRE does all the normal tests to be sure it is permissible for the caller to perform the download. If allowed, SPITFIRE copies the selected files to the directory configured as your External Transfer Path. PLEASE NOTE THAT SPITFIRE COPIES THE SELECTED FILES. WITH EXTERNAL BATCH DOWNLOADS IT IS DOUBLY IMPORTANT THAT ENOUGH DISK SPACE BE AVAILABLE FOR THE FILES TO BE COPIED. However, in adding files to the batch queue if SPITFIRE discovers the addition of another file exceeds the amount of available disk space or exceeds the number of daily allotted downloads for the caller, an appropriate message is displayed prior to downloading the files presently in the batch queue. 16.3 - TEXT FILE EXTERNAL BATCH DOWNLOAD PROTOCOLS -------------------------------------------------- SPITFIRE can be configured to create a text file in the EXTERNAL directory which contains a list of the files to be downloaded. By using the file list, the path and name of each file is stored in a text file. By using the text file, it is no longer necessary for SPITFIRE Page 143 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- to copy the files into the EXTERNAL directory. It should be mentioned that the external protocol must have the capability of reading this text file. GSZ, Graphical ZModem, is one such external protocol. There are several advantages to using this particular method with batch transfer protocol downloads. First, because files are no longer required to be copied to the EXTERNAL directory, downloads can be performed much faster. Speed is important for multi-node systems. Secondly, you eliminate the risk of running out of disk space since files are duplicated when copied to the EXTERNAL directory for downloading. Also, the number of files that can be downloaded in a single batch transfer is significantly increased using the text file. Where the typical batch download (discussed in the previous section of the manual) allows 7 files to be downloaded per batch; using the text file allows up to 99 files to be downloaded per batch. To initiate an external batch download protocol using a text file, simply add ,UseFile at the end of the line of your SFEXTDN.BBS where the text file feature is to be used. For example, here is a sample SFEXTDN.BBS: <A> JModem GSZ ZModem Batch,Batch,UseFile The SFEXTDN.BBS must reside in the path assigned as the Display File Path. Place GSZ.EXE in the directory configured as the External File path. Using your favorite text editor, Sysops should next create the appropriate SFEXTDN<A..N>.BAT file which contains the commands necessary to execute the batch download. In the above example, SFEXTDNB.BAT is created to perform an external GSZ batch download from SPITFIRE. The commands for the SFEXTDNB.BAT file should look like this: BRK OFF ECHO OFF ECHO EXECUTING EXTERNAL PROTOCOL # 2 CD\SF\EXTNOD1 GSZ %2 sz @C:\SF\EXTNOD1\SFEXTRAN.LST IF ERRORLEVEL 1 GOTO END IF ERRORLEVEL 0 GOTO GOOD :GOOD APPENDIT ZMODEM.TXT \SF\CALLERS.TMP :END CD\SF BRK ON Page 144 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Note that the commands used in the SFEXTDNB.BAT (above example) uses the text file C:\SF\EXTNOD1\SFEXTRAN.LST. This is the text file where SPITFIRE stores the names of the files which the caller has selected for download. It should again be noted that when an External Protocol is selected, SPITFIRE does all the normal tests to be sure it is permissible for the caller to perform the download. In adding files to the batch queue if SPITFIRE discovers the addition of another file exceeds the number of daily allotted downloads for the caller, an appropriate message is displayed prior to downloading the files presently in the batch queue. 16.4 - EXTERNAL UPLOAD PROTOCOLS -------------------------------- SPITFIRE allows up to 14 external protocols <A..N> to be utilized for uploads. Since SPITFIRE handles external protocols for uploading slightly different than downloading, it is a good idea at this point to go through setting up an upload external protocol, step by step. To begin, Sysops need to obtain a copy of JModem. Those without a copy can download it from Buffalo Creek's BBS. Using your favorite text editor, create a display file named SFEXTUP.BBS. This is a simple text file which contains the names of the external protocols which are available. For the purpose of setting up JModem as the first upload external protocol, the SFEXTUP.BBS file has one line that looks something like this: <A> JModem SFEXTUP.BBS is placed in the directory configured as the Display Files Path. To verify, or modify, the EXTERNAL TRANSFER FILE PATH, press ALT+P at the SPITFIRE "Ready..." prompt. Selecting option D allows modification of SPITFIRE's default setting. An assumption (for demonstration purposes) is made that SPITFIRE is run from drive C in a directory named SF with an External Transfer path of C:\SF\EXTNOD1. The next step is to place JMODEM in the directory set up as the External Transfer Path (example... C:\SF\EXTNOD1). Next, using your favorite text editor, a batch file is created named SFEXTUPA.BAT in the directory designated as the External Transfer Path. SPITFIRE shells to this batch file when a caller selects <A>... from the upload protocol list. At this point, prior to executing the commands within the batch file, SPITFIRE sets the attribute of all files contained in the External Transfer Path (in this example, C:\SF\EXTNOD1) to Read Only. This is done to prevent callers from uploading and overwriting files which exist in your External Transfer Path. It is appropriate at this point to show the suggested contents of this batch file: Page 145 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Echo Off BRK OFF Echo Executing External Protocol #1 CD\SF\EXTNOD1 JMODEM R%2 %3 CD\SF BRK ON Now that SFEXTUPA.BAT, with the above listed commands, resides in the directory set up as the External Transfer Path, the first upload External Protocol is successfully configured. The actual contents of the batch files used will depend on the specific protocols. The above is only a sample batch file and should work well with JModem. 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 (SFEXTUP.BBS), SPITFIRE shells to a batch file named SFEXTUPB.BAT. As stated before, there are fourteen external protocols allowed and they are denoted by command letters "A" thru "N". Through their use, SPITFIRE shells to the corresponding batch files. A = SFEXTUPA.BAT B = SFEXTUPB.BAT C = SFEXTUPC.BAT D = SFEXTUPD.BAT E = SFEXTUPE.BAT F = SFEXTUPF.BAT G = SFEXTUPG.BAT H = SFEXTUPH.BAT I = SFEXTUPI.BAT J = SFEXTUPJ.BAT K = SFEXTUPK.BAT L = SFEXTUPL.BAT M = SFEXTUPM.BAT N = SFEXTUPN.BAT Now, an explanation of these batch files and what SPITFIRE does in preparation to use them is appropriate and important for the Sysop to 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 are passed, SPITFIRE changes to the directory configured as the External Transfer Path. SPITFIRE stays resident in memory but shells to the appropriate batch file (as described above). Keep in mind that SPITFIRE is resident in memory as well as a second copy of the command processor (COMMAND.COM), consequently the external file transfer protocol is going to require some memory. Therefore, the minimum memory requirement of 256 K stated earlier in the manual, may be insufficient for systems including the external protocol file transfer options. Upon performing this shell, SPITFIRE is passing four parameters to the appropriate batch file. The first parameter is the baud rate. The second parameter passed is the number of the COM 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 Page 146 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- external file transfer programs and can now be used with DOS batch commands. The file name is passed in ASCII text as %3. The baud rate, %1, is a number representing baud rate of the caller, such as 2400. The COM port, %2, is the number of the COM port being used (1 through 8). Sysops who are not familiar with the use of the % command in batch files should refer to their 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, SPITFIRE resets the attributes of all files in the External Transfer Path (in this instance, C:\SF\EXTNOD1) back to archive. Then, SPITFIRE changes back to the directory in which the SPITFIRE system files reside. SPITFIRE now checks to see if the file that was to be uploaded exists in the File Area in which the uploaded file should reside, if all went correctly. If SPITFIRE finds the file in the appropriate File Area, the caller is credited with the upload and other clean-up chores are performed. SPITFIRE will then automatically move the uploaded file to the directory the Sysop has configured as the file upload path (i.e. - C:\SF\UPLOADS). In the event SPITFIRE does not find the file in the appropriate File Area, SPITFIRE assumes that the upload was aborted. Notice that the example batch file (above) has a command to change to the directory configured as the External Transfer Path. Also notice that there is a another command to change back to the SPITFIRE system files directory. These commands do not have to be in the batch files created because SPITFIRE automatically performs these chores. However, it is quite permissible for them to be in the batch file so they can act as a safeguard. Finally, notice a command BRK OFF at the beginning of the batch file example, as well as a BRK ON at the end. BRK is a Shareware utility distributed by Solid Systems of Newport News, Virginia. It is used to disable and enable the CTRL+BREAK, which can be used to terminate a batch file. Sysops may need this utility for the protection of their systems. BRK.ZIP can be downloaded from Buffalo Creek's BBS. 16.5 - EXTERNAL BATCH UPLOAD PROTOCOLS -------------------------------------- SPITFIRE also allows for batch uploads to be transferred with the use of external protocols, provided the external protocol is written to include batch upload transfers. Much of the information discussed in the EXTERNAL UPLOAD PROTOCOLS section of this manual also applies to External Batch Upload Protocols. However, there are some significant differences which warrant mentioning. When creating the SFEXTUP.BBS file, Sysops should use their favorite text editor to list the name of the external batch file protocol that Page 147 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- is available. On the same line, the protocol description is followed by a comma and the word BATCH. For the batch upload protocol GSZ will be used as the example. The SFEXTDN.BBS file might now look like this: <A> JModem GSZ Graphical ZModem Batch,Batch The SFEXTUP.BBS must reside in the path assigned as the Display File Path. GSZ.EXE must be placed in the directory configured as the External File path. Next, using a favorite text editor, a SFEXTUP<A..N>.BAT file is created which contains the commands necessary to execute the batch upload. Using the above example, SFEXTUPB.BAT needs to be created to perform external GSZ 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\EXTNOD1 GSZ %2 restrict rz CD\SF BRK ON Note, when using GSZ, do NOT list the % file and path parameters on the command line or it is possible that the uploaded files will end up with the wrong names. For example, say the caller entered the first file name to upload as FILE1.ZIP and the second file to be uploaded as FILE2.ZIP. Then, rather than sending FILE1.ZIP first, FILE2.ZIP was sent first and FILE1.ZIP was sent second. FILE1.ZIP would be named FILE2.ZIP and FILE2.ZIP would be named FILE1.ZIP. However, the lack of % file parameters allows GSZ to receive more files than the number specified by the caller. To overcome this problem, SPITFIRE creates a simple little text file containing the names of all files within the External Transfer Path just prior to shelling to the appropriate batch file. When control is returned to SPITFIRE, it checks the files in the External Transfer directory against the files listed in the previously created text file. If any additional file(s) are found, and if such file(s) do not already exist in a File Area, SPITFIRE prompts the caller for a description of the file. If a description is entered by the caller, then SPITFIRE moves the file to the appropriate File Area and updates the SFFILES.BBS. If the caller hangs up or does not enter a description, SPITFIRE uses the default description, "No Description Provided". The "restrict" parameter is a feature of GSZ which prevents the uploader from specifying the file path when uploading to the BBS. Page 148 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- If the external protocol requires the passed parameters, it should be noted %4 represents the directory the Sysop has designated as the upload directory and %3, %5, %6, %7, %8, %9 represent the file names. SPITFIRE allows up to six files to be uploaded during an external batch upload. After selecting the batch transfer protocol the caller is prompted to enter the name of the file to be uploaded and provide a brief description for each file to be uploaded. As explained in the EXTERNAL UPLOAD PROTOCOLS section of this manual, SPITFIRE automatically moves the uploaded file(s) to the directory the Sysop has configured as the upload file path. 16.6 - EXTERNAL BI-DIRECTIONAL FILE TRANSFER PROTOCOLS ------------------------------------------------------ External protocols which support simultaneous uploading and downloading are referred to as bi-directional protocols. In other words, having bi-directional file transfer protocols available enables the BBS to send and receive files at the same time. Before attempting to explain the installation of bi-directional file transfer protocols on a SPITFIRE BBS, it may be beneficial to review how SPITFIRE processes a bi-directional file transfer request. When a caller initiates a download using a bi-directional file transfer protocol, SPITFIRE checks the amount of disk space available and compares it to what the Sysop has configured using the ALT+Z's Upload Disk Space Requirement option. If disk space is not sufficient to allow uploads, the caller receives a message explaining, "...disk space currently prohibits uploads" and the transfer process is aborted. Provided the available disk space is sufficient to permit uploads, the caller is prompted to enter the name of the file to be downloaded. If the caller has tagged files for downloading, SPITFIRE automatically defaults in the file name(s) with the name of the file(s) tagged by the caller. If no files have been tagged, the caller must type in the file name(s). SPITFIRE will continue to prompt the caller for a file name until no name is entered. After completing the download information, SPITFIRE prompts the caller to enter the file name and file description of the file(s) to be uploaded. SPITFIRE will continue to prompt the caller for a file name and description until none is entered. At that time, SPITFIRE immediately shells to the appropriate batch file so that the file transfer can begin. When the bi-directional file transfer program is completed, control is automatically returned to SPITFIRE. Page 149 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Normally SPITFIRE determines the amount of time a caller should be compensated for uploads according to the amount of time required for the transfer process. However it is impossible to determine what amount time in the bi-directional transfer was spent uploading. Therefore, at the conclusion of the bi-directional file transfer, SPITFIRE checks the size of any files which were uploaded, calculates an approximate upload time and compensates the caller accordingly. SPITFIRE's support of bi-directional file transfer protocols allows them to be installed on a SPITFIRE BBS in much the same manner as other external protocols. HS/Link, by Samuel H. Smith, will be used to explain the process of setting up a bi-directional file transfer protocol on a SPITFIRE BBS. To begin, Sysops will need to use their favorite text editor to create or modify their existing SFEXTDN.BBS. This is a simple text file which will contain the names of the external protocols that are available on the BBS. Each line in SFEXTDN.BBS should contain the letter A through N which is used by the caller to select the respective download protocol and the title of transfer protocol (which will display to the caller). For bi-directional file transfer protocols these need to be followed by a comma and the term "bi-directional" (without the quotes). Building on the SFEXTDN.BBS created earlier (refer to section, External Batch Download Protocols) our sample SFEXTDN.BBS might look like this: <A> JModem GSZ Graphical ZModem Batch,Batch <C> HS-Link Bi-Directional Protocol,Bi-Directional When the ",bi-directional" is found on a line of the SFEXTDN.BBS, SPITFIRE automatically assumes a batch mode and a usefile mode. In other words, you are not required to include a ",batch" or ",usefile" on the menu line for bi-directional file transfer protocols. (Refer to the sections External Batch Download Protocols and Text File External Batch Download Protocols for further explanation of the Batch and Usefile features in SPITFIRE.) Sysops need to place SFEXTDN.BBS in the directory configured as the Display Files Path. The HS/Link executable file (HSLINK.EXE) must be placed in the directory configured as the External Transfer Path. To verify, or modify, file paths in SPITFIRE, press ALT+P at the SPITFIRE "Ready..." prompt. For the purpose of demonstration, an assumption is being made that SPITFIRE is being run on drive C in a directory named SF and that the External Transfer file path is C:\SF\EXTNOD1. As stated earlier in this documentation, SPITFIRE supports up to 14 external protocols <A..N> to be utilized for downloads. Unlike Page 150 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- other external download protocols which use batch files named SFEXTDN<A..N>.BAT, bi-directional file transfers are initiated by batch files named SFEXTBI<x>.BAT. <x> can be any letter A through N and must match the character which the caller uses to select the the respective file transfer protocol. In other words, if the bi-directional transfer protocol is option <A> from the caller's menu (SFEXTDN.BBS) the batch file would be named SFEXTBIA.BAT, if the bi-directional transfer protocol is option <E> from the caller's menu (SFEXTDN.BBS) the batch file would be named SFEXTBIE.BAT, etc. Using the example above, our sample batch file would be named SFEXTBIC.BAT. Next, using your favorite text editor, create the appropriate SFEXTBI<x>.BAT file which contains the commands necessary to execute the bi-directional file transfer. Using the above example, a SFEXTBIC.BAT needs to be created to perform the HS/Link bi-directional transfers. SPITFIRE will shell to this batch file when a caller selects <C>... from the download protocol list. The contents of our sample SFEXTBIC.BAT file might look like this: @Echo Off BRK OFF HSLINK -P%2 @C:\SF\EXT\SFEXTRAN.LST BRK ON The actual contents of the batch files in use depends upon the specific protocol. The above is only a sample batch file that should work well with HS/Link. The bi-directional file transfer protocol batch file (SFEXTBI<x>.BAT) must reside in your SPITFIRE External Transfer file path directory after it is created. 16.7 - EXTERNAL PROTOCOL SUPPORT -------------------------------- Configuring the use of external file transfer protocols is supported by Buffalo Creek Software for registered users of SPITFIRE. Those who have problems with the external file transfer program itself are urged to read the documentation and then contact the author of the program. 17.0 - HARDWARE/SOFTWARE DATA FLOW CONTROL ------------------------------------------ When Sysop selects ALT+M to configure their modem, they will notice a DTE Locked option. This switch is turned on (set to Yes) when using a modem that automatically adjusts to the baud rate of the incoming call rather than depending upon the software to reset the baud rate of the COM port. If the switch is set to Yes, then SPITFIRE does Page 151 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- not adjust the COM port to the baud rate of the incoming call. If the switch is set to No, then SPITFIRE monitors the speed of the incoming call and will adjust the COM port speed to match the baud rate of the incoming call. It should be mentioned, most modems manufactured today have the capability of locking the DTE and in most instances, should be configured to handle the port monitoring rather than SPITFIRE. Those who are not sure if their modem is capable of DTE locking (adjusts to the baud rate of the incoming call) should refer to their modem manual. 18.0 - ADDITIONAL SPITFIRE FEATURES ----------------------------------- There are some additional features in SPITFIRE which merit mentioning so the Sysop is fully aware of SPITFIRE's capabilities. 18.1 - SCREEN SAVE FEATURE -------------------------- SPITFIRE contains its own Screen Save Feature to prevent screen burn. Sysops who are presently using a memory-resident screen save utility should discontinue its usage and instead use the screen save feature included in SPITFIRE. 18.2 - SPITFIRE UTILIZES EMS (Expanded Memory) ---------------------------------------------- Upon boot-up, SPITFIRE automatically attempts to copy SPITFIRE.OVR to EMS. If there is adequate EMS available, SPITFIRE will access it from there. This will increase the speed at which SPITFIRE operates and save wear and tear on the drive. If this is done, SPITFIRE upon boot-up displays the message "EMS memory is used for SPITFIRE.OVR". 18.3 - SPITFIRE RECORDS CALLER ID INFORMATION --------------------------------------------- SPITFIRE is capable of recording Caller ID information to the CALLERS.LOG. However, before SPITFIRE will record the Caller ID information, certain criteria must be met. The BBS must be connected to a phone line and modem which supports Caller ID and the modem must be configured so it will report the Caller ID information. If these conditions are met, SPITFIRE will record any valid phone number to the CALLERS.LOG. Page 152 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 19.0 - SPITFIRE NET-MAIL CAPABILITIES ------------------------------------- SPITFIRE supports net-mail in three basic formats. In the first format, SPITFIRE is used in conjunction with a front-end type program where net-mail messages are imported and made available to callers. Secondly, SPITFIRE supports Postlink style net-mail which, when used in conjunction with a Universal Text Interface (UTI) program will directly import net-mail into SPITFIRE's message base. In addition, Buffalo Creek Software's program, SHILOH, is a QWK based net-mail message system designed exclusively for use on SPITFIRE Bulletin Board Systems. 19.1 - EXCHANGING MAIL WITH A FRONT END PROGRAM ------------------------------------------------ Using SPITFIRE with a front-end program requires the use of such programs as BinkleyTerm or FrontDoor for sending and receiving net-mail messages. Sysops who run their copy of SPITFIRE with a front-end type program will have to boot SPITFIRE using the baud rate of the caller as a command line parameter. For example: SPITFIRE 2400 NOTE: The SF.BAT file included with the SPITFIRE package should be used even with a front-end program. Using the SF.BAT file, the front-end program should boot SPITFIRE in this manner - SF 2400. Then within the SF.BAT file the SPITFIRE command would have to be followed by a %1. (For example - SPITFIRE %1) When SPITFIRE is booted in the above manner, SPITFIRE assumes there is a caller and begins the process of logging the caller on. When the caller logs off, then SPITFIRE does not recycle to the "SPITFIRE ready for use..." prompt but rather terminates so control can be returned to the front-end program. It should be noted that if SPITFIRE is used with a front-end program, the scheduled events feature within SPITFIRE becomes basically inoperative since events are run while SPITFIRE is at the "SPITFIRE ready for use..." prompt. However, when used in this environment, SPITFIRE does check when the caller logs off to see if an event is scheduled to run. 19.2 - EXCHANGING MAIL USING A UTI DRIVER ----------------------------------------- Certain features within SPITFIRE allow it to be compatible with specific net-mail drivers. Page 153 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Each Message Conference available on the BBS must be configured as to whether it will support net-mail. (Refer to CONFIGURING MESSAGE CONFERENCE RECORDS of this manual for more detailed information.) When a caller enters a message in a Message Conference configured to allow net-mail, the caller will be prompted as to whether they wish to send the message via net-mail. If the caller responds with a Y for Yes, the caller can send a message to someone who is not a caller on the BBS. Furthermore, the message is marked as a net-mail message, which allows net-mail utilities, such as the BCSUTI, to go through and extract the net-mail messages for processing and exchanging with other BBS systems. The BCSUTI serves as a conversion driver between SPITFIRE and the Postlink net-mail software and allows messages transferred between other BBS systems to be imported directly into SPITFIRE's existing message base. (Sysops should refer to the Postlink and BCSUTI documentation for complete instructions regarding setting up a SPITFIRE BBS for exchanging mail with these programs.) 19.3 - EXCHANGING MAIL USING QWK PACKETS ---------------------------------------- Buffalo Creek's Software program, SHILOH, allows SPITFIRE BBS systems to exchange QWK mail packets with other SPITFIRE boards. SHILOH determines what messages should be extracted by whether the Message Conference are configured as net-mail conferences, whether the Message Conferences are included in the caller's message queue and by the last read message pointers for the caller in each net-mail conference in his/her queue. Each Message Conference must have the Net ID Name configured (Refer to CONFIGURING MESSAGE CONFERENCE RECORDS of this manual for more detailed information) according to the Net ID Name assigned by the mail system the BBS is participating in. When importing messages, SHILOH matches the Net ID Name with those in the QWK packet to be imported and those messages are imported directly into SPITFIRE's message base. (For additional information regarding SHILOH, please refer to SHILOH.DOC.) 20.0 - OPERATING A MULTI-NODE SPITFIRE -------------------------------------- The SPITFIRE Bulletin Board System is fully capable of operating in a multi-node BBS environment. A multi-node BBS system is one that allows multiple copies of SPITFIRE to run, having two or more nodes that share a significant number of the files used during system operation. When configured for multi-node operation, all nodes of a SPITFIRE BBS share files contained in the WORK, MESSAGE and DISPLAY file paths. The SYSTEM and EXTERNAL protocol file paths must be set up individually for each node. Page 154 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 20.1 - MULTI-NODE BBS REQUIREMENTS ---------------------------------- In order to operate SPITFIRE in a multi-node environment, the Sysop must either be using a multi-tasking software or have multiple computer systems networked together. Under most circumstances, each node the Sysop wishes to install will require its own telephone line and modem. The exception to this being, if in either the multi-tasking or network environment, the Sysop configures a copy of SPITFIRE BBS with a maximum baud rate of 0 (making that node only accessible by local log on). 20.2 - CONFIGURING SPITFIRE FOR MULTI-NODE OPERATION ---------------------------------------------------- In general, SPITFIRE is configured much the same for multi-node as it is for a single node system. (Refer to the SPITFIRE CONFIGURATION section of this manual for more detailed information.) However, there are several configuration options the Sysop must be sure to set correctly when installing or expanding to a multi-node system. To begin, press ALT+Z to open SPITFIRE's configuration window. Modifications must be made so that a node number is assigned for the individual node being configured and the total number of available nodes entered. Also, it is possible to configure one or more of the available nodes as a private BBS. If this is done, be sure to use the ALT+Z option to set the security required for accessing the private node being configured. For any node not configured as a private BBS, simply have the security required set to zero. These settings need to be appropriately configured for each node on the system. In addition, when operating SPITFIRE in a multi-node environment, the DOS SHARE program is normally required to be used. This can be accomplished by placing SHARE in the AUTOEXEC.BAT so SHARE is loaded each time that the computer is booted. 20.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 currently 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. Page 155 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Several features unique to the multi-node SPITFIRE environment relate to packing the message base or caller's file. It is extremely important that there is no other BBS activity during the packing of these files. Therefore, certain safeguards are included in SPITFIRE which monitor activity on all nodes to prevent system access when packing of these files is in progress. Similarly, SPITFIRE will not allow these files to be packed if there is activity on any of the available nodes. SPITFIRE does not allow a Sysop to use the internal SPITFIRE commands for packing the caller file or packing the message base while a caller is logged on one of the other nodes. If the Sysop attempts this, the following message will be displayed: "Sysop, you are not allowed to pack the caller's file/message base while other nodes are busy." Depending upon which activity is trying to be performed, either the text of caller's file or message base will display in the above message. If a caller attempts to log onto the system when SPITFIRE is packing the message base or caller's file, SPITFIRE displays the following message, "A maintenance operation is presently being performed! Please call back in a few minutes." Upon logging on the caller is shown the SFPRELOG.BBS and the WELCOME1.[BCR] but after entering their name and password the above message will be displayed. Sysops may create their own screen for displaying the maintenance message if preferred. This screen, SFMAINT.[BCR] displays immediately after the caller enters their name, replacing SPITFIRE's default message mentioned above. If configured as a multi-node system, when booted, SPITFIRE checks to determine whether maintenance is being performed (packing the callers file and packing the message base). In the event SPITFIRE discovers that maintenance is being performed, the following message is displayed: Report - Maintenance Being Performed. Pausing Until Maintenance Is Complete. Press Any Key To Return To DOS. SPITFIRE then goes into a loop and continues to check the maintenance status indefinitely until the maintenance has been completed. When the maintenance is completed, SPITFIRE continues initialization and waits for a caller. During the time while SPITFIRE is doing the continuous maintenance check loop, if a key is pressed SPITFIRE terminates and returns to DOS. In other words, when booting SPITFIRE, if it is discovered that maintenance is being performed by another node, SPITFIRE loops until the maintenance status changes or until the Sysop presses a key to return to DOS. Page 156 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 20.4 - NODE CHAT ---------------- On a multi-node SPITFIRE BBS, a caller is able to chat with callers on another node via the Node Chat feature. This feature is accessed by selecting the "<W>ho's On The Other Node?" Menu Selection which is available from the Main Menu. Configuring Node Chat --------------------- To set up Node Chat, the Sysop will need to configure the Node Chat Drive from SPITFIRE's ALT+Z configuration window. This field should be configured to the drive letter where the node chat file will be stored. The Node Chat Drive should be a common drive shared by all nodes. Due to the constant reading of the node chat file, it is highly recommended that a RAM drive be used for storing the node chat file. DOS comes with the necessary software needed for creating a RAM drive and the DOS manual contains instructions on how to set up a RAM drive. After configuring the Node Chat Drive, the Sysop may need to edit DAILYLMT.DAT. Node chat parameters are specific to each security level. The default values allow for five Node Chats of five minutes each per day. To set specific values for a given security level, the following parameters (preceded by ONE comma) may be appended to any security level's entry in DAILYLMT.DAT: #OCA=(Number Of Node Chats Allowed Each Day) TPNC=(Time In Minutes Permitted For Each Node Chat) An example DAILYLMT.DAT might look like this: 4,MPC=0,MPD=0,DLPD=0,#OCA=0,TPNC=0 (Zero Permitted, Zero Minutes) 5,MPC=30,MPD=30,DLPD=10,KB=2000 (Default Number And Time) 10,MPC=60,MPD=60,DLPD=15,KB=5000,#OCA=10,TPNC=20 (10 Chats Daily, 20 Minutes Each) 20,MPC=60,MPD=60,DLPD=15,KB=5000,TPNC=30 (Default Number, 30 Minutes Each) 30,MPC=60,MPD=60,DLPD=15,KB=5000,#OCA=20 (20 Chats Daily, Default Time) To use default values for both Number Of Chats Daily and Time Per Chat for ALL security levels, no changes need to be made to DAILYLMT.DAT. ***NOTE*** It is REQUIRED that ALL nodes on a multi-node SPITFIRE BBS have a common Node Chat Drive in order to be available for Node Chat! Page 157 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 entering messages * when they are involved in the transmission of files * when those with Sysop-Level Security are using Sysop Utilities The caller desiring the Node Chat sees something like this: "This BBS supports 3 nodes. -------------------------- 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 then prompts the caller: " Chat with which node # " If the caller who desires a node chat enters a valid node number, the caller on the desired node is notified that a Node Chat with them is requested and by whom. They then see something like this: " (2nd Caller) would like to chat! Would you like to chat with (1st Caller)? <Y/n> " " Awaiting other node response...Press ESC to abort! " If the chatted caller agrees to chat, Node Chat begins with the following message: There are <xx> minutes allowed for this chat. Press ESC when ready to terminate chat. If the chatted caller does not want to chat, the caller who requested the chat is returned to the BBS after a short period of time. They are free to request another Node Chat later or attempt to chat with another node. Page 158 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Terminating Node Chat --------------------- The chat conversation will proceed in the same fashion as the Sysop chat, with each caller alternating their exchange until one of the callers terminates the chat by pressing the ESC key or the chat is terminated as a result of exhausting all the time allowed for the node chat. When the chat is terminated by one of the chat participants, the message: <Caller> aborted chat. displays and the callers are returned to the section of the BBS that they were in before the Node Chat began. Prior to the chat being terminated as a result of using all of the allowable time for the node chat, SPITFIRE will display a message notifying the participants that 2 minute (or less) remain in the chat. In the event the chat is terminated due to the amount of time allowed for the node chat being exhausted, both callers in the node chat are notified of this and returned to the BBS. Also, if either caller drops carrier for any reason, the Node Chat is terminated and the other caller is returned to the BBS. 21.0 - SPITFIRE MULTI-TASKING/NETWORK ENVIRONMENT ------------------------------------------------- In order to operate a multi-node SPITFIRE BBS system, SPITFIRE must be configured to run in either a multi-tasking or networked environment. In a multi-tasking environment multiple copies of SPITFIRE need to be loaded on one computer with the aid of such multi-tasking programs as Windows 3.X, Windows 95, OS/2 or DESQview. In a networked environment individual copies of SPITFIRE need to be loaded on any number of computers that are networked together via such networking systems as LANtastic. The SPITFIRE distribution package contains text files which outline the necessary procedures for installing SPITFIRE in such environments. 22.0 - USING SPITFIRE TO RECEIVE FAX CALLS ------------------------------------------ SPITFIRE is capable of receiving both data and fax calls on the same line. This will work with most Class 2/2.0 and with a few Class 1 fax modems. Most Class 1 modems (such as the US Robotics 16.8 series) will not be fax capable. Page 159 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- To determine whether your modem will properly receive an incoming fax call, issue the following command from your terminal program: AT+FCLASS=? Possible return codes include: 0 = Data 1 = Fax Class 1 capable 2 = Draft Fax Class 2 "compatible" ----\ These modems 2.0 = Fax Class 2.0 capable ----/ will work! ERROR = NO fax capabilities Adaptive answering mode describes a state where a modem is capable of discriminating between an incoming data call and an incoming fax call and taking appropriate action. On a SPITFIRE BBS, SPITFIRE will answer the phone in all cases. If the modem returns a code indicating an incoming data call, SPITFIRE will present the BBS to the caller. In the case of an incoming fax call, SPITFIRE will then run SFFAX.BAT. Sysops need to create and configure their SFFAX.BAT according to the modem and the fax reception software in use. SFFAX.BAT should be placed in each node's SPITFIRE Home Directory. Once the fax has been received, SPITFIRE will re-initialize the COM port and will accept subsequent calls of either type. 22.1 - CONFIGURING YOUR SYSTEM TO RECEIVE FAX CALLS --------------------------------------------------- To begin, it is necessary to store all modem settings related to receiving data calls in the modem's NRAM. All of SPITFIRE's strings should therefore only be used for fax-related parameters. Consult your modem documentation to determine which registers need to be changed and how to store those changes. Currently, no known modem stores fax-related settings in NRAM. To configure your modem to be fax-capable, first press ALT+M from the SPITFIRE "Ready..." prompt. Here are some suggested setups: CLASS 2 MODEMS -------------- Initialization String: AT+FCLASS=2+FAA=1+FCR=1+FLID="515 225 8496"+FDCC=1,5^M <A> Answer String: AT+FAA=1A <F> FAX Connection Result Message: +FCON (You may substitute an alphanumeric string of up to 20 characters for the phone number listed above in quotes.) Page 160 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- CLASS 2.0 MODEMS ---------------- Initialization String: AT+FCLASS=2.0+FLI="515 225 8496"^MAT+FNR=1,1,1^M <A> Answer String: AT+FCLASS=2.0+FAA=1A <F> FAX Connection Result Message: +FCO ZyXEL CLASS 2 MODEM Initialization String: AT#B1+FCLASS=6^M <A> Answer String: ATA <F> FAX Connection Result Message: FZYX These are just SOME of the strings related to fax reception used by capable modems. Consult your modem manual for further information. As you can see, there are MANY possibilities. 22.2 - SFFAX.BAT ---------------- SFFAX.BAT needs to include all the necessary commands which are required for receiving the incoming fax calls, using the fax reception program of your choice. The shareware fax program, BGFAX, will be used in the following example to demonstrate how the SFFAX.BAT might be set up to receive incoming fax calls. The following example demonstrates the batch commands needed to receive a fax using a USR fax modem: REM This Batch File Will Run BGFAX from SPITFIRE 3.5 C: CD\BGFAX BGFAX /FCO C:\BGFAX 1 Q CD C:\SF EXIT (The above receives a fax using COM1: in QuickLink II mode.) Many other configurations are possible, depending upon the software used to receive the fax. The BGFAX documents provide an excellent overview of fax modem capability and their use as well as instructions for its own use. It is important to remember that unless a fax modem returns a code which can be recognized by SPITFIRE, it will NOT work with SF 3.5. SPITFIRE itself does NOT receive the fax! What it does, is recognize the code configured in ALT+M and then passes control to a third party Page 161 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- program which is capable of receiving and printing incoming fax calls. After configuring their BBS to receive fax calls, Sysops can use their fax capabilities to receive questionnaires, subscription applications, proofs of identity, etc., thus, providing a valuable additional feature for their SPITFIRE Bulletin Board System. 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. In such an instance, please contact Buffalo Creek's BBS for information regarding the record structure information needed. We will make the information available to you, if possible. When a caller goes through a Door or uses any of the Sysop configurable features available from each menu, SPITFIRE creates a simple text file named SFDOORS.DAT, SFMAIN.DAT, SFMESS.DAT, SFFILE.DAT, or SFSYSOP.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. 24.0 - SPITFIRE COMPANION PROGRAMS ---------------------------------- Several SPITFIRE companion programs are included within the SPITFIRE distribution package. These programs are designed to work with SPITFIRE. Those which are optional and work independently of SPITFIRE are noted as such with (OPTIONAL) after the utility name. It is the intention of Buffalo Creek Software to provide these programs with SPITFIRE in hopes they are found to be an asset in the operation of a SPITFIRE BBS. Some of these programs are shelled to during the execution of special features within SPITFIRE and are noted as such with (SHELL) after the program name. Among these, some may also be executed independently of SPITFIRE as well. This will be noted in the individual program description. It should be emphasized that the following programs all contain individual documentation that should be referred to for complete Page 162 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- details. Any of these programs may be updated prior to the next SPITFIRE release without written notification. Therefore, it is recommended that you call Buffalo Creek's BBS periodically to check for updated versions of these programs. 24.1 - DAILYLMT (OPTIONAL) -------------------------- DAILYLMT provides an easy to use menu program for creating or editing SPITFIRE's DAILYLMT.DAT file. It easily allows SPITFIRE Sysops to add, change or delete security levels within DAILYLMT.DAT. In addition, an option is provided for the Sysop to review the contents of the existing DAILYLMT.DAT file. The responses to DAILYLMT's prompts set the minutes per call, minutes per day, downloads per day, quick log-on status, kilobytes per day, number of chats allowed, time per node chat, violation warning ratio and violation enforcement ratio for each security level. DAILYLMT uses the information that has been input to format individual lines in the DAILYLMT.DAT file. 24.2 - SFDOOR (OPTIONAL) ------------------------ SFDOOR is a SPITFIRE utility that is used to create and or modify SPITFIRE's SFDOOR.MNU file. SFDOOR is menu driven for ease of use and aids the Sysop in installing or deleting door programs on a SPITFIRE BBS. SFDOOR also provides an option for reviewing the current SFDOOR.MNU file. When adding or changing the SFDOOR.MNU file, Sysops provide information regarding the title for the door's name; whether the security will be greater than or equal to, equal to, or less than; and the security level required to access the door. SFDOOR will then update the SFDOOR.MNU file accordingly. 24.3 - SFSENDIT (OPTIONAL) -------------------------- SFSENDIT is a SPITFIRE utility that is used to flag files for sending to a specific caller or group of callers with a common security level. The file flagged for sending must exist in a SPITFIRE File Area although it need not be listed in the SFFILES.BBS. SFSENDIT stores the file area and the file name in the SFUSERS.DAT file. When the caller next logs on the BBS, he/she is notified that the file is there for download. SFSENDIT is a limited to flagging one file per caller or group of callers with a common security level. Similar utilities exist that offer more complex file flagging schemes. If SFSENDIT does not meet a Page 163 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Sysop's needs, they may wish to use one of these other utilities. However, it should be mentioned that it is possible for SFSENDIT to send more than one file at a time by compressing the desired files together into one file. Also, SFSENDIT does not work when a caller is logged on locally. If the file to be downloaded is in a free file area, the caller's statistics are not updated. If the file downloaded is in a non-free file area, the caller's download statistics will be adjusted. SFSENDIT is menu-driven and easy to use. SFSENDIT provides options for flagging a file for download by caller or security level, removing flags by caller or security level, and viewing flags set by caller or security level. 24.4 - LAKOTA (SHELL) --------------------- LAKOTA is a SPITFIRE utility which allows the caller to download messages in QWK format. Using a QWK offline reader, the caller can read messages, reply to messages and/or enter messages offline. The compressed reply packet (in QWK format) can then be uploaded with LAKOTA the next time the caller logs on the BBS. LAKOTA will insert messages contained in the reply packet into SPITFIRE's message base. When downloading the caller is given the option of downloading messages to the caller or all new messages. The caller is also asked to specify which conferences the messages to be downloaded will be extracted from. Conference options include All Conferences, Select A Conference or Your Queued Conferences. Once the selection is defined, LAKOTA creates the QWK mail packet and compresses it in ZIP format. Next, if the caller is logged on locally the message packet is placed in the SPITFIRE home directory. If the caller is logged on remotely they are prompted to select a file transfer protocol to be used in the message download. If the download is successful the caller is then prompted as to whether they wish to have their message pointers updated. When uploading the reply packet, if the caller is logged on locally, LAKOTA will prompt the caller to enter the drive, path and file name of the mail packet to be uploaded. When logged on remotely, the caller is presented with a menu that allows them to select a file transfer protocol to be used in the message upload. The messages from the uploaded packet are then inserted into SPITFIRE's message base. LAKOTA is a simple, get-the-job-done QWK mail upload/download program. There are a number of similar mail doors which offer more complex options for exchanging mail on a BBS. If LAKOTA Page 164 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- does not meet a Sysop's needs, they can choose other mail exchange utilities. If you do not wish to have this option available to callers, the security of the SFMSG.MNU for this feature should be set high enough so the caller cannot access it. LAKOTA must be used with SPITFIRE and cannot be executed independently of SPITFIRE. 24.5 - SFPCKUSR (SHELL) ----------------------- SFPCKUSR is a SPITFIRE companion utility which is used to purge the caller's record from the caller data base, SFUSERS.DAT. SPITFIRE will shell to SFPCKUSR when Pack Users File is selected from the Sysop Menu. SFPCKUSR can also be used independently of SPITFIRE. When the Sysop selects the Pack User File from the Sysop Menu, the Sysop is prompted whether inactive callers should be purged. If the Sysop responds with a Y, the Sysop is then asked to enter the number of days to be used for purging inactive callers. If the number of days between today's date and the caller's last log on is greater than the number of days the Sysop enters here, the caller is considered inactive and will be purged. Once these questions have been answered, SPITFIRE shells to SFPCKUSR, passing the purging criteria to it. SFPCKUSR will purge any callers who have been marked for deletion and if the inactive purge has been selected, any callers who have not called for the amount of days specified by the Sysop will also be purged. Once SFPCKUSR has completed the purge process, a list of the callers who were purged is written (or appended to) SFPURGED.USR in the WORK directory and control is returned to SPITFIRE. SFPCKUSR can also be used independently from SPITFIRE. When initiated from the DOS prompt or from within a batch file without any command line parameters, only callers who have been marked for deletion will be purged. Command line parameters can be used to specify the number of days for purging inactive callers. When SFPCKUSR has completed the purge process, a list of the callers who were purged is written (or appended to) SFPURGED.USR in the SPITFIRE WORK directory. 24.6 - SFPCKMSG (SHELL) ----------------------- SFPCKMSG is a SPITFIRE companion utility which is used to pack the message base. The Sysop can control which messages Page 165 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- are packed according to the following criteria: number of days old, threaded messages, and unreceived messages. This criteria can be set independently for each Message Conference available on the BBS. When Event M is activated, SPITFIRE will shell to SFPCKMSG to pack the message base. When the Sysop elects to use the Pack Message Base option from the Sysop Menu, SPITFIRE will shell to SFPCKMSG to pack the message base. When SPITFIRE shells to SFPCKMSG the settings on the Message Conference record for each conference are used to determine the criteria for purging messages from the system. SFPCKMSG can also be used independently of SPITFIRE. If you choose to use SFPCKMSG from the DOS prompt or from within a batch file, command line parameters are available to define the criteria for which messages will be purged from the system. 25.0 - COMMENT FROM THE AUTHOR ------------------------------ While SPITFIRE is a full-featured BBS software package, there are additional features that can be added. SPITFIRE is not designed to have every whistle and bell possible. There are already other BBS software available that attempts to provide all the whistles and bells. SPITFIRE is designed, written and upgraded with a simple, fast, get-the-job-done BBS package in mind (the KISS system). 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 continue to improve without the loss of its simplicity. 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.6 and spent a tremendous amount of time revising the manual. As mentioned earlier, SPITFIRE is written in Borland's Turbo Pascal and linked with Assembler code. This entire program was written by yours truly (Mike Woltz). It has taken over seven years to get SPITFIRE to this point (maybe I'm slow). This opportunity is taken to thank my wife Ann, my children Mason, Jesse and Amanda for tolerating the countless number of hours that were spent writing and testing SPITFIRE. I also would like to mention my grown children, Matthew, Page 166 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- Joell, and Sue, as well as my grandchildren, Joshua and Lexie. Lord knows, I could be a better husband, father and grandpa. Most important, I thank God for my family and giving me the ability to write SPITFIRE. 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, 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 eight years of my life into SPITFIRE, I have attempted to keep the cost of this software as reasonable as possible. I have noticed lately that there are many third party utilities, etc. being written for SPITFIRE and I have also noticed that in some cases the registration fee for these utilities is nearly half the cost of SPITFIRE. It doesn't seem right to charge $20.00 to $35.00 for a SPITFIRE utility that can be written in a day or two and I would ask those authors to attempt to keep their prices comparable to the SPITFIRE project. No rip-offs, OK? Thank you! Page 167 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- NOTES: ------ Page 168 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- APPENDIX A ---------- SPITFIRE QUESTIONS AND ANSWERS ------------------------------ QUESTION: Why is the "Do You Want ANSI Graphics? <y/N>" displayed each time a caller logs on the BBS? ANSWER: Some BBS software stores in the caller's file whether a caller uses ANSI, and if so, then each time the caller logs on, ANSI graphics are automatically displayed. When creating SPITFIRE it was decided to provide the caller with the opportunity to select the display preferred at each log-on. There are two basic reasons for including this prompt to each caller upon log on. First, some callers may call the BBS from different locations. For instance, many callers call the BBS from work as well as from home and while they may have a color monitor at home, they may not at work. In such a case, they would not want to use color graphics each time they log-on. Also, observation has proven that a caller may sometimes choose ANSI graphics and other times not. This may be due to the amount of time a caller has to spend on the board since ANSI graphics display slower than those created in ASCII. For whatever their reasons may be, SPITFIRE demonstrates increased flexibility by allowing the caller to make that choice. QUESTION: With SPITFIRE at the "Ready For Use..." prompt, the phone rings and SPITFIRE simply does NOT answer the phone, but rather stays at the "Ready For Use..." prompt. Why? ANSWER: SPITFIRE relies on verbose result codes to determine an incoming call, the baud rate of the incoming call and whether the incoming call is an error correction modem. This problem would indicate that the modem initialization string is not correct. You should try using a different initialization string. Your modem initialization string requires a V1 in it because this tells your modem to send verbose result codes. This manual contains a list of initialization strings which have been tested and are reported 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 169 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 cannot find this file on my drive. Was it neglectfully not included in my SPITFIRE package? ANSWER: When executing a door, SPITFIRE creates two files containing pertinent caller information required for door operation. These files are SFDOORS.DAT, required by SPITFIRE, and DOOR.SYS, a universal format door caller information file. These are only used during door operation and once the caller returns to SPITFIRE, SFDOORS.DAT is automatically erased. Similarly, SFMAIN.DAT, SFFILE.DAT, SFMESS.DAT and SFSYSOP.DAT created during execution of the Main, File, Message AND Sysop Menu's Sysop configurable command option are erased when the caller returns to SPITFIRE. QUESTION: When a caller uploads a file to "Sysop Only", how is the Sysop made aware of the uploaded file? ANSWER: SPITFIRE incorporates two techniques by which the Sysop is notified that a file has been uploaded privately. A message is written both in the CALLERS.LOG and also the HEYSYSOP.LOG file that informs the Sysop that a file Page 170 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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 some time, 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 use 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. Another option is to use the SFNODE.EXE utility provided by Buffalo Creek Software to update any changes to your node configurations. QUESTION: After adding new files to the various file areas for the callers to download, I noticed that when a caller logs onto the BBS and does a check for new files, these files are not displayed. What is the problem? ANSWER: There are basically two reasons this could happen. The first being, it is possible the files were copied into the download directories but not added to the appropriate SFFILES.BBS file. Another possible explanation would be Page 171 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- 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: The callers log reveals "Message sent and erased" for a caller who logged onto the BBS. What does this mean? ANSWER: This would depict a special notice ( <x>.BBS; refer to the section - SPITFIRE FILE CLARIFICATION - of the manual for further explanation regarding this subject) was left for a specific caller. Once the caller receives this message it is automatically erased. The CALLERS.LOG displays the above mentioned message to inform the Sysop the message was sent and then erased. QUESTION: The HEYSYSOP.LOG reveals a message that a specific archived file fails the CRC check. What does this mean? ANSWER: Anytime the Sysop is notified that an archived MS/PC DOS file fails the CRC check, this means that the specified file is corrupt and should be erased from your system. QUESTION: What is the purpose of the SPITFIRE.OVR overlay file? ANSWER: By accessing the overlay file, many SPITFIRE procedures and functions are called into memory only when they are needed rather than being held in memory continuously. Thus the overlay file drastically reduces the amount of memory which is required to run SPITFIRE. This is very significant to Sysops running SPITFIRE in a multi-tasking or networking environment that is required for multi-node operation. QUESTION: I recently registered a door program and was requested by the author to add him to the caller's file. This was so he could call the BBS and upload my registered version. The call was long distance and he wanted to avoid the time required to complete the log-on questionnaire. Is it possible to add a caller to the callers data base? ANSWER: A caller may be added to the SFUSERS.DAT file by selecting ALT+A at the SPITFIRE "Ready For Use..." prompt. A caller may also be added by using the ... Modify Callers feature found within the Sysop Menu. Page 172 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- QUESTION: Why does SPITFIRE limit the number of files allowed in an external batch download to seven files and in an external batch upload to six? ANSWER: These limits are set by DOS rather than SPITFIRE. DOS will only allow a command line to contain a specific number of characters. The seven files for the batch download and the path for the upload directory and the six files allowed in a batch upload attain the allowable DOS limits. SPITFIRE can be configured through the UseFile feature to allow 99 files per download batch, provided the external protocol has this capability. QUESTION: When running SPITFIRE, I get a Runtime error 004 and SPITFIRE stops. Why? ANSWER: This runtime error problem is caused by too many files being open at one time. You will need to increase the number of files that DOS will allow to be opened at once by changing your CONFIG.SYS file. Refer to your DOS manual for further information regarding this subject. Your system will have to be rebooted after changing your CONFIG.SYS file. QUESTION: Why am I able to upload files that are contained in the SFNOUP.DAT file? As I understand this is a list of files which should not be able to be uploaded to the BBS. ANSWER: SFNOUP.DAT has no affect on any caller with Sysop status. In other words, any caller with a security equal to or greater than what you have designated as Sysop security for your system may upload files, even though they may be contained in your SFNOUP.DAT. QUESTION: Why are callers unable to leave a comment to Sysop on my BBS? ANSWER: Before SPITFIRE will allow a comment to be left to a Sysop, the Sysop must be a caller of the BBS. The name the Sysop uses to log onto the BBS must be the same as the Sysop Caller Name configured using the ALT+Z configuration window. If a Sysop enters Sysop as the Sysop Caller Name and then logs onto the BBS using their real name, SPITFIRE will not allow a comment to be left to the Sysop because Sysop is not a caller of the BBS. In this example, the Sysop would need to Page 173 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- change the Sysop Caller Name from Sysop to their real name. Once this is done SPITFIRE will allow comments to be sent to the Sysop. In other words, the Sysop caller name must be the same as the name used for logging onto the BBS. QUESTION: I just updated my bulletin number #9, yet when a caller logs on, SPITFIRE does not list bulletin number #9 as being updated. Why? ANSWER: For purposes of speed, SPITFIRE stops searching the drive for new bulletins once a bulletin file is not found. For example, let's say that SPITFIRE finds BULLET[1..7].BBS and then does not find BULLET8.BBS. In such case, SPITFIRE 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. QUESTION: I keep seeing the message, "SFCALLOG.DAT not found WORK directory!" written to my CALLERS.LOG. What is the problem? ANSWER: The file entitled, SFCALLOG.DAT, needs to be copied to the WORK directory or the SFCALLOG.DAT is not compatible with your current version of SPITFIRE. The SFCALLOG.DAT file Page 174 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- contains information which is used to write the CALLERS.LOG. If this file is not found by SPITFIRE or if the SFCALLOG.DAT does not correspond to the version of SPITFIRE you are running, your CALLERS.LOG will be missing important information which clarifies the recorded activity. QUESTION: I just purchased a new 14400 modem. SPITFIRE will not accept 14400 as the baud rate. What am I doing wrong? ANSWER: Valid baud rates are 110, 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200. Normally you will want to configure SPITFIRE's System Baud Rate at 57600 for most modems advertised as 14400. QUESTION: SPITFIRE thinks that all calls are high speed. In other words, I have my system configured at 57600 and SPITFIRE thinks that every call is at 57600. What is wrong? ANSWER: SPITFIRE only knows the speed of the call by what your modem reports. By default, most high speed FAX modems report the speed of the port (DTE) rather than the actual speed of the call (DCE). Normally, you will have to add a W2 or a S95=3 or both to your modem initialization string to force your modem to report the actual speed of the call. These commands work with most modems but not all, thus, you will have to refer to your modem's manual. Thank you very much for selecting SPITFIRE. Page 175 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- NOTES: ------ Page 176 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- NOTES: ------ Page 177 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 1 <x>.[BCR] - 45, 55, 63, 64 19200 - 7, 10, 76, 174 38400 - 6, 7, 174 57600 - 7, 12, 174 1K-XMODEM - 91, 92, 119 @ABORTON@ - 64 @BEEP@ - 64 @BIRTHDATE@ - 65 @CITYSTATE@ - 64, 65 @CLS@ - 64 @DOWNK@ - 65 @DOWNLOADS@ - 64, 65 @FNAME@ - 64, 65 @LASTCALL@ - 65 @LOGTIME@ - 65 @NAME@ - 65 @NOABORT@ - 64 @ORGLOG@ - 65 @PASSWORD@ - 65 @PHONENUM@ - 65 @PROMPT@ - 65 @PROMPTOFF@ - 64, 65 @SLEVEL@ - 65 @SUBDATE@ - 64 @UPLOADS@ - 64, 65 @UPK@ - 65 <<<<<< A >>>>>> ALL.BBS - 22 Alt+A - 58, 73, 77, 127, 171 Alt+C - 73, 76, 84 Alt+D - 73, 84, 123 Alt+E - 73, 84, 85 Alt+F - 32, 46, 73, 76, 85 Alt+F1 - 46, 73, 76 Alt+F2 - 73, 76 Alt+F3 - 73, 76 Alt+J - 73, 85, 123, 169 Alt+L - 58, 73, 85 Alt+M - 5, 6, 8, 9, 60, 67, 73, 85, 150, 159, 160 Alt+P - 25, 40, 67, 73, 85, 139, 144, 149 Alt+Q - 73, 86, 136 Alt+R - 26, 73, 86 Alt+S - 9, 73, 86, 136 Alt+T - 16, 19, 35, 49, 59, 69, 73, 81, 86 Alt+Z - 14, 21, 46, 48, 55, 56, 73, 82, 86, 89, 95, 123, 128, 129, 148, 154, 156, 172 Page 178 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 2 ANSI - 14, 19, 22, 23, 44, 47, 49, 50, 53, 54, 64, 72, 91, 112, 115, 117, 168, 170 ANSI.SYS - APPENDIX A - 5, 6, 168 APPENDIX B - 3 ARC - 37, 62, 109, 118, 146, 171 ARQ - 10, 11 ASCII - 8, 24, 34, 42, 44, 45, 47, 49, 50, 52, 53, 54, 58, 59, 65, 68, 91, 92, 116, 119, 125, 135, 140, 146, 168 AUTOEXEC.BAT - 62, 68, 154, 169 <<<<<>>>>> BPS - 7, 76, 93 Backup Files - 66, 77, 126 BADINIT - 42, 63 Batch - 40, 41, 42, 44, 46, 52, 53, 56, 60, 61, 62, 63, 66, 67, 110, 119, 120, 121, 122, 132, 134, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 160, 164, 165, 172 Batch Download - 46, 52, 56, 119, 120, 121, 141, 142, 143, 149, 172 Batch Upload - 46, 52, 121, 122, 146, 147, 172 Baud Rate - 5, 6, 7, 10, 11, 12, 46, 66, 67, 85, 140, 145, 146, 150, 151, 152, 154, 168, 174 BBSNAME - 44, 63 Beep - 64 Binkleyterm - 152 BRK - 4, 139, 141, 142, 143, 145, 146, 147, 150 Buffalo Creek's BBS - 4, 34, 53, 57, 63, 66, 85, 118, 135, 137, 138, 139, 141, 144, 146, 161, 162, 169 BUFFERS - 4 Bulletins - 45, 46, 50, 51, 81, 87, 88, 132, 136, 137, 173 BULLET<x>.[BCR] - 45 <<<<<< C >>>>>> CALLER ID - 151 CALLERS.TMP - 41 CALLERS.LOG - 12, 16, 18, 41, 43, 70, 75, 77, 82, 126, 132, 151, 169, 170, 171, 173, 174 Capture Chat To Disk - 73 Cd-Rom - 20, 24, 36, 110 Chat - 14, 19, 41, 45, 50, 54, 55, 57, 73, 74, 75, 76, 84, 88, 89, 90, 107, 116, 129, 156, 157, 158, 162 CHATDONE - 45, 50 Check Today's Statistics - 72 Page 179 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 3 Command Line Parameters - 6, 8, 66, 67, 164, 165 COMMAND.COM - 5, 169 Conference - 19, 23, 24, 26, 27, 28, 29, 30, 31, 32, 35, 40, 43, 46, 47, 61, 66, 73, 78, 80, 86, 88, 94, 95, 96, 97, 99, 100, 101, 102, 103, 104, 106, 107, 123, 125, 126, 128, 130, 134, 153, 163, 165 CONFIG.SYS - 4, 22, 49, 172 CRC - 92, 119, 171 <<<<<< D >>>>>> DAILYLMT.DAT - 15, 17, 38, 41, 42, 48, 54, 55, 56, 57, 156, 162 Delete - 18, 26, 28, 29, 30, 36, 37, 66, 78, 80, 84, 99, 101, 102, 105, 106, 107, 110, 128, 129, 132, 162 Desqview - 158 Device - 4, 22 Disconnect Delay - 10, 12 Display File Path - 25, 34, 44, 47 DLMT - 45 Doors - 4, 52, 62, 134, 136, 137, 138, 163 DORBUL - 45, 137 DOS - 1, 4, 5, 6, 14, 15, 19, 33, 40, 52, 59, 61, 66, 67, 73, 76, 84, 85, 123, 132, 135, 136, 140, 141, 146, 154, 155, 156, 164, 165, 169, 171, 172 Download - 2, 17, 20, 32, 33, 34, 35, 37, 38, 41, 42, 44, 45, 46, 47, 48, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 75, 76, 78, 79, 90, 94, 95, 109, 110, 111, 112, 115, 117, 118, 119, 120, 121, 135, 137, 138, 139, 140, 141, 142, 143, 144, 146, 148, 149, 150, 162, 163, 169, 170, 172 DTE Locked - 10, 150 DTR Hangup - 7, 10 <<<<<< E >>>>>> EMS - 151 Erase - 38, 41, 60, 63, 64, 77, 93, 108, 109, 110, 112, 114, 118, 124, 126, 132, 136, 141, 161, 169, 170, 171, 173 Eventime - 45 Events - 40, 61, 62, 67, 68, 73, 84, 85, 123, 130, 131, 132, 133, 152 Exit - 84, 85, 93, 101, 108, 113, 115, 118, 124, 131, 136, 160 External Protocols - 4, 138, 139, 140, 141, 144, 146, 148, 149 Page 180 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 4 <<<<<< F >>>>>> F1 - 72, 73, 76, 127, 170 F2 - 9, 51, 72, 74 F3 - 72, 74 F4 - 72, 75 F5 - 72, 75 F6 - 72, 75 F7 - 73, 75 F8 - 73, 75 F9 - 73, 76 F10 - 73, 76 FA<x> - 34, 36, 42, 58, 59 FAX - 6, 7, 10, 11, 42, 60, 158, 159, 160, 161, 174 File Area - 20, 24, 26, 32, 33, 34, 35, 36, 37, 38, 39, 40, 42, 45, 46, 47, 54, 58, 59, 60, 66, 73, 78, 81, 85, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 128, 146, 147, 162, 163, 170 File Tag - 109, 110, 117 FILE<x>.[BCR] - 45 FILECTRL - 45, 49 FILST<x>.[BCR] - 45 Free File - 38, 163 Frontdoor - 152 <<<<<< G >>>>>> GOODBYE - 9, 45, 68, 88, 90, 94, 108, 109, 110, 111, 113, 114, 115, 120, 121, 123, 124, 136 <<<<<< H >>>>>> Hardware - 4, 7, 12, 150 HEYSYSOP.LOG - 16, 43, 70, 77, 113, 126, 169, 170, 171 High Speed Async Routines - 10 <<<<<>>>>> Initialization String - 5, 6, 9, 10, 13, 66, 67, 85, 159, 160, 168, 174 International - 3, 19 Page 181 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 5 <<<<<< J >>>>>> JOKER.DAT - 43, 45, 57, 58, 80, 81 <<<<<< L >>>>>> Lantastic - 158 LOCKOUT.[BCR] - 45, 58 Loop - 132, 135, 136, 155 <<<<<< M >>>>>> Main Menu - 9, 21, 40, 41, 43, 45, 47, 51, 52, 55, 59, 62, 68, 71, 74, 82, 86, 87, 88, 93, 94, 108, 109, 116, 123, 127, 129, 134, 136, 137, 154, 156 MAIN<x>.[BCR] - 45 MAINCTRL - 45, 49 Maintenance - 47, 66, 77, 78, 123, 125, 155, 173 MAXUSERS - 15, 45 Message Conference - 26, 27, 28, 29, 30, 31, 32, 40, 43, 46, 47, 61, 66, 80, 86, 88, 95, 96, 97, 99, 100, 102, 103, 104, 106, 107, 123, 125, 126, 128, 130, 134, 153, 165 Message Files Path - 25 MGLST<x>.[BCR] - 46, 96 MKSFMENU - 53 Modem - 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 41, 42, 60, 62, 63, 66, 67, 73, 75, 76, 77, 84, 85, 86, 150, 151, 154, 158, 159, 160, 168, 174 MSG<x>.[BCR] - 45 MSGCTRL - 45, 49 Multi-Tasking - 22, 154, 158, 171 Multi-Node - 16, 17, 42, 43, 44, 55, 88, 89, 125, 143, 153, 154, 155, 156, 158, 171 <<<<<< N >>>>>> NEEDSYS.[BC ] - 46, 76 Network - 154, 158, 171 Net-Mail - 26, 27, 30, 44, 62, 63, 67, 97, 99, 102, 104, 133, 134, 152, 153 Newsletter - 47, 88, 90 NEWUSER.[BCR] - 46 Page 182 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 6 Node Chat - 14, 19, 41, 54, 55, 57, 89, 90, 129, 156, 157, 158, 162 NUCALLER - 59, 60 <<<<<< O >>>>>> OFFLINE - 44, 58, 60, 61, 110, 163 Old Message Purge - 29 <<<<<>>>>> Pack - 2, 8, 29, 30, 40, 42, 43, 44, 51, 53, 57, 58, 61, 62, 64, 67, 77, 80, 84, 95, 99, 123, 124, 125, 126, 130, 133, 134, 135, 152, 153, 155, 158, 161, 163, 164, 165, 169 Pack Message - 123, 125, 165 Pak - 119 Password - 9, 14, 15, 19, 20, 21, 22, 23, 46, 47, 65, 78, 80, 84, 86, 91, 92, 123, 125, 136, 137, 155 Paths - 24, 25, 33, 34, 39, 40, 59, 73, 85, 86, 149, 153 Preview Area - 32, 37 PRIVATE.[BCR] - 17, 22, 46 Protocols - 4, 25, 39, 46, 48, 56, 66, 111, 113, 116, 119, 138, 139, 140, 141, 142, 144, 145, 146, 148, 149, 150 Purge Allowed - 78, 84 <<<<<< Q >>>>>> Questionnaires - 43, 52, 68, 69, 89, 161 Queue - 23, 94, 95, 96, 103, 106, 107, 119, 120, 121, 122, 142, 144, 153, 163 Quick Log - 41, 45, 54, 55, 86 <<<<<< R >>>>>> RATIO - 14, 16, 17, 18, 48, 54, 55, 56, 57, 162 Registration - 1, 166 Result Message - 5, 10, 11, 60, 159, 160 RIP - 19, 23, 24, 25, 44, 45, 49, 50, 52, 53, 54, 60, 64, 72, 91, 92, 111, 112, 114, 115, 117, 166 Page 183 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 7 <<<<<< S >>>>>> SF.BAT - 6, 8, 40, 42, 61, 62, 67, 68, 131, 132, 135, 136, 138, 152 SF1STF - 46 SF1STM - 46 SF2SLOW - 12, 46, 50 SFASLEEP - 46, 50 SFBATCHD - 46, 52, 53 SFBATCHU - 46, 52, 53 SFBBSLST.DAT - 44, 93 SFBDAY - 46 SFCALLER - 129, 130 SFCALLOG - 43, 173, 174 SFCHAT.CAP - 41, 76 SFDOOR.MNU - 41, 42, 52, 134, 135, 162 SFDOORS.DAT - 41, 124, 136, 137, 161, 169 SFDORBAK - 46, 138 SFDORBUL - 46, 137 SFDOWN - 46 SFDR<x>.[BCR] - 46 SFEVENTS - 40 SFEXTDN - 46, 50, 56, 139, 140, 141, 142, 143, 144, 147, 149, 150 SFEXTDN,<x>.BAT - SFEXTUP - 46, 50, 144, 145, 146, 147 SFEXTUP<x>.BAT - SFFAREA - 8, 40, 66 SFILEREQ.LOG - 44, 60, 61, 77, 110, 126 SFFAX.BAT - 42, 60, 159, 160 SFFILE.BAT - 41, 42, 62, 118 SFFILE.MNU - 40, 50, 51, 109 SFFILES.BBS - 34, 35, 44, 46, 47, 50, 54, 59, 60, 61, 110, 112, 113, 114, 115, 116, 118, 147, 162, 170, 171 SFFILE.DAT - 41, 118, 161, 169 SFIL<x>.BBS/CLR/RIP - 36, 37 SFIL<x>.[BCR] - 47 SFIMPEXP - 47, 52, 53, 111, 114 SFINIT.BAT - 5, 41, 42, 62 SFLOGON.BAT - 42 SFLOG - 42, 131, 132 SFMAIN.BAT - 41, 42, 62, 93 SFMAIN.MNU - 40, 50, 51, 87, 137 SFMAINT - 47, 125, 155 SFMAIN.DAT - 41, 93, 161, 169 SFMCONF - 8, 40, 66 SFMESS.BAT - 41, 42, 62, 108 SFMESS.DAT - 41, 108, 161, 169 SFMQDONE - 47 Page 184 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 8 SFMSG.MNU - 40, 50, 51, 58, 94, 164 SFMSGPCK - 5, 43, 44, 62, 134 SFNEWU - 43, 68, 70, 71 SFNODE - 8, 40, 170 SFNOTIME - 47 SFNOUP - 43, 44, 59, 60, 110, 112, 114, 172 SFNWSLTR - 47, 59, 90 SFORDER.MNU - 41, 42, 52, 71 SFORD<x> - 47, 52, 53 SFPAGED.[BCR] - 47, 63, 74, 75, 90, 108, 116 SFPRELOG.BBS - 47, 50, 86, 155 SFPROMSG.[BCR] - 47, 93, 138 SFPROTCO.HLP - 42, 116 SFRATIO.[BCR] - 48, 56, 57 SFREMIND.[BCR] - 48 SFREMOTE.BAT - 40, 42, 61, 62, 123, 169 SFSEC<x>.BAT - 42, 63 SFSENDIT - 162, 163 SFSUBCHG - 18, 48, 82 SFSYSOP.BAT - 41, 42, 62, 124 SFSYSOP.DAT - 41, 124, 161, 169 SFSYSOP.MNU - 40, 50, 52 SFSYSTEM - 8, 43 SFTIMEUP.[BC ] - 48 SFUP.[BCR] - SFUPCASE.DAT - 21, 43, 44, 61 SFUSERS - 8, 9, 17, 42, 43, 57, 64, 77, 80, 83, 124, 126, 127, 162, 164, 171 SFWHOSON.DAT - 44, 154, 173 SF.BAT - 6, 8, 40, 42, 61, 62, 67, 68, 131, 132, 135, 136, 138, 152 SOP<x> - 52, 53 SPITFIRE.HLP - 42, 93, 108, 118 SPITFIRE.OVR - 40, 151, 171 Subscription - 18, 48, 60, 64, 70, 78, 81, 82, 90, 161 SUBWARN - 18, 82 SYSINIT - 50 Sysop Utilities - 88, 93, 94, 108, 109, 118, 123, 131, 133, 157 <<<<<< T >>>>>> Telink - 92, 119 This System's Info - 88, 90 THOUGHTS.BBS - 50, 66 Tilde - 13, 70 TOOMANY.[BCR] - 15 Page 185 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- SUBJECT INDEX - Page 8 <<<<<>>>>> Undelete - 18, 102, 128 Upload - 14, 15, 16, 17, 18, 19, 22, 23, 32, 33, 38, 42, 44, 46, 52, 55, 56, 57, 58, 59, 60, 62, 64, 65, 75, 76, 78, 79, 90, 94, 95, 109, 111, 112, 113, 114, 116, 119, 121, 122, 128, 133, 144, 145, 146, 147, 148, 149, 163, 169, 170, 171, 172 Usefile - 56, 149, 172 USERINIT.[BC ] - 74 Utilities - 21, 33, 62, 88, 93, 94, 108, 109, 118, 123, 131, 133, 153, 157, 161, 162, 163, 164, 166 <<<<<< W >>>>>> WATCHDOG - 61 WELCOME1.[BCR] - 47, 86, 155 WELCOME<x>.[BCR] - Wildcards - 112, 115, 117 Wildfire - 137 Windows - 158 Work Files Path - 25, 39 <<<<<< X >>>>>> Xmodem - 92, 119 Xpert - 88, 90, 94, 108, 109, 118 <<<<<< Y >>>>>> YMODEM - 66, 92, 119 YMODEM-g - 66, 119 <<<<<< Z >>>>>> ZIP - 21, 111, 118, 119, 163 ZMODEM - 92, 119, 138, 142, 143, 147, 149 Page 186 ----------------------------------------------------------------------- -+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.6 -- August 20, 1999 +- ----------------------------------------------------------------------- NOTES: ------