Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / USBDOR54.ZIP / USBBSDOR.DOC < prev next >

Wrap

Text File | 1995-05-09 | 78.0 KB | 1,706 lines

------------------------------------------------------------------ | | | | | | | | | USBBSDoor Version 5.4 | | (Formerly known as USBBSDOR) | | | | | | * Continuously updated and supported for over seven years! * | | | | | | Search the USBBS National BBS Listings for Area Codes, | | States, Text, Internet, Brand of BBS, & New listings. | | | | | | Works with many brands of BBS including: PCBoard 14.x-15.x, | | Wildcat 4.x, RBBS, GAP, Spitfire, Remote Access, and any BBS | | software which can create compatible PCBOARD.SYS, DOOR.SYS, | | DORINFO1.DEF, or SFDOORS.DAT door information files. | | | | | | | | * * * COMPLETELY AUTOMATED MONTHLY MAINTENANCE * * * | | | | | | USBBSDoor Version 5.4 | | | | (C) Copyright 1987-1995 Brent Yandell All Rights Reserved | | | | Distributed by: | | | | Yandell Custom Software | | 9438 U.S. Hwy 19 North - Suite 212 | | Port Richey, FL 34668 | | | | DATA - (813) 842-8099 | | | | | | | | May 9, 1995 | | | | | | | | | | | ------------------------------------------------------------------ -------------------------------------------------------------------- USBBSDoor -------------------------------------------------------------------- TABLE OF CONTENTS Page ----------------- ---- INTRODUCTION 1.0 What is USBBSDoor 3 1.1 What's New 4 1.2 Upgrading from Previous Versions 4 PRELIMINARIES 2.0 A Word on Installing Doors 5 2.1 Obtaining the Current USBBS List 5 2.2 Required Files 5 INSTALLATION 3.0 Setting Up USBBSDOR.CNF 6-9 3.1 Setting Up Door Files to Call USBBSDoor 10 3.2 Setting Up PROTOCOL.DAT 11 3.3 Setting Up SEND.BAT 12 3.4 Setting Up and Modifying Text Files 13 RUNNING USBBSDoor 4.0 Running USBBSDoor Locally 14 4.1 Notes on Automated Monthly Maintenance 14 4.2 Notes on Searching USBBS Lists 15 4.3 Notes on Downloading from USBBSDoor 15 4.4 Notes on FOSSIL Use 16 4.5 Notes on Using ARJ Instead of ZIP Files 16 4.6 Caller "Command Line" Search Information 17 4.7 On-Line Sysop Functions 17 4.8 Multi-nodes, Networks, Multi-taskers 17 QSUSBBS 5.0 What is QSUSBBS (Quick-Search USBBS) 18 5.1 Restrictions On QSUSBBS Distribution 18 5.2 QSUSBBS Disclaimer 18 5.3 Personalizing Your Copy of QSUSBBS 19 MISCELLANEOUS 6.0 Where to Receive Assistance 20 6.1 Technical Notes 20 6.2 Log Entries 20 6.3 Error Messages 21 6.4 Disclaimer and Warranty 21 6.5 License to use USBBSDoor 21 6.6 Macro Chart 22 6.7 Local Status Line Layout 23 6.8 Parameters Used in 'Generic DOOR.SYS' Mode 24-25 REGISTRATION 7.0 Registering USBBSDoor 26 7.1 Register with CONFIDENCE - Author Information 26 -------------------------------------------------------------------- Page 3 USBBSDoor Page 3 -------------------------------------------------------------------- 1.0 What is USBBSDoor ---------------------- USBBSDoor is a door program which allows the caller to access the USBBS National BBS List on-line. The caller may search the list for area codes, state, up to twenty characters of text, systems offering Internet, brand of BBS software, and new or changed listings in the list. If the Sysop desires, the caller may also download the list from within USBBSDoor. An optional security level may be attached to downloading. Searches may be conditional. Callers may specify where (area code, state, or entire list) to perform searches for Text, Internet, Brand of BBS, or New listings. Automated monthly Sysop maintenance! The Sysop simply places a new list each month in a specified location and USBBSDoor will know it is there and use it (registered copies only). USBBSDoor works with many types of BBS software, including PCBoard, Wildcat!, RBBS, GAP, Spitfire, Remote Access, and any software which uses door information files compatible with those BBS types. "Header" and "footer" information files from the list are created automatically! Built-in local maintenance mode and configuration file editor with F1 pop-up help at each parameter for easy installation and testing. For callers in color mode, the list output is colorized "on-the-fly" for a nice effect. (H)elp is embedded in the Area code and State input prompts, in case a caller needs help determining an area code or state abbreviation. USBBSDoor is DESQview aware. Screen and keyboard I/O are limited to their assigned window. USBBSDoor gives back time slices while idling at input prompts. Text files (MENU, etc.) may contain PCBoard macros, Wildcat macros, or ANSI for color. Several USBBSDoor information @macros@ may be used in text files. USBBSDoor supports non-standard COM port operation. USBBSDoor supports FOSSIL communications. USBBSDoor runs at all baud rates and has been thoroughly tested with COM ports locked at 115kb. -------------------------------------------------------------------- Page 4 USBBSDoor Page 4 -------------------------------------------------------------------- 1.1 What's New --------------- Refer to the enclosed HISTORY.TXT file for complete details of new features and changes to this and previous releases of USBBSDoor. 1.2 Upgrading from Previous Versions ------------------------------------- * * * * * * If upgrading from USBBSDoor 5.3 or earlier: ------------------------------------------------------- Use the new MENU, HELLO, HELPx, AREAx, STATE, and BRAND files. Remove the MODEM file. Review the HISTORY.TXT file. Set any new configuration switches as needed. * * * * * * If upgrading from USBBSDoor 4.4 or earlier: ------------------------------------------------------- All of the above, plus: Remove the old AREA.HLP, STATE.HLP, MODEM.HLP, and BRAND.HLP files. If using non-standard COM ports (COM ports other than 1 or 2) USBBSDoor now passes the SEND.BAT file the base address and IRQ for use with the DSZ "portx" option. See section 3.3 page 12 for more. See the section on PROTOCOL.DAT for modifying this file for Sysop selectable USBBSDoor status line placement during shelled protocol transfers (Top or Bottom of the screen). * * * * * * If upgrading from USBBSDoor version 4.3: ---------------------------------------------------- All of the above, plus: You should review the sections of this manual concerning QSUSBBS. * * * * * * If upgrading from USBBSDoor versions 4.0 through 4.2: ----------------------------------------------------------------- All of the above, plus: In USBBSDoor's configuration file editor, set the "Set non-standard COM information" (if appropriate) and the "(F)ast-search area code or state" parameters. F1 help is available at all setup parameters to facilitate a quick upgrade. BYE and BYEG files are no longer used in USBBSDoor. * * * * * * If upgrading from USBBSDoor version 3.0 or earlier: -------------------------------------------------------------- USBBSDoor will need to be completely reinstalled. With the F1 key help at each local setup parameter it should take about 5 minutes! -------------------------------------------------------------------- Page 5 USBBSDoor Page 5 -------------------------------------------------------------------- 2.0 A Word on Installing Doors ------------------------------- The purpose of this documentation is to explain to you how to install the USBBSDoor program. It assumes that you have already read the manual which comes with your BBS software concerning doors and their use. It is not within the scope of this manual to cover door installation for each type of BBS USBBSDoor is compatible with. 2.1 Obtaining the Current USBBS List ------------------------------------- The USBBS National BBS List is required. It is not possible for a USBBS list to be included within USBDOR54.ZIP, since the list is updated monthly. A recent USBBS list is always available on our system in the USBBS door. The current "home" of the USBBS list is Bob Breedlove's BBS: 916-929-7511. The USBBS list follows a pattern for naming in the convention of USBBSxxx.LST. The ZIP file which contains it follows this same pattern. The "xxx" is the version number and increments monthly. As of this writing the version is 132 (USBBS132.LST in USBBS132.ZIP) for 05/95. Using this method you can determine the 6/95 list would be USBBS133.ZIP, etc. Each USBBSxxx.ZIP contains a file called USBBSxxx.TXT. This file lists the current distribution and update points for the USBBS list. Although Yandell Custom Software is currently a distribution and update point for the USBBS listings, there is no affiliation between them and the owners and editors of the USBBS list. 2.2 Required Files ------------------- The following files should be enclosed with USBDOR54.ZIP : QUICK.DOC - Quick and easy installation guide. USBBSDOR.EXE - The executable program file. USBBSDOR.DOC - This documentation file. USBSETUP.HLP - Help file for F1 help in local setup screen. USB-CONV.EXE - Convert default text files to Sysop's choice. MENU - The door program's main menu. HELP, 2, 3 - Help files shown when a caller requests (H)elp. HELLO - A text file displayed when entering the door. AREA, 2, 3 - Help files for the Area Code prompt. STATE - Help file for the State prompt. BRAND - Help file for Brand of software prompt. SEND.BAT - A single batch file for all external protocols. PROTOCOL.DAT - A configuration file for external protocols. QSUSBBS.EXE - Small, fast off-line USBBS list search & viewer. QSUSBBS.DOC - Documentation for QSUSBBS. QSREG.BAT - Use to personalize QSUSBBS (registered only). LOCAL.BAT - Batch file for USBBSDoor's local maintenance mode. FILE_ID.DIZ - USBBSDoor description file. HISTORY.TXT - Over seven years of USBBSDoor! ORDER.FRM - Order form for registering USBBSDoor. There should be twenty-four files in USBDOR54.ZIP. All of the files should be dated 05-09-95. -------------------------------------------------------------------- Page 6 USBBSDoor Page 6 -------------------------------------------------------------------- 3.0 Setting Up USBBSDOR.CNF ---------------------------- Create a directory where USBBSDoor will reside. Extract the entire contents of USBDOR54.ZIP into this location. USBBSDoor uses a configuration file for certain door parameters. The default name is USBBSDOR.CNF, however you may designate any name for this file. USBBSDoor contains a built-in editor for this file. The first installation step is to properly configure this file for your system. You must enter USBBSDOR /L at your DOS prompt or use the enclosed LOCAL.BAT file (which is easier to remember) to invoke the door in its local maintenance mode. Select option #1 for "creating or modifying config files". You will then be prompted for a config file name. Simply hit enter to use the default USBBSDOR.CNF or enter a file name of your choice. You may use one configuration file for all nodes, unless you wish to enable certain features on some node's and not on others. You may use F1 to see the information below in a pop-up help window. * BBS software (door file) type ------------------------------- Please read this section carefully to avoid making incorrect assumptions about this parameter. 1) PCBoard 14.5 through 15.x ONLY!. 2) PCBOARD.SYS Generic PCBOARD.SYS, Auntie (auntie.sys), etc. 3) DOOR.SYS Generic DOOR.SYS systems. 4) DOOR.SYS Wildcat 3.x and 4.x ONLY. 5) DORINFOx.DEF RBBS and software which writes color mode as 2. 6) DORINFOx.DEF RA and software which writes color mode as 1. 7) SFDOORS.DAT Spitfire, etc. Selection #2 will allow entering an alternate file name. Press enter for the default file name displayed, or enter the name of the file your BBS software creates. For instance, Auntie Sysops would select #2, then enter AUNTIE.SYS. With the exception of #5 and #6 USBBSDoor only supports the original software's format for each information file. On multi-node systems which utilize DORINFOx.DEF (x = node #), USBBSDoor will select the appropriate file (DORINFO1 DORINFO2 etc.) based on the node number. * Name of this system --------------------- The name entered here is displayed at USBBSDoor's termination in the "Registered To:" message (registered copies only). The name used in this parameter MUST be identical to the name used when ordering a customized registration number for USBBSDoor. If registered, this name is also used when personalizing the QSUSBBS utility. Section 3.0 continues on the next page -------------------------------------------------------------------- Page 7 USBBSDoor Page 7 -------------------------------------------------------------------- 3.0 Setting Up USBBSDOR.CNF (continued) ---------------------------------------- * Idle keyboard time-out (minutes) ---------------------------------- Enter the number of minutes before a keyboard time-out occurs. USBBSDoor cycles back to the BBS should this happen. USBBSDoor will beep at the caller once every fifteen seconds during the last minute of the time-out period before returning the caller to the BBS. * Disable CTS signal checking ----------------------------- Always answer no to this question unless you know for a fact that disabling (answering yes) is best for your system. NEVER disable (answer yes) CTS when using a high speed or MNP modem. * Location of current USBBSxxx.LST -------------------------------- Enter the location where you will be keeping the EXTRACTED USBBSxxx.LST each month (xxx = version). NEVER place a file name in this parameter. USBBSDoor looks for the newest USBBSxxx.LST in this location each time it runs. This is also the location USBBSDoor will automatically extract a new list to (if your copy of USBBSDoor is registered) if a new list is detected in a new USBBSxxx.ZIP file. See page 14 section 4.1. * Disable (D)ownload option --------------------------- USBBSDoor provides the caller a simple facility for downloading the the current USBBSxxx.ZIP. When (D) is selected USBBSDoor will choose the current USBBSxxx.ZIP file and display its size and download time to the caller. The caller then chooses a transfer protocol. If the caller has insufficient time remaining to transfer the file, the download will not be allowed. If you do not wish your callers to be able to download inside the door, answer Yes to disable downloading. * Security needed to Download ----------------------------- Enter the security level required for downloading. Some Sysops may want to allow new or non-subscribing callers access to the list but not want them to be able to use USBBSDoor's download feature. This parameter facilitates this Sysop preference. USBBSDoor uses the caller's security level as it is provided in the BBS software's door information file (not available in generic PCBOARD.SYS mode #2). Section 3.0 continues on the next page -------------------------------------------------------------------- Page 8 USBBSDoor Page 8 -------------------------------------------------------------------- 3.0 Setting Up USBBSDOR.CNF (continued) ---------------------------------------- * Minimum Connect Speed to Download ----------------------------------- Enter the lowest connect rate a caller can connect with and still be able to download USBBSxxx.ZIP and QSUSB21.ZIP (if installed). If you are using your BBS software facility for limiting downloads based on connect rates, you should set this parameter similarly. * Location of newest USBBSxxx.ZIP --------------------------------- If you allow downloading, this parameter works in the same fashion as "Location of current USBBSxxx.LST". Simply enter a location where the newest USBBSxxx.ZIP (xxx = version) will be located. USBBSDoor will look for the newest USBBSxxx.ZIP in this location when a caller requests a download. If you wish to allow the caller to download QSUSB21.ZIP in USBBSDoor the location entered here is also used for QSUSB21.ZIP. Even if downloading is not desired, this parameter is also used if USBBSDoor is registered and you wish it to automatically detect and extract a new USBBS list to its appropriate location. See page 14, section 4.1 for a detailed explanation of this feature. Files compressed in ARJ format may also be used. See section 4.5 on page 16 of this manual before attempting to use them. * Disable `searching' message ----------------------------- When performing certain search functions on a USBBS list, USBBSDoor will display a "searching.." message between "finds". On faster systems, these "searching.." messages come and go so fast that they appear to be little glitches on the screen. After you have installed USBBSDoor, select CA as a state to display then observe between area codes as listings are displayed. Usually, only node's running on 8088's, slow drives, or extremely heavy network traffic will need this option enabled. * Line separating each listing ------------------------------ You may specify whether to put a dashed line, a solid line, double lines, or no line between each listing as it is displayed. Valid answers are 0, 1, 2, or 3 as shown below: Type 0: None. Each listing will be displayed with no separation. Type 1: ASCII 45 characters (dashes) Type 2: ASCII 196 characters (solid line) Type 3: ASCII 205 characters (double line) Separator type #2 is highly recommended for easiest viewing. Section 3.0 continues on the next page -------------------------------------------------------------------- Page 9 USBBSDoor Page 9 -------------------------------------------------------------------- 3.0 Setting Up USBBSDOR.CNF (continued) ---------------------------------------- * Set non-Standard COM information ---------------------------------- If you are using COM 1 or 2, ignore this parameter. If COM ports other than 1 or 2 are used, the base address and IRQ of each non- standard port must be defined. Enter the base address in HEX for the appropriate ports in use. Enter the IRQ (1-15) for the appropriate ports in use. Allowing multiple ports to be defined in a single USBBSDOR.CNF file facilitates the need for only one configuration file for all nodes. When a COM port other than 1 or 2 is detected in the BBS door infor- mation file, the appropriate information is used for that port. The base address and IRQ for COM 1 or 2 cannot be changed. USBBSDoor does not support IRQ sharing in PS/2 machines. * (F)ast-search area code or state ---------------------------------- The Sysop may configure the (F)ast-search command to immediately display an Area code or State without any additional prompting from the caller. Simply enter a three digit area code, or two digit state code (Sysop's choice) at this parameter. To disable the (F)ast-search command, simply leave this field blank. * Use a FOSSIL driver --------------------- USBBSDoor can communicate with an installed FOSSIL driver instead of communicating directly with the serial port(s). If your BBS software does not use a FOSSIL driver, answer No to this question. If you are not sure if your BBS uses a FOSSIL driver, it probably does not. If your BBS software requires a FOSSIL driver, you may wish to have USBBSDoor use it. Check your BBS manual for additional information on the use of doors that support FOSSIL communications. * USBBSDoor registration number ------------------------------- USBBSDoor is fully functional in unregistered copies except for the "automatic new list extraction" feature. Registration enables this feature. When USBBSDoor terminates, the message "Unregistered Copy" and a brief delay appears. A custom registration number will replace this with the name of your system and remove the brief delay. Registration also will allow you to personalize a copy of QSUSBBS with your BBS name and phone number (see pages 18 and 19). You may receive a customized registration number INSTANTLY by using a major charge card. See the enclosed file ORDER.FRM for details. -------------------------------------------------------------------- Page 10 USBBSDoor Page 10 -------------------------------------------------------------------- 3.1 Setting Up Door Files to Call USBBSDoor -------------------------------------------- The purpose of this section is to describe the command line calling parameters for USBBSDoor in a door (batch) file. You must refer to your BBS manual for complete instructions on installing doors with your BBS software. USBBSDoor has the ability to know the location where USBBSDOR.EXE has been executed. It is therefore unnecessary to change drives and directories in the door batch file used to call USBBSDoor. This is shown in method #1 below, using the location of USBBSDoor in-line. The naming conventions of door batch files varies greatly between different BBS systems. Some BBS systems allow the Sysop to call the door batch file anything they like (USBBS.BAT). Others might not even require the .BAT extension (USBBS). Other systems may have a pre-determined pattern for naming door batch files based on the door number on the system (DOOR1.BAT, etc.). Refer to your BBS manual for door batch file naming requirements. Sample door batch file (method #1): ----------------------------------- @echo off D:\USBBSDOR\USBBSDOR.EXE USBBSDOR.CNF C:\PCB board.bat | | | | | | The program Config file. Location where the BBS makes is called with this node's door info file. the location Location ONLY! in-line as shown. Sample door batch file (method #2): ----------------------------------- @echo off D: cd\usbbsdor USBBSDOR.EXE USBBSDOR.CNF C:\PCB D: | | cd\pcb | | board.bat Config file. --- Location where the BBS creates this node's door information file. Location ONLY! Multi-node DORINFOx.DEF type systems (RBBS) - place a %1 after the node's door information file location, so USBBSDoor will know which node is being used. USBBSDoor will work fine with either method shown above. Method #1 simply results in slightly faster loading and exiting of the door. Each example above ends with BOARD.BAT which should be replaced with the name of the batch file that runs your BBS. Your BBS software may or may not require this, especially if your BBS software has been set-up to "shell" to USBBSDoor. -------------------------------------------------------------------- Page 11 USBBSDoor Page 11 -------------------------------------------------------------------- 3.2 Setting Up PROTOCOL.DAT ---------------------------- If you allow downloading, you may wish to review the enclosed PROTOCOL.DAT file to see if it meets your needs. PROTOCOL.DAT is used to configure the designated "letter" for each type of protocol. USBBSDoor contains no internal protocols, and relies solely on external protocols such as DSZ for this function. Sample PROTOCOL.DAT ------------------- X,N,Xmodem,T C,N,Xmodem/CRC,T O,N,1K-Xmodem,T F,Y,1K-Xmodem/G,T Y,N,Ymodem,T G,Y,Ymodem-G,T Z,N,Zmodem,T There are 4 parameters on each line, each separated by a comma: Parameter #1 - the protocol letter choice. Parameter #2 - Y if error correction is required for this protocol, N or blank if not. Parameter #3 - short protocol description. Parameter #4 - B will force the USBBSDoor status line to appear at the bottom of the screen, a T or blank will make the USBBSDoor status line appear on top of the screen during the protocol shell. Parameter #4 recommendations: For DSZ protocols use T (top). For GSZ protocols use B (bottom). Place SET GSZWINDOW=21 in each node's batch file which starts the BBS. For HS-Link use T (top). Example line in PROTOCOL.DAT (using DSZ): Z,N,Zmodem,T (using GSZ): Z,N,Zmodem,B Others: Use what works (looks) best for you. You may use any letter as a protocol except "V". The caller will have the opportunity at the protocol prompt to view the contents of the USBBSxxx.ZIP file by selecting View. The ZIP view is internal to USBBSDoor. See the next section about setting up SEND.BAT. See page 15 section 4.3 for additional details about downloading. -------------------------------------------------------------------- Page 12 USBBSDoor Page 12 -------------------------------------------------------------------- 3.3 Setting Up SEND.BAT ------------------------ USBBSDoor uses a single batch file for all external protocols. It is not within the scope of this manual to provide instructions for setting up different types of protocols and all of their individual command line options. The enclosed SEND.BAT and PROTOCOL.DAT, along with the popular DSZ external protocol, should provide ample protocol coverage for the simple task of downloading the current USBBS list or QSUSBBS from USBBSDoor. If you wish to add or delete protocols, the information below might assist you. SEND.BAT is passed the following parameters from USBBSDoor: %1 (speed) %2 (port) %3 (filename) %4 (protocol letter used in USBBSDoor) %5 base address (hex) for com port (use with portx option). %6 IRQ for com port (use with portx option). %7 DTE (locked baud rate - may be needed by FOSSIL protocols). An examination of SEND.BAT will demonstrate how the protocol letter is used to branch to the appropriate protocol command. If you are familiar with this type of batch file programming you may wish to modify it. If not, our best recommendation is to use it "as is". As mentioned previously the default configuration used with the popular DSZ protocol will provide ample coverage. IMPORTANT: If using GSZ (the graphical counterpart to DSZ) for any of the protocols, place the following SET command in the batch file used to start the BBS on each node: SET GSZWINDOW=21 Sysops using non-standard com ports may use one SEND.BAT for all nodes without the need for DSZPORT environment variables, etc. On non-standard nodes USBBSDoor will pass the base address and IRQ as defined for the com port in USBBSDOR.CNF. On nodes with standard COM ports USBBSDoor will always pass 3f8,4 for COM1 and 2f8,3 for COM2. Example DSZ command line in SEND.BAT for non-standard COM ports: :Zmodem DSZ portx %5,%6 pB4096 sz -m %3 | (note comma) NOTE: The above paragraph applies only to those Sysops using COM ports other than 1 and 2 on their systems. See page 15 section 4.3 for additional details about downloading. FOSSIL NOTE: If you are using USBBSDoor in its FOSSIL mode, DSZ and GSZ mentioned above cannot be used. There are FOSSIL "equivalents" which are available. Their use and implementation is beyond the scope of this manual. -------------------------------------------------------------------- Page 13 USBBSDoor Page 13 -------------------------------------------------------------------- 3.4 Setting Up and Modifying Text Files ---------------------------------------- This section deals with the text display files USBBSDoor uses. These files are MENU, HELLO, HELPx, AREAx, STATE and BRAND. The files which come with USBBSDoor utilize the PCBoard color macro method instead of ANSI. This allows one file to be used instead of two files. USBBSDoor allows three different file types to accommodate different BBS systems. The examples below illustrate the MENU file but apply to all of the files listed above: Type #1 - PCBoard color macros. Using PCBoard color macros, both color & non-color versions of the file are in one file called MENU. Type #2 - Wildcat color macros. Using Wildcat color macros, both color & non-color versions of the file are in one file called MENU. Type #3 - Ascii and ANSI files. The non-color file is a regular Ascii text file called MENU. The color file is an ANSI file that is called MENUG. When ANSI is used in any of the above files, the "G" must be added to the file name. If you wish to modify the enclosed text files using a different method, use the USB-CONV.EXE program to convert the enclosed type #1 files to type #2 or type #3. USB-CONV.EXE will only convert the enclosed text files mentioned above. Important: When modifying ANSI files, TheDraw is recommended. When saving the file, if you wish the screen to clear you will need to select that option. When asked for the "Line Length" by TheDraw when saving a file, always answer NONE for best performance in USBBSDoor. Previously, some Sysops experienced difficulty when editing the multi-paged text files such as HELP and AREA. USBBSDoor now supports linking files together, by specifying a "next" filename in the file currently being displayed. This is done by placing a % (percent) in the LEFT-MOST (column #1) position on line #24 of the current file. The % must then IMMEDIATELY be followed by the file USBBSDoor is to display next, such as %HELP2. This allows the Sysop to edit each page easily and separately, especially those wishing to use the ANSI file method. It is recommended the %FILENAME be located on the 24th line of each file where it is being used, so the new file will begin immediately after a "More?" prompt appears. IMPORTANT: Regardless of the file type in use, do not designate the %FILENAME parameter while using a color ANSI or macro editor. These editors will place color instructions BEFORE the % on the line, thereby removing the % from the first position in the line. The %FILENAME must be added with a plain text editor AFTER saving the file with the color editor. Refer to the enclosed AREA? and HELP? files for examples of linking these long files together by making individual shorter files. Refer to page 22 section 6.6 for the macro chart. -------------------------------------------------------------------- Page 14 USBBSDoor Page 14 -------------------------------------------------------------------- 4.0 Running USBBSDoor Locally ------------------------------ Start USBBSDoor with /L (USBBSDOR /L) or the LOCAL.BAT file. Select option #2. You will be prompted for the configuration file to use, then you will be asked whether you would like to begin with color mode on or off. These selections allow you to see how USBBSDoor will appear to a caller on-line. USBBSDoor also works through the BBS in local mode and behaves in the same fashion as if a caller were on- line. When running USBBSDoor in local maintenance mode (/L) the name appearing on the status line will be (Local) SYSOP and will default to a time limit of 90 minutes. 4.1 Notes on Automated Monthly Maintenance ------------------------------------------- USBBSDoor automatically detects the presence of new USBBS lists and new USBBS zip files and acts accordingly. When USBBSDoor is run, it checks the "list location" the Sysop specified in the configuration file for the presence of USBBSxxx.LST files. It determines which is the newest one and uses it for the caller's on-line session. Two files are needed by USBBSDoor for the "Explain symbols" command and the "(I)nformation about list" command. These files contain information found at the beginning and end of USBBS lists. If these files do not exist, USBBSDoor automatically creates them from the list when it is run. If they do exist, USBBSDoor checks to see if a list has been installed which is NEWER than these two information files. If the list is newer, new information files are automatically created from the new list. When a caller selects (D)ownload, USBBSDoor checks the "USBBSxxx.ZIP file" location the Sysop specified in the configuration file. It determines the newest USBBSxxx.ZIP and presents it to the caller for downloading. If no USBBSxxx.ZIP files are found, USBBSDoor will search for USBBSxxx.ARJ files, but only after looking for ZIP files. To update the monthly list in registered copies of USBBSDoor all the Sysop has to do is put the new USBBSxxx.ZIP file where the door has been told it is. USBBSDoor will determine the newest USBBSxxx.ZIP file each time it runs. USBBSDoor will then look inside this newest ZIP and determine the date of the USBBSxxx.LST file inside. If this date is NEWER than the current USBBSxxx.LST, or if for some reason there is no "current" USBBSxxx.LST, USBBSDoor will extract it and place it where you have indicated it should be in USBBSDOR.CNF. PKUNZIP.EXE must be available via a DOS path in order for this "automatic extraction" to work. If a new list is automatically extracted, the files USBBSxxx.TXT and USBBSxxx.NWS will be extracted also (when present) and USBBS.INF and USBBS.SYM (see above) will be created accordingly. Sysops who have not registered USBBSDoor will need to remember to extract the contents of the ZIP file to the location you have indicated for the list file in USBBSDOR.CNF. USBBSDoor will not perform this extraction for you until you have registered it. -------------------------------------------------------------------- Page 15 USBBSDoor Page 15 -------------------------------------------------------------------- 4.2 Notes on Searching USBBS Lists ----------------------------------- USBBSDoor contains a file engine which permits extremely fast searches on unformatted (sequential text) files. On AT class or faster machines, end to end searches of USBBS lists are nearly instantaneous. Several methods of searching can be performed in the list. Area Code, States, 20 characters of Text, BBS brand, Internet access, and listings which are New or changed in the current list can be searched for. When performing searches for Text, Internet, Brands, or New, the caller may specify whether to search for them in an Area code, a State, or the Entire list. Commands may be parsed at the USBBSDoor command prompt, such as: A 813 Searches for area code 813 immediately. S FL Searches for Florida immediately. N 606 Searches for NEW systems in area code 606. I KY Searches for systems offering Internet in Kentucky. I E Searches the Entire list for systems offering Internet. (T)ext and (B)rand of BBS software may be searched this way also, except the text search will not accept the last parameter (where to search), as it must be entered at the "where to search" prompt. 4.3 Notes on Downloading From USBBSDoor ---------------------------------------- USBBSDoor does not contain a "display entire list" command. If the caller wants the entire list they may download it in compressed form rather than listing the entire contents, which saves a tremendous amount of on-line time. You must use a DSZ log compatible protocol in conjunction with the DSZLOG= environment setting in order for USBBSDoor to determine if a download was successful or not. If you use the default SEND.BAT and PROTOCOL.DAT, USBBSDoor will expect to find DSZ in the current directory or in a DOS path. If the environment setting DSZLOG= is being used, USBBSDoor will correctly place successful/aborted download information in a file called USBBSDOR.LOG. On PCBoard and Wildcat systems USBBSDoor will will write the download information to the node's caller file (activity log). All downloads from USBBSDoor are considered free, as USBBSDoor does not write to any BBS software's USER files. If a caller does not have sufficient time remaining to download a file, the transfer will not be permitted. NOTE: It has been noted that some BBS packages which use DORINFOx.DEF as a door file place the locked DTE modem speed, not the callers connect rate, into the door file. In these cases, callers at speeds BELOW the locked DTE rate will be told the transfer time is shorter than it actually is. -------------------------------------------------------------------- Page 16 USBBSDoor Page 16 -------------------------------------------------------------------- 4.4 Notes on FOSSIL Use ------------------------ Beginning with USBBSDoor 5.1 FOSSIL communications are supported. If your BBS uses a FOSSIL driver you may now have USBBSDoor use the FOSSIL driver also. USBBSDoor has been tested with popular FOSSIL drivers currently available. You may also take advantage of this feature if your BBS software supports Multi-port serial cards and permits FOSSIL input to these cards through the same driver used for the BBS software. Some BBS packages have Multi-port drivers which allow this, even though these drivers are not considered to be FOSSIL drivers themselves. To force USBBSDoor to place output to the FOSSIL specification instead of normal COM output, set the toggle in the USBBSDoor local configuration screen (USBBSDOR /L). To download USBBS lists from USBBSDoor while using the door in its FOSSIL mode, the enclosed recommendations for using the popular DSZ package must be disregarded. Sysops already using FOSSIL drivers in conjunction with their BBS software should already be familiar with FOSSIL replacements for DSZ. These replacements must be installed in SEND.BAT in place of the DSZ recommendations. A discussion of this process is beyond the scope of this manual. 4.5 Notes on Using ARJ Instead of ZIP Files -------------------------------------------- Due to the growing popularity of this compression utility, USBBSDoor can now use USBBSxxx.ARJ files (if downloading is allowed). For the purpose of downloading and "new list auto extraction" (registered feature), USBBSDoor always looks for ZIP files first, then ARJ if no USBBSxxx.ZIP files are found. The off-line QSUSBBS search utility may now also be downloaded from the door in ARJ format (same as USBBSxxx, the door looks for QSUSB21.ZIP first). If you create corresponding USBBSxxx.ARJ and QSUSBBS.ARJ files from their .ZIP counterparts, you MUST remove the .ZIP files or USBBSDoor will see them first and use them instead of your .ARJ files. If you prefer to use .ARJ files for these two files, substitute .ARJ for .ZIP whenever it appears in conjunction with a filename in this manual and all of those operations will perform in the same manner. NOTE: If your copy of USBBSDoor is registered and you use the "auto- extraction" feature each month, please be aware that ARJ requires MUCH more memory than PKUNZIP to extract the files. If you are SHELLING to USBBSDoor from your BBS software and not swapping your BBS software out of memory during the shell (if your BBS permits), there will probably NOT be enough memory for ARJ to extract the files from USBBSxxx.ARJ files. In other words, if your BBS is not in memory when USBBSDoor runs and detects a new USBBSxx.ARJ, it will probably be able to extract its contents (unless there are a lot of other memory resident applications running). ARJ.EXE must be avail- able via a DOS path. -------------------------------------------------------------------- Page 17 USBBSDoor Page 17 -------------------------------------------------------------------- 4.6 Caller "Command Line" Search Information --------------------------------------------- PCBoard software supports the passing of information by the caller to a door program. USBBSDoor takes advantage of this feature. For instance, if the door is named USBBS, and the caller enters USBBS NY at the PCBoard prompt, USBBSDoor will load and immediately begin searching for state NY and USBBS 813 would search for area code 813. Any valid USBBSDoor "stacked" command may also be entered, such as USBBS N 813 which immediately searches for (N)ew/changed listings in area code 813. USBBSDoor will always exit when the search has been completed if the door is started in this manner. This process is handled automatically by USBBSDoor and PCBoard. 4.7 On-line Sysop Functions ---------------------------- The following function keys may be used by the Sysop while a caller is on-line. To see these keys defined, enter ALT-H and they will be displayed in a portion of the status line. Only the keys which are valid with the type of BBS software USBBSDoor is running with will be displayed. F3 - Toggles printer on or off. This command is only valid when using USBBSDoor with PCBoard software. USBBSDoor follows this toggle from PCBoard and prints information such as downloads, carrier drops and keyboard time-outs. F6 - If you have attached a security level to USBBSDoor's Download function and the caller does not have sufficient security to download, hitting F6 will allow the caller to download the file. This option does not appear in the status line when ALT-H is used as there is extremely little chance of this Sysop function being used in the USBBSDoor application. F7 - Certain user input errors will cause USBBSDoor to beep at them. The Sysop has the ability to toggle whether the host beeps also. This toggle is followed from BBS packages which use a PCBOARD.SYS or DOOR.SYS door file and accurately set this toggle. F9 - Toggles the display on & off. USBBSDoor will follow the display toggle with all BBS software using a PCBOARD.SYS or DOOR.SYS file. F10 - This key will begin an on-line chat session. Press ESCape to end the chat and return the caller to USBBSDoor. 4.8 Multi-nodes, Networks, Multi-taskers ----------------------------------------- USBBSDoor has been developed in a networked environment. All multi- node features have been tested on our own multi-node system. USBBSDoor's primary test facility is a thirty-two node system. USBBSDoor is DESQview aware. It is automatically detected, screen and keyboard I/O are "well behaved", and time slices are given back to other applications while USBBSDoor is idle at an input prompt. -------------------------------------------------------------------- Page 18 USBBSDoor Page 18 -------------------------------------------------------------------- 5.0 What is QSUSBBS (Quick-Search USBBS) ----------------------------------------- QSUSBBS is an "off-line" quick search program for the popular USBBS listings. It provides extremely fast area code, state, or text searches on the USBBS list. Sysops who have registered USBBSDoor may personalize a copy of QSUSBBS.EXE for distribution. QSUSBBS will display a message each time it is run which says: "This copy of QSUSBBS is compliments of:" NAME OF BBS & PHONE NUMBER If QSUSBBS has been distributed by a BBS which has not registered USBBSDoor, the contents above will be: [ UNREGISTERED BBS COPY ] This personalization is available as a FREE option to Sysops who have purchased a USBBSDoor registration number. A personalized copy of QSUSBBS cannot be purchased separately. QSUSBBS may be downloaded from USBBSDoor. If QSUSB21.ZIP is located in the same location as specified for USBBSxxx.ZIP files, the caller will be given a choice (by number) of which files to download. If USBBSDoor does not find QSUSB21.ZIP, it will look for QSUSB21.ARJ. 5.1 Restrictions on QSUSBBS Distribution ----------------------------------------- The files QSUSBBS.EXE and QSUSBBS.DOC may be distributed without the entire USBBSDoor package (USBDOR54.ZIP) among BBS systems as long as ONLY those TWO files remain together in the same compressed file. Under no circumstances may either or both of these files be distrib- uted with any other product or service, including any national BBS listing. Files including but not limited to BBS advertisements or BBS lists may NOT be packaged with QSUSBBS. The compressed file name for the two QSUSBBS files must be QSUSB21 plus the extension name name reflecting the compression type (QSUSB21.ZIP). 5.2 QSUSBBS Disclaimer ----------------------- There are no warranties, expressed or implied, for QSUSBBS. Anyone who runs QSUSBBS on any computer assumes any and all liabilities for anything which may result as a consequence of running QSUSBBS. Under no circumstances shall Yandell Custom Software or the author of QSUSBBS be liable for any loss of profit or any other damages, including but not limited to special, incidental, consequential, or other damages, arising out of the use or inability to use QSUSBBS. -------------------------------------------------------------------- Page 19 USBBSDoor Page 19 -------------------------------------------------------------------- 5.3 Personalizing Your Copy of QSUSBBS --------------------------------------- * * * A great way to advertise your system! * * * The following files should be located with USBBSDOR.EXE: QSUSBBS.EXE QSUSBBS.DOC QSREG.BAT PKZIP.EXE must also be available via a DOS path. Run the QSREG.BAT file. 3 steps will AUTOMATICALLY be performed: Step #1 - You will be prompted for your system's telephone number. The QSUSBBS.EXE file will then be stamped with your BBS name (as it appears in USBBSDOR.CNF) and the phone number you just entered. This will appear on the screen each time QSUSBBS is started (as shown in section 5.0, page 18). Note: Step #1 will be skipped if USBBSDoor has not been registered. Step #2 - PKZIP.EXE will be used to create QSUSB21.ZIP which will contain QSUSBBS.EXE and QSUSBBS.DOC. PKZIP.EXE must be accessible via a DOS path. Step #3 - QSUSB21.ZIP will be copied to the location specified in the USBBSDOR.CNF configuration file for USBBSxxx.ZIP download list files. QSUSB21.ZIP must be located in that location so that it may be downloaded from USBBSDoor. QSUSB21.ZIP will not be copied to this location if (A) The location is blank or NONE, or (B) the location is the same location as QSUSB21.ZIP when created with USBBSDOR.EXE. If QSUSB21.ZIP exists with USBBSxxx.ZIP for download, USBBSDoor will allow the caller to choose between the two for download. USBBSDoor will also look for .ARJ files for the above to files, but only if the corresponding .ZIP files are not found. If you wish, you may place QSUSB21.ZIP in one of your regular BBS directories for download. The restrictions stated in section 5.1 on page 18 apply at all times. You may use other compression types for QSUSBBS.EXE and QSUSBBS.DOC in other areas of your system, however USBBSDoor itself will only recognize QSUSB21.ZIP or QSUSB21.ARJ. QSUSBBS.DOC should be read for additional info regarding QSUSBBS. -------------------------------------------------------------------- Page 20 USBBSDoor Page 20 -------------------------------------------------------------------- 6.0 Where To Receive Assistance -------------------------------- Yandell Custom Software (YCS) provides the following technical assistance for USBBSDoor: 813-842-8099 The YCS Support System. Available to all BBS Sysops. INSTANT on-line credit card registration and support system for YCS Shareware. On-line 7 days per week, 24 hours per day. Limited voice support is available to registered users of USBBSDoor. 6.1 Technical Notes -------------------- Carrier is monitored by USBBSDoor. USBBSDoor uses approximately 128K of memory. USBBSDoor performs its own "ansi-detect request" to the callers communications program. If the caller supports ANSI sequences then USBBSDoor uses ANSI for special cursor movement, screen clearing, and prompting. If running in the PCBoard or Wildcat specific modes, USBBSDoor uses the information in the door information files rather than performing its own ansi-detect request. All of the enclosed executable files have been compressed with a commercial compression utility. Uncompressed versions of these files are not available. 6.2 Log Entries ---------------- The following information is written to USBBSDOR.LOG: Completed downloads Aborted downloads Carrier drops Keyboard time-outs File access errors (Path not found) (Invalid drive) (File not found) On PCBoard and Wildcat systems the following is written to the caller (activity) logs: The same entries in USBBSDOR.LOG Sysop chat active Sysop chat ended Successful downloads are also entered in the DOWNLOAD.TXT file on PCBoard systems. -------------------------------------------------------------------- Page 21 USBBSDoor Page 21 -------------------------------------------------------------------- 6.3 Error Messages ------------------- The only error messages which should ever be displayed by USBBSDoor are self-explanatory file access error messages (not found, invalid drive, invalid directory, etc.). * bad command or filename * This message will be echoed to the screen if DSZ (or the specified external protocol) could not be found during a download attempt. External protocols must reside in the directory with USBBSDoor or in a valid DOS path. 6.4 Disclaimer and Warranty ---------------------------- USBBSDoor is a shareware product. USBBSDoor may be uploaded to BBS systems provided copyright notices are not removed and no changes are made to the program. There are no warranties, expressed or implied, for unregistered copies of USBBSDoor. Sysops who install USBBSDoor assume any and all liabilities for anything which may result as a consequence of running USBBSDoor. For registered copies of USBBSDoor, Yandell Custom Software warrants that USBBSDoor will perform as described in this documentation. In the event USBBSDoor does not perform as specified, then Yandell Custom Software will elect to either fix USBBSDoor or refund the amount paid, if notified within 30 days of registration. Under no circumstances shall Yandell Custom Software or the author of USBBSDoor be liable for any loss of profit or any other damages, including but not limited to special, incidental, consequential, or other damages, arising out of the use or inability to use USBBSDoor. 6.5 License to use USBBSDoor ----------------------------- USBBSDoor is not "public domain" or free software. A limited license is granted to evaluate USBBSDoor for thirty days after the initial installation. USBBSDoor must be registered if it is used after the initial thirty day evaluation period. Once USBBSDoor has been registered the registration may be used only on the original licensee's BBS system and only on nodes the original licensee owns and operates for their own purposes. If the original licensee provides some or all of their nodes to another entity, those nodes will require their own USBBSDoor registration. USBBSDoor registrations are not transferable. A USBBSDoor registration is a license to use the USBBSDoor software on one (1) BBS System at a single location with as many nodes as the original licensee owns and operates at THAT location. When the licensee owns and operates other BBS' in other locations, each location will require a separate USBBSDoor registration. If USBBSDoor has not been registered after 30 days, a Sysop reminder will begin appearing at program termination. -------------------------------------------------------------------- Page 22 USBBSDoor Page 22 -------------------------------------------------------------------- 6.6 Macro Chart ---------------- USBBSDoor utilizes color macro conventions used in PCBoard 14.5-15.x and Wildcat 3.x and 4.x. The color chart is enclosed below for other BBS system Sysops who wish to use color macros instead of ANSI. Background (first digit) Foreground (second digit) ----------------------- ------------------------- Black = 0 Black = 0 Blue = 1 Blue = 1 Green = 2 Green = 2 Cyan = 3 Cyan = 3 Red = 4 Red = 4 Magenta = 5 Magenta = 5 Yellow = 6 Yellow = 6 White = 7 White = 7 Background(Blinking Foreground) High Intensity(Bright Foreground) ------------------------------- --------------------------------- Black = 8 Black = 8 Blue = 9 Blue = 9 Green = A Green = A Cyan = B Cyan = B Red = C Red = C Magenta = D Magenta = D Yellow = E Yellow = E White = F White = F Examples: Bright White on Black background: @X0F (PCB) or @0F@ (WC) (0=black F=bright white) Bright Yellow on Red background: @X4E (PCB) or @4E@ (WC) (4=red E=yellow) Blinking Bright Red on Black background: @X8C (PCB) or @8C@ (WC) (8=black C=bright red) Other macros allowed (in any text file) @CLS@ clear screen @FIRST@ is the callers first name, (cased, i.e. Brent). @SYSDATE@ is the current date. @DATE@ is also the current date. @SYSTIME@ is the current time. @TIME@ is also the current time. @TIMELEFT@ is the minutes left for the caller. @LEFT@ is also the minutes left for the caller. @FILENAME@ is the NAME of the newest USBBSxxx.LST (list) found. @FILEDATE@ is the DATE of the newest USBBSxxx.LST (list) found. @ZIPNAME@ is the NAME of the newest USBBSxxx.ZIP (USBBSxxx.ARJ). @F@ is the (F)ast-search parameter. -------------------------------------------------------------------- Page 23 USBBSDoor Page 23 -------------------------------------------------------------------- 6.7 Local Status Line Layout ----------------------------- * LEFT side of the status line: ------------------------------- ----- Node # | ----Connect speed | | ------Error correction | | | ------Caller Name | | | | ------Caller City & State | | | | | 1 (14400E) BRENT YANDELL - PORT RICHEY, FL G (05-05-95) Sec(1)=110 Times On=9812 (PABF) | | | | | | | | | | | --- See Note #1 | | | | ------ Times on system | | | ----- Current security | | ---- Current Conference | ----- Date of last call ---Caller's Screen (G) = Color (ANSI capable) (A) = Mono (ANSI capable) (N) = Mono (No ANSI) (R) = RIP (Ripscrip) * RIGHT side of the status line: -------------------------------- Time of this call ---- Minutes in door ----------- | Press to describe function keys -- | | | | | ALT-H=Help 8 15:07 USBBSDoor 5.4 368K 112 15:15 | | | | Door name and version ---------- | | | Available free memory --------- | | Minutes remaining ----- | Current time ----- NOTE #1: The bottom status line may sometimes contained letters in parentheses (). These will appear depending on your BBS software. P = Printer toggle (PCBoard only). If logging caller log activity to the printer, USBBSDoor will do so also. A = The 'caller alarm' bell is on. USBBSDoor will beep locally at caller input errors if this is set in door information files. B = Information purposes only. PCBoard only. B = page bell 'ON'. F = FOSSIL communications mode is being used. -------------------------------------------------------------------- Page 24 USBBSDoor Page 24 -------------------------------------------------------------------- 6.8 Parameters Used In 'Generic DOOR.SYS' Mode ----------------------------------------------- This information only applies to Sysops using BBS type #3 (door.sys) in USBBSDoor's setup screen. This reference is for Sysops whose BBS does not create the standard "52 line" DOOR.SYS file. These Sysops may be able to use this information to configure door converters, DOOR.SYS macro generators, etc. NOTICE: This DOOR.SYS technical reference section is excluded from all warranties, expressed or implied. The author has attempted to make USBBSDoor flexible as possible when reading DOOR.SYS files made by Sysops, door converters, and other BBS author's. It is impossible to guarantee this flexibility will be sufficient to run USBBSDoor in DOOR.SYS mode when using a non-standard DOOR.SYS file. The following is each line number, an example in quotes (the quotes do not exist in actual DOOR.SYS files), and what USBBSDoor expects. LINE #1 "COM1:" (etc.) COM Port - USBBSDoor uses the numeric part only. In order for USBBSDoor to work in local mode through the BBS, this must be represented as COM0 (that's a zero) when your BBS runs the door with you on locally. This MUST be represented as COM0, COM1, COM2, etc. This is mandatory run-time caller information. The colon is in standard DOOR.SYS, but USBBSDoor does not require it. LINE #2 "14400" (etc.) Connect speed - This should be the connect speed of the caller, not the locked DTE. It is used to calculate file download times, it is displayed on the status line, and is passed to SEND.BAT for downloads. This entry is mandatory. LINE #4 "1" Node Number - While the DOOR.SYS standard dictates this default to a 1 on a single node system, USBBSDoor will tolerate a 0 here if that is what the BBS or converter places here. The only use for this information in DOOR.SYS mode for USBBSDoor is placing it in LOG file entries and displaying it on the status line. This entry is optional but highly recommended on multi-node systems. LINE #5 "38400" (etc.) DTE speed - This should be the locked DTE speed of the system, not the caller connect speed. Its only use is if it is needed by external non-DSZ protocols (sent to SEND.BAT as the %7 parameter). This is optional unless needed as described. LINE #6 "Y" or "N" - Local screen display on or off. USBBSDoor will always assume the screen display is ON unless this contains a "N". This line is optional, but should be a "Y" or blank if your local screen is always on. LINE #9 "Y" or "N" - Sysop page on/off. Used only to display on the status line whether the Sysop has paging turned on in the BBS. This is optional. Section 6.8 continues on the next page -------------------------------------------------------------------- Page 25 USBBSDoor Page 25 -------------------------------------------------------------------- 6.8 Parameters Used In 'Generic DOOR.SYS' Mode (continued) ----------------------------------------------------------- LINE #9 "Y" or "N" - Alarm bell on/off. Used to display on the status line if the Sysop has alarms (local beep on caller input errors) turned on in the BBS. USBBSDoor use is optional. LINE #10 "BRENT YANDELL" - Caller's name. USBBSDoor will truncate the name at 25 characters. Mandatory information. LINE #11 "PORT RICHEY, FL" - Caller's city and state. USBBSDoor will truncate this at 24 characters. Optional but highly recommended. LINE #15 "110" - Caller's security level. This must be a numeric value passed by the BBS. It is used to determine if (D)ownloads are allowed, for the (S)elect commands, and it is displayed on the status line. This is optional, unless limiting caller downloads by security level or access to text with (S)elect is desired. If this line is 0 or blank USBBSDoor will place "N/A" on the status line. LINE #16 "78" - Number of times caller has called the system. This is displayed on the status line. This is optional. If this line is 0 or blank USBBSDoor will place "N/A" on the status line. LINE #17 "12-23-93" - The date of the caller's last call. This is displayed on the status line. This is optional. If this line is blank USBBSDoor will place the current date on the status line. LINE #19 "60" - Minutes remaining this call. This is mandatory. LINE #20 "GR" or "NG" or "RIP" - Graphics (color). USBBSDoor will assume the caller is NOT in color UNLESS this field is "GR" or "RIP" by the BBS or converter. Optional but highly recommended. LINE #24 "1" - Last conference (area) in. Displayed on the status line. Use of this parameter is optional, however a 0 (zero) should be written to this line if not used. LINE #27 "Z" - Default protocol. This will be used as the default protocol for downloading unless the caller chooses differently. Use of this parameter is optional. If blank USBBSDoor will make the default protocol "(N)one" and allow the caller to choose. LINE #38 "Y" or "N" - Error correcting connection. This is part of what is considered the "extended" DOOR.SYS. If "error correcting" connect protocols are defined in PROTOCOL.DAT, USBBSDoor will only allow their use if this field is a "Y". If this line does not exist in your DOOR.SYS, USBBSDoor will assume "N", which is only a problem if you have assigned protocols in PROTOCOL.DAT as needing error correction. If your DOOR.SYS does not have this entry, protocols which require modems with error-correction such as YModem-G should not be defined in PROTOCOL.DAT, since there is no way to determine if the caller has made an error correcting connect. -------------------------------------------------------------------- Page 26 USBBSDoor Page 26 -------------------------------------------------------------------- 7.0 Registering USBBSDoor -------------------------- USBBSDoor is not free software. USBBSDoor must be registered within 30 days of installation. USBBSDoor is fully functional in unregistered copies except for the "automatic new list extraction" feature. Registration enables this feature. When USBBSDoor terminates, the message "Unregistered Copy" and a brief delay appear. A custom registration number will replace this with the name of your system and remove the brief delay. Registration also enables personalization of the enclosed QSUSBBS off-line utility. Registration also entitles you to limited voice support. You may receive a customized registration number INSTANTLY by using a major charge card. See the enclosed file ORDER.FRM for details. 7.1 Register with CONFIDENCE - Author Information -------------------------------------------------- Brent Yandell has been programming for over thirteen years including more than seven years of developing telecommunications software. Most Sysops will be familiar with PCBFV, the popular on-line PCBoard File Viewer, QReader, the `full-screen' text door, and ChatBox, the split-screen page utility for PCBoard. Yandell Custom Software (YCS) is a licensed business, operating and existing under the laws of the State of Florida since July, 1990. Writing BBS Shareware doors and utilities, in addition to custom programming, is our business... our ONLY business. First Door Release: 7/6/87 (USBBSDoor). Still updated and supported! YCS Shareware is GUARANTEED (each product's documentation contains each product's specific guarantee). Yandell Custom Software is an *AUTHORIZED* credit card merchant for VISA, Mastercard and American Express charge cards. A dedicated multi-node BBS for support and on-line registrations, a toll-free voice line for registrations, and a voice support line for registered customers are just a few of our offerings in our efforts to provide you with RELIABLE, FAST, FRIENDLY SERVICE.