Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!agate!darkstar!ucscb.UCSC.EDU!unknown From: unknown@ucscb.UCSC.EDU (The Unknown User) Newsgroups: comp.sys.apple2 Subject: Re: Bug in ProTerm 2.2? Message-ID: <13630@darkstar.ucsc.edu> Date: 20 Mar 91 16:41:31 GMT References: <9103201526.AA07284@apple.com> Sender: usenet@darkstar.ucsc.edu Organization: University of California, Santa Cruz; Open Access Computing Lines: 25 In article <9103201526.AA07284@apple.com> EWNORT@WMVM1.BITNET (Eric) writes: > All telecommunications packages that I know of do attempt to re-send bad >packets. Unless there is some physical reason that it cannot do a re-send, it >should (and most do) attempt this until they reach a preset limit on the number >of tries. In any case, ProTerm should (I keep referring to ProTerm in a hypo- >thetical manner because I am not familiar with it) have returned a message to >the effect that it did have trouble sending a specific packet and terminated >its transmission due to this error. According to my slight knowledge about Zmodem, you are incorrect in your assumptions, because Zmodem does not conform to the "regular" specifications of a modem transfer protocol. It just keeps blazing happily away whether or not there are errors. It prints to the screen (or maybe a file in some implementations?) a list of what blocks are in error... In non-brain-damaged versions of Zmodem (i.e. anything but ProTERM), you can tell it to resend a bunch of blocks or resend from a specific point on. Now if I could only get my damn graphics project to work.. aaah --