                                    iRMX KERMIT


        INTRODUCTION

        MSKERMIT, the richest and most widely used implementation of KERMIT
        for  the small computer, has been ported  to iRMX.  Version 2.26 of
        MSKERMIT  (essentially unchanged) has been placed in a cradle which
        leaves  it blissfully  unaware that  it is  not running  under DOS.
        Columbia has offered to pick up the few syntax changes necessary to
        make the source acceptable to either the Microsoft assembler, MASM,
        or ASM86.   We hope  to have Version  2.28 available by  the end of
        1985.  Then,  future  versions  of  Columbia  source  code  can  be
        converted to RMX with a simple edit pass.

        This   document  describes   installation  and   configuration  and
        discusses  differences  between  RMXKERMIT  and  MSKERMIT.    Users
        unfamiliar with  MSKERMIT may  prefer to  read this  in conjunction
        with KERMIT.DOC.

        INSTALLATION

        The first diskette contains all  you  need  to  use  KERMIT.    The
        following files are included:

        READ.ME.1ST     this document

        KERMIT.DOC      Columbia's KERMIT User Guide with documentation
                        for the MSKERMIT implementation

        KERMIT          the executable program

        MSKERMIT.INI    a sample initialization and configuration file
                        Warning: this file contains escape sequences

        The second, optional, diskette  contains  source  code  and  submit
        files  to assemble and link KERMIT.  ASM.CSD assembles the modules,
        and  LINK.CSD puts it all together.  If you have a local version of
        MSKERMIT, the additional submit  file,  EDT.CSD,  can  be  used  to
        convert the MASM modules to ASM86 format.

        Both disks are copyable, and you are free to make as many copies as
        you  wish.  KERMIT may be given away  but must not be sold.  KERMIT
        is easiest  to use if it and MSKERMIT.INI  are copied to one of the
        automatic search directories such as /UTILS.

        CONFIGURATION

        The  first line of MSKERMIT.INI is used to configure KERMIT to your
        terminal using OSC sequences  (see BIOS  App. F).   First  you must
        decide if  that's what  you want.   Presently  (Oct. '85),  the RMX
        Terminal Support Code is reluctant to permit transparent input when
        translation  is enabled.   As  a consequence,  you have  the choice
        between a decent  screen format  during file  transfer, or  a fully
        functional keyboard.  When you choose the acceptable screen format,
        RMX holds up the escape key for one extra keystroke, and if ^E, ^X,
        or  ^Z are needed for terminal configuration (several terminals use
        ^Z for clear screen),  they  won't  work  as  escapes  during  file
        transfer.   On the other hand, opting for the keyboard results in a
        hideous screen during file transfer.
        The sample MSKERMIT.INI file configures KERMIT for the Qume QVT102,
        Televideo 910 Plus, 912, 920, 925, & 950, and Zentec Zephyr & Cobra
        terminals.   Let's look at it to see how configuration works.  This
        example has the escape codes replaced by '{ESC}':

        ;{ESC}]T:T=1,F=1,U=32,E6=93,E30=75,E31=116{ESC}\
        SET SEND PACK 94
        SET BAUD 1200

        T=1     enables translation
        F=1     vertical cursor coordinate precedes horizontal
        U=32    value for cursor row or column 1.  32 is the code for space
        E6=93   translate cursor positioning to {ESC}=
        E30=75  translate clear screen to {ESC}+
        E31=116 translate clear to end of line to {ESC}T

        Configuration  OSC's must appear in the first line of MSKERMIT.INI.
        It  must begin with a semi-colon so that KERMIT won't treat it as a
        command.  Referring to the manual for your terminal and BIOS Tables
        F-4  and F-5, edit MSKERMIT.INI to match your terminal.  To disable
        translation and choose the keyboard over the screen, delete line 1.

        RMXKERMIT  looks for MSKERMIT.INI first  in your default directory,
        $.   If not found, it looks in  the directory from which KERMIT was
        loaded.   Suppose KERMIT is installed in  /UTILS.  The search would
        be, first  :$:MSKERMIT.INI, then, :UTILS:MSKERMIT.INI.   A multiple
        terminal  system with different brand  terminals can configure them
        all by using a different default directory for each.

        SERIAL PORTS

        MSKERMIT expects at least one serial communication port, COM1:, and
        will accept  a second, COM2:.   RMXKERMIT associates logical device
        names with COM1: and  COM2:.    For  COM1:,  which  must  exist  at
        initialization  time, RMXKERMIT  looks first  for :COM1:,  then for
        :T1:.  If neither are found, a warning message is issued and :TERM:
        is used.  On multiple port systems it's best to ATTACHDEVICE before
        calling KERMIT.  RUN ATTACHDEVICE in MSKERMIT.INI won't work.

        MSKERMIT's second serial port, COM2:, is always associated with the
        logical device  name :COM2:.   :COM2: may be  defined and redefined
        while in  KERMIT by  using the  KERMIT RUN  command with  the Human
        Interface commands, ATTACHDEVICE and  DETACHDEVICE.    The  initial
        association with COM1: can not be changed.

        SINGLE PORT SYSTEMS

        You  can use KERMIT  on a single  port system, if  you have another
        computer that you can connect directly to it.  For example, connect
        a  PC's COM port in place of your  terminal.  Call up KERMIT on the
        PC,  set the baud rate to match your RMX system, and connect to it.
        Use the  PC as the  RMX terminal.   Make sure that  neither :T1: or
        :COM1:  exist as logical names before calling up RMXKERMIT.  Before
        initiating a file transfer, do the following:

        SET REMOTE ON   ; necessary
        SET BAUD 4800   ; recommended, see below under usage notes
        SERVER          ; the baud rate won't change 'til this command
        Escape  back to the  PC's KERMIT, set  it's baud rate  to match the
        above, and use SEND or GET for file transfer.  When done, issue the
        FINISH command,  reconnect to  RMXKERMIT, and  exit to  the system.
        The  terminal's baud rate and other  attributes will be restored to
        their initial  values.  If you  want to continue using  the PC as a
        terminal, you'll have to  escape back  to the  PC, change  its baud
        rate, and reconnect.

        PATH AND FILE NAMES

        MSKERMIT  expects file  specifications in  the standard  MS-DOS 2.x
        form, d:path\file.type.  RMXKERMIT  associates  the  single  letter
        drive  specifier with the  corresponding RMX prefix.   For example,
        Z:SOURCE.P86  refers to the  RMX file, :Z:SOURCE.P86.   The default
        directory, :$:, is used when the drive specifier is omitted.

        MSKERMIT accepts either \ or  /  as  path  separators.    RMXKERMIT
        substitutes ^  for \.  Filename and type,  or extension are 8 and 3
        characters  maximum, respectively.  FILENAME. and FILENAME refer to
        the  same file under DOS.   You cannot refer  to FILENAME. while in
        RMXKERMIT.

        FEATURES NOT IMPLEMENTED

        PUSH has  not been  implemented.   Unlike the  DOS implementations,
        there  is nothing that could  be done with PUSH  that can't be done
        with RUN.

        Heath/Zenith-19 emulation, SET KEY, and  SHOW  KEY  have  not  been
        implemented.  You can use the terminal of your choice and configure
        RMXKERMIT to work with it.

        You  cannot transmit a break to the remote computer.  Although some
        serial  communication board's firmware supports sending breaks, the
        RMX device drivers do not.

        Wildcards  cannot be  used to refer to files at the RMX end.

        SET  DEFAULT will accomplish nothing.  Use RUN ATTACHFILE to change
        disk drives and/or directories.

        USAGE NOTES

        A HANGUP command  has been  added which  drops DTR  momentarily for
        serial ports which support modem control.

        The RMX Terminal  Support  Code,  when  operating  with  unbuffered
        serial boards such as the 8251, can accept only a few characters at
        9600 baud  before losing  some.   RMXKERMIT can  send at  9600 baud
        through such boards, but receiving is limited to 4800 baud.  It can
        connect to a remote computer at  9600  baud,  but  will  drop  some
        characters if  they are sent faster than  fast typing speed.  There
        should  be no baud rate problems  with buffered serial boards, such
        as the 544 or 188/48.

        RMXKERMIT can't read past NULs.  This won't effect file transfer as
        long as the pad character is anything but NUL when padding is used.
        If your  remote host computer  sends NULs while  RMXKERMIT is being
        used  as a terminal, you can recover  by escaping back to the local
        system and reconnecting.
        While SET DESTINATION PRINTER  works, it  is very  slow.   The line
        printer driver  hogs  the  processor,  as  a  result,  simultaneous
        read/write/compute is not  possible.    It's  probably  quicker  to
        receive to disk and then copy to the printer.

        RMXKERMIT reads  commands from  the submit  file when  operating in
        batch.

        RMXKERMIT will accept any RMX DIR command.

        Continuation can be used with the RUN command.  For example:

                RUN ATTACHDEVICE T4 AS COM2 &
                RUN PHYSICAL

        is equivalent to:

                RUN ATTACHDEVICE T4 AS COM2 PHYSICAL

        RUNning AEDIT (or  any other  program that  may object  to Terminal
        Support Code translation) under RMXKERMIT may not work very well.

        AVAILABILITY

        RMXKERMIT is presently available on 5 1/4" DSDD RMX format disks at
        $6/disk (media, postage, handling, tax, and license) from:

                University Bookstore Computer Shop
                6049 E. 7th St.
                Long Beach, CA 90840

        WHERE TO GRIPE

        Send problems to:

                Jack Bryans
                Finance Dept.
                CSULB
                1250 Bellflower Blvd.
                Long Beach, CA 90840

        Or, if you have access to BITNET, send to JAFW801@CALSTATE.
