Maximus for OS/2 V1.20 release notes, Mon  08-06-1990
-----------------------------------------------------

Here is the third version of Maximus for os/2 to be made freely
available.

History:
        v0.99.OS/2      - Initial release
        v1.00.OS/2.R2   - Second release (a stable Beta version)
        v1.02.OS/2      - This release.


It is assumed that you have already installed MAX_102.LZH,  the dos
version of Maximus.  To install the OS/2 version,  simply copy all
of the *.EXE files to your \MAX directory (or wherever you installed
MAX_100).  If you place SNSERVER.DLL and COMM.DLL in this dir,  make
sure \MAX is on your LIBPATH.  Alternatively,  put SNSERVER.DLL and
COMM.DLL in a dir that is already on your LIBPATH.  Your LIBPATH is
defined in C:\CONFIG.SYS.

If you have no desire to keep the DOS executables,  you may erase
them.  Note that ALL of the protect mode (os/2) programs, that have
a similar dos program,  end in the letter 'P'.   If you have already
been running the DOS version,  and created batch files that
reference the programs,  you may wish to rename the OS/2 EXEs to the
names used by the DOS version.  You can also "ren *.bat *.cmd" to
turn them into OS/2 batch files.  Snip this out to rename the OS/2
EXEs:

ren ANSI2BBP.EXE  ANSI2BBS.EXE
ren CVTUSRP.EXE   CVTUSR.EXE
ren EDITCALP.EXE  EDITCALL.EXE
ren MECCAP.EXE    MECCA.EXE
ren PIPERP.EXE    PIPER.EXE
ren SCANBLDP.EXE  SCANBLD.EXE
ren SILTP.EXE     SILT.EXE
ren MAXRENP.EXE   MAXREN.EXE
ren MAXP.EXE      MAX.EXE

New features:
-------------

 -  All features in the DOS version of Maximus, v1.02

 -  Maximus uses COMM.DLL for all com port i/o.  These routines provide
    better throughput,  yet use less CPU time.

 -  PmSnoop now takes a command line parameter: a pipe name.  This
    was provided so that you can recover from a mis-typed pipe name.
    If you find yourself in the situation where PmSnoop aborts with
    an error "SYS0110",  go to a command line an start pmsnoop
    something like this: "Pmsnoop \pipe\pipename".  Then "S)ave
    Options" from the F)ile menu.

Comments:
---------

 - The <ahem> correct init string for an HST 9600+ modem,  locked at
   a high baud rate, is, in part:

        "AT &B1 &H1 &I0 &R2"

   In conjuction with a MODE setting, in part,  of:

           MODE comx:<baud>, n, 8,1, IDSR=OFF,ODSR=OFF,OCTS=ON,RTS=HS

   However, this will not work with most versions of BTP :-(.  BTP
   will force the RTS settion to "TOG" with the above setting.  I
   think btp 2.40 solves this problem.  If you're having problems,
   try RTS=ON and cross your fingers.

   The modem init string is put in binkley.cfg.  The MODE command is
   used before you start BTP.EXE.

 - Most COM0?.SYS's are BRAIN DAMAGED.  If Binkley and/or Maximus
   start reporting errors like:

       ! 06 Aug 21:25:20 BINK SYS0021: ComGetDCB()
       ! 06 Aug 21:25:20 BINK SYS0021: ComGetDCB()
       ! 06 Aug 21:25:20 BINK SYS0021: ComGetDCB()

   It means COM0?.SYS has taken a holiday.  You may also get a
   pop-up saying either "COM?: is not responding" or "COM?: is not
   installed".

   None of this is bink's or max's fault.

   I have yet to find a COM0?.SYS under os/2 1.20 that does not do
   this regularly.  The most reliable one I have found was a 1.10 EE
   version.  Unfortunately,  the more reliable 1.10 com0?.sys's
   don't support extended buffering on the 16550 UART.

Peter Fitzsimmons, Mon  08-06-1990