Date   : Sun, 10 Feb 1991 22:05:05 GMT
From   : mvb.saic.com!ncr-sd!simasd!simasd!pnet07!donm@ucsd.edu (Don Maslin)
Subject: uudecode for a K10...

ewen@actrix.gen.nz (Ewen McNeill) writes:
>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.
>
I phrased it poorly, I am afraid.  I was attempting to paraphrase the
NightOwl doc file from memory.  What I should have said (and what
NightOwl did say) is '... MEX 1.14 is fully compatible with the emerging
YMODEM specification [...] insofar as the 1k blocks are concerned....'
 
>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.
>
Thanks for the clarification, Ewen.  I completely agree.
 
                                              - don
 

Keeper of the CP/M System Disk | UUCP: {nosc ucsd crash ncr-sd}!pnet07!donm
Archives for the Dino(saur)SIG | ARPA: simasd!pnet07!donm@nosc.mil
- San Diego Computer Society - | INET: donm@pnet07.cts.com