Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1992-03-03 | 23.4 KB | 649 lines

User Verifier Door for PCBoard 14.x (Version 3.01) to be used in Conjunction with: The Mailing List Manager Written by: Lance Williams Kadet PCBoard P. O. Box 266 Camden, NY 13316-0266 (315) 245-3815 USR HST Dual Standard User Verifier Door Page 1 License Agreement The Mailing List Manager, Verifier Door & User-Reg utility ("The Software") is COPYRIGHT 1990, 1991, 1992 by Lance Williams, ALL RIGHTS RESERVED. You may not engage in, nor permit third parties to engage in, any of the following : A) Making alterations of any kind in the software. B) ATTEMPTING TO DISASSEMBLE, DECOMPILE, OR REVERSE ENGINEER THE SOFTWARE OR THE FILES IT GENERATES IN ANY WAY. C) Granting sub-licenses, lease or other rights in the software to others. D) This release is SHAREWARE, if you continue to use this package for more than 3 weeks, you must register it with the author. The author of the software grants you a license to use this software as long as you meet the above conditions. Any violation of the above conditions will result in the termination of your license to use this software. Upon termination of this license for any reason, you must stop using the software and destroy all copies of it in your possession immediately. In addition, the author reserves the right to cancel your license to use this software at any time for any reason that he sees fit. The author of this software is not liable for damages suffered as a result of the improper use, proper use, or inability to use this software. This type of disclaimer is prohibited by law in some states, and is therefore void in those states. General Program Characteristics: This door serves as a great user verifier by mail for PCBoard sysops. It insures some degree of satisfaction that all of your users are real persons. The door has three functions, the first function is a registration door complete with unlimited script questionnaires. Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 2 The second is a user verifier which requires all new users to stay at a lowered security level until they receive a registration number in the mail. When a new user logs in, you can send him to this door to fill out the registration and mailing information for a registration card. You will have to send out cards on a regular basis to your users, and when they get the registration number, they can reenter the door and chose option #2, verify registration, to be upgraded to a verified user. The third function is a Mailing List Manager for those of you who like to send out occasional flyers and such to your users. The Sysop Utility program (MAILING.EXE) contains many options for printing out labels for your users. See the Documentation file on the Mailing program for more details. Set-up for Verifier Door: The Door is very simple to set up if you have ever set up a DOORPCH door before. The door requires both a configuration file and address definition file (ADDRESS.DAT). The configuration file for the door MUST be on the command line and contain the following information: Example Configuration File: 1> C:\PCB\PCBOARD.SYS 2> Kadet PCBoard 3> Lance 4> Williams 5> 0 6> WELCOME 7> GOODBYE 8> BASIC 9> NEWUSER 10> REGS 11> YES 12> 8,42,0,42 13> 9,90,0,90 See Explanations for these lines below: Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 3 Line 1: The path/filename of your PCBOARD.SYS file. Line 2: The Name of your BBS. Line 3: Sysop's First Name. Line 4: Sysop's Last Name. Line 5: Your Registration Number (0 if Unregistered) Line 6: Path/Filename of your opening screen Line 7: Path/Filename of your closing screen Line 8: Path/Filename of your door usage information screen Line 9: Path/Filename of your new user information screen Line 10: Path/Filename of your registration information screen Line 11: Time credited while in door (YES or NO) Line 12 The various un-verified security levels, corresponding Thru EOF: verified upgrade level, new days till expiration and expired security level separated by a comma. The program now supports a "No Expiration Date" mode for verified subscriptions. To use this option, just put a "0" in for the number of days till expiration for that security level. Also, if you put a "0" in for additional conferences, an appropriate message will be displayed to users, rather than adding conference 0. This goes for both SYSOP & SPECIAL Conferences This new version also supports file sharing for multi-node operations. To accommodate this change, single node systems will have to have SHARE.EXE loaded. It is best load SHARE in your AUTOEXEC.BAT file to insure it is present in memory. ADDRESS.DAT File maintenance & creation: The ADDRESS.DAT file is created with the program ADDRESS.EXE and MUST reside in the directory where VERIFIER is run from. Refer to the document file "ADDRESS.DOC" for details on setting up an ADDRESS.DAT file. It's easy and painless. Adding the Door to PCBoard: The implementation of a Door in PCBoard is relatively simple and fairly well documented in the PCBoard User Manual. See the file SYSOP.DOC for more installation information not specific to this door. Sample Batch File: @echo off e: cd \doors\verifier <--- Location of the Door Files verifier verifier.cfg <--- Be sure to include CFG file on c: command line. cd \pcb <--- Return to the PCBoard Directory board Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 4 Door Usage Log Files: Caller's Log Output: The Verifier door accesses your Callers Log (via filename found in your PCBoard.DAT file). It writes all the major events occurring inside the door to your Callers Log. If you have your caller's log set to go to the printer, the door will also send the output to the printer. VERIFIER.LOG Output: The Verifier Door maintains a running log of all activity in this file. I suggest you review and delete this file regularly, or it will grow excessively large over time.... VERIFIER.ERR Output: Any User-caused errors (IE: Bad registration numbers, attempts to reverify, etc) will be logged to the file VERIFIER.ERR showing the date and time it occurred. You may want to review this file occasionally, if it has been created (Only when an error occurs), to see what your users are doing wrong. If a user enters a wrong number, the proper number is send to this file and to the caller's log. PCBoard User File Comment: The door also writes a comment into the PCBoard USER file for the user. The Door writes to SYSOP COMMENT #2, and writes either "Registered via Verifier 3.0" or "Verified via Verifier 3.0" depending on whether the user was registering or verifying. Hard-Coded Files Used by Program: BRUN45.EXE All the programs in this package require a copy of the QuickBasic 4.5 Runtime Library. The Door requires a version patched for proper DTR handling. Call my system if you need a copy. VERIFIER.CFG This is the door configuration file. See above. (also used by MAILING.EXE & USER-REG.EXE) MAILLIST.DAT This is the Mailing List Data file used by both the Verifier Door and the Sysop Utility program (MAILING.EXE). It contains all the mailing addresses for your users that have gone through the door. (Created by program) Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 5 VERIFIER.ERR This is a log of User-caused errors that have occurred in the door. See the notes on log files above for details. ADDRESS.DAT This is the sysop maintained Address Definitions file. It hold the prompts for the Mailing Label Information section. Use ADDRESS.EXE to edit this file. Files included in archive: VERIFIER.EXE Verifier Door Program MAILING.EXE Sysop Utility Program ADDRESS.EXE Address Definitions File Editor Program CONFIG.EXE Configuration program for .CFG and script files. USER-REG.EXE Simple Program to get registration numbers VERIFIER.CFG Sample VERIFIER/MAILING/USER-REG configuration file VERIFIER Sample Batch File to Run Door VERIFIER.DOC This Documentation file MAILING.DOC Documentation for Sysop Utility Program USER-REG.DOC Simple Docs for USER-REG program. SYSOP.DOC Installation instructions for DOORPCH Doors ADDRESS.DAT Sample ADDRESS.DAT file for US, Canada & Australia BASIC.DAT Sample Script for regular users SYSOP.DAT Sample script for visiting sysops NEWUSER Sample PCB @X## screens BASIC Sample PCB @X## screens SYSOP Sample PCB @X## screens SPECIAL Sample PCB @X## screens REGS Sample PCB @X## screens WELCOME Sample PCB @X## screens MEMBERS Sample PCB @X## screens MAILING.HST Revision History for the MAILING.EXE file VERIFIER.HST Revision History for the VERIFIER.EXE file UPGRADE.DOC Upgrade instructions for upgrading from version 2.0 25TO30.EXE Conversion Program for Ver. 2.5 to Ver. 3.0 25TO30.DOC Documentation for the 2.5 => 3.0 Conversion Program Sysop Definable screens: The 5 Sysop definable filenames are described below. These can either be ANSI and ASCII screens or one PCB @X## screen. The file names are listed as part of the CFG file. The script ANSWER files and script display screens are also definable within the script questionnaire files as well. WELCOME(G): This is the opening screen displayed after the hardcoded program opening lines. NEWUSER(G): Displayed to New Users before entering the mailing list data. Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 6 BASIC(G): Displayed to New Users before doing any registration. It describes what the door does, or whatever you want to use it for. REGS(G): Displayed to Any User before entering his/her registration number for verification GOODBYE(G): Displayed when exiting the door. I use it to give system information. Any of the screens can be any ASCII/ANSI screen you like, and work the same as PCBoard screens. The door also supports PCBoard's @X## color macros. The code will look for a filename with a "G" appended to the end if the user is in graphics mode. Script Questionnaire Formats: This door currently supports unlimited script questionnaires. The control to the access to the questionnaires is contained in the file SCRIPTS.DAT. This file is editable with your text editor. The file format is as follows: BASIC.DAT,8,60,8,2,0 SYSOP.DAT,9,60,9,8,4,6,7 METRO.DAT,10,60,10,9,5 Where: There are at least 6 entries in each line: Entry 1: Name of the Script questionnaire data file Entry 2: New security level after answering script Entry 3: New expiration date Entry 4: New expired security level Entry 5: Minimum security to answer script: This entry will look at the current upgraded security level, if equal or greater than this entry, the user will be asked if he wants to answer the script. Your initial script should be no higher than your new user security level, then after that, you can control access to scripts by how their security has been upgraded so far. Entries 6+: These are the added conferences for this script. (1-39) 0 = no additional scripts The SCRIPTS.DAT file will be created for you, along with your script questionnaires, if you use the CONFIG.EXE program to set up your door. The format of your individual script questionnaires follows: Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 7 Script Questionnaire File Format: The first four lines contain the following information: Line #1: Path/filename of the Questionnaire answer file. The Answer file is now sysops definable, so you can have the answers appended to the end of an existing script answer file. I think this is a good option to have added. Line #2: The display screen describing the script questionnaire. Use this line to enter a ANSI/ASCII or PCBoard @X## display screen you wish to have displayed to the caller describing the script. It gives more information than a one-line prompt for the script. Line #3: The script name prompt. This is a single line entry that will be displayed to the caller naming the script. IF you want ALL CALLERS to answer this script, put a $ALL$ in this line. They will not be prompted as to whether to answer the script, and the $ALL$ will not be displayed to them. $ALL$ will FORCE ALL CALLERS to answer that script questionnaire. Line #4: Number of questions in the questionnaire file. This entry is the total number of QUESTIONS found in the script file. You do not have to count screens or comments for this value, but it doesn't matter if you do. The number can be LARGER than the total number of questions, but NEVER Smaller. It is used to dimension an array to store the answers into, so larger than necessary will just use a small amount of extra memory. Each remaining line in the script file has 2-5 parts separated by a semi-colon. Part 1: The type of line being displayed: ? = a question is being asked # = a comment is being displayed * = an ASCII/ANSI screen is being displayed Part 2: Either the line to be displayed (for questions or comments) OR the path/filename of the ASCII/ANSI screen to display. Parts 3-5 are used for questions only: Part 3: This is the MINIMUM length of an answer to accept. Part 4: This is the maximum length of the answer. The overall maximum length is set at 60 characters, to conform to PCBoard Script questionnaires. If you select a length greater than 60, it will be set to 60. Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 8 Part 5: This is the type of input to accept. The testing is done character by character. The following types are accepted: Type Code Characters Accepted ASCII A Everything Date D 0-9,-,/ Numeric N 0-9/,/. Phone Numbers P 0-9,-,(,),[,] Letters & Punct. L A-Z, punctuation characters Yes/No Y Single Character (Y or N) Sample Script Questionnaire lines: 1> #;And some questions about yourself: | ^----- Comment line to be displayed ^----- Indicates a comment is to be displayed 2> ?;What is your birth date (mm/dd/yy);8;10;D | | | | ^--- Type of input testing | | | ^--- Maximum answer length | | ^--- Minimum answer length | ^--- Question line to be displayed ^--- Indicated a question is to be asked/displayed. 3> *;MEMBERS | ^----- Name of Screen to Display (Can be complete path\filename ^----- Indicates this is an ASCII/ANSI screen to display Sample script file: <BASIC.DAT> e:\doors\mailing\basic.log REGULAR $ALL$ 8 ?;What City & State (& Country) are you calling from?;5;60;A #;I may need to contact you so please give me your ?;Daytime VOICE phone number where you can be contacted?;8;14;P #;Please answer a couple questions about your computer: ?;What is your Computer system?;3;60;A ?;What is your Modem Brand (include max baud)?;5;60;A ?;Do you have a Hard Drive (Y/N)?;1;1;Y #;And some questions about yourself: ?;What is your occupation?;5;60;A #;Where specifically did you hear about us? ?;(NAME of the PERSON, BBS or PUBLICATION);5;60;A ?;What is your birth date (mm/dd/yy);8;10;D *;MEMBERS Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 9 All three of my script files are included in the archive. Please feel free to modify them to suit your needs. Questions or Comments?? If you have any questions or comments concerning this program, please give me a call at Kadet PCBoard and I'll get back to you usually within 24 hours. I may even call your system to see what I can do to help you out. But, there will always be a reply waiting for you on my system within 24-48 hours. Multi-Node Operations: This door is now fully functional on Multi-Node systems. It supports full file sharing for both PCBoard files, and it's own files. The only requirement is that you have a SEPARATE configuration file for each node using the door. For more information, refer to the instructions in DOORPCH for Multi-node operations. *** Remember, SHARE MUST BE LOADED even when *** *** you are running under a single node system *** Registration for Complete Package: This package is distributed as Shareware. You are required to register it if you continue to use it after a 3 week trial period. To register, fill out the registration form found in the file REGISTER.FRM and send to: Lance Williams P. O. Box 266 Camden, NY 13316-0266 Registration for the User Verifier Door and Sysop Utility program is $40 payable in Cash/Check or Money Order in US Funds, or by Visa/MasterCard. All checks must be drawn on US Banks. Foreign orders must be paid by Visa/MasterCard or Postal Money Order. Visa/MasterCard registrations are handled by phone ONLY thru MIDIMaze BBS in Manchester, Tennessee. You may reach them at (615) 723-1867 or (615) 723-1953. Both nodes are 2400 baud. There is a special conference set up for Verifier Door registrations. Join Conference #20, and Open Door #1 for Visa/MasterCard registration. You will receive a disk set and registration in the mail in 10 days to 2 weeks. If you prefer to register by mail, your registration will include a complimentary set of 100 printed post cards, I can not offer these post cards on Visa/MC registrations due to the processing costs of Visa/MC registrations. Use the inclosed form for registering by mail. See the documentation for the Mailing List Manager for the Mailing Card Format. Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std. User Verifier Door Page 10 *** User Verifier Door Registration Form *** Lance, I wish to register your User Verifier Door & Mailing Utility program. Enclosed is $40. Please send my registration number and complimentary set of post cards to: Name : ________________________________________________ Address : ________________________________________________ City : _________________ State: _____ Zip: __________ In case of problems you can reach me at: Voice Phone : _________________ Data Phone : ________________ Disk Format to Send: _____ 5-1/4 (360K) _____ 3-1/2 (720K) *** The following MUST be the Same as in your Configuration file: *** Sysop Name : __________________________ BBS Name : __________________________ (The above will be printed on your Registration Post Cards and be) (used to create your personal registration number for the door) ──────────────────────────────────────────────────────────────────────── *** Order Form for More Registration Post Cards *** Lance, I'd like to order additional postcards for the User Verification Door. Please send them to the following address: Name : ________________________________________________ Address : ________________________________________________ City : _________________ State: _____ Zip: __________ Please send _____ sets of 100 cards @ $4.95 per set made out with the following information: Return address if different than above: Name : ________________________________________________ Address : ________________________________________________ City : _________________ State: _____ Zip: __________ BBS Name : ________________________________________________ Lance Williams, Kadet PCBoard, (315) 245-3815 USR HST Dual Std.