




  --- Mutant BBS v1.1 UTI Documentation ---                             Page 1

  Introduction
  ------------
  Universal Text  Interface (UTI) drivers are a set of executables which allow
  an application to be designed to work with any BBS program.  Current primary
  uses of UTI drivers are for PCRelay and PCLink networking.  I have written a
  set  of UTI drivers for Mutant which are  as compatibile as possible.  Below
  is a list of the drivers, their function and any Mutant related notes.

  UTIHIGH.EXE
  -----------
       The application passes a conference id and a filename to the EXE.  My
  UTI drivers treat the conference ID as Mutant's area number.  This will
  write out the last message number in the message base based on the base
  configuration, not the number of the last number.  This should not cause any
  problems as they should be the same.  
       In order to "find" the message bases, all the UTI drivers use an
  environment variable, MTNTRUN, in the form:

       MTNTRUN=d:\path\CONFIG.DAT node

  which is basically the name of the current configuration file and Mutant's
  node number.  If you run under Mutant v1.06+, Mutant will automatically set
  this for you.  Also with v1.06, you may set this in advance of running
  Mutant and Mutant will use these rather than any command line parameters.

  UTIEXPRT.EXE
  ------------
       The purpose of this is to extract messages in a given area from a
  number specified to the last message.  If it is called with the /NETWORK
  option, the driver will only export messages which are not marked as "sent". 
  In order to conform with text limitations, Mutant chops off the to, from,
  and subject fields to 25 characters.  Also, the messages are rewrapped to 72
  characters and are truncated if they exceed 2000 lines.  Also, this ignores
  any line in a message beginning with a ^A (FIDOnet kluge line).  Also, the
  msg filter flags specificed in the configuration are used to strip colors
  and upper bits, etc.

  UTIIMPRT.EXE
  ------------
  Several notes:

  1.   If /NETWORK is specified, or the message has a 'N' for echo status, the
       message will be marked as "sent".
  2.   Even though the UTI spec only allows for 25 characters for TO:, FROM:
       and SUBJECT: fields, the driver supports 35 for TO: and FROM: and 71
       for SUBJECT:.  This means that user's with a name >25 characters may
       have trouble receiving messages.
  3.   No Tag or origin line is added to the imported message.  Also, no MSGID
       is generated (because my current scheme in Mutant is inadequete).




  --- Mutant BBS v1.1 UTI Documentation ---                             Page 2

  UTILIST.EXE
  -----------
       Generates a list of all available conferences.  All this does is read
  in INDEX.MSG and toss out the names and area numbers.  My UTI driver uses
  the area number as the conference id and the name of the conference and the
  name of the base as the conference description.  Mutant may support a short
  name in the future which would then be used for the conference name.

  UTILSTRD.EXE
  ------------
       This generates a list of last read pointers for a specific user or sets
  a user's last read pointers.  When listing the pointers, the driver will use
  a -1 if the user does not have access to the area or has de-selected it from
  within Mutant.  When updating the pointers, anything out of range (0-65535)
  will be ignored.

  PLEASE NOTE:   The generated/imported list must exactly match the list
                 generated by UTILIST.EXE.  Therefore, DO NOT modify your
                 message bases while the UTI drivers are in use as the list
                 correspondence may change.

  Because I assumed that the driver may not have access to online information
  the following SACS have been modified:

  C -  the sysop is never available for chat.
  H -  always false since there is no current file/msg area.
  @ -  any temporary variable/flag used will result in a false condition. 
       Variables stored in the user record will be evaluated properly.
  B -  Always false, user is neither on remotely or locally.
  T -  Always false
  R -  User never meets any ratios.
  M -  Never a sponsor
  V -  User has ASCII
  I -  Never parsed (always true).

  UTIVER.EXE
  ----------
       This writes a two to the first line of the specified file, and "Mutant
  BBS v1.1 UTI driver by Tom Johnson" to the second line.

  UTIDOOR.EXE
  -----------
       This is NOT part of the Mutant UTI drivers for a couple of reasons. 
  First, I feel UTI is inadequete for offline mail reading which is more than
  likely the reason for this file.  Second, Mutant can generate it via
  DOORFMTS.TXT by entering the following:




  --- Mutant BBS v1.1 UTI Documentation ---                             Page 3

  :UTI Door
  OPENFILE:utidoor.txt
  USERFULL U
  BAUD
  LOCAL 0
  NLOCAL COMPORT+
  BAUD
  TIMSEC

  UTIRFLAG.EXE
  ------------
       This sets the "received" flag in the specified range for all messages
  to the specified user.

  Disclaimer
  ----------
       I make no express no implied guarantees about the functionality of
  these drivers.  Therefore, use them at your own risk.  I will say that the
  UTI specification is not 100% compatible with Mutant and therefore problems
  may arise.
