macmillan%wnre.aecl.cdn%ubc.CSNET@RELAY.CS.NET (John MacMillan) (12/01/86)
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. Any help you can give would be appreciated. Ed Wuschke Has anyone experienced this problem before? Does anyone have a version of XMODEM on the VAX that does not show this problem? (if so, would you please send a copy?) Thanks.. John MacMillan Atomic Energy of Canada Whiteshell Nuclear Research Establishment Pinawa, Manitoba, Canada R0E 1L0 (204) 753-2311 x2539
WGLP09@SLACTWGM.BITNET.UUCP (12/04/86)
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