Date: Sun, 9 Feb 92 23:49:12 EST
From: ALF::MOOREB@icd.ab.com
      (Bruce Moore x3631--Blue Hell--Home of the Blue Devils)
To: fdc@watsun.cc.columbia.edu
Subject: Atari ST C-Kermit Status

> For purposes of credit, do you want to be identified with an organization,
> listed with a title, etc?

Bruce Moore, Software Project Engineer, Allen-Bradley Co.  I don't care if you
use the title or not.  Do what you think is best.  But my organization should
be identified; although the work was done on my own machine I wouldn't have
had access to the net without them.

> Also, at some point I'd like to get some info about the Atari environment:
> the file system, syntax of device names, directory structure and names ...

o       The file system is 99 44/100 % identical to MS-DOS.  An Atari ST can
        read/write a DOS formatted disk, but not vice-versa.

o       The port was done using the Mark Williams C package.  Shell stuff
        only works when kermit is run from their msh shell or from the
        public domain shell, gulam.

o       The init file ckermit.ini is searched for in the current directory,
        the $HOME directory, and finally in the root directory of the
        current drive.

I went down the "UNIX Kermit Capabilities At A Glance" list and checked each
one.  Deficiencies are as follows:

        o Remote operation is untested (might work).
        o International text may work if sources are rebuilt.
        o Automatic parity detection does not work (parity ignored).
        o IBM mainframe connections are untested (don't have any handy).
        o No dialout modem support.
        o No network support.
        o Act as server is a bit strange (more below).
        o No UUCP script support.

I also tried all the commands listed in the documentation.  Besides the
obvious ones for which no support is present, deficiencies are as follows:

        o CLEAR command is a no-operation.
        o PUSH does not work (but spawning a single command does).

C-Kermit ST does act a server.  One must SET SERVER DISPLAY ON, and SET SERVER
TIMEOUT.  If this is not done, then one cannot abort the server.  An idle
server can only be aborted when a timeout occurs. This means if the server is
set to 15 seconds, one may have to wait as long as 15 seconds before the
control-C is detected.  Exiting the program is recommended after a control-C
from an idle server.

I'll try to get to edit 179 in the next few days.

Bruce