Path: utzoo!attcan!uunet!lll-winken!ames!killer!elg
From: elg@killer.DALLAS.TX.US (Eric Green)
Newsgroups: comp.sys.amiga
Subject: Re: Atalk III 1.0e
Message-ID: <6818@killer.DALLAS.TX.US>
Date: 17 Jan 89 02:38:22 GMT
References: <470@infohh.rmi.de>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 22

in article <470@infohh.rmi.de>, shimoda@infohh.rmi.de (Markus Schmidt) says:
> If the uploader handled the file correct there should be no problem
> with chopping. According to Chuck Forsberg you may pad either with NUL
> or CMP_EOF, and there is no reason for not using CMP_EOF when the last
> byte of the file is NUL. 
> Of course the receiver may only chop those PADs that match the last byte
> in the transfer and not mixed 00 and 1A.

Let's say that your file length is an exact multiple of 128 bytes.
Further, let's say that your file ends with fifteen NUL characters.
Xmodem will not create an extra empty padding block. Thus an
autochopper will chop off 15 bytes of your file.

That's just one example of why Xmodem is brain-dead for use with
non-CP/M systems. I personally use Batch Ymodem or Zmodem whenever
possible, just to bypass those problems.

--
Eric Lee Green    ..!{ames,decwrl,mit-eddie,osu-cis}!killer!elg
          Snail Mail P.O. Box 92191 Lafayette, LA 70509              
Netter A: In Hell they run VMS.
Netter B: No.  In Hell, they run MS-DOS.  And you only get 256k.