23-Sep-84 21:59:07-EDT,2807;000000000011
Return-Path: <@COLUMBIA-20.ARPA:CONTEXT@WASHINGTON.ARPA>
Received: from COLUMBIA-20.ARPA by CU20B.ARPA with TCP; Sun 23 Sep 84 21:59:05-EDT
Received: from WASHINGTON.ARPA by COLUMBIA-20.ARPA with TCP; Sun 23 Sep 84 21:58:38-EDT
Date: Sun 23 Sep 84 18:57:32-PDT
From: Ronald Blanford <CONTEXT@WASHINGTON.ARPA>
Subject: 86kermit
To: cc.fdc%cu20b@COLUMBIA-20.ARPA

Frank,

Here is an updated change list for 86kermit.  The files are all loaded
on my account and ready to ftp.  The source files are 86*.* and the
object files in APCKERMIT.H86 and APCKERMIT.CMD.

I didn't hear anything from Jeff or Bernie, but it seems as though the
changes you mentioned were all to the system-dependent code for the
Rainbow, which I wouldn't be able to test anyway.  I'll let you or whoever
add that at your leisure.

The current defaults of drive and user number are now displayed in the
command line prompt, as for example:
	Kermit-86 B3>

The SET DEFAULT-DISK option has been implemented to allow specification
of the default drive and user number for subsequent file reception and
transmission.  The specification following the command must be in one
of the following forms:
	d:	= go to drive d (A through P) without changing user
	u:	= go to user u (0 through 15) without changing drive
	du:	= go to drive d and user u
	:	= go to the defaults when Kermit was loaded
Whenever a drive is specified, even if it is the same as the current
default drive, the drive is logged in so that disks can be swapped
without exiting Kermit to type control-C.  Kermit restores the original
drive and user upon termination.

Local DIRECTORY and SPACE commands have been added to show the files
present and the remaining space available on disk.  The DIRECTORY command
matches wildcard filenames within the current default user number, while
both commands allow a drive specifier for action with other than the
default drive.  

The other change corrects a problem that was discovered some time ago,
that is, that when the RECEIVE command was followed by the optional
filename, it was interpreted as a server command equivalent to the
GET FILENAME command.  Of course the proper interpretation as implemented
by this change is that the RECEIVE occur in non-server mode, and
to save the file under the given filename rather than the one received
from the foreign host.  If the filename is wild, it is used as a mask
where the wildcard characters are replaced by the corresponding characters
in the actual filename received, so that this option can be used even with
wildcard sends.  Since it is legal to have a drive specification (with or
without the remainder of the filename), this also allows files to be
received to a disk other than the current default drive.

-- Ron
-------