RBBS-UTI Driver Ver. 1.1 Compatable w/ UTI Revision 2 The original UTI was written under a time constraint of a couple days notice and although it was tested and debugged, I have decided to make a new release. The upgrades are listed below. Installation - Replace version 1.0 of the UTI with the new files. NOTE : All files now read version 1.1 UTILIST.EXE - There was a small cosmetic change made, if a sysop entered the conference names in small letters, the M.DEF would appear in the users reader. This caused no functional problem, it just created an unappealing look. UTIEXPRT.EXE - There are several versions of RBBS out there and several functional utilities for maintaining the message bases. There are a few utilities that do not prescribe to the RBBS exact specifications. Those type utilities would cause the UTI to be off by a single digit on mail exporting. RBBS is VERY tolerant of these offsets. I have therefore added the same amount of tolerance to the UTI. Since I was in the UTI code I also spent time increasing the speed of the export program. Your performance will depend on machine type, cpu speed, conference size, and amount of mail exported. UTIIMPRT.EXE - Like in the UTIEXPRT program, as a result of other message base utilities the last message number in a conference could be shifted out of position. This resulted in the RBBS-UTI allowing RBBS to display a false Last Message Number. After seeing several message bases with strange headers I have implemented several "safety" features for the message bases to provide a greater level of compatability with outside utilities. If a conference is public (No Users File) UTI will still work. The Number of maximum messages allowed is no longer adjusted downward in proportion to the file size. NOTE : RBBS has a maximum of 999 active messages per conference. UTILSTRD.EXE - When writing the users Last Message Read Pointer, which is done when the user has received their messages, RBBS-UTI displays the users name and turns the mail waiting flag off in that conference. UTIDOOR.EXE - If the Sysop logs on locally (COM0) the name "SYSOP" is placed in the door information file. "SYSOP" is now converted to the Sysops Remote Logon Name (AKA - Sysops Psuedonym) so that mail will be properly processed. If a Sysop/user had more than 546 minutes left in the session, the number of seconds remaining (needed by MegaDoor) would exceed the maximum integer value allowed and send them back to RBBS. Seconds remaining is now calculated and adjusted for the door to accept. UTIVER.EXE - Displays/Writes RBBS-UTI Version 1.1 UTIHIGH.EXE - Displays the name of Conference being checked and the highest message number. If the a conference does not exist the highest message number will be set to 0 and an error message will be displayed. UTIRBBSC.EXE - No Operational Changes. Displays Ver 1.1 Cosmetic change explaning that just pressing return will provide a blank answer for conferences with no associated users file.