home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!faatcrl!jprad
- From: jprad@faatcrl.UUCP (Jack Radigan)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: 'SZ'
- Message-ID: <3375@faatcrl.UUCP>
- Date: 22 Jul 92 04:15:04 GMT
- References: <Br5yDy.K2n@news.cso.uiuc.edu> <5377@ucru2.ucr.edu> <clemon.08fm@lemsys.UUCP> <!fbm+cn.fuzzy@netcom.com> <jbickers.0bib@templar.actrix.gen.nz>
- Organization: FAA Technical Center, Atlantic City NJ
- Lines: 11
-
- jbickers@templar.actrix.gen.nz (John Bickers) writes:
-
- > It might have really been a flow control problem. ZMODEM is easily
- > crippled by such things, while the XMODEM derivatives are not.
-
- Not true. ZMODEM does not require 256 byte transparency as the X/YMODEM
- protocols need. Further, hardware flow control is only needed for ZMODEM
- and YMODEM-g as they are not segmented protocols (when ZMODEM does not have
- a window value entered).
-
- -jack-
-