Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!csd4.milw.wisc.edu!jgreco From: jgreco@csd4.milw.wisc.edu (Joe Greco) Newsgroups: comp.sys.cbm Subject: Re: Zmodem on commodores? Message-ID: <1371@csd4.milw.wisc.edu> Date: 1 Mar 89 06:58:57 GMT References: <1647.23FB6F1E@isishq.FIDONET.ORG> <15177@cup.portal.com> Sender: news@csd4.milw.wisc.edu Reply-To: jgreco@csd4.milw.wisc.edu (Joe Greco) Organization: Not around here. Totally Unorganized. A Real Mess. Lines: 33 In comp.sys.cbm article <15177@cup.portal.com>, Hank@cup.portal.com (Hank W Oxford) wrote: ]Perhaps getting Zmodem to run on a Commodore isn't as difficult as ]everyone thinks. Zmodem does not *have* to send data constantly. ]Taken from various places in the Zmodem Reference: ] ZMODEM allows a choice of data streaming methods ] selected according to the limitations of the sending ] program operating environment, receiving program ] operating environment, and the transmission channel(s). ] If the receiver cannot overlap serial and disk I/O, it ] uses the ZRINIT frame to specify a buffer length which ] the sender will not overfill before sending a ZCRCW ] packet. ] ZCRCW data packets expect a response before the next ] frame is sent. If the receiver does not indicate ] overlapped I/O capability with the CANOVIO bit, the ] sender uses the ZCRCW to allow the receiver to write its ] buffer before sending more data. Obviously this fella has never encountered real world implementations of Z-Modem :-) :-) :-) :-) Come on, when was the last time anybody did even a 3/4 implementation of Z-Modem? There are probably a lot of reasonably good ones out there. No fault of the authors, since Z-Modem is a complex protocol and a "full" implementation is almost unreasonable. -- jgreco@csd4.milw.wisc.edu Joe Greco at FidoNet 1:154/200 USnail: 9905 W Montana Ave PunterNet Node 30 or 31 West Allis, WI 53227-3329 "These aren't anybody's opinions." Voice: 414/321-6184 Data: 414/321-9287 (Happy Hacker's BBS)