RBBS-UTI Driver Ver. 1.2
                       Compatable w/ UTI Revision 2

  Several additional enhancements and corrections have been made to
  the UTI for RBBS.  The upgrades are listed below.

  All known problems and suggestions have been resolved/incorporated. 

  Installation - Replace Previous version of the UTI with the new files.

  NOTE : All files now read version 1.2

  UTILIST.EXE -

     No operational changes made.

  UTIEXPRT.EXE -

     Since RBBS supports group security levels for mail, the users
     security level is checked to insure no mail is exported to a user
     without sufficient access.

     Killed and password protected mail are no longer allowed to leave
     the system.  The only private mail departing the system is mail
     addressed directly to the user.
      
      MegaDoor requests messages be parsed in a range.  They send a
      Start and End message number.  The Start number being passed is
      the Users LAST MESSAGE READ so I have incremented the counter
      to export the users LastRead +1 thru to the requested ending
      message.  Hopefully they will NOT change the Specs and allow this
      one to come back and bite me.

      If you include your MAIN message base to be processed by the UTI
      and MegaDoor, users may get into the habit of NOT reading online.
      Now how do you know when to kill those messages in the Main Area?
      Normally once they are read you would do so, well with a reader
      you have no way of knowing.  I have therefor added a feature to
      indicate that the message has been picked up by the user it was
      intended for.  You will find a (æ) micro symbol as the last
      character of the subject field.

  UTIIMPRT.EXE -

     We found that RBBS expects certain message header information that
     was previously not included.  An example would be the seconds in
     the time a message was left.

     All incoming mail recieves a group security of 1.

     RBBS Left justifies numbers and UTIIMPRT previously right justified
     which caused message bases to be slow and possibly grow.
     NOTE: This only occured in message bases where message numbers were
           less than 1000.

  UTILSTRD.EXE -

     No operational changes made.

  UTIDOOR.EXE -

     To support private mail the UTI must know who is requesting mail.
     UTIDOOR now creates a 2 line file, RUTIDOOR.DEF, which contains
     the users Name and Security level in support of UTIEXPRT.

     Private Mail was NOT getting to the user.  MegaDoor looks for the
     user name padded out with spaces to a length of 25 characters.
     RBBS writes the DorInfo.Def file in a blank stripped fashion.  I
     have therefore added spaces to the end of the user name when
     passing this info to the MegaDoor program.

     *** NOTE ***

     If using the reader outside of the BBS you will need to create a
     two line file in your READER directory called RUTIDOOR.DEF
     consisting of the two lines show below :

     SYSOP
     50

     The word "SYSOP" (no quotes) must be the first line and the
     security level of the sysop on the second.
     Before executing the MEGADOOR this file must be copied to the
     MEGADOOR directory in order for the UTI to function correctly.

  UTIVER.EXE -

     Displays/Writes RBBS-UTI Version 1.2

  UTIHIGH.EXE -

     No operational changes made.

  UTIRBBSC.EXE -

     No Operational Changes.  Displays   Ver 1.1

  RBBS-UTI.DOC -

     Ammendments to this this file are contained in :

            UPDATE.UTI
            UPTD12.UTI

 ********************************************************************

 KUDOS go to the following people who have helped in one way or the
       other to improve the RBBS-UTI:

                           Gregg Snyder
                           Jim Thompson
                           Bob Kurtz
                           Ridge Gardner
                           Curt Akin
                           Charles Baldridge