Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!rutgers!iuvax!bobmon
From: bobmon@iuvax.cs.indiana.edu (RAMontante)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DSZ downloads
Message-ID: <8036@iuvax.cs.indiana.edu>
Date: 20 Apr 88 06:31:48 GMT
References: <6208@swan.ulowell.edu> <1922@bgsuvax.UUCP>
Reply-To: bobmon@iuvax.UUCP (RAMontante)
Organization: Computer Science Dept., Indiana University
Lines: 23

boneill@hawk.ulowell.edu (SoftXc Coordinator) writes:
.> 
.> When using sz on our Dynix system, and DSZ (2-08 was the last one I tried)
.> on my PC running at 2400 baud, and I download a binary file, I get many CRC
.> fail errors, some timeout errors, and bad data errors every 8K or so. This
.> tends to slow down the progress of the download, especially when enough
.> errors arise to cause it to switch to 256 byte packets. Sometimes it even
.> aborts the download.

I just tried DSZ0414 the other day, connecting to an 8800/Ultrix machine.
When I go in through a directly-attached modem, dsz works extremely well.
(But through this modem, Procomm can use ymodem and do about as well as dsz.)
When I login to the same machine, through a modem onto a campus-wide network
called the Sytek cable, dsz shows the same poor performance that boneill
describes -- a file transfer that was estimated at 12 minutes took over 75
minutes! -- but Procomm is completely unable to establish a ymodem handshake,
much less any transfer.  I know little about the Sytek cable (Sytek is a
brand name), but I do know that it thinks it's 8-bit and it processes some
characters including ctrl-S and ctrl-Q.  I'm kind of impressed that dsz got
a binary through at all, in light of the performance degradation.  (Kermit
works okay for text transfers over this line.)

So maybe it's your connection to your machine.