Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!julius.cs.uiuc.edu!wuarchive!psuvax1!psuvm!art100
From: ART100@psuvm.psu.edu (Andy Tefft)
Newsgroups: comp.sys.apple2
Subject: Re: Proterm 2.2 problems
Message-ID: <90275.233317ART100@psuvm.psu.edu>
Date: 3 Oct 90 03:33:17 GMT
References: <1990Oct2.210457.23936@uokmax.ecn.uoknor.edu>
Distribution: usa
Organization: Penn State University
Lines: 21

In article <1990Oct2.210457.23936@uokmax.ecn.uoknor.edu>,
jstraigl@uokmax.ecn.uoknor.edu (Jeffrey S Traigle) says:
>
>3. The Kermit protocol doesn't work at all. When trying to receive, I
>   get "Data Timeout" errors and have to abort the transfer. When trying to
>   send, I get "Block Timeout" and "Ack Failure" until it reaches the
>   maximum number of consecutive errors and aborts the transfer.

Before you blame this on Proterm, make sure the parity is set
the same on both ends of your connection. Set the parity
from within kermit on the remote end to whatever you have
it set at in proterm. Set both ends to even parity, since
there might be a terminal controller somewhere that is changing
the parity that you don't know about. It took me a while to figure
this out using Kermit 3.86. I call up a data switch that takes
any parity but talks to the mainframe with even parity, so the
remote kermit wanted to talk even parity and my apple wanted to
talk no parity.

If you still get timeouts, then blame proterm :-) even though
it might be something else.