Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site uiucuxc
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!uiucuxc!hamilton
From: hamilton@uiucuxc.CSO.UIUC.EDU
Newsgroups: net.dcom
Subject: Re: XON/XOFF Deadlock between vt100 and
Message-ID: <11200004@uiucuxc>
Date: Sat, 11-Jan-86 16:46:00 EST
Article-I.D.: uiucuxc.11200004
Posted: Sat Jan 11 16:46:00 1986
Date-Received: Fri, 17-Jan-86 02:39:08 EST
References: <892@rlgvax.UUCP>
Lines: 14
Nf-ID: #R:rlgvax.UUCP:892:uiucuxc:11200004:000:599
Nf-From: uiucuxc.CSO.UIUC.EDU!hamilton    Jan 11 15:46:00 1986


>Kermit XON/XOFF Deadlock Bug Caused by Hayes Command Echo Enabled
>...Best solution: Disable Hayes echoing during command mode, and
>this problem cannot occur.

better solution: don't type ^S when talking from a vt100.
seriously, disabling echo is pretty drastic, and perhaps
more important, is insufficient.  what happens if you get
a line hit that looks like a ^S?  or you accidently cat
a binary file that contains a ^S byte? if you really want
to make this (~)impossible, modify kermit (and tip, etc) to
not send ^S's to terminals (possibly only vt100's).

best solution: get rid of the vt100.