Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!princeton!allegra!ulysses!mhuxr!mhuxt!houxm!hjuxa!petsd!fredc
From: fredc@petsd.UUCP (Fred Cassirer)
Newsgroups: net.micro.amiga
Subject: RE:RE: VT100 and Kermit
Message-ID: <856@petsd.UUCP>
Date: Thu, 23-Oct-86 22:33:30 EDT
Article-I.D.: petsd.856
Posted: Thu Oct 23 22:33:30 1986
Date-Received: Fri, 24-Oct-86 16:10:31 EDT
Organization: Perkin-Elmer DSG, Tinton Falls, N.J.
Lines: 56

>Article 5307 of net.micro.amiga:
>Relay-Version: version B 2.10.1 6/24/83; site petsd.UUCP
>Path: petsd!hjuxa!houxm!mhuxt!mhuxr!ulysses!bellcore!petrus!scherzo!allegra!mit-eddie!think!rutgers!sri-spam!sri-unix!hplabs!oliveb!glacier!labrea!navajo!rokicki
>From: rokicki@navajo.STANFORD.EDU (Tomas Rokicki)
>Newsgroups: net.micro.amiga
>Subject: Re: VT100 and Kermit
>Message-ID: <981@navajo.STANFORD.EDU>
>Date: Mon, 20-Oct-86 00:00:35 EDT
>Date-Received: Tue, 21-Oct-86 20:33:58 EDT
>References: <851@petsd.UUCP>
>Organization: Stanford University
>Lines: 14
>Summary: me too
>
>In article <851@petsd.UUCP>, fredc@petsd.UUCP (Fred Cassirer) writes:
>> Help.  I'm using DBW's VT100 terminal program and cannot get the kermit
>> to work.
>
>I can't get it to work either.  The C-Kermit supplied on the fish
>disks works fine, but the Kermit built in does not.  No packets
>are getting transferred at all, so I suspect a checksum problem;
>handshaking shouldn't even be required for the first packet.
>I've even tried 300 baud just to be safe; still no go.
>
>I would be more than willing to help find the problem if someone
>would point me in the right direction . . .
>
>-tom "sign me up for Dave's fan club" rokicki
>
>
First let me say thanx for the feedback, now I'm sure that my postings get
mailed to someplace besides dev/null.  

Since the posting I have gotten C-Kermit and DBW's vt100 kermit to work 
fine.  As soon as I got a direct connect line to my host everything flew.
As I suspected, the XON/XOFF that Kermit(s) is usin' was getting
swallowed by the system switch box (nts).  Nts is basically a port selector
that can buffer between different speed lines.  What happens is nts will
generate a ^S/^Q when buffering between say 9600 baud and a 1200 baud 
line.  This normally works fine, but when kermit generates one, and nts
has just issued the same one, the second one gets lost (same as doing
a ^S ^S on most systems, 1st one stops I/O, 2nd one is tossed by the 
driver).  Nts turns around and does a ^Q which starts the remote kermit
sending while the other kermit isn't listenin'.  

So the morale of the story is:  If your using a similar switch and having
trouble with your kermit(s) this could be your problem, it was mine.

While I'm here let me just say I've been using the vt100 program since
the 1st version have found very few problems with it.  I even use the
48 line interlaced feature now and then with no problems. 
    
                         Good Stuff Dave! (Got any more images?)


                                          Fred Cassirer (Fredc)