============================================================================
            ReVive, v2.20 HISTORY File by Dotoran of Frontiers!
============================================================================

-- v2.20 --

    - A little bug fix release: January 1, 1996!
        - I was noticing when logging off that the ReViveDBM would say it
          was UPDATING my entry in the database, even though none of my info
          had changed. Upon looking into this, I discovered that when the
          file EXPANDS the database when a new user logs on, the old data
          was being deleted(and would then subsequently be recreated when
          each user signed on next call). This would cause problems if the
          database held a hole when you needed to ReVive their account.
        - If you specified an account id number that was NOT deleted, or if
          you chose to NOT ReVive an account id number after checking it's
          data, the file would still tell you it needed to run POINTERS. It
          will now only ask to run POINTERS when it NEEDS to.
    - New additions:
        - You now have the ability to have ReVive BackUp the users' mail
          directories at AutoMaintenance time, instead of right after they
          logoff.
        - When backing up the users' mail directories, you can now specify
          whether or not you wish the older backed up files to be DELETED,
          before the current files are backed up. Stating NOT to delete the
          files will lessen the amount of fragmentation on your hard drives,
          but at the cost of possibly building numerous "extra" backed up
          files that the user has deleted themselves in the past.

-- v2.10 --

    - A bug fix release: October 15, 1995.
        - New users would cause an error to occur when saving the mail dir
          contents if they were a "high-end" new user, meaning if they were
          using an id number greater than the highest id number presently
          in use. The database manager will now GROW the file as needed to
          support any new users that may join the board.
        - A section was added to also run the POINTERS file after ReVives
          were performed, so that the bbs would recognize HANDLES of ReVived
          users. (Typing EA Handle after reviving a handle would present
          you with the "enter handle list" routine, which made it look like
          the handle didn't exist on the system).
        - The multiple colors used in the logentries of the previous version
          were causing the word-wrapping features of CNet to fail, so when
          you chose to view the log containing these entries, they tended to
          appear all jumbled up. I've gone with using just one color code
          per each log line.
    - New additions:
        - In order so that the database could GROW, I needed to save an extra
          value to the start of the database file which listed the current
          number of accounts, since the file last grew. It is this value
          which the program compares to your current total users value to
          make the determination as to whether or not the file needs to grow
          or not. Because of this change, the present database should be
          deleted and recreated(meaning the v2.0 db is NOT compatible with
          the v2.10 db)!
        - Added a variable to both the "ReVive" and "ReViveDBM" files to
          allow you to specify the path the "users2/" directory will be
          created. After giving it some more thought, I wasn't sure having
          the "users2/" directory stored in virtually the same location was
          such a good idea, so this variable allows you to specify another
          location, preferably one located on another PHYSICAL drive. This
          insures against a loss of data if one of the drives should become
          faulty, or show other adverse affects which could result in data
          being lost irretrievably.

-- v2.0 --

    - Second release version: September 24, 1995.
    - Total rewrite of the file. Creates a database of information which
      contains the user's serial id number, handle, and password in an
      encrypted file stored in your SysData: directory.
    - If enabled, also creates a mirror version of your "mail:users/"
      directory in the "mail:users2/" directory for use in reviving a users
      mail contents as well as their account.
    - Allows a user to be FULLY revived, with the same serial id number,
      handle and password they possessed before they were deleted, as well
      as getting back all information stored in their uucp mail directories.
    - Changes were made directly to memory as well as to disk, so that the
      need to reboot the system for the changes to stick is no longer needed.

-- v1.0 --

    - My first version of this work.
    - Allowed you simply to reactivate a deleted user, however you still
      needed to manually edit their Handle, Password, and Serial ID Number
      to hold the correct data.
    - You also needed to REBOOT your system for the revived account to be
      fully recognized.
    - No support for user mail directory backups present.

============================================================================
                       Frontiers BBS (716)/823-9892!
============================================================================