          Columbia University Macintosh Kermit Prerelease #1

                            April 25, 1985

This document describes briefly how to operate the preliminary release
of MacKermit v 0.6(1).  This, in conjunction with the beware file
(ckmker.bwr), should get you over any rough spots.  The most important
fact to be aware of is that this is a prelimary version.  Feel free to
pass it on to anyone, but don't expect this version to be "supported".
Please send any bug reports and suggestions to Info-Kermit@CU20B.  Be
very specific in your reports, as vague "MacKermit doesn't work" comments
are of little help.  Have fun and down with MacTerminal!


			      Installation

There are a number of different ways and levels of installing MacKermit.
The simplest way is to just use MacPut to download the file ckmker.rsrc.
After doing this you must use SetFile on the Mac to set the author to
KERM, the type to APPL and turn on the bundle bit.  You can instead
download the binhexed version (ckmker.hcx), run binhex on the downloaded
file and then follow the SetFile procedure.

The final, and most involved, way is to use SUMacC C to compile and link
MacKermit.  Then download MacKermit as before using MacPut.  In order to
use SUMacC the following addition may be necessary to the file h.h in
the IO library:

| Edit by Bill on Apr 23, 1985.  Add toolequ.h for appfiles.s, same reason
| Edit by Bill on Apr 12, 1985.  Add syserr and prequ for ser.s, it
| doesn't link otherwise.

	.insrt	"../../h/toolequ.h"
	.insrt	"../../h/toolmacs.h"
	.insrt	"../../h/sysequ.h"
	.insrt	"../../h/syserr.h"
	.insrt	"../../h/prequ.h"


			    Using MacKermit

If you are already familiar with Kermit then you should have very little
difficulty using MacKermit.  If you are not familiar with Kermit then
read to Kermit User Guide to understand how Kermit works.  The main
difference between MacKermit and other versions of Kermit is that in
MacKermit you are always connected via a terminal emulator (VT102).  You
run Kermit on the host via this emulator and then issue Kermit commands
by means of pull-down menus.

The file transfer commands are under the File menu and some remote host
commands are available under the Remote menu.  In order to see the
responses to the remote commands you must pull down Show Response in the
Remote menu.  You can specify which fork (data or resource) of a file
the file transfer uses.  The default is data unless when receiving a
file the file has an extension of ".rsrc" in which case it is put in the
resource fork.

Any Kermit protocol transaction, file transfer or remote commands, can
be cancelled by typing Command-. during the operation.  It may take a
few seconds for this to take effect, but you will be asked whether you
really meant to cancel the transaction.

You can change both communications and protocol values by using the
Settings pull-down menu.  You can save and restore these settings by
invoking the appropriate selection in the File menu.  If the bundle bit
has been correctly set on your version of MacKermit you can double-click
on the resulting document to start MacKermit with those settings.

The terminal emulator sends escape when the "`" key is pressed
unshifted.  The character "`" can be sent by type control (command) and
the same key.  The backspace key sends a delete and control backspace
sends a backspace.  The Enter key sends a BREAK (a real 275 msec BREAK).

One problem often encountered in transmitting files is that it is often
necessary to give a command similar to "set file type binary" to the
host computer.  This is always needed when sending resource files and
possibly at other times as well.


			      Limitations

The following comments concern limitations and possible problems that
may be encountered in the present version of MacKermit. 

    There is no line terminator (CRLF) translation available at present.
    This may cause problems trying to use MacWrite files.

    Receive does not allow receive as or explicit resource/data fork
    selection. 

    You can not receive both a data and a resource fork into a single
    file.

    The terminal emulator does not use XON/XOFF and can begin to lose
    characters after a few screens worth of continuous output.

    If parity other than "none" is set any incoming character that does
    not match that parity is discarded.  As some systems require parity
    but then do not themselves use it correctly this may cause some
    problems.

    There is no way to either scroll back the screen or to save lines
    off the top.


