Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!megatest!palowoda
From: palowoda@megatest.UUCP (Bob Palowoda)
Newsgroups: comp.dcom.modems
Subject: Re: xyzmodem problems
Message-ID: <5011@megatest.UUCP>
Date: 18 May 89 07:01:51 GMT
References: <24440@agate.BERKELEY.EDU>
Distribution: usa
Organization: Megatest Corporation, San Jose, Ca
Lines: 27

From article <24440@agate.BERKELEY.EDU>, by ked@garnet.berkeley.edu (Earl H. Kinmonth):
> In article <8457@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes:
>>In article <24404@agate.BERKELEY.EDU> ked@garnet.berkeley.edu (Earl H. Kinmonth) writes:
>>>machines at UC-Davis and UC-Berkeley. xyzmodem (any of the protocols)
>>>work for downloads, but uploads INVARIABLY stop after 16 blocks have
>>>been transferred.  This is consistent over half a dozen different machines
>>
[some text deleted]
> 
> I haven't timed zmodem vs kermit on uploads yet. On downloads, at least
> with base 85 encoded files, kermit seems to win: average xfer rate on
> 9600 baud line of 560 chars/sec vs 340 for zmodem. Maybe there is more
> tuning that needs to be done.

  Hmm, something is wrong with 340. I run Xenix and also use Zmodem 
  to download/upload from a dos machine that's hard port connected @9600
  and via a TrialBlazier. On hard connected I see 928cps, modem I see
  910cps. Haven't tried 19.2k yet.

  ---Bob


-- 
 Bob Palowoda    *Home of Fiver BBS*                   login: bbs               
 Work: {sun,decwrl,pyramid}!megatest!palowoda                           
 Home: {sun}ys2!fiver!palowoda   (A XBBS System)       2-lines   
 BBS:  (415)623-8809 2400/1200 (415)623-8806 1200/2400/9600/19200