Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!think!nike!ucbcad!ucbvax!YALE.ARPA!ram-ashwin
From: ram-ashwin@YALE.ARPA (Ashwin Ram)
Newsgroups: net.micro.atari16
Subject: UniTerm
Message-ID: <8610180211.AA04061@yale-celray.YALE.ARPA>
Date: Fri, 17-Oct-86 22:11:35 EDT
Article-I.D.: yale-cel.8610180211.AA04061
Posted: Fri Oct 17 22:11:35 1986
Date-Received: Tue, 21-Oct-86 08:06:25 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 45


The latest posting of UniTerm works fine -- thanx a lot, Simon.  I also  like
the ARC program; it makes downloading easier since the files are (a) collated
into one file, and (b) compressed.

I have a question about a weird bug(?) that seems related to UniTerm.  When I
use UniTerm to connect to a remote machine, I can't use Kermit to Send  files
from my Atari to the remote machine.  I can Get files all right,  and  I  can
Send files using the same Kermit if I use any other terminal  emulator.   But
if I've used UniTerm in a particular session, then  even  if  I  use  another
emulator without resetting the Atari, this bug appears.  What happens is that
somewhere between 1500 and 2000 bytes of  the  file  get  sent,  after  which
Kermit hangs and eventually times out.  I can see it  sending  some  sort  of
signal periodically, but the remote Kermit doesn't seem to respond, not  even
to a Quit request.  The only way to kill the remote Kermit is to  connect  to
the remote machine, hit a control-Q (upon which I get several error  messages
from the remote Kermit), undo back to my Kermit, try Quit again (resulting in
an "unexpected packet type" message), and finally do Quit again (which brings
everything back to normal).  This always happens if (and only if) I have used
UniTerm to connect to any remote machine before using Kermit.

However, I can use UniTerm to do everything  else,  such  as  run  a  display
editor on the remote machine, and even Get files using Kermit; it's only Send
that dies.

I suspect what is happening is that UniTerm is redefining some obscure  RS232
parameter that no-one else cares about, or perhaps it is redefining something
that causes a particular control character to get  swallowed  up  or  changed
(the character being one that Kermit in one of its protocol sequences).   The
effect of whatever UniTerm is doing lasts even after it has been exited.

I don't know enough about UniTerm or Kermit's protocols  to  figure  out  why
this is happening.  If anyone has any suggestions, please mail  them  to  me.
So far I've been using the Emulator accessory to transfer files  and  UniTerm
for everything else, and I would love to get this straightened out so that  I
can use UniTerm and nothing but.

Thanx a lot -- Ashwin Ram.

ARPA:    Ram-Ashwin@yale
UUCP:    {decvax,linus,seismo}!yale!Ram-Ashwin
BITNET:  Ram@yalecs

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