Path: utzoo!attcan!uunet!pmafire!uudell!sequoia!execu!cs.utexas.edu!sun-barr!lll-winken!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!brian From: brian@cunixf.cc.columbia.edu (Brian Hoffman) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: what is the quickest (most efficient?) File xfer protocol? Summary: wrongo Keywords: zmodem Message-ID: <1990Nov30.224121.15936@cunixf.cc.columbia.edu> Date: 30 Nov 90 22:41:21 GMT References: <33558@netnews.upenn.edu> <3765@bnr-rsc.UUCP> Organization: Columbia University Lines: 18 In article <3765@bnr-rsc.UUCP> lalibert@bcarh188.UUCP () writes: >My brother once set up a download using ZMODEM. He came back an hour >later expecting to be logged out. (Autologout when download completed.) >But the modem was still chugging along with a block size of 1 byte! >He quickly brok out and used XMODEM. Turns out if ZMODEM feels too many >errors are occuring it decreases the block size to reduce retransmission >time. But if the trouble clears up, it doesn't increase the size. >What likely happened is the phone got picked up, giving mega noise, and >dropping the block size. Wrongo. Zmodem will automatically increase the block size if the errors go away. Most likely, your brother was using a crummy unix implementation. |Brian Hoffman | |brian@cunixf.cc.columbia.edu | |Quote: "A red sky at night may be a shepard's delight, but you're |