[comp.protocols.kermit] Info-Kermit Digest V6 #26

SY.CHRISTINE@CU20B.COLUMBIA.EDU (Christine M Gianone) (12/12/87)

Info-Kermit Digest         Fri, 11 Dec 1987       Volume 6 : Number 26

Departments:

  ANNOUNCEMENTS -
        Japan DECUS, November 1987
        New Release of DEC-20 Kermit
        Latest Test Release of RMX86 & RMX286 Kermits
        OS-9 Kermit Available for Eltec Eurocom-3
        KERMIT File Protocol on COMPUSERVE
        Finally Kermit on Compuserve
        FTPing Files From Columbia
        Kermit Network File Organization

  UNIX KERMIT -
        RE: VMS 4.6 Bug Report with C-Kermit 4E(067)
        Re: Amiga Kermit
        C-Kermit on Apollo
        C-Kermit on Minix?

  Macintosh KERMIT -
        MacKermit with multilingual 7171
        [Andre PIRARD: MacKermit with multilingual 7171]
        Mac Kermit 0.8(35) on the Mac II
        MacKermit 0.9(36) Initial Impressions
        MacKermit 0.9(36) B3 Testing
        Macs, Versaterm and Kermit Errors

  MISCELLANY -
        IRMX86 Kermit -- I've found it!

----------------------------------------------------------------------

Date: Thu 10 Dec 87 09:40:03-EST
From: Frank da Cruz <SY.FDC@CU20B.COLUMBIA.EDU>
Subject: Japan DECUS, November 1987
Keywords: Japan DECUS, DECUS

Sorry for the long delay since the last Info-Kermit digest.  The week of
November 16, we were in Japan at the invitation of Japan DECUS to make
presentations at the 1987 Japan DECUS Symposium and at NTT, which was quite
an experience.

The DECUS presentations were accompanied by simultaneous translation into
Japanese, for which the attendees, usually about 80-100 per session, wore
special headsets, like at the UN.

Our first presentation was "Kermit, Current Status, Future Directions," in
which 30-minutes were devoted to Kermit history, philosophy, the mechanics
of Kermit development and distribution, and an overview of some of the new
and forthcoming Kermit releases; a brief technical talk was given on the
Kermit protocol performance enhancements (data compression, long packets,
sliding windows); and Ken-Ichiro Murakami of NTT, Japan's "Kermit-san",
spent some time speeking about special considerations for use of Kermit in
Japan -- versions for Japanese computers, use of and conversion among the
various Japanese character sets, Japanese translations of the Kermit
manuals, etc.  (Some of this session got written up in Nov 30 Digital News,
Page 10.)

A 3-hour "Fast-Paced Kermit" course was also conducted for about 40
students, consisting of 2 hours lecture and an hour of practice (using PCs
and a MicroVAX running VMS), with Japanese translation.

We were charmed by the hospitality and generosity of our hosts, and we were
pleasantly surprised at the high level of knowledge of, interest in, and
support for Kermit in Japan.

- Chris & Frank

------------------------------

Date: Fri 11 Dec 87 15:34:19-EST
From: Frank da Cruz <SY.FDC@CU20B.COLUMBIA.EDU>
Subject: New Release of DEC-20 Kermit
Keywords: DEC-20 Kermit

I never thought I'd touch this program again, but it contained a thoughtless
restriction, namely that it wouldn't let you issue commands to servers unless
you were in local mode (e.g. after dialing out through another line).  This
prevented you from putting a bunch of commands (multiple SENDs and/or GETs,
followed by FINISH) into a TAKE file, TAKing the file, escaping back to the PC
and putting it in server mode.  The new release, 4.2(260), removes this
restriction so long as the commands (like GET, FINISH, BYE) are issued from
TAKE files.  The old problem of inferior process capabilities not getting set
right, e.g. after a PUSH command, is also fixed.  The new version is in
KER:K20MIT.MAC on CU20B.  - Frank

------------------------------

Date: Tue, 01 Dec 87 10:52:47 PST
From: JAFW801%CALSTATE.BITNET@CUVMA.COLUMBIA.EDU  (Jack Bryans)
Subject: Latest Test Release of RMX86 & RMX286 Kermits
Keywords: RMX Kermit

The latest version mostly brings the RMX Kermits up to date with more recent
MS-Kermit sources.  The documentation (MSTRMX.DOC) has been edited to clarify
issues reported by users and to include information on obtaining Terminal
Support Code fixes from Intel for the ^W problem.

[Ed. - Thanks Jack!  The new files have replaced the old ones in
KER:MSTRMX.BOO, KER:MSTRX2.BOO, and KER:MSTRMX.DOC.]

------------------------------

Date: Mon 2 Nov 87 18:37:00-EST
From: Frank da Cruz <SY.FDC@CU20B.COLUMBIA.EDU>
Subject: OS-9 Kermit Available for Eltec Eurocom-3
Keywords: OS-9 Kermit, Eltec Eurocom-3

I got the following letter....                      21 October 1987

"I appreciate very much the idea of Kermit and I'm a happy user of OS-9
Kermit, VAX-Kermit-32, and the Kermit facility of Smarterm (MS-DOS).
Therefore I like to offer my knowledge and services to other people:

OS-9/68000 Kermit Implementation for ELTEC EUROCOM-3

Media: 5.25" DSDD 96tpi standard OS-9 diskette (others on request)
comprising source, executable object, user manual (including hints
for use of /t1) and actual info about Kermit and other implementations.

Order by prepayment of sFr. 30.- to post-office account 60-52873-4 or
with accompanying check or by charging to account (sFr. 50.-) from
Beat Brunner, Hinterherdschwand 30, 6020 Emmenbruecke, Switzerland.

Thanks for your services.

Sincerely yours,

Beat"  (No network address)

------------------------------

Date: Thu, 19 Nov 87 22:39:45 EST
From: "Joseph A. Bruno" <B562JB4G@VB.CC.CMU.EDU>
Subject: KERMIT File Protocol on COMPUSERVE
Keywords: CompuServe Kermit

When I logged onto COMPUSERVE today, the "what's new" messages informed me
that the KERMIT file transfer protocol is now supported.  I tried to
download a small file and it worked OK form me.  I am using KERMIT-11 on a
PDP-11 with the TSX+ operating system.  I think you should let other users
know about this through the news letter and ask for feedback when others try
it with different versions of KERMIT especially if they have problems.

------------------------------

Date: Sat 14 Nov 87 10:02:24-PST
From: Bob Larson <BLARSON@ECLA.USC.EDU>
Subject: Finally Kermit on Compuserve
Keywords: Compuserve Kermit

(Compuserve is probably the largest commercial bbs.)

Compuserve is now beta testing their implemintation of the kermit protocol
in the os9 sig.  (Presumably it is in their other sigs that do beta tests as
well.)

My understanding is it is a rather limited version that can only do single
file sends and receives.  Nobody has yet said if it supports full duplex
windows, long packets, or other optional features of kermit and I havn't yet
tested it.  (Compuserve charges extra for bad service, so it may be in no
rush...)

------------------------------

Date: Sun, 15 Nov 87 07:27:28 EST
From: eric@EDDIE.MIT.EDU (Eric Van Tassell)
Subject: FTPing Files From Columbia
Keywords: FTP

Hi,
	Are you trying to discourage ftp's? I have been trying for a month
to get VMS kermit to MIT and continually been amazed at the abyssimally low
transfer rates. What's up?

				eric@eddie.mit.edu

[Ed. - Apparently many people have been having problems FTPing files from
Columbia's computers.  Someone is checking on the problem.  Sorry for an
inconvenience.]

------------------------------

Date: Sun 8 Nov 87 02:22:45-PST
From: Jim Lewinson <a.Jiml@GSB-WHY.Stanford.EDU>
Subject: Kermit Network File Organization 
Keywords: Kermit Files

I am a little confused about the organization of the Kermit directories
on CU20B these days.

As far as I can see, there are two sets of directories, <KERMIT-n> n=2,3,4,5
which I assume are used for creating tapes, and
<KERMIT-EXTRA>, <KERMIT-BINARIES>, <KERMIT-TOOLS> (?) which I don't know what
they do any more.

Which of these sets of directories are still being maintained?  Which ones
are accessed when someone asks for a file by saying KER:file.ext to FTP?

If both are being maintained, would it be possible to get a AAFILx.DIR file
for each of them.  There currently seems to be an AAFILB.DIR file in
both <KERMIT-2> and <KERMIT-BINARIES>, but they are of drastically different
sizes.   (However, both seem to be recent.)

Sorry to be a bother about this, but I am trying to make sure that our local
set of directories are up to date so that people at Stanford can pull out
of them instead of putting any more load on CU20B.

							Jim

[Ed. - Apparently, this has been confusing for other users as well. All the
Kermit files can be found by using the logical name KER:, which will direct
the user to either KERMIT, KERMIT-2 ..... etc.  We'll try to make an effort
to keep AAFILx.DIR files in all these directories.]

------------------------------

Date: Tue, 10 Nov 87 14:44 CST
From: <MCGUIRE%GRIN2.BITNET@CUVMA.COLUMBIA.EDU>
Subject: RE: VMS 4.6 Bug Report with C-Kermit 4E(067)
Keywords: C-Kermit, VMS Kermit

> Date: 19 Oct 87 10:49:00 EDT
> From: "ETD1::LABOVITZ" <labovitz%etd1.decnet@afwal-aaa.arpa>
> Subject: VMS 4.6 Bug Report with C-Kermit 4E(067)
>
> I have just compiled the source modules for C-Kermit 4E(067) under VAX/VMS
> 4.6 on our VAX 11/785, using the supplied XMVKER.COM file.  During the
> final link of the KERMIT executable, the following warning message is
> produced by the linker:
>
>     %LINK-W-MULDEF, symbol SYSTEM multiply defined
>         in module C$UNIX file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;1
>
> While I have not had a chance to confirm this with our DEC Software Analyst
> (he's on vacation until next week), this seems to be directly attributable
> to the new VMS 4.6 C Run Time Library.
>
> [Ed. - Thanks for the report.  It's been forwarded to the new C-Kermit/VMS
> developer and added to the XKVKER.BWR file.  Since compilation and linking
> were tested with VAX-11 C 2.3 on VMS 4.6, and this problem didn't arise,
> the culprit is indeed most likely the runtime system.]

Was C-Kermit/VMS really tested under VMS V4.6?  Before VMS V4.6, there was
no `system' function in the VAX C runtime library.  Starting with VMS V4.6,
Digital provides a `system' function.  The error message basically
indicates that the linker was provided with two routines named `system'.
It sounds like the developer of C-Kermit/VMS implemented `system' in the
code, and that it now conflicts with the new V4.6 standard `system'.

It should be straightforward for VMS V4.6 users to remove the definition
of `system' from the C-Kermit/VMS code and recompile/relink.  Perhaps the
developer can find some nifty way to define `system' conditionally
depending upon which VMS version is being used.

Ed

------------------------------

Date: Wed, 11 Nov 1987 14:27:29 EST
From: John Owens <OWENSJ%VTVM1.BITNET@CUVMA.COLUMBIA.EDU>
Subject: Re: Amiga Kermit
Keywords: C-Kermit, AMiga Kermit

>I have obtained all the files identified in the file CKIAAA.HLP from the
>BITNET Kermit server.  I FTP'd these to a UNIX system and then downloaded them
>
>    they can send me?  I would prefer it be sent from a VM/CMS to a VM/CMS
>    system to be sure it does not undergo brain damage from ASCII/EBCDIC
>    conversion gremlins; remember it's a binary.
>
>[Ed. - The problem is probably ASCII/EBCDIC gremlins as you surmise.  No one
>else has complained so far, but then we have no way of knowing if anyone
>else has tried this yet!  Can anybody help?]

Typically, the ASCII/EBCDIC translation tables used by Kermit and FTP on your
VM/CMS system should match those used by your protocol converters, and, if
your system people are reasonably diligent, they probably do.  The problem
comes when you have an EBCDIC file that was originally ASCII and was converted
to EBCDIC using a different table.  The way I got around this problem for
Kermit BOO files was to use VM/CMS Kermit with no local translation table,
since its table matches that used at Columbia.  Our installation had
a SYSTEM KERMINI that changed the translation table, so I just created
a SYSTEM KERMINI A with one line: ECHO NULL KERMINI
then transferred the file with kermit.  If you must use FTP, you're
out of luck as far as I know, unless you want to give the UNIX dd
translation tables a shot:  use BINARY FTP mode, then say, on the UNIX
system, "dd if=ebcdic-file of=ascii-file conv=ascii".  Good luck!

        -John Owens
        Virginia Tech Communications Network Services
        OWENSJ@VTVM1.BITNET    owens@vtopus.cs.vt.edu
        +1 703 961 7827               john@xanth.UUCP

------------------------------

Date: Tue, 3 Nov 87 23:59:40 est
From: seung%husc8@harvard.harvard.edu (Seung)
Subject: C-Kermit on Apollo
Keywords: C-Kermit, Apollo Kermit

Has anyone tried running C-Kermit on an Apollo DOMAIN/IX system?  The
sources build OK when I type "make bsd" but Kermit gives various error
messages when I try to run it.  The most common ones are "Warning, problem
getting exclusive access," and "Warning, problem relinquishing exclusive
access."  I am working on an Apollo DN3000 running 4.2 BSD DOMAIN/IX SR9.6.
The version of C-Kermit is 4D(061).

Sebastian Seung

[Ed. - The problems you're seeing have to do with the UUCP lock files.
Since you're probably running a single-user system, you don't have to worry
about these anyway.  The messages are harmless.]

------------------------------

Date: Mon 9 Nov 87 10:35:12-EST
From: Frank da Cruz <SY.FDC@CU20B.COLUMBIA.EDU>
Subject: C-Kermit on Minix?
Keywords: C-Kermit

Has anyone tried C-Kermit (preferably version 4E(067)) on Andy Tanenbaum's
Minix (Unix v7) OS for the PC?

------------------------------

Date: Fri, 6 Nov 1987 12:38:30 ULG
From: Andre PIRARD <A-PIRARD%BLIULG11.BITNET@CUVMA.COLUMBIA.EDU>
Subject: MacKermit with multilingual 7171
Keywords: MacKermit, 7171, EBCDIC

This message describes problems to adapt MacKermit screen and keyboard
drivers, especially to international requirements in terminal mode.  I have
read that a revision of the keyboard handling is planned.  So, it must be the
right time to contact the right person about this.  Could you please forward
this message to him/them?  I am of course willing to discuss the problem and
carry out related tests needing a national keyboard.

We have settled our mind here (Belgium) to use Kermit micro to CMS mainframes
communication and file transfer.  This is done mainly through 7171's.

The new scheme I have worked out with John Chandler and the IBM-Kermit group
now allows to perform correct ASCII-EBCDIC conversion of the ISO multilingual
character set during files transfer.

In terminal mode, there is no way to have the 7171 use 8-bit data. I however
used a trick to support a limited set of the ISO covering our own nationals.
This works by having the micro send special escaped sequences for these codes.
The 7171 parses these sequences and works out the correct character.  On
return however, the 7171 cannot be instructed to send escape sequences, so I
used the control codes that were not used to another purpose. This is why the
terminal mode set is limited.

This requires some logic on the micro side. I have implemented it in our
traditional ftp, now converted to the Kermit protocol.

But here is the problem. Mac people use Mac Kermit (I neither feel able nor
eager to program the Mac, and MacKermit is fine the way it is).  But they're
crying out for their national characters in terminal mode.  The following two
facts prevent me to implement the above scheme:

- Escape characters received by the Mac terminal mode do not display at all.
  Is this the result of its own ANSI driver or an incomplete font?
  Some control over the display of the *complete* set of non-action characters
  is needed. Possibly by simply specifying a specially tailored font?
  Can this be done now?

- MacKermit keyboard driver is wonderful at building the required escaped
  sequences with appropriate setup. But using our national characters
  requires that some of them be composed by a succession of a dead key
  (bearing an accent) followed by the underlying letter. This composition is
  normally done by the appropriate (localized) keyboard interface layer wich
  I understand is bypassed by MacKermit.

  Using the standard keyboard interface (and still allow for codes conversion
  and escaping) would be simpler in terms of keyboard independence, but would
  restrict the keys combinations to those effectively used by the interface.
  I do not have enough insight of the Mac to propose a solution to this
  point, but I feel it should sound reasonable to suggest a compromise such as:
  Is is possible to have the MacKermit keyboard driver normally receive the
  keyboard codes through the full interface and however steal selected
  keystrokes at the hardware level when instructed to do so by the setup
  tables, with conversion possible at both levels?
  Or is there even a simpler solution?

  This would not only solve the problem, but also make the keyboard setup
  a much more simpler task (every new Mac I saw needed an adjustment).

I hope to help finding minor modifications that could enhance MacKermit.
I understand that not being able to carry on tests on unavailable hardware
is a problem. This is why I will be glad to help towards this.

Andre.

[Ed. - See message below.]

------------------------------

Date: Fri, 6 Nov 87 17:41:31 EST
From: paul@ohio-state.arpa (Paul W. Placeway)
Subject: [Andre PIRARD: MacKermit with multilingual 7171]
Keywords: MacKermit

At first glance, this looks like quite a problem.  According to what I have
read about the new Apple keyboard mapping standards, It shouldn't be a problem
to define any key to produce any sequence (of up to 255 chars, I believe)
8-bit sequence, or use any key as a deadkey for a following one (<Option-e o>
for example).  The other advantage is that it allows an abstraction away from
the hardware level, so that the same map will do the "right things" for a Mac
512 keyboard, and also recognize and deal with the control key on the IIgs and
the "USS Serritoga" keyboards.

One of my goals for the display code is to be able to display an 8 bit wide
character set, so that people who don't happen to speak only American English
(the majority, of course) can have extended character sets.  Fortunately,
Apple is very aware of the "language barrier", and has a system designed to
deal with it.

In other words, it isn't a problem, and I will keep this in mind when working
on the Mac stuff.

       -- Paul W. Placeway		    Dept. of Computer & Info. Science
(now)  paul@ohio-state.arpa		    2036 Neil Avenue Mall
(soon) paul@tut.cis.ohio-state.edu	    Columbus, OH 43210-1277
(in a pinch) ...!cbosgd!osu-cis!tut!paul    (614) 292-0915

------------------------------

Date: Mon, 9 Nov 1987 17:12:01 ULG
From: Andre PIRARD <A-PIRARD%BLIULG11.BITNET@CUVMA.COLUMBIA.EDU>
Subject: Mac Kermit 0.8(35) on the Mac II
Keywords: MacKermit

I have downloaded MacKermit 0.8(35) on a Mac II (and adjusted the keyboard
table using 0.8(6) on an SE). It performs great for what I have tried
(terminal mode and file transfer with VM CMS).

But I happened to QUIT it and enter MacWrite while my CMS session was still
active. After a while, the system bombed in my back, while completely idle.
Suspecting comm line interrupts, I restarted the system and Kermit. A message
appeared on the refreshed screen indeed. I quit again and sent my session yet
a message. The system bombed again after some mouse clicks. This happened
several times with varying interval between message and the time the crash
occurs.  Everything looks like the line interrupts are kept enabled to nowhere
code.  This happened with System 4.1 (french) and Finder 5.5 on an SE or
Multifinder 6.0B2 ona a II. I could not reproduce it with 0.8(34) (on the SE
of course).

------------------------------

Date: Mon, 9 Nov 87 22:26:33 CST
From: brian@sally.utexas.edu (Brian H. Powell)
Subject: MacKermit 0.9(36) Initial Impressions
Keywords: MacKermit

Regarding:

>Date: Thu, 29 Oct 87 17:07:50 PST
>From: dplatt@teknowledge-vaxc.arpa (Dave Platt)
>Subject: Initial Impressions of Mac Kermit 0.9(36)

>2) I wasn't able to figure out how remap a key so that it would send a
>   Break.
     Enter \bs (short break) or \bl (long break).  This is explained if you
click "help" in the "Set key macros..." dialog.

>4) The screen image is not restored properly after a dialog box is
>   erased (e.g. after a download, or after changing the settings).
     I find this to be a pretty common happening, and it needs to be fixed
soon.

     I don't know if you're really soliciting BeWaRes or not for this version
of MacKermit, but here are some, all regarding MacKermit 0.9(36).

     Other problems I have found:
* I'm unable to set command-spacebar to NUL.  It keeps wanting to set it to
  "\177" when I try to set it to "\0".
* The meta-key option (for the option key) is not available.  I want my
  meta-key back, so I'll probably dump this version of kermit and go back to my
  other terminal program (uw) and the old kermit.  The old ckmkey could set
  modifier keys to act as meta-keys.  (I want a real meta-key, not just one
  that prefixes with ESC.)  Actually, if you fiddle around with "Set key
  macros...", it's possible to set some meta-key combinations explicitly.  I
  haven't gotten it to behave rationally, yet, but there are possibilities
  there.  One also runs into the old problem of dead-keys.  (e.g., you have to
  press option-e twice to get it to register.)  There are ways to work around
  dead keys.
* In the "set modifiers" dialog, if I choose to make both control and clover
  act as a control key, only the control key really acts like a control key.
  clover-b, for instance, sends a 'b'.  This forces me to "Set key macros..."
  for each clover-key.  (Which is how I found out that cmd-spacebar can't be
  set to NUL (above).)  I'm not sure if this is a bug in the code or a bug in
  the dialog box for letting me choose both modifiers at the same time.
* (An oldy but a goody) I like it when the (mouse) cursor disappears when I
  start typing.  (Using ObscureCursor in QuickDraw.)  I wish kermit did this.
* When "Menu Clover-keys active" is turned off, I'd like the clover-keys to
  disappear from the menu.  It's too confusing to an unready user to see those
  cmd-equivalents listed in the menu but semantically disabled.
* In certain instances, things I type to the "Set key macros..." dialog get
  sent to the host as well.  This can be duplicated by choosing "Set key
  macros..." and typing option-`.  Click OK twice and type something (say 'f').
  The host echoes `f.

     I look forward to the real MacKermit.

Brian H. Powell
		UUCP:	...!uunet!ut-sally!brian
		ARPA:	brian@sally.UTEXAS.EDU

   _Work_					 _Not Work_
  Department of Computer Sciences		P.O. Box 5899
  Taylor Hall 2.124				Austin, TX 78763-5899
  The University of Texas at Austin		(512) 346-0835
  Austin, TX 78712-1188
  (512) 471-9536

------------------------------

Date: Tue 1 Dec 87 00:48:18-PST
From: Jim Lewinson <a.Jiml@GSB-WHY.Stanford.EDU>
Subject: MacKermit 0.9(36) B3 Testing
Keywords: MacKermit

I grabbed a copy of this from CU20B to try it out, and I still can't get the
Keyboard stuff to do what it used to do for me.  The OPTION key used to
ONLY insert an ESCAPE in front of the keystroke, and make no other changes.

Pressed			What I want		What IS
			   Sent			  Sent
OPTION d		ESC d			ESC d
OPTION SHIFT D		ESC D			ESC D  (Not too important)
OPTION SHIFT .		ESC >			ESC .  (IMPORTANT)

I use the latter keystrokes all the time to get to the end of a file.  I
suspect other people may use OPTION SHIFT 4 to get the EMACS spell checker.
(In fact, I might start using this, now that I think of it.)  I suspect I
may also use OPTION SHIFT 3 for Query-Replace, but not often enough to
notice it.

If I had to give up a feature to get this, I would get rid of the concept
of Modified/Unmodified.  Kermit is generally used to talk to other machines
in 7 bit ASCII.  The ability to send a E with an accent grave on it sounds
really neat, but isn't very useful when you get down to it.

I wouldn't worry too much about trying to get the window postion of the new
settings file right.  After all, you did write a new file, and this is
something that I do very very rarely.  Usually, it is just to create a new
version for a different speed or something similar, so I usually create a
new file anyway.

I tried to use the long packets, but the Unix machine I was trying to use
only has a short packet Kermit on it.  I thought I grabbed a new
long-packet one, but I guess I got the wrong one.

I did use 0.9(36) B2 to transfer B3 down, and it seemed to do a fine job,
except it transfered the files I told it to, not the ones I wanted.  :-)
I guess a little more DWIM is needed in that department.  (Or maybe a little
less DIMWitted behaviour on my part. :-) )

						Jim

------------------------------

Date: Tue, 10 Nov 87 09:07 GMT
From: OBSchou@UK.AC.LOUGHBOROUGH.MULTICS 11-NOV-1987 11:11
Via: SYSKERMIT%vax1.central.lancaster.ac.uk@NSS.Cs.Ucl.AC.UK
Subject: Macs, Versaterm and Kermit Errors
Keywords: MacKermit, Versaterm

We have been using both the "formal" Mac Kermit based on "C" kermit and a
terminal emulator/file transfer packaged called Versaterm at Loughborough with
mixed success. 

We selected Versaterm as the suggested terminal emulator and file transfer
program over the distributed Mac Kermit for two reasons: terminal emulation was
far better, and could also "do" Tektronix emulation, and more importantly,
appeared to be more reliable in Kermit transfers than Mac Kermit. 

However, we have had a rash of file transfer problems, resulting in truely
garbled data at the Mac end.  (Early bits of the file keep appearing thoughout
the file, not all the file is available even though the transfer says it has
completed, etc.)  Closer investigation showed an unusual bug in Multics
(Amaranth) Kermit.  We FTP-ed the files to a VAX and again tried to transfer
the files to the Mac, with similar results.  It therefore seems as if Versaterm
is not a good as it is made out to be. 

Has anyone else used Versaterm and had problems, and better still come up with
som work-arounds? 

In anticipation, Bertil Schou.

------------------------------

Date: Wed, 28 Oct 87 17:08:23 EST
From: dfs@nadc.arpa (N. Topping)
Subject: iRMX86 Kermit -- I've found it!
Keywords: RMX Kermit

About a month ago I made an appeal for information on Kermit for iRMX86.
Apparently there was some discussion, confusion and advice generated by this
request.  I say "apparently" because I did not personally read any messages
since I do not subscribe to this mailing list.  As a nonsubscriber, I asked
that responses be mailed directly to me (dfs@nadc).  However I received only
one direct response from Jack Bryans (Thanks!) and he alluded to these
kermit-digest discussions.

I am posting this message to inform the Kermit community that I have finally
located a version of iRMX86 Kermit that works.  I found the name of Larry Grim
of Mesh Inc. in the "aawait.hlp" file.  I contacted Larry and he graciously
provided the Kermit source code (ASM86) and documentation.  Larry's iRMX86
version of Kermit was developed for an Intel 86/310 sometime in 1985.  He
developed this iRMX86 Kermit by converting the IBM PC DOS version of Kermit.
The conversion effort was sponsored by the Dupont Corporation.

Since Larry does not have network access to the Kermit repository, I promised
him that I would inform the Kermit community of his accomplishment and
volunteer to mail his Kermit source and documentation to the Kermit
repository.  If the keepers of Kermit are interested in obtaining this version
of Kermit, please let me know (by direct response, please!) where to mail it.

All credit and questions regarding this version of KERMIT should be referred
to:

	Larry Grim
	Mesh, Inc.
	2802 Bethel Rd.
	Oxford, PA
	215-932-3709

Sincerely,
(dfs@nadc)
Michael Lipczynski
Veda, Inc.
Warminster PA.
215-672-3200

P.S. We assembled and linked iRMX86 Kermit (with no modifications!!) on a OEM
system that contains an Intel 8026.  We have not had any problems so far.

[Ed. - We seem to have no end of Kermits for Intel iRMX and MDS systems, and
so far have little idea which to keep and which to throw out.  For (i)RMX,
we have the ones with prefixes RMX, IRM, and I86, plus Jack Bryan's new
version based on MS-Kermit 2.29C (MSTRM*), and for MDS systems we have the
MDS programs and the MD2 ones.  Comparative reviews would be appreciated.
Meanwhile, you might want to coordinate with Jack Bryans about whether the
iRMX Kermit you've described should be added to maze at Columbia, or maybe
Jack's version will make it unnecessary.]

------------------------------

End of Info-Kermit Digest
*************************
-------