Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!comp.vuw.ac.nz!actrix!ewen
From: ewen@actrix.gen.nz (Ewen McNeill)
Newsgroups: comp.os.cpm
Subject: Re: uudecode for a K10...
Message-ID: <1991Feb9.093717.13309@actrix.gen.nz>
Date: 9 Feb 91 09:37:17 GMT
References: <1991Feb6.232504.5663@simasd.uucp>
Organization: Actrix Information Exchange, Wellington, New Zealand
Lines: 21
Comment-To: donm@pnet07.cts.com

In article <1991Feb6.232504.5663@simasd.uucp> donm@pnet07.cts.com (Don Maslin) writes:
>
> Actually, MEX114 will handle Xmodem and Xmodem batch in both CRC and Checksum
> modes.  It will also handle 1k block transmission - Ymodem, but not Ymodem
> batch.  You should be able to transfer binary files with no problem.
> 
Are you sure that Mex 1.14 (I haven't used it in ages), does Ymodem,
rather than Xmodem-1K?  There is a big difference between the two; True
Ymodem sends the file name and a few other useful details (like exact
file length) with the file.

Because of a fate of the naming, someone called the new Xmodem variant
Ymodem, when Omen Techology had already released a program with another
protocol which they called Ymodem.

This leads to strange things, like the protocol being called True Ymodem
(Omen Technology's variety).  However, Ymodem batch has always been True
Ymodem, to my knowledge.

-- 
Ewen McNeill.				Email: ewen@actrix.gen.nz