Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / RBBSV101.ZIP / RBBSV101.EXE / RBBSVRFY.DOC < prev next >

Wrap

Text File | 1993-07-20 | 86.5 KB | 1,560 lines

┌────────────────────────────────────────────────────────────────────────┐ ░│ │░ ░│ ┌──────┐ ┌──────┐ ┌──────┐ ┌─────┐ Lightning Software Technical │░ ░│ │ ┌──┐ │ └┐ ┌─┐ │ └┐ ┌─┐ │ │ ┌───┘ Support BBS: │░ ░│ │ └──┘ │ │ └─┘ │ │ └─┘ │ │ └───┐ ┌────┐ │░ ░│ │ ┌─┐ ┌┘ │ ┌─┐ │ │ ┌─┐ │ └───┐ │ └────┘ Software Express │░ ░│ │ │ │ └┐ ┌┘ └─┘ │ ┌┘ └─┘ │ ┌───┘ │ (404) 941-2822 │░ ░│ └─┘ └──┘ └──────┘ └──────┘ └─────┘ │░ ░│ ┌─┐ ┌─┐ ┌─────┐ ┌──────┐ ┌───┐ ┌─────┐ ┌─┐ ┌─┐ │░ ░│ │ │ │ │ │ ┌───┘ │ ┌──┐ │ └┐ ┌┘ │ ┌───┘ │ │ │ │ │░ ░│ └┐└┐ ┌┘┌┘ │ └─┐ │ └──┘ │ │ │ │ └─┐ │ └─┘ │ │░ ░│ └┐└┐┌┘┌┘ │ ┌─┘ │ ┌─┐ ┌┘ │ │ │ ┌─┘ └─┐ ┌─┘ │░ ░│ └┐└┘┌┘ │ └───┐ │ │ │ └┐ ┌┘ └┐ │ │ │ │ │░ ░│ └──┘ └─────┘ └─┘ └──┘ └───┘ └─┘ └─┘ │░ ░│ │░ ░│ Version 1.01 │░ ░│ RELEASED: July 31st, 1993 │░ ░│────────────────────────────────────────────────────────────────────────│░ ░│Superior Callback Verification Door For RBBS-PC v16.x or Greater│░ ░│Copyright (C) 1993 By Lightning Software, All Rights Reserved Worldwide│░ ░│ │░ ░│ * * U S E R ' S G U I D E * * │░ └────────────────────────────────────────────────────────────────────────┘ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ "RBBS-PC: The Best Things in Life Are Still FREE!" [ Written & Coded By Robert L. Folmer & Jerry W. Highland ] TABLE OF CONTENTS ───────────────── Shareware Notice . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Limited Software License . . . . . . . . . . . . . . . . . . . . . . 2 Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Introduction (Overview/Summary) . . . . . . . . . . . . . . . . . . 5 Introduction (Overview/Summary) (Continued) . . . . . . . . . . . . 6 Installing RBBS-Verify . . . . . . . . . . . . . . . . . . . . . . . 7 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 8 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 9 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 10 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 11 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 12 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 13 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 14 Installing RBBS-Verify (Continued) . . . . . . . . . . . . . . . . . 15 The Optional Door Utilities . . . . . . . . . . . . . . . . . . . . 16 Files Included . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Files Created During Run-Time . . . . . . . . . . . . . . . . . . . 18 Optional Files Created During Operation . . . . . . . . . . . . . . 19 Optional Command Line Switches . . . . . . . . . . . . . . . . . . . 20 Optional Command Line Switches (Continued) . . . . . . . . . . . . . 21 Sysop Function/ALT Keys . . . . . . . . . . . . . . . . . . . . . . 22 Using RBBS-Verify on Non-RBBS Systems . . . . . . . . . . . . . . . 23 The RBBS-Verify Batch File . . . . . . . . . . . . . . . . . . . . . 24 The RBBS-Verify Configuration File . . . . . . . . . . . . . . . . . 25 The VERIFIED.DAT Data File . . . . . . . . . . . . . . . . . . . . . 26 The TRASHCAN.DAT Data File . . . . . . . . . . . . . . . . . . . . . 27 The USERS.DAT Data File . . . . . . . . . . . . . . . . . . . . . . 28 TABLE OF CONTENTS ───────────────── The LDCODES1.DAT Data File . . . . . . . . . . . . . . . . . . . . . 29 The LDCODES2.DAT Data File . . . . . . . . . . . . . . . . . . . . . 30 The NUMBER.LOG File . . . . . . . . . . . . . . . . . . . . . . . . 31 The VERIFYx.LOG File . . . . . . . . . . . . . . . . . . . . . . . . 32 The ERRORx.LOG File . . . . . . . . . . . . . . . . . . . . . . . . 33 The SUCCESSV.x Door Information File . . . . . . . . . . . . . . . . 34 The SUCCESSC.x Door Information File . . . . . . . . . . . . . . . . 35 The LOGOFF/LOGOFFG Optional Display File . . . . . . . . . . . . . . 36 The RBBSVRFY.KEY File . . . . . . . . . . . . . . . . . . . . . . . 37 Troubleshooting RBBS-Verify . . . . . . . . . . . . . . . . . . . . 38 Troubleshooting RBBS-Verify (Continued) . . . . . . . . . . . . . . 39 Troubleshooting RBBS-Verify (Continued) . . . . . . . . . . . . . . 40 Support For RBBS-Verify . . . . . . . . . . . . . . . . . . . . . . 41 RBBS-Verify User's Guide Page 1 SHAREWARE NOTICE ──────────────── RBBS-Verify v1.01 has been released under the shareware concept, you are therefore granted a limited evaluation license to use this software on your own RBBS-PC system for a period of 30 days, after which you must either register the software, or discontinue it's use and remove the door from your system. RBBS-Verify is the result of thousands of hours of development and deserves your support. RBBS-Verify may be freely distributed to all online services, bulletin board systems, user groups, shareware distributors etc, as long as the software is distributed complete and in unmodified form. No fee may be charged for the enclosed software package. Shareware distributors may distribute RBBS-Verify on disk for a modest disk duplication and packaging charge not to exceed $6.00 per disk. Registered versions of RBBS-Verify must NEVER be distributed to ANYONE. Doing so violates U.S. and International copyright and trademark laws. Lightning Software will seek full criminal prosecution against violators. RBBS-Verify is a fully functional package when unregistered, however does have several limitations. The software however is not in anyway crippled, which means you can fully test the package, run it on your own system, and determine if the software meets you and your user's needs, then if you find that RBBS-Verify works for you, then you are required to register your copy if you wish to continue using the door. The registered version of the door does offer several additional features not included in the unregistered version, these are the VERIFIED.DAT and TRASHCAN.DAT data records, which will prevent duplicate phone numbers from being used. The registered version also offers the NUMBER.LOG logging file for the Sysop, which can aid greatly in matching user names with phone numbers. Also included when you register RBBS-Verify is a 100% menu driven utility to help manage the RBBS-Verify online door and your RBBS-PC system, it is multitasker and network aware and is super easy to use, a bound printed manual, and lifetime support, not to mention the latest version of the software. As you can see from the above, registering RBBS-Verify offers tremendous benefits, you only need to register the door once, thereafter all future releases and upgrades are offered to you free of charge, plus when you register any Lightning Software product, you are given special pre-registered access on our 24 hour a day/7 day a week support BBS. For complete details on registering your copy of RBBS-Verify, please read the included file ORDER.DOC. Thank you for choosing the RBBS-Verify door, we hope you find the software of value and will support the shareware concept by registering your copy today! RBBS-Verify User's Guide Page 2 LIMITED SOFTWARE LICENSE ──────────────────────── RBBS-Verify v1.01 is Copyright (C) 1993 By Lightning Software, All Rights Reserved Worldwide. RBBS-Verify is not, nor has ever been, public domain or free software. The commercial, registered version of RBBS-Verify may not be duplicated other than for backup purposes. A registered copy of RBBS-Verify must be treated like a book, in that the same registered copy of RBBS-Verify may not be used on more than one computer at the same time, just as a book may not be read by more than one person at the same time (without making an illegal copy). User's are granted a limited license to use the User Supported, trial version of RBBS-Verify for a limited evaluation period of up to 30 days, in order to determine if the software suits their needs. Any other use of RBBS-Verify or use past this period requires registration. All user's are granted a limited license to copy the User Supported version of RBBS-Verify only for the purpose of allowing others to try it, subject to the above restrictions as well as these: RBBS-Verify must be distributed in absolutely unmodified form, including ALL program, documentation, and other files. RBBS-Verify may not be included with any other product for any reason whatsoever without written permission from Lightning Software. No charge or payment may be levied or accepted for RBBS-Verify, with the one exception, user groups and shareware distributors may freely distribute RBBS-Verify on disk for a modest disk duplication and packaging charge, not to exceed $6.00 per disk. Bulletin board system operator's may post the unregistered, User Supported version of RBBS-Verify on their BBS for downloading by their user's without written permission only if the above conditions are met, and only if no special fee is necessary to access RBBS-Verify files (a general and modest fee to access the BBS is OK). RBBS-Verify User's Guide Page 3 WARRANTY ──────── RBBS-Verify 1.01 is distributed without warranty. In no event will Lightning Software be liable to you for any damages from running this program. Including any loss of profits, lost savings, or other incidental or consequential damages arising out of your use of or inability to use the program, even if Lightning Software or a authorized representative has been advised of the possibility of such damages. Lightning Software will not be liable for any such claim by any other party. All risk associated with using this program are the complete responsibility of the user. RBBS-Verify User's Guide Page 4 ACKNOWLEDGEMENTS ──────────────── RBBS-Verify v1.01 - Copyright (C) 1993 By Lightning Software, All Rights Reserved Worldwide. All products mentioned throughout the documentation for the RBBS-Verify online door are copyrights and/or registered trademarks of their respective authors/publishers. There has been tremendous response to the RBBS-Verify online door, and we would like to say a very special thanks to all of those who have contributed in one way or another to it's success. The RBBS-Verify online door represents our strong belief in the QuickBasic programmer's environment, we hope that it proves QuickBasic's abilities and will give others inspiration to use the language. RBBS-Verify's logic is very safe and reliable thanks to the tremendous amount of hours that was put into beta testing the door under practically every situation. The tools used in the development of RBBS-Verify are what has made the door one of the best available, we would like to thank Todd Miller (creator of Door Source 4.0) for his wonderful library of door routines and for all of his support, Jeff Sumberg (creator of QBserial 3.0) for for his superior serial I/O library, Christy Gemmell (creator of The Assembly Language Toolbox for QuickBasic), and last but certainly not least Harold Thomson (creator of the QB4BAS assembly toolkit for QuickBasic), both two of the finest assembly language toolkits available. RBBS-Verify is written, coded, and debugged entirely in Microsoft QuickBasic 4.5 and utilizes the Door Source 4.0 library of door routines, the QBserial v3.0 interrupt driven serial I/O library, The Assembly Language Toolbox for QuickBasic and the QB4BAS library of assembly language functions. RBBS-Verify User's Guide Page 5 INTRODUCTION (OVERVIEW/SUMMARY) ─────────────────────────────── Congratulations! You have selected the finest of RBBS-PC callback verification doors. RBBS-Verify is the perfect compliment to your RBBS system for both security and reliability needs. RBBS-Verify offers many features and customization options for the system operator. Listed below are only a few of RBBS-Verify's many quality features: - Complete multinode support. - Extremely easy installation and zero maintenance. - Supports baud rates up to 115,200 locked DTE using non-fossil routines! - Supports the use of a fossil driver however is not required. - Supports non-standard interrupt and IRQ's and communication ports 1-8. - Does not require the use of WatchDog or similar utilities. - Detects carrier loss and terminates cleanly if carrier is dropped. - Includes easy to use completely menu driven installation utility. - Fast high speed communication routines. - Fully supports all networks and multitasking software, a few include DesqView, Microsoft Windows, DoubleDOS, Lantastic, Novell and many more. - Colorful ANSI/non-ANSI graphics. - Fully Sysop configurable. - Supports local and long distance callback verification. * Features verification and trashcan records - will not allow same number to be verified again. * Features NUMBER.LOG - log file for the Sysop which lists the telephone number, user's name and date of verification for all caller's successfully verified. This information is vital for the Sysop, it's purposes greatly vary, however one of the most notable uses is to assist in locating/matching a user name with a phone number. - Supports an optional RBBS-PC callback statistic bulletin for your caller's to read. Logs successful and un-successful user's who used the door. - Offers password security codes to protect you and your system. - Does not require the use of any run-time modules - all routines are handled internally. - Offers an extensive log for the Sysop - logs all user's who used the door, time, date, number dialed, whether security was raised, verify attempts successful and un-successful, plus much more. - Any program errors which occur are logged to a disk file for the Sysop. - Offers an optional callback mode so that user's may enter the door and have RBBS-Verify call them back to reverse the originating connection (normally helpful if the caller is experiencing a noisy phone line). - Built in macro code language ("@") support. RBBS-Verify User's Guide Page 6 INTRODUCTION (OVERVIEW/SUMMARY) ─────────────────────────────── - Offers built in - internal verification and callback instructions and allows the use of Sysop supplied instructions for both verification and callback mode. - Supports areas where when dialing long distance to some locations it is required to specify the area code, but the preceding '1' must be left off. Also supports areas where when dialing long distance to some locations it is required to dial the preceding '1' but no area code. * Features an easy to use completely menu driven RBBS-Verify/RBBS-PC management utility. Included when you register RBBS-Verify. - Features an easy to use bulletin purge/maintenance utility which can be run either from the DOS command line or used as a system event. Keeps RBBS-Verify's optional statistic bulletin updated to reflect the most recent statistics. * = Requires registration to enable this feature As you can see from above RBBS-Verify is one of the most full featured verification systems for RBBS-PC ever developed, and there are certainly more features than we can list here. We think after trying RBBS-Verify, you will agree - it is a one of a kind verification system offering both security and reliability. Please read this document carefully before installing the software for the first time. Thank you for choosing RBBS-Verify for your callback verification needs! RBBS-Verify User's Guide Page 7 INSTALLING RBBS-VERIFY ────────────────────── RBBS-Verify has been designed to make installation of the software as simple as possible. To make the installation even easier, we have included a completely menu driven configuration setup utility. Please read through the following important installation instructions before attempting to use the software for the first time. [1.] Create a directory to hold all of the RBBS-Verify files, then decompress the RBBSV101.EXE archive into the above created directory. You may install RBBS-Verify into any directory you wish, in this documentation we will assume you have installed RBBS-Verify into the directory C:\RBBS\RBBSVRFY. [2.] Next, change to the above created directory and run the supplied INSTALL.BAT file. This file will run the RBBS-Verify configuration setup program, where you will decide how you want RBBS-Verify to be installed on your system. The following is the questions the setup utility will prompt you for. Please note when installing RBBS-Verify on a multinode RBBS system, you will need to create different configuration files for each node. Enter a configuration filename ------------------------------ This should be the current configuration filename you are installing. You may use any standard DOS filename you wish. For multinode systems, use a different config filename for each node, you might wish to use numbers if using multiple config files, such as RBBSV1.CFG for node 1, RBBSV2.CFG for node 2 and so on. Name of interface file (ie PCBOARD.SYS) --------------------------------------- This should be the full path and filename in ALL uppercase to your DORINFOx.DEF interface file (where x is the node number). Name of BBS ----------- Here enter your BBS's name EXACTLY the way you want RBBS-Verify to display it upon connection with a remote user, this will be used to display "This is ... calling for ...". Sysop's first name ------------------ Here enter the Sysop's first name (your name) as you are known to your caller's. Sysop's last name ----------------- Here enter the Sysop's last name (your name) as you are known to your caller's. RBBS-Verify User's Guide Page 8 INSTALLING RBBS-VERIFY ────────────────────── Modem reset command - ex: ATZ ----------------------------- This should be the command needed to reinitialize your modem, for Hayes and compatible modems ATZ should work just fine, if you find that RBBS-Verify is unable to reset your modem, check your modems documentation for the correct command. EC modem dial string - ex: ATDT ------------------------------- This should be the initialization string you want sent to the modem when RBBS-Verify dials a remote user with an error correcting (reliable) connection, if you are not using a modem equiped with error correction capability, then this will be the dialing string RBBS-Verify will use in all cases, this should be the dialing prefix you want to use, and any additional commands to send to the modem. For touch tone dialing add DT to the end of the AT command, for pulse dialing add DP to the end of the AT command. You may add any additional commands you wish - such as turning the modems speaker on and off etc, however any additional commands you use MUST be entered before the dialing prefix (DT or DP). For Hayes and compatible modems ATDT should work just fine, if you find that RBBS-Verify is unable to dial and connect with the remote caller correctly, check your modems documentation for the correct commands. Non-EC modem dial string - ex: AT\N0DT -------------------------------------- This should be the initialization string you want sent to the modem when RBBS-Verify dials a remote user with no error correcting (reliable) connection established, this should be the initialization commands needed to disable error correction on your modem and the dialing prefix you want to use, as well as any additional commands to send to the modem. For touch tone dialing add DT to the end of the AT command, for pulse dialing add DP to the end of the AT command. You may add any additional commands you wish - such as turning the modems speaker on and off etc, however any additional commands you use MUST be entered before the dialing prefix (DT or DP). If you are not using a modem equiped with error correction such as MNP/REL, etc, then you should enter a "N" here for none. For Hayes and compatible modems AT\N0DT should work just fine, if you find that RBBS-Verify is unable to dial and connect with a remote caller correctly, check your modems documentation to find the correct commands. RBBS-Verify User's Guide Page 9 INSTALLING RBBS-VERIFY ────────────────────── NOTE: RBBS-Verify supports both a error correcting and non-error correcting dialing string. If you have an error correcting modem, you may have noticed when calling a non-error correcting modem, stray garbage appears on the receiving end. By placing a command to disable error correction this garbage can be avoided. If you are NOT using a modem equiped with error correction ability, such as MNP/REL, then the second dialing string does NOT apply to you, you should therefore enter a "N" for this parameter for none. RBBS-Verify will then use it's standard dialing string (the first modem dialing string). Also please note that since there are so many makes and models of modems now equiped with error correction ability, it is possible that your modem will not use the dialing string specified in our example, although more than likely our example will work, if you are unable to use our example, you should refer to your user's guide included with your modem, or better yet contact your dealer for support. Allow long distance dialing (Y/N)? ---------------------------------- Enter a "Y" here if you want RBBS-Verify to make long distance calls, or enter a "N" if you do not want RBBS-Verify to call long distance. RBBS-Verify will automatically disconnect long distance caller's after successful verification. Security level of caller's to verify? ------------------------------------- This should be the security level of caller's to verify (normally the security level for new caller's), any user attempting to enter RBBS-Verify with a security level less than or greater than this security level will be entered into the door in callback only mode (if enabled), if the callback mode is disabled, the caller will simply be informed that their security level is either too high or too low for RBBS-Verify and will be rejected from the door and returned to the board. Security level to raise caller's to? ------------------------------------ This should be the security level you want RBBS-Verify to upgrade caller's to if they have been successful with callback verification. Path/filename of bulletin (N for none)? -------------------------------------- At this prompt, select whether you want RBBS-Verify to create a statistic bulletin. Entering an "N" at this prompt will not generate a statistic bulletin, however entering the path and filename of a bulletin here (without the graphic designator i.e: C or G) will cause RBBS-Verify to generate a statistic bulletin for your caller's to read. RBBS-Verify User's Guide Page 10 INSTALLING RBBS-VERIFY ────────────────────── Path/filename of door info file? -------------------------------- This should be the full path and filename of your door information file RBBS uses to receive information back from a door. RBBS usually uses this file in the main RBBS directory with a filename of DOUTx.DEF (where x is the node number). Path/filename of caller info file? ---------------------------------- This should be the full path and filename of your caller information file RBBS uses to restore itself upon return from a door. RBBS usually uses this file in the NODEx directory with a filename of DRSTx.DEF (where x is the node number). Enable callback mode (Y/N)? --------------------------- At this prompt select whether you wish to enable the callback mode of RBBS-Verify. If this option is enabled (by specifying a "Y") then any user attempting to enter the RBBS-Verify door with a security level less than or greater than the security level to verify (specified above) will enter the door in callback only mode, RBBS-Verify will then allow the user to have RBBS-Verify call them back to reverse the originating connection (normally helpful if the user is experiencing a noisy phone line), no security changes are made while in callback only mode. This option can be disabled by specifying a "N" at this prompt, any user attempting to enter RBBS-Verify with a security level less than or greater than the security level to verify (specified above) will be informed that their security is either too low or too high to use the RBBS-Verify door, they will then be rejected and returned to the board. Comm port to use (1/2 or base address)? --------------------------------------- Here you should enter the communication port RBBS-Verify will use, this value should be either 1 or 2 depending on which communication port you will be using (COM1 or COM2), enter ONLY the port number here, do NOT enter COM1. If you are running RBBS-Verify on a non-standard communication port, then you should enter the 3 character HEX base port address at this prompt. Refer to the table on page 20 of this guide for a listing of valid communication port address and IRQ levels. RBBS-Verify User's Guide Page 11 INSTALLING RBBS-VERIFY ────────────────────── IRQ to use (1-15 or 0 if standard)? ----------------------------------- Here you should enter the communication port IRQ RBBS-Verify will use, this value should be set to 0 if you are using a standard communication port, otherwise you should enter the communication port IRQ you wish to use, this value can range from 1-15. Refer to the table on page 20 of this guide for a listing of valid communication port address and IRQ levels. Number of redial attempts (1-999)? ---------------------------------- This option should be set to the maximum number of times RBBS-Verify is to attempt to make connection with a remote caller, if RBBS-Verify is unable to make connection in one attempt, it will hang up and redial the caller again (up to this value). If this value is set to 1, RBBS-Verify will attempt only once to make connection with a caller. This value can range from 1 up to 999 times, the recommended setting is 3. Dialing delay factor to use? ---------------------------- This option requires a little explanation. This value is used to determine how many seconds to delay after RBBS-Verify dials a remote caller, this value is multiplied by 3. What this means, is that RBBS-Verify will delay a series of 3 times after it calls a user back and each time delaying this number of seconds while polling for carrier detection. So for example if this value was 10, RBBS-Verify would wait 30 seconds maximum after dialing a remote caller. RBBS-Verify uses this method to provide "quick-response" connect times, this allows the door to quickly determine if carrier from a remote modem is present, once the door sees that carrier detection is true, it continues execution with the "This is ... calling for ..." message. The recommended setting for this option for most modems is 10. Normally this value is always the best, however there is certain modems where a change to this value would become necessary, several high speed HST modems for example might require a change to this value. It is best to go with the recommended value of 10, however if you experience problems with RBBS-Verify hanging up too soon after calling a remote user back, then this value should be increased. RBBS-Verify User's Guide Page 12 INSTALLING RBBS-VERIFY ────────────────────── Use internal verification instructions? --------------------------------------- RBBS-Verify supports the use of Sysop created instruction files, however the door also includes it's own built in door instructions, at this prompt you should select whether you wish to use RBBS-Verify's internal callback verification instructions, if you do, simply enter a "Y" to enable RBBS-Verify's built in instructions for use. If you prefer you may use your own custom door instructions by simply including the full path and filename of the instruction file you wish to use, this file should be in standard ASCII format, ANSI display files are not supported, however you can control several aspects of the display by using RBBS-Verify's built in macro language, these macros allow displaying the user's name, sending a bell to the user, changing display colors, etc. For a listing of the macro codes supported by RBBS-Verify, please refer to the included file MACRO.LST, included with RBBS-Verify v1.01. Use internal callback instructions? ----------------------------------- RBBS-Verify supports the use of Sysop created instruction files, however the door also includes it's own built in door instructions, at this prompt you should select whether you wish to use RBBS-Verify's internal callback mode instructions, if you do, simply enter a "Y" to enable RBBS-Verify's built in instructions for use. If you prefer you may use your own custom door instructions by simply including the full path and filename of the instruction file you wish to use, this file should be in standard ASCII format, ANSI display files are not supported, however you can control several aspects of the display by using RBBS-Verify's built in macro language, these macros allow displaying the user's name, sending a bell to the user, changing display colors, etc. For a listing of the macro codes supported by RBBS-Verify, please refer to the included file MACRO.LST, included with RBBS-Verify v1.01. RBBS-Verify User's Guide Page 13 INSTALLING RBBS-VERIFY ────────────────────── LD code file to use 1-3 (N for none)? ------------------------------------- Several phone companies are now introducing areas in the U.S. where when dialing long distance to certain areas it is required to leave the preceding '1' off and dial only the area code, prefix and suffix and there are other areas where it is required to leave the area code off but dial the preceding '1', prefix and suffix. Either way RBBS-Verify fully supports these areas. This is done via 2 door control files, the LDCODES1.DAT and LDCODES2.DAT data files, each file is a standard ASCII file and are explained later in the RBBS-Verify file reference beginning on page 23. Here you should specify which (if any) file you which to use. You should enter a "1" here if you live in an area where when dialing long distance to some locations requires that you leave the preceding '1' off but dial the area code, prefix and suffix. You should enter a "2" here if you live in an area where when dialing long distance to some locations requires that you dial the preceding '1', prefix and suffix but leave the area code off and finally if your phone company uses both of these dialing standards, then you should specify a "3" here and RBBS-Verify will use both control files. If your local phone company does not require either of these dialing standards, then you should enter a "N" here meaning none, RBBS-Verify will then use it's standard dialing method. For most areas in the U.S. using these different dialing schemes is not required, therefore entering a "N" here is generally appropriate. NOTE: If you will be using the LDCODES1.DAT or LDCODES2.DAT or both door control files, these files and their formats are explained in the RBBS-Verify file reference beginning on page 23 of this user's guide. IMPORTANT: Syntax examples above with included quotes i.e.: ("Y") are provided only for clarity, the configuration file should NOT contain any quotes. RBBS-Verify User's Guide Page 14 INSTALLING RBBS-VERIFY ────────────────────── [3.] When you have completed entering configuration information, the next step is to create a batch file to run the door. The following is an example RBBS-Verify batch file used to run the door: ECHO OFF - Sets the DOS echo feat- ure to off to prevent the commands from echo- ing to the screen. ECHO Loading RBBS-Verify Please Wait... >COM1 - Sends the caller a message to wait. CD\RBBS\RBBSVRFY - Changes to the direct- ory containing all of the RBBS-Verify files. RBBSVRFY RBBSVRFY.CFG x. - Runs RBBS-Verify pass- ing the full path and filename of the config- uration file plus the node number. CD\RBBS - Changes back to the RBBS directory. The above batch file is pretty straight forward, just remember where you see an x substitute x for the node number, edit the COM port number in line number 2 to reflect the correct communication port number. [4.] The final step to installing RBBS-Verify is to decide how you would like to setup RBBS-PC to run the door. RBBS-PC supports 2 different door setup methods, the first is by simply using a batch file, all that's required in order to use this method is to simply copy the above batch file to your main RBBS-PC directory. The caller will then be allowed to run the door from RBBS-PC by going to your door menu and entering the door's DOS filename. Although this method is probably suitable for some systems, it does not provide near the flexibility as the 2nd method...The RBBS-PC door control file, usually located in the RBBS\SYSTEM directory with a filename of DOORS.DEF. This in most cases will be the best way to go and we strongly recommend using this method. With the DOORS.DEF file RBBS will allow you to prompt the user upon return from the door for his/her password, you can also control which security levels may actually access the door and every entry in the DOORS.DEF file can have a different minimum security level necessary to use the door, etc. The following is an example DOORS.DEF entry for RBBS-Verify: RBBSV,10,,D,"RBBSV.BAT [NODE]",Y,,, RBBS-Verify User's Guide Page 15 INSTALLING RBBS-VERIFY ────────────────────── The above entry tells RBBS the doors name is RBBSV (this should be the same as the door's batch file name), the minimum security level necessary in order to invoke RBBS-Verify is 10, no questionnaire is to be executed before running the door, RBBS is to "drop" out to the door rather than shelling (RBBS-Verify requires a considerable amount of memory), the template used to invoke the door runs the batch file RBBSV.BAT and passes the node number on the command line to the batch file, prompt the user after returning from the door for his/her password, RBBS is not to display any file when returning from the door, and the user will receive whatever time he/she currently has on the system to use the door. If you specify that RBBS is to pass the node number to RBBS-Verify in the template, then you will need to edit your batch file to replace the node number with %1, RBBS will then pass the node number to RBBS-Verify through the batch parameter %1. This is mostly useful for multinode systems. A full explanation of the door control file RBBS uses as well as methods to invoke doors can be found in the RBBS-PC manual under "THE USE OF RBBS-PC "DOORS", there is really no better substitute for the RBBS-PC manual. And if you are new to installing doors on your RBBS-PC system, you should read over the section "THE USE OF RBBS-PC "DOORS" carefully. Please note that RBBS can also automatically execute RBBS-Verify when a new user logs on, this is accomplished by setting RBBS's CONFIG parameter number 107 to the drive/path/filename of the RBBS-Verify batch file to invoke, and CONFIG parameter number 108 to the security level of new caller's. This will force all new user's into RBBS-Verify on their first logon and until they are successful with callback verification. After completing all of the above steps, RBBS-Verify is completely setup and ready to run! So let's give it a try to be sure everything is working properly. Change to your directory containing the RBBS-Verify files, and enter the following command at the DOS prompt: RBBSVRFY RBBSVRFY.CFG x LOCAL Substitute your configuration filename above if different. Replace the x with the current node number. RBBS-Verify does not support local logon's, so after entering the above command RBBS-Verify should report such and return to DOS. If everything is well, you might wish to edit the TRASHCAN.DAT file (if you are running a registered copy of RBBS-Verify) to add your board's number to the list. TRASHCAN.DAT is a standard ASCII text file and can be edited using any standard ASCII text editor. Refer to the section titled "THE TRASHCAN.DAT FILE" in this guide for details on the format used by this file. RBBS-Verify User's Guide Page 16 THE OPTIONAL DOOR UTILITIES ─────────────────────────── RBBS-Verify includes several additional utilities which help manage the RBBS-Verify online door - neither is required in order to use the door. The following is a listing of these utilities and a brief description of each, utilities included only with the registered version of RBBS-Verify will be designated by an "*" next to the title: RVBULL.EXE - This is an easy to use purge utility designed specifically for use with RBBS-Verify's optional callback verification statistic bulletin, which will "trim" the bulletin to keep the last xxx number of most recent statistics, it can be run from both the DOS command line, or used as a daily system event, it creates backup files everytime the program is run to protect you from loss. It keeps your statistic bulletins cut down in size as well as keeps the most recent statistics for your user's to read. See RVBULL.DOC for installation and operation instructions. EDITDATA.EXE * This is a COMPLETE management utility for use with the RBBS-Verify door and your RBBS-PC system, it provides tremendous functions for editing data files the door uses, running external utilities, viewing files and even using standard DOS functions! EDITDATA is also very simple to learn and use since it uses a 100% menu driven environment, simple interface, online help and much more! EDITDATA.EXE is STRONGLY recommended for maintaining the data files RBBS-Verify uses since improper editing may damage the door's data files, and render the program inoperative. See EDITDATA.DOC for installation and operation instructions. RBBS-Verify User's Guide Page 17 FILES INCLUDED ────────────── The files included with the registered and unregistered versions of RBBS-Verify differ slightly, the following is a listing of the files you should have within the RBBSV101.EXE self extracting file, files which are included only with the unregistered version will have a "U" beside the filename. Files which are included only with the registered version will have a "R" beside the filename. All other files are included in both the unregistered and registered versions: RBBSVRFY.EXE - Main RBBS-Verify executable program. RBBSVRFY.CFG - Sample RBBS-Verify configuration file. RBBSVRFY.BAT - Sample RBBS-Verify batch file. RBBSVRFY.DOC - User's guide for the RBBS-Verify online door RBBSVRFY.KEY R RBBS-Verify registration key file. VERIFIED.DAT - Verified data file - stores all phone numbers verified successfully. TRASHCAN.DAT - Trashcan data file - stores invalid phone numbers. LDCODES1.DAT - Long distance area code file 1. LDCODES2.DAT - Long distance area code file 2. USERS.DAT - User's data file. DOORINST.EXE - Door Installer - used to setup RBBS-Verify configuration files. RBBSVRFY.SET - Data file used by the Door Installer above. INSTALL.BAT - Installation batch file for RBBS-Verify. MACROS.LST - Listing of RBBS-Verify's optional built in macro language commands. EDITDATA.EXE R Network/multinode aware utility to help manage your RBBS-Verify door and RBBS-PC system. EDITDATA.BGR R Overlay file used by the EDITDATA.EXE program above. EDITDATA.HLP R Help file used by the EDITDATA.EXE program above. EDITDATA.DOC R Documentation for the EDITDATA.EXE program above. EDITOR.BAT R Editor batch file called by EDITDATA.EXE program above. EDITOR.COM R Default ASCII text editor used by the EDITDATA.EXE program above. RVBULL.EXE - Purge and maintenance utility to help manage RBBS-Verify's optional callback statistic bulletin. RVBULL.DOC - Documentation for the RVBULL.EXE program above. ORDER.DOC U Registration form and instructions to register your copy of RBBS-Verify. MAILER.TXT U RBBS-Verify instant registration mailer. README.1ST - Important last minute information which was not included in this user's guide. UPGRADE.DOC - Upgrade instructions for RBBS-Verify. WHATS.NEW - What's new in this release of RBBS-Verify. FILE_ID.DIZ U Imbedded description file for RBBS-Verify. DESC.SDI U Imbedded description file for RBBS-Verify. If you are missing any of the above files which you should have, you may wish to contact our support BBS and download RBBS-Verify directly from us, see the "SUPPORT FOR RBBS-VERIFY" section in this guide for more information. RBBS-Verify User's Guide Page 18 FILES CREATED DURING RUN-TIME ───────────────────────────── The following is a listing of files RBBS-Verify creates during normal run-time operation, and a brief description of each file. DOUTx.DEF - This file is created using the name and path specified in line 11 of the configuration file and is used to pass information back to RBBS-PC after successful verification. RBBS-PC *MUST* be able to locate this file! Note that x designates the node number. VERIFIED.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. If you are running an unregistered version of the door, this file will be initialized but ignored thereafter. TRASHCAN.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. If you are running an unregistered version of the door, this file will be initialized but ignored thereafter. USERS.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. If you are running an unregistered version of the door, this file will be initialized but ignored thereafter. LDCODES1.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. LDCODES2.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. NUMBER.LOG - This file will be created only after a caller has fully completed the callback verification process and only if you are running a registered version of the door. VERIFYx.LOG - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. ERRORx.LOG - This file will be created by the door only in the event of a run-time error. SUCCESSV.x - This file will be created only after a caller has successfully completed the callback verification process. SUCCESSC.x - This file will be created only after a caller has successfully completed the callback process. NOTE: Detailed descriptions of most of the files above can be found in the RBBS-Verify file reference starting on page 23 of this guide. RBBS-Verify User's Guide Page 19 OPTIONAL FILES CREATED DURING OPERATION ─────────────────────────────────────── If you specified a bulletin to be created in line number 10 of the configuration file, then 3 versions of that file will be created. RBBS-Verify automatically adds the appropriate G or C to the end of the filename you specify, therefore make sure and DO NOT add either of these characters to the end of the filename specified in your configuration file. RBBS-Verify User's Guide Page 20 OPTIONAL COMMAND LINE SWITCHES ────────────────────────────── RBBS-Verify provides many optional command line parameters to offer very flexible use, the following is a listing of the optional parameters that RBBS-Verify supports: LOCAL - Forces RBBS-Verify to run in local mode. This is really meant for RBBS-Verify's file initialization purposes, but it still reads the configuration file, but doesn't read the BBS interface file. Using this option will cause RBBS-Verify to re-create it's TRASHCAN.DAT, VERIFIED.DAT, VERIFYx.LOG, LDCODES1.DAT and LDCODES2.DAT files if any do not exist. NETWORK - Forces file sharing to be active in case you are using something other than SHARE to manage file locking. IRQ=n - Lets you change the IRQ used for the COM port specified in the BBS interface file. (See below for more information) ADDR=&Hnnnn - Lets you change the address used for the COM port specified in the BBS interface file. (See below for more information) PS2 - Forces the PS/2 IRQ's and addresses if a PS/2 isn't detected (normally it is, but you can't always tell!). The full command syntax for RBBS-Verify is as follows: RBBSVRFY <config file> <node> [option] Parameters shown inside <> brackets ARE REQUIRED, parameters shown inside [] brackets are optional and are shown above, these are not required for operation of the door. When you use the IRQ or the ADDR option, you must include the other. You can't use just the IRQ and not the ADDR, and you can't use just the ADDR and not the IRQ. Here's a chart with the STANDARD IRQ's and addresses for the PS/2's and IBM PC's: RBBS-Verify User's Guide Page 21 OPTIONAL COMMAND LINE SWITCHES ────────────────────────────── Non PS/2 COM Port IRQ Address 1 4 &H3F8 2 3 &H2F8 3 4 &H3E8 4 3 &H2E8 5-8 4 &H3F8 --------------------------------------------- PS/2 COM Port IRQ Address 1 4 &H3F8 2 3 &H2F8 3 3 &H3220 4 3 &H3228 5 3 &H4220 6 3 &H4228 7 3 &H5220 8 3 &H5228 PLEASE NOTE: RBBS-Verify uses 2 different sets of parameters when using the door on non-standard communication ports, the address and IRQ level specified in the configuration file for the door is the same as the command line parameters, except you should NOT include the "&H" prefix (shown above) in the configuration file, for example when running RBBS-Verify on port 4 on the standard IBM PC, you should specify 2E8 as the HEX address in the configuration file, NOT &H2E8, however you would still specify the parameter ADDR=&H2E8 on the command line when invoking the door. The above address and IRQ information applies only if you plan to use RBBS-Verify on non-standard communication ports and interrupts. RBBS-Verify User's Guide Page 22 SYSOP FUNCTION/ALT KEYS ─────────────────────── RBBS-Verify offers many Sysop specific commands while a caller is in the door, these are as follows: F3 * Printer toggle F4 * Page bell toggle F5 - Shell to DOS F6 - Auto-disconnect caller F7 * Caller alarm toggle F8 - Return caller to board and notify caller F9 - Return caller to board and don't notify caller F10 - Start Sysop chat ESC - Enter/exit Sysop chat ALT-X * Drop to DOS after caller logs off ALT-N * Sysop next on flag Function keys with an "*" beside their description are not currently available in RBBS-Verify. These have been included for possible future additions in the door. Description of auto-disconnect ------------------------------ This is an extremely useful function offered by RBBS-Verify for the Sysop's use. There are 2 different ways to utilize this feature. First, RBBS-Verify supports 2 optional display files titled LOGOFF/LOGOFFG, the first is a standard ASCII display screen and the second is a ANSI color display screen. The first method of using the auto-disconnect feature is to create either one or both of these display files, then when you press the F6 function key, RBBS-Verify will display the contents of the LOGOFF file if the user is in non-graphics mode or LOGOFF/LOGOFFG (depending on which one it finds) if the user is in ANSI graphics mode and will immediately hang up on the caller. RBBS-Verify will search for for the existance of these files and will display the appropriate file for the user's graphics selection. Which is either LOGOFF or LOGOFFG if the user has ANSI graphics capability or LOGOFF if the user has no graphics capability. If however neither of these files are present, RBBS-Verify simply immediately hangs up on the caller. Either way you decide to implement this feature, the user will never be notified by the door what is going on, this makes this feature very useful for problem caller's. RBBS-Verify User's Guide Page 23 USING RBBS-VERIFY ON NON-RBBS SYSTEMS ───────────────────────────────────── RBBS-Verify should run on any system that is capable of generating a DORINFOx.DEF format interface file however, RBBS-Verify will not be able to raise a user's security level on a non-RBBS-PC system. If you wish to use RBBS-Verify to it's full capability on a non-RBBS system, you will need to seek a good conversion utility capable of converting the door information file DOUTx.DEF to another BBS format. And of course you would also need a standard door conversion utility to convert to and from the door interface file DORINFOx.DEF, an example of such a convertor and one of the absolute best that we know of is DoorMaster found on many BBS's across the country and is available on our own support BBS as DM56.ZIP. RBBS-Verify User's Guide Page 24 THE RBBS-VERIFY BATCH FILE ────────────────────────── The following is the format of the RBBS-Verify batch file, this is simply an example - you may add/change/delete anything you wish, this example will hopefully also help those user's who are not familiar with creating batch files for online doors: ECHO OFF - Sets the DOS echo feat- ure to off to prevent the commands from echo- ing to the screen. ECHO Loading RBBS-Verify Please Wait... >COM1 - Sends the caller a message to wait. CD\RBBS\RBBSVRFY - Changes to the direct- ory containing all of the RBBS-Verify files. RBBSVRFY RBBSVRFY.CFG x. - Runs RBBS-Verify pass- ing the full path and filename of the config- uration file plus the node number. CD\RBBS - Changes back to the RBBS directory. RBBS-Verify User's Guide Page 25 THE RBBS-VERIFY CONFIGURATION FILE ────────────────────────────────── The following is the format of the RBBS-Verify configuration file, if for some reason you need to edit the configuration file using something other than DOORINST.EXE, this example should help familiarize you with the format used by the configuration file. All lines ARE REQUIRED! THERE SHOULD BE NO BLANK LINES IN THE CONFIG FILE!!! C:\RBBS\DORINFO1.DEF - Full path/filename of DORINFOx.DEF file (IN ALL UPPERCASE!) Software Express - Your BBS name Jerry - The Sysop's first name Highland - The Sysop's last name ATZ - Modem reset command ATDT - Error correcting modem dialing string AT\N0DT - Non-error correcting modem dialing string or N for none N - Allow long distance caller's (Y=Yes N=No) 10 - Security level to verify (normally new user access level) 20 - Security level to raise successful caller's to C:\RBBS\BULLETIN\BULLET1 - Path/filename of optional statistic bulletin without graphic designator (N for none) C:\RBBS\DOUT1.DEF - Path/filename of RBBS-PC door information file (normally DOUTx.DEF where x is the node number) C:\RBBS\NODE1\DRST1.DEF - Path/filename of RBBS-PC caller information file (normally DRSTx.DEF where x is the node number) Y - Enable callback mode (Y=Yes N=No) 1 - Communication port to use (1/2 or base address) 0 - Communication port IRQ to use (1-15 or 0 if standard) 3 - Number of redial attempts (1 to 999) 10 - Dialing delay factor to use (10 is recommended for most modems) Y - Use internal verification instructions (Y or path/filename of instruction file to use) Y - Use internal callback instructions (Y or path/filename of instruction file to use) N - Long distance area code file to use (1-3 or N for none) The remainder of the configuration file is ignored by RBBS-Verify and may be used freely for any comments you might wish to add. RBBS-Verify User's Guide Page 26 THE VERIFIED.DAT DATA FILE ────────────────────────── RBBS-Verify uses the VERIFIED.DAT file to hold all of the phone numbers of user's who have been successfully verified. This file is a standard ASCII text file and can be edited using any standard ASCII text editor. The format of the VERIFIED.DAT file is: 000-000-0000 - each line should contain the full phone number (including area code) with the separators in place i.e: (-). PLEASE NOTE: The file above is used only in the registered version of RBBS-Verify - it will be created and initialized but thereafter ignored in the unregistered version. Editing this file incorrectly can cause MAJOR problems, since each record is in a fixed length format. Registered user's may may find it easier (and safer) to edit the file using the included EDITDATA.EXE utility, see the file EDITDATA.DOC for instructions. RBBS-Verify User's Guide Page 27 THE TRASHCAN.DAT DATA FILE ────────────────────────── RBBS-Verify uses the TRASHCAN.DAT file to hold all of the phone numbers which the Sysop does not want dialed. This file is a standard ASCII text file and can be edited using any standard ASCII text editor. The format of the TRASHCAN.DAT file is: 000-000-0000 - each line should contain the full phone number (including area code) with the separators in place i.e: (-). PLEASE NOTE: The file above is used only in the registered version of RBBS-Verify - it will be created and initialized but thereafter ignored in the unregistered version. Editing this file incorrectly can cause MAJOR problems, since each record is in a fixed length format. Registered user's may may find it easier (and safer) to edit the file using the included EDITDATA.EXE utility, see the file EDITDATA.DOC for instructions. RBBS-Verify User's Guide Page 28 THE USERS.DAT DATA FILE ─────────────────────── This file is a standard ASCII text file which is used to hold all user's names and phone numbers who have successfully completed the callback verification process, it is a comma delimited data file, the format is: "USER NAME","000-000-0000" - each line consists of the user's full name in all uppercase, and the user's full phone number in the same format used by the VERIFIED.DAT and TRASHCAN.DAT data files above, with each field being enclosed in quotes and separated by a comma. This file is not currently used by RBBS-Verify, however has been added for future use. DO NOT under any circumstances delete and/or modify this data file! This file can prove useful for third party authors who wish to write applications for use in conjunction with the RBBS-Verify online door. PLEASE NOTE: The file above is used only in the registered version of RBBS-Verify - it will be created and initialized but thereafter ignored in the unregistered version. This file should NEVER be modified or deleted! RBBS-Verify User's Guide Page 29 THE LDCODES1.DAT DATA FILE ────────────────────────── The LDCODES1.DAT data file is applicable only if you live in an area where when dialing long distance to some locations requires leaving the preceding '1' off but dialing the area code, prefix and suffix. This file is a standard ASCII text file and can be edited using any standard ASCII text editor. The format of the LDCODES1.DAT file is: 000 - each line should contain a 3-digit area code (in the format shown) which requires using this dialing standard. You may list as many area codes as needed in your area. If using this data file, you must specify a "1" as the 21st parameter in the RBBS-Verify configuration file if you only require this file or "3" if you require using both the LDCODES1.DAT and LDCODES2.DAT control files. PLEASE NOTE: Editing this file incorrectly can cause MAJOR problems, since each record is in a fixed length format. Registered user's may find it easier (and safer) to edit the file using the included EDITDATA.EXE utility, see the file EDITDATA.DOC for instructions. RBBS-Verify User's Guide Page 30 THE LDCODES2.DAT DATA FILE ────────────────────────── The LDCODES2.DAT data file is applicable only if you live in an area where when dialing long distance to some locations requires dialing the preceding '1', the prefix and suffix but requires leaving the area code off. This file is a standard ASCII text file and can be edited using any standard ASCII text editor. The format of the LDCODES2.DAT file is: 000 - each line should contain a 3-digit area code (in the format shown) which requires using this dialing standard. You may list as many area codes as needed in your area. If using this data file, you must specify a "2" as the 21st paremeter in the RBBS-Verify configuration file if you only require this file or "3" if you require using both the LDCODES1.DAT and LDCODES2.DAT control files. PLEASE NOTE: Editing this file incorrectly can cause MAJOR problems, since each record is in a fixed length format. Registered user's may find it easier (and safer) to edit the file using the included EDITDATA.EXE utility, see the file EDITDATA.DOC for instructions. RBBS-Verify User's Guide Page 31 The NUMBER.LOG File ─────────────────── The NUMBER.LOG file is a standard ASCII text file and is used to hold the user's telephone number, name and the date of verification, this file is created just after a caller has been successfully verified and is provided as a general log file for the Sysop, it can be used for many different purposes, however, the most notable is allowing the Sysop to match telephone numbers with a user's name, which can assist greatly in locating duplicate user names. This file is separate from the VERIFYx.LOG file since the size of the VERIFYx.LOG file can at times get quite large requiring deletion, this file remains relatively small. PLEASE NOTE: This file is used only in the registered version of RBBS-Verify - it will be ignored in the unregistered version. RBBS-Verify User's Guide Page 32 THE VERIFYx.LOG FILE ──────────────────── The VERIFYx.LOG file is a standard ASCII text file which is used to log all of the door's activities, such useful logging features includes, who and at what time and date entered the door, the number RBBS-Verify dialed the user at, plus many more functions and activities are logged, this file is designed to be an extensive log for the Sysop. Note that x indicates the node number. RBBS-Verify User's Guide Page 33 THE ERRORx.LOG FILE ─────────────────── The ERRORx.LOG file is a standard ASCII text file which is used to log all of the run-time errors which occurred during the operation of RBBS-Verify, this file lists the run-time error, the error number that occurred and at what time and on what date the error occurred. If you have trouble with RBBS-Verify, check this file for the error number, if you are unable to resolve the trouble, have this error number handy and contact us for support. RBBS-Verify User's Guide Page 34 THE SUCCESSV.x DOOR INFORMATION FILE ──────────────────────────────────── The SUCCESSV.x file is provided as a means for RBBS-Verify to transfer data to another external application. Where the x indicates the node number. This was provided to encourage third party software development for the RBBS-Verify door, this file will be created when a user has been successfully verified, each line contains useful information which is necessary for a door or utility author who wishes to write external applications for use in conjunction with RBBS-Verify, the file is a standard ASCII text file and consists of the following information: *** Verification successful *** - Header message Jerry Highland - The user's full name Lithia Springs, Ga - The user's location 24 - The user's time left on the system 20 - The user's NEW security level 2 - The user's graphics selection (0=No graphics/1=ASCII/2=ANSI color) When utilizing this file - please note that RBBS-Verify does NOT delete this file each time the door is run, it simply re-writes the file again. This file is ONLY updated and re-written when a caller has been successful with the verification process. RBBS-Verify User's Guide Page 35 THE SUCCESSC.x DOOR INFORMATION FILE ──────────────────────────────────── The SUCCESSC.x file is provided as a means for RBBS-Verify to transfer data to another external application. Where the x indicates the node number. This was provided to encourage third party software development for the RBBS-Verify door, this file will be created when a user has successfully completed the callback process (this is assuming the callback mode is enabled), each line contains useful information which is necessary for a door or utility author who wishes to write external applications for use in conjunction with RBBS-Verify, this file is a standard ASCII text file and consists of the following information: *** Callback successful *** - Header message Jerry Highland - The user's full name Lithia Springs, Ga - The user's location 24 - The user's time left on the system 20 - The user's CURRENT security level 2 - The user's graphics selection (0=No graphics/1=ASCII/2=ANSI color) When utilizing this file - please note that RBBS-Verify does NOT delete this file each time the door is run, it simply re-writes the file again. This file is ONLY updated and re-written when a caller has been successful with the callback process. RBBS-Verify User's Guide Page 36 THE LOGOFF/LOGOFFG OPTIONAL DISPLAY FILE ──────────────────────────────────────── The 2 files LOGOFF and LOGOFFG are both optional display files you may wish to create, they are used in conjunction with RBBS-Verify's F6 (auto-disconnect) function key. LOGOFF is a standard ASCII text display file and LOGOFFG is a ANSI color display file. They are both optional files, if neither of these files exist, pressing the F6 function key simply disconnects the current user. If however either one or both of these files exist, RBBS-Verify will display the contents of the LOGOFF file if the user is in non-graphics mode or LOGOFF/LOGOFFG (depending on which one it finds) if the user is in ANSI graphics mode and will disconnect the caller. RBBS-Verify will search for the existance of these files and will display the appropriate file for the user's graphics selection. Which is either LOGOFF or LOGOFFG if the user has ANSI graphics capability or LOGOFF if the user has no graphics capability. Experiment with using this feature and be creative! Either way you decide to implement this feature RBBS-Verify will never inform the caller of anything, this makes this a very useful feature for problem caller's. RBBS-Verify User's Guide Page 37 THE RBBSVRFY.KEY FILE ───────────────────── When you register RBBS-Verify you will receive a registration key file registered in your board's name, this key file will be used to register the software and enable several additional features of the door. To install your key file, all that is necessary is to simply copy the file into the directory holding all of your RBBS-Verify files. It's a good idea to make a backup of this file, since there will be only ONE to go around. Then place the backup in a safe place. RBBS-Verify User's Guide Page 38 TROUBLESHOOTING RBBS-VERIFY ─────────────────────────── This section is designed to isolate most of the common problems user's may experience while operating the RBBS-Verify online door. Hopefully in the event of a problem, this section will be of some help, if after going over this section you are still unable to resolve the problem, please refer to the "SUPPORT FOR RBBS-VERIFY" section in this guide. (P) = Problem (S) = Solution (P) - RBBS-Verify reports to the caller "File not found - report to Sysop!". (S) - This indicates that RBBS-Verify tried to open it's user supplied door instructions, however the file was not found. Make sure that the path and filename to the file has been specified correctly in the configuration file and the file actually exists. Although not required it is strongly recommended that you place all of RBBS-Verify's files the door uses within it's own directory, this provides clarity. (P) - Receive message "Error xx opening comm port" while trying to run RBBS-Verify. (S) - This error indicates there was an error while trying to open and initialize the communication port, this error is normally due to an invalid communication port or baud rate being passed to the door from the door interface file. If you are using the door on a non-standard communication port - this error can also indicate an illegal port address or IRQ level. Check these parameters carefully to insure all information is correct. Please also note that this error can occur when trying to operate RBBS-Verify in local mode from RBBS, this is due to RBBS not passing a valid baud rate to doors in local mode. RBBS-Verify does not support local logons anyway however, if you have trouble running some doors in local mode, we have a patch program available which will patch the door interface file to run with most doors in local mode, this patch is available on our support board (Software Express) under the filename of PATCHLCL.ZIP. Note that this patch is not needed for RBBS-Verify. RBBS-Verify User's Guide Page 39 TROUBLESHOOTING RBBS-VERIFY ─────────────────────────── (P) - BBS calls door and returns to the board. (S) - Check your configuration file to be sure all information has been entered correctly, also make sure that the full path and filename of your DORINFOx.DEF interface file has been entered in ALL uppercase, do NOT use lowercase! If this is correct, recheck all batch files used to run the door, normally it's something very simple. (P) - RBBS-Verify displays fatal error message. (S) - This error can mean many, many things, this is RBBS-Verify's way of preventing the entire door from going down, by terminating cleanly and exiting back to the board. This error message occurs when it is un-safe for RBBS-Verify to continue, when you receive this error message, view the log file RBBS-Verify creates ERRORx.LOG (where x is the node number), this file contains the run-time error that occurred and the date and time, these error codes indicate QuickBasic's standard errors, check to be sure all information in the config and batch files have been entered correctly, ensure all files are where they should be and try the door again, if you are unable to correct the trouble, see the "SUPPORT FOR RBBS-VERIFY" section in this guide, write this error code down, you will need it when writing or calling for support. (P) - Run-time error number 255 logged to ERRORx.LOG (S) - This is a run-time error you will probably see quite often being logged to the ERRORx.LOG file, this occurs when a user hangs up (drops carrier) in the door. RBBS-Verify logs this as an error 255 for reference purposes, it does NOT indicate a malfunction within RBBS-Verify itself. RBBS-Verify User's Guide Page 40 TROUBLESHOOTING RBBS-VERIFY ─────────────────────────── (P) - Receive error "Internal stack overflow System Halted" and system "freezes". (S) - This is an error generated by DOS, RBBS-Verify sets aside stack space for it's interrupt handling when the door is loaded, if there is not enough physical stack space set aside in DOS, you will most likely receive this error when the door is started, or shortly thereafter and your machine will appear to "freeze" requiring a reboot, the solution to this problem is simply editing your CONFIG.SYS file to include the following line: STACKS = <number of stacks>,<size of each stack> The value of <number of stacks> can range from 0 to 64, and the value of <size of each stack> can range from 0 to 512. An example STACKS = setting might be: STACKS = 16,256 <- this value should be very sufficient for most systems, however this value might need increasing if you are operating under a multitasking/network environment. Hopefully the above listed problems and solutions will help you correct any problem you are having with the RBBS-Verify online door, if not we would be glad to assist you, please read the "SUPPORT FOR RBBS-VERIFY" section in this guide. RBBS-Verify User's Guide Page 41 SUPPORT FOR RBBS-VERIFY ─────────────────────── Support may be obtained 24 hours a day, 7 days a week for the RBBS-Verify online door on the Lightning Software support BBS (Software Express) at (404) 941-2822. The latest version of RBBS-Verify plus all of our other quality software products may be obtained on our support BBS. We would appreciate any comments/suggestions or future enhancements you might have, we would be glad to hear from you! Support is also available by writing to us at the following address: Lightning Software P.O. Box 177 Lithia Springs, Ga 30057 Please, when contacting us for support, be as specific as possible describing your problem, statements such as "It won't dial." are all too common and unfortunately do not provide details. Also READ THIS MANUAL!!! We find that 95% of all user's who have difficulty with RBBS-Verify have not read the manual, read and follow this guide carefully, it is your best source of support.