Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!vtserf!morpheus!frank From: frank@morpheus.UUCP (Frank McPherson) Newsgroups: comp.sys.amiga.datacomm Subject: Re: Downloading problems !!! Help !!! Message-ID: Date: 20 Mar 91 11:43:32 GMT References: <1991Mar19.215425.9317@sbcs.sunysb.edu> Organization: Virginia Polytechnic Institute Lines: 29 In article <1991Mar19.215425.9317@sbcs.sunysb.edu> dtiberio@csserv2.ic.sunysb.edu (David Tiberio) writes: > At 2400 baud, expect twice the above cps, with a max zmodem of about 240 cps. >At most I have gotten 280 cps xmodem and 1760 cps with ymodem (at 19200 baud). >Always avoid Kermit (really slow). > > Always try to use zmodem, or then try ymodem. They are 30% faster and more >reliable. If a file is over 800k, then it can be split if it is a disk >compressor. If it is a normal archive, then only decompress enough to fit >in each disk (or all of it in ram). > > David Tiberio SUNYStonyBrook2-3481 DDD MEN > isOP -- One of the main reasons Xmodem and Kermit are so slow compared to Y and Z modem is that Xmodem and Kermit normally have a very small packet size, while Y and Zmodem have larger (1 K) packet size. The normal size packet for Kermit is something around sixty bytes, so you end up having a transfer where the time to transfer is dominated by the protocal handshake, instead of by the actual transfer of data. Same problem, to a lesser extent, with Xmodem. With some versions of Kermit, you can make the problem less obvious by instructing both ends of your transfer to use larger blocks. When using Xmodem, either try Xmodem with 1K blocks, or use a different protocal. -- Frank McPherson INTERNET: emcphers@fox.cs.vt.edu --