


                               PURITY 1000

                                 v 2.7

                           February 14, 1994

                        PCBoard 14.x and GAP 4.x
                           WILDCAT!, Spitfire
                             QBBS, RBBS, RA

                                   by

                             Dennis Maidon

                          PAROLE TECHNOLOGIES
                          9411 Buffalo Rd
                          Clayton, NC  27520
                        (919) 965-3600 -> Voice


                          The Parole Board BBS
                            FIDO: 1:151/185

              (919) 965-4696 -> US Robotics Dual Standard
              (919) 965-9885 -> Hayes OPTIMA 288 V.FC

                                OVERVIEW
                                ________

        NOTICE:  PURITY 1000 is not a drop in replacement for PURITY
        500.  You will need to do a complete installation from scratch.

        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 fairly easy and straight-forward. The following steps and
   examples should have you up and running in a very short period of time.
   It is assumed that you are familiar with setting up DOORS on your system.
   To this end, only examples of the configuration file and Door batch file
   are described.

      1) Create a directory to hold all PURITY 1000 files

      2) Unzip PURITYxx.ZIP into the the above directory

      3) Run 'INSTALL.BAT' This will unzip all the files and create the
         necessary subdirs.

      4) Create a configuration file, with a name of your choice, or
         modify the  PURITY.CFG file that is enclosed.
         A description follows:


   C:\WILDCAT\CALLINFO.BBS Ŀ  <- For Wildcat!
   C:\WC30\USERINFO.DAT        <- For Wildcat! 3.0 (NODEx directory)
   C:\PCB\PCBOARD.SYS          <- For PCBoard using PCBOARD.SYS only
   C:\PCB\USERS                <- For PCBoard using USERS only
   C:\BBS\DOOR.SYS             <- For Systems that support DOOR.SYS
   C:\BBS\DORINFOx.DEF         <- For QBBS/RBB/RA.  Replace x with Node #.
   C:\BBS\SFDOORS.DAT          <- For Spitfire
   C:\BBS\TRIBBS.STS        <- For TriBBS
   The Parole Board BBS         <- Your BBS Name
   Dennis                       <- SysOp's First Name
   Maidon                       <- SysOp's Last Name
   00000                        <- Registration Number
   YES                          <- Create .DNR Log (Y/N)
   C:\WC\BULL\BULL1.SCR         <- Path and Name of Color Bulletin
   C:\WC\BULL\BULL1.BBS         <- Path and Name of ASCii Bulletin
   50                           <- Minimum # of Questions before scoring
   100                          <- Minimum security level allowed in door.
   N                            <- WC = WC! PCB = PCBoard N = ANSI/ASCii
   Y                            <- (Y/N) Allow users to logoff from door
   RIP                          <- Create RIPSCRIP bulletins

     Edit this .CFG file to suit your individual BBS.  All 13 lines MUST
     be present.


   Line 1:  This line points to where PURE1000.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

   Line 6:  YES to create .LOG log or leave blank

   Line 7:  Enter the complete path and name of the ANSI bulletin that
            you want  PURITY 1000 to create.

   Line 8:  Enter the complete path and name of the ASCii bulletin that
            you want  PURITY 1000 to create.

   Line 9:  Minimum # of questions to answer before user is scored

   Line 10: The minimum security level that is allowed in the door.

   Line 11: This line checks to see if WC! 3.0 bulletin is to be
            created.  (See Note below)

   Line 12:  (Y/N) Allow the users to logoff from the door or return to
             the BBS to logoff.

   Line 13:   RIP= create RIPSCRIP bulletins
              N = do not create a RIP bulletin


        If you use the above CFG file be sure to remove all remarks and use
   a pure ASCII editor such as EDLIN or QEDIT.  Hidden control codes could
   cause the program to depart for worlds unknown.

      4) Create a batch file or modify the PURITY file supplied. A
         description of this file follows:

            ECHO OFF
            CD \DOORS\PURITY        Location of  PURITY 1000 files
            PURE1000 PURITY.CFG     EXE filename and CFG filename

       5) When running in more than one node, be sure to supply a
          different configuration name for each node (your choice of name).

          EX: PURITY1.CFG  PURITY2.CFG

           PURITY 1000 has been tested under LIVECAT! and performs very well.

     NOTE:    If you use the WC! 3.0 specific bulletin you will need to
              enter the bulletin name on Line #7 of the CFG file in
              place of the ANSI bulletin.  You can leave the Line #8
              blank or put a fake filename in there.  NO ASCii file will
              be written.   If you use Livecat! and put the door
              bulletins under Livecat! you cannot use this option as LC!
              will  not display them properly.

              If there are other BBS systems that use specific color
              codes, send me the specs and I will try to incorporate
              them into my doors.

NOTE: Wildcat!3.x+ creates the USERINFO.DAT and DOOR.SYS in the node
      directory. Your first line of the CFG file must point to the
      proper NODEx directory.

      EXAMPLE:  C:\WC30\WCWORK\NODE%WCNODEID%\USERINFO.DAT
                C:\WC30\WCWORK\NODE1\USERINFO.DAT

NOTE: DoorFrame supports COM 1-4 on the standard IRQ's - COM1/COM3 = IRQ4 and
      COM2/COM4 = IRQ3. If you wish to use 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 and 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 that
      is 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
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.

When specifying the location of the system file on line 1 of the doors .CFG
file, you may use the environment variables %pcbdrive%, %pcbdir%, %pcbnode%,
and %wcnodeid%. Some examples:
 PCBoard: 
   USERS.SYS in C:\PCB           - %pcbdrive%%pcbdir%\USERS.SYS
   USERS.SYS in C:\PCB\NODE1     - %pcbdrive%%pcbdir%\NODE%pcbnode%\USERS.SYS

 Wildcat!:
 USERINFO.DAT in C:\WC30\WCWORK\NODE1 -> C:\WC30\WCWORK\NODE%wcnodeid%

Non-PCBoard systems may use the PCB environment variables by setting them
in either AUTOEXEC.BAT or in the batch that runs the door. For example:
 SET PCBDRIVE=C:
 SET PCBDIR=\BBSDIR
 SET PCBNODE=1


      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.

      When a user first log onto ' PURITY 1000' the program checks his
security level to make sure that he has a high enough level to enter the
door.  If the user passes this test, he may proceed in playing 'Purity
1000".  All the users information will be stored in the Users database.
This info will be used each time the user logs on to pick
up his ALIAS and other info.

    A few extra niceties were added in at the very end of the eta test.
PURITY 1000 will now give the users a chance to restart their questions.
Some users log on the first time and screw around answering the
questions, then they get serious and have to ask the sysop to erase
their user files so that they can start over.  The user is prompted
right after the opening screen if they want to start over.  If they
answer "Y" there is NO turning back.  P1000 will erase their PRO
files.  Some users also get into a rut answering some of the questions
and let a good one slip up on them.  They are now able to back up to a
previous question and change their answer.  They may backup to questions
#1 if they so desire.

     PURITY 1000 will automatically save the users stats every 25
questions.  This will be a big help in cases where the power goes off
after the user and spent many minutes answering 2-300 questions.

    PURITY 1000 will also write a file (.PRO) which contains all of the
answers that a user inputs.  I have written a companion file which will
allow users to take these profiles and compare them to their own
answers.   ANALYZE.EXE will scan all 1000 answers and figure the
percentage of matches for the entire test plus give statistics on the
thirteen individual parts of the test.

    There is also a companion program called PSA (Purity Stand-Alone)
which will enable your users to run PURITY 1000 offline and not tie up
your BBS for long periods of time.


                              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.



                             REGISTRATION
                             ____________


   The registration key is already included.





                                 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.0.

    Tom Lamere, The Petting Zoo BBS, Phoenix, AZ  A eta tester that
    KNOWS what "BETA TEST" means.

    Chris Valk, Infinity BBS, for discovering and reporting a few bugs.

