Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site occrsh.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!okstate.UUCP!occrsh.UUCP!rct
From: rct@occrsh.UUCP
Newsgroups: net.micro.pc
Subject: Re: XTALK 3.6 and Kermit
Message-ID: <3000001@occrsh.UUCP>
Date: Sun, 8-Dec-85 12:19:00 EST
Article-I.D.: occrsh.3000001
Posted: Sun Dec  8 12:19:00 1985
Date-Received: Wed, 11-Dec-85 04:27:55 EST
References: <1412@sphinx.UChicago.UUCP>
Lines: 25
Nf-ID: #R:sphinx.UChicago.UUCP:1412:occrsh.UUCP:3000001:000:1365
Nf-From: occrsh.UUCP!rct    Dec  8 11:19:00 1985


/* Written 12:58 pm  Dec  3, 1985 by cjdb@sphinx.UChicago.UUCP in occrsh.UUCP:net.micro.pc */
/* ---------- "XTALK 3.6 and Kermit" ---------- */

XTALK version 3.6 is supposed to support Kermit. I've tried it with a
Kermit server on a DEC-20 without success. The XTALK support people say
they've tried it (on another mainframe) with success. Does anyone have
any ideas as to where I might start looking for the problem? (Let me
add that I have been using version 2.0 of MS-DOS Kermit on an IBM PC to
talk to Kermit on the same DEC-20 without any problem at all.)
/* End of text from occrsh.UUCP:net.micro.pc */

Getting one Kermit to talk to another on different machines is sometimes
a pretty sticky proposition due to what the involved hardware does with
the eighth bit.  You might try fiddling with the parity settings on both
ends.  The default "PARITY=none" doesn't make it for many of the machine
combinations we've tried it on here at OKC.  When nothing else seemed to
work, "PARITY=mark" usually did.  Forcing the software to do something
with the 8th bit is generally a good idea, because you normally can't
make any assumptions about what the hardware is going to do with it.
DISCLAIMER: I haven't tried XTALK version 3.6, so I can't say whether
this will help or not.

--Bob Tracy				AT&T Network Systems
...!ihnp4!okc_5b!occrsh!rct		Oklahoma City Works