What is New with this version?

 Error: If a User left as first account he would enter the second
  account in whatever conference he left from the first account.

 Fix: The User always is placed in Conference 0 in second account now

                                 * * *

 What is coming in the future?

 (excerpt of docs of the alpha ver.2.0 now running on my BBS):

 Record #1 of the USERS file (second account) can only be accessed by
 record #1 of first account USERS file.  In no place is the Sysop
 password checked for or written by this program.  LOCK and ALLOW
 features are now available, letting the Sysop run this program with
 ability to LOCK anyone not entered by him, or to LOCK individual
 users from access.  The ALLOW feature is similar to LOCK, but it
 will give an explanation to the User (Sysop defined), and is meant
 to let a user know that the Sysop has not allowed him access for a
 reason such as, underage, Sysop needs to review before allowed, etc.
 With LOCK, a User is returned to the first account with no obvious
 sign of what transpired.

 Better documentation!

 File holds 1st Account & 2nd Account User Names, and flags to
 control access to the Second Account

 Sysop can specify up to 3 Users as able to maintain the PCB2ACT.NAM
 file.  Sysop always has that option, and only Sysop can alter those
 3 Users records in the PCB2ACT.NAM file for security reasons.
 Only User of Record 1 of 1st account can get access to record 1 of
 2nd account.  Those Users have access to maintenance upon loading
 PCB2ACT.

 Will place new Users names & aliases in PCB2ACT.NAM file if Sysop
 so configures (less work for Sysop!)

 LOCK and ALLOW functions very configurable by Sysop.

 Writes all important occurrences to the CALLERS file.

 Better security, including Virus-self-check.

PCB2ACT.CFG:

  LOCK line - this line must be N, Y or ALL
     This allows turning on/off the flag placed in the .NAM file
     to lock-out a User from being effective.
     Under Sysop maintenance, the LOCK flag can be set on/off for
     any User registered in the .NAM file.  The Sysop can create a
     record and LOCK any User regardless of whether he/she has a record
     in the PCBoard Users file.
     If set to N, the LOCK parameter is disabled, all Users have access
     based on other parameters set, even if they are flagged as LOCKed
     If set to ALL, every User is assumed to be LOCKed from access
     they have an entry in the .NAM file and it does not have the LOCK
     flag set.

  ALLOW line - this line must be N, Y or ALL
     This controls how Users are handled, generally New Users into
     the Second Account.
     If set to N, the flag which can be set by the Sysop is ignored
     entirely in the .NAM file.
     If set to Y, only Users with the ALLOW flag set to Y in the .NAM
     file are allowed in.  This does not stop anyone with no record
     from entering.  It would appear to be the same in this function
     as the LOCK, except a User with a record, and no Y flag here is
     given a polite "Sorry, the Sysop must authorize your access".
     Regardless of setting, any New User will not be entered in the
     .NAM file until maintenance is run to place the name & alias.

NOGOOD:
  This file is built when PCB2ACT is unable to decide how to handle
  a user for some reason, and exits back to the first account.  It
  is written only in case the Sysop has a reason to check at another
  level for access to the second account.  It can be checked for in
  the BAT file if the Sysop requires it for other use.

NEWGUY:
  This file is built when no account if found for the user in the
  PCB2ACT.NAM file.  It's existenece means the user will not have a
  PCBOARD.SYS file written for him, and must enter the second account
  as a New User.  If you choose, this can be used to call other
  programs you may need to run.

PCBoard Files:

    It is suggested you make several changes to your PCBText file to
 be used in the Second Account - such as a change to the initial logon
 for a New User of the Second Account to insure he is prompted for an
 alias; also, it is a good idea to change the Main Command prompt to
 add a word to let the User realize he is in the Second Account

    The BRDM file normally used for the Main Menu should have one major
 change.  Unless you chose to add a couple lines in the calling BAT
 file to remove the "good" PCBoard.sys written by the first account and
 force the User to exit the system after leaving the second account, he
 will be returned to the first account upon entering a G.  The menu
 should reflect this (noticeably!) as "(G)o back to Main Board" in some
 manner.  Enclosed is the BRDM in use on Polymath One BBS.

   The you may wish to use a different TCAN file on the second account,
 as you may be more lenient (or strict) on that account.


                            * * *

   Any comments or suggestions are welcome at this time.  The 2.0 version
 will not be released in the very near future, as it is a complete
 rewrite of what began as a simple utility for my own use.
   Anything suggested will be considered to be a part of this program
 for the release of version 2.0.
   If you are now using PCB2ACT with the Comment 2 entries, a converter
 is included with the 2.0 version to create the required file with
 no work on your part.
   I am glad so many Sysops have given the initial, "crude" version a
 try - and because of this already wide acceptance that I decided to
 make it a more friendly, proficient program.

   Thank you...


            Dalaye Gabriel