home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
-
-
-
-
- ON-LINE TRIVIA
- SYSOP'S MANUAL
-
- v3.5
-
- March 6, 1993
- PCBoard 14.x and GAP 4.x
- WILDCAT!, SPITFIRE
- QBBS, RBBS, RA
- WWIV
-
- by
-
- Dennis Maidon
- PAROLE TECHNOLOGIES
- 311 Buffalo Rd
- Clayton, NC 27520
- (919) 965-3600 -> Voice
- (919) 965-9885 -> FAX
-
- The Parole Board BBS
-
- (919) 965-4696 -> US Robotics Dual Standard
-
- Free Advice BBS
-
- Node 1 (919) 934-1002 USR HST
-
- OVERVIEW
- ________
-
-
- CONGRATULATIONS! You and your users will find ON-LINE TRIVIA
- entertaining and educational. On-Line trivia is a carefully
- selected collection of 1750 questions segregated into user
- selectable multiple categories. Your users can limit, mix or
- combine the question categories. The program maintains a record of
- replies so the user may resume answering questions on another call.
- The door displays a "top trivia player bulletin to the caller while
- it creates bulletins and logs for your use. Best of all..this door
- is not crippleware. It isn't full of advertisements and
- limitations...best of all I don't charge an arm and a leg. You'll
- also find we are responsive to your questions. If you need help or
- have a suggestion for improving this product, let me know!
- FILES AND DESCRIPTIONS
- ______________________
-
- The archive includes the following files:
-
- OLT.EXE -- The main executable file
- OLTSAMP.CFG -- The sample configuration file
- MASTER.DAT -- The main trivia data file
- SCREENS.ZIP -- Screens for the OLT\SCREENS sub directory
- ^┌──WELCOME.ANS -- The program color Welcome Screen,
- ││ (Can be modified by Sysop).
- ││ WELCOME.ASC -- The program mono Welcome Screen
- └┤ (Can be modified by Sysop).
- │ INSTRUCT.ANS -- The color user instruction file
- └──INSTRUCT.ASC -- The mono user instruction file
- SYSOP.DOC -- The installation instructions...(this file)
- QUIKUP.DOC -- Quick and Dirty installation instructions.
- REGISTER.TXT -- Information and registration form...This will
- give you a personalized door, voice or bbs
- support services, new issues of master.dat
- files, a clear conscience and a still poor but
- happy door programmer.
- SAMPLE.BAT Sample door batch file
-
- IT IS FORBIDDEN TO DISTRIBUTE THIS ARCHIVE WITH THE "AV" REMOVED!
-
- This ZIP file was created using the -AV function of PKZIP. If my
- AV is missing then this file may not be complete of has been
- tampered with. Complete and current editions of this program are
- always available for D/L on The Parole Board BBS. If the AV is
- missing please complain to your sysop to stop the practice of
- removing AV's as this is your assurance from the programmer that
- the file is complete and virus free.
-
-
- INSTALLATION
- ____________
-
- Installation is quite simple and straight-forward. Follow these
- steps and example and you should be up and running in a matter of
- minutes. Although OLT is an easy program to install on most any
- BBS, there may be some Sysop who has trouble. Support is available
- in those situations.
-
-
- 1) Create a directory to hold all OLT files
-
- 2) Unzip OLT-xx.ZIP into the above directory
-
- 3) Run INSTALL.BAT
-
- 4) Create a configuration file, with a name of your choice
- or modify the OLTSAMP.CFG file which is enclosed.
-
- 5) Create a door batch file or use the sample enclosed.
-
-
- 6) Modify your particular BBS System Menus to add the
- door. The BBS setup various depending on the type BBS
- software you are running. We assumed you are familiar
- with the general DOOR setup on your system. Therefor our
- description includes only examples of the OLT specific
- configuration file and door batch file. Refer to your
- BBS documentation for door installation on your
- particular software.
-
-
- BBS USER FILES
-
- The BBS user file provides information to OLT !!, such as COM
- port, user name, time allowed in the door, etc. This file is
- necessary for OLT to function. The complete path\filename of
- the BBS user file must be passed to OLT.exe as the 1st
- parameter in the command line. The user file is created by
- your BBS EACH time a user runs a door....The BBS USER file has
- a different name on each type of BBS. When you create your
- OLT configuration file, you must tell OLT the name for your
- particular BBS system.
-
- The following is a list of the user files used by the
- BBS types we support (we included a typical path).
-
- drive\dir\filename
-
- C:\WILDCAT\CALLINFO.BBS ──┐ <- For Wildcat!
- C:\WC30\USERINFO.DAT │ <- For Wildcat! 3.0 (Point to NODEx dir.)
- C:\PCB\PCBOARD.SYS │ <- For PCBoard using PCBOARD.SYS
- │ only
- C:\PCB\USERS │ <- For PCBoard using USERS only
- C:\BBS\DOOR.SYS │ <- For Systems which support
- │ DOOR.SYS
- C:\BBS\DORINFOx.DEF │ <- For QBBS/RBB/RA. Replace x with
- │ Node #.
- C:\BBS\GTUSER.BBS │ <- For GT Power systems
- C:\BBS\SFDOORS.DAT │ <- For Spitfire
- C:\BBS\CHAIN.TXT ───┘ <- For WWIV
-
-
- NOTE: There are 2 additional lines necessary when using GTUSER.BBS. Since
- this file does not provide the ComPort% and NodeNum% variables, advise
- your Door users to add them to this .CFG file on lines 5 and 6
- respectively. Both variables will default to 1. All other lines
- will move down 2 numbers.
-
- CONFIGURATION FILE
-
- One (and only ONE) of the above will be LINE 1 of your
- configuration file. You MUST specify the path and name (including
- any extension) correctly if you expect OLT to find it. Sample for
- Lines 2 through 10 are:
-
- The Parole Board BBS <- Your BBS Name
- Dennis <- SysOp's First Name
- Maidon <- SysOp's Last Name
- 00000 <- Registration Number
- 100 <- Minimum security level allowed
- in door.
- 35 <- Maximum questions allowed per visit
- to the door.
- C:\WC\BULL\BULL1.SCR <- Path and Name of Color Bulletin
- C:\WC\BULL\BULL1.BBS <- Path and Name of ASCii Bulletin
- WC <- WC = WC! 3.x Color Code Bulletins
- PCB = PCBoard Color Code Bulletins
- N = ANSI & ASCii Bulletins
-
- 2 <- Number of times per day a user may
- enter the door
-
- RIP <- "RIP" enable RIP bulletins "N"
- disables
-
- Edit the Sample.CFG file to suit your individual BBS. You
- must have all 12 lines and no extra characters.
-
- Line 1: This line points to where OLT.EXE will find the callers
- information file. Just include the line that your
- particular BBS uses. DO NOT put all of them in the CFG
- file.
-
- Line 2: Place the name of your BBS on this line.
-
- Line 3: SysOp's first name goes here.
-
- Line 4: SysOp's last name goes here.
-
- Line 5: Your Registration Number goes here if registered. If
- you haven't registered you can still use the
- door...just enter 00000 until you get your registration
- number.
-
- Line 6: The minimum security level that is allowed in the door.
-
- Line 7: Maximum number of questions allowed per visit to the door.
- I would suggest 25-30 as a reasonable number. The smaller
- this number, the more likely that the users will continue to
- use the door.
-
- Line 8: Enter the complete path and name of the ANSI bulletin
- that you want OLT to create.
-
- Line 9: Enter the complete path and name of the ASCii bulletin
- that you want OLT to create.
-
- Line 10: "WC" to create WC!3.x specific bulletins or "N" for ANSI and
- ASCii bulletins. Place "PCB" on this line for PCBoard
- Color Coded bulletins. If you Config for WC! or PCB Bulls, Place
- the name of the bulletin on Line 8 of the CFG file. Be
- sure to add the ".BBS" extension to it. You may leave Line
- 9 blank but it still MUST be included in the CFG file.
-
- Line 11: Place the number of times that you want the users to be
- able to play OLT each day. For instance, a "2" placed on
- this line will limit users to 2 plays per day.
-
- Line 12: Place "RIP" on this line to create RIP style bulletins.
- Place an "N" to disable.
-
- If you use the sample CFG file be sure to remove all
- remarks and use a pure ASCII editor such as EDLIN or QEDIT. Word
- processors typically leave hidden control codes. Those hidden codes
- could cause the program to depart for worlds unknown. Save your
- newly edited file using any name you want....suggested OLT-01.cfg.
-
-
-
-
-
- DOOR BATCH FILE
-
- Create a batch file or modify the sample OLT.BAT file
- supplied. This is what you need:
-
- @ECHO OFF Keeps a clean screen (optional)
- CD \DOORS\OLT Change to the OLT door files directory
- OLT OLT-01.CFG Run OLT using OLT-01.CFG configuration
- CD\WCAT Change back to the WCAT BBS directory
- CAT.BAT Restart the BBS. On BBSs which shell to
- dos to run the door this line may be
- omitted or maybe the word "EXIT." Check
- your BBS door instructions.
-
- MULTIPLE NODES
-
- Create a configuration file for each node. Each file
- should have a unique name.
-
- EX: OLT1.CFG OLT2.CFG
-
- OLT has been tested under LIVECAT and DESQVIEW and performs
- very well under either or both.
-
- COMM PORT IRQs
-
- OLT is written using DoorFrame. DoorFrame supports COM 1-4 on the
- standard IRQ's - COM1 or COM3 as a standard uses IRQ4 while COM2
- and COM4 use IRQ3. If your system uses a non-standard IRQ, add the
- IRQ number after the configuration filename. Let's assume your
- Door is called FOOBAR and you want to use COM1 but non-standard
- IRQ5. The command line passed to your Door would be:
-
- FOOBAR FOOBAR.CFG /5
- FOOBAR FOOBAR.CFG *5
-
- The /5 tells DoorFrame to use IRQ5 rather than the standard
- IRQ4 normally used with COM1. No /x parameter is needed for the
- standard IRQ's.
-
- Fossil Driver Support
- ---------------------
- DoorFrame supports the use of Fossil drivers. To tell your Door to use the
- Fossil driver instead of the standard COM ports, just put /FD on the command
- line when running the door. For example:
-
- MYDOOR MYDOOR.CFG /FD
- MYDOOR MYDOOR.CFG *FD
-
- indicates that a Fossil driver is present and should be used. If no Fossil
- driver is detected, DoorFrame will print a message to that effect and exit
- the door gracefully.
-
-
- TIPS AND TRAPS
-
- Be sure to read all the READ.ME, README.1ST AND UPGRADE.DOC
- files if they are included in the package. They sometimes contain
- some very useful information. <G>
- Of course you can do like me, just set the darn thing up without
- the docs then fuss at the door author for not making it simple
- enough to work the first time.
-
- IF You get an error...check every path to make sure you typed
- it correctly. Check the file name...does it match exactly? Does
- the configuration filename match? Did you leave off the
- configuration file extension? Do you have the correct BRUN module
- in a directory on your path? If all those seem correct and the
- door still won't work...call me......preferably not in the middle
- of the night...no door is that important.
-
- When the door is in use...you can use the sysop options
- listed at the bottom of your screen to chat, increase or decrease
- the users time or log the user off.
-
- LOCAL USE:
-
- You may type "OLT LOCAL" from the DOS prompt. This will enable
- OLT to operate out of the BBS environment.
-
-
-
-
- MISCELLANEOUS NOTES
- ===================
-
- DoorFrame requires DOS 3.x and up since all files are opened in SHARED mode.
-
- When using PCBOARD.SYS, OLT requires that PCBOARD.DAT be in the same
- directory as PCBOARD.SYS. OLT also accesses the USERS file.
-
- When using USERS.SYS, OLT also accesses PCBOARD.SYS, PCBOARD.DAT and the
- USERS file.
-
- The DOOR.SYS used by OLT is the standard 52 line GAP (tm) file.
-
- The CALLINFO.BBS used by OLT currently contains 36 lines.
-
-
-
-
-
- LEGALITIES
- __________
-
-
- THIS SOFTWARE AND ACCOMPANYING MATERIALS ARE DISTRIBUTED "AS
- IS" WITHOUT WARRANTY, EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT
- NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL ANYONE
- INVOLVED WITH THE CREATION AND PRODUCTION OF THIS PRODUCT BE LIABLE
- FOR INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES, ARISING OUT OF ANY
- USE THEREOF OR BREACH OF ANY WARRANTY.
-
-
- DISTRIBUTION
- ____________
-
- You may make this file available for downloading from your BBS
- or you may upload it to any BBS of your choice, provided that you
- do not make any changes to the contents of the archive (ZIP file).
- The archive and its individual contents may not be used by any
- service that charges any money whatsoever, without the written
- permission of the author. The "AV" of PAROLE software MAY NOT be
- removed from this archive.
-
- REGISTRATION
- ____________
-
- I am not a subscriber to the "Crippleware" concept, and this
- program reflects that philosophy. This is a full-featured program,
- whose functionality is not hampered in any way, whether you
- register it or not. It is only $15 to register this door. There is a
- 15 second pause which will be removed upon registering OLT.
-
- Remember, whether you are registered or not, should you have any
- problems, questions or suggestions for improvements, feel free to call.
-
- THANKS
- --------------
-
- Special thanks goes out for my wife who is definitely a
- "Computer Widow".
-
- Ted Freeman the author of DoorFrame, a first class BBS Doors
- Development Library.
-
- My BBS users who have had to endure constant badgering to help
- me test the programs that I have written.
-
- A *VERY SPECIAL THANKS* to Mustang! Software for developing the
- greatest BBS Software on the market, WILDCAT! 3.x. And about
- to be even better when they revamp the on-line chat feature.
-
- Liane Benway, SysOp, Running Wild !!! in Norcross, GA. Without
- Liane, you wouldn't have these fine DOCs.
-
- John Kutas, SysOp, THE SWINGERS CONNECTION BBS in Philadelphia, PA.
- After countless long hours on the telephone, we finally solved the
- world's problems.
-
-