Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!dayton!umn-cs!ndsuvax!ncreed
From: ncreed@ndsuvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Using VT100/KERMIT and IBM systems
Message-ID: <372@ndsuvax.UUCP>
Date: Tue, 14-Apr-87 08:05:38 EST
Article-I.D.: ndsuvax.372
Posted: Tue Apr 14 08:05:38 1987
Date-Received: Thu, 16-Apr-87 00:32:04 EST
References: <9241@decwrl.DEC.COM> <823@xanth.UUCP>
Reply-To: ncreed@ndsuvax.UUCP (Walter Reed)
Organization: North Dakota State University  Fargo, ND
Lines: 22
Keywords: kermit IBM amiga
Summary: The fix for C-Kermit


The reason that C-kermit on the amiga doesn't work with the IBM, is because
the parity is not set!  I got my version of C-Kermit from kermserv@cuvma
on BITNET, and it still contains this bug.  In the CKICON.C module, look
in the connect mode function.  In about the middle of it, there is a call
to the output a character function ttocq(c).  This needs to be changed to
ttocq(dopar(c)).  There! It now works with IBM and sets parity correctly.
According to the comments in the code, Kermit does its own parity checking
and the serial.device is always in 8 bit no parity.  I always use kermit on
the mainframe and the vax.  One thing you will notice is that the standard
amiga keymap does not generate codes to be compatible with anything!  I am
in the process of writing a keymap module for amiga c-kermit to make it look
like a vt100.   Good luck!
-----Walter Reed



-----------------------
UUCP :  ihnp4!umn-cs!ndsuvax!ncreed
Bitnet: ncreed@ndsuvax  OR NU105451@NDSUVM1
Walter Reed
----------------------