Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!uokmax!munnari.oz.au!metro!usage.csd.unsw.oz.au!plod.cbme.unsw.oz.au
From: troy@plod.cbme.unsw.oz.au (Troy Rollo)
Newsgroups: comp.sources.wanted
Subject: Re: xmodem problems
Message-ID: <1447@usage.csd.unsw.oz.au>
Date: 11 May 91 09:51:01 GMT
References: <1991May10.071226.20251@fwi.uva.nl>
Sender: news@usage.csd.unsw.oz.au
Reply-To: troy@plod.cbme.unsw.oz.au
Lines: 20

From article <1991May10.071226.20251@fwi.uva.nl>, by smagt@fwi.uva.nl (Patrick van der Smagt):
smagt> I have been struggling with the xmodem program for quite a while now.
smagt> I've tried to use it (version 3.4) to send data to my home computer.
smagt> The problem is that, no matter whether I use xmodem, ymodem, or
smagt> modem7; no matter if I use 128 bytes or 1K packets; no matter if I use
smagt> CRC or not, it ALWAYS stops sending at packet #19.  I get bad blocks
smagt> at the receiver end (my home computer), and the other side remains silent.

Didn't you notice that 19 is ^S? Make sure that XON/XOFF protocol in your
terminal program is disabled, and if that doesn't do it, do an stty -tandem
before running xmodem.

The problem is that the block number being sent is control-S, andis beiug
taken as a stop message somewhere. From memory (it's a long while since I
was writing XMODEM), XMODEM doesn't send block numbers in its ACKnowledgements,
so it's probably XON/XOFF being enabled on your machine (or on a terminal
server if you are using one)
--
___________________________________________________________
troy@mr_plod.cbme.unsw.oz.au