Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!feg
From: feg@clyde.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Experiences with Crosstalk
Message-ID: <10308@clyde.ATT.COM>
Date: Wed, 17-Jun-87 11:22:11 EDT
Article-I.D.: clyde.10308
Posted: Wed Jun 17 11:22:11 1987
Date-Received: Thu, 18-Jun-87 05:33:50 EDT
References: <1808@zeus.TEK.COM> <3314@islenet.UUCP>
Organization: AT&T Bell Labs, Whippany, NJ
Lines: 38
Summary: Procomm has problems

In article <3314@islenet.UUCP>, jons@islenet.UUCP (Jonathan Spangler) writes:
> In article <1808@zeus.TEK.COM> bobr@zeus.UUCP (Robert Reed) writes:
> >Has anyone had any experience with sending files using Crosstalk (sorry, I
> >don't know what version, but I bought it last December)?  I have a Compaq
> 
> You're going to love this. My experience with Crosstalk is: PROCOMM!
> 
> Get it.
> 
> Aloha,
> 
> Jonathan Spangler
> {ihnp4,vortex,dual}!islenet!jons
> 	OR
> jons@islenet.hawaii.edu
> -- 
> Jonathan Spangler
> {ihnp4,vortex,dual}!islenet!jons
> 	OR
> jons@islenet.hawaii.edu

Procomm on a color crt is very pretty.  It has lots of bells and
whistles, the latter literally, but unless I have it improperly
configured, it is unable to recover from a timeout error while
receiving using xmodem.  After a timeout it hesitates several
seconds, then successively racks up transmission errors until
some internal count is reached and aborts.  Then it fails to
to tell the sender what it has done, so the sender spews your
screen with garbage.  Hitting cntl x enough times will finally
stop the sender if you are lucky.  QMODEM, in xmodem receive
always recovers from a timeout error.  After approximately
30 seconds, the sender will resend the block, and if
successfully received, the session will continue.  Procomm's
aborting in the 19th minute of a 20 minute transmission can
be frustrating.  Is there a solution to this, besides
sticking with Qmodem?
               
Forrest Gehrke