Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!SLACTWGM.BITNET!WGLP09
From: WGLP09@SLACTWGM.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: Re: XMODEM and XFER gasping...
Message-ID: <8612041419.AA19884@ucbvax.Berkeley.EDU>
Date: Wed, 3-Dec-86 18:34:00 EST
Article-I.D.: ucbvax.8612041419.AA19884
Posted: Wed Dec  3 18:34:00 1986
Date-Received: Fri, 5-Dec-86 00:11:14 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 19
Approved: info-vax@sri-kl.arpa

RE: xmodem and xfer gasping

>WE have two versions of XMODEM. XFER, written in C, came from the University
>of Regina; the other was written in Fortran and I don't know where it came
>from. Both quit at the same point.
>
>
>I tried XFER on the vax, sending to SYMPHONY on an IBM PC and it also
>hangs up after sending 2432 bytes (19 blocks). Short files transfer ok.
>XFER seems much faster than XMODEM.

        I would suspect your XMODEM programs don't internally disable
TTSYNC or HOSTSYNC: Block 19 starts with the character 19 which is a
ctrl-S. The solution is to SET TERM/NOTTSYNC/NOHOSTSYNC/NOREADSYNC.
I wrote (yet another) XMODEM program that does all this internally.
If you're interested, post a message.

        Willy Langeveld
        Bitnet address: WGLP09@SLACTWGM