Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!dsac.dla.mil!dsacg3.dsac.dla.mil!nfs1675
From: nfs1675@dsacg3.dsac.dla.mil ( Michael S Figg)
Newsgroups: comp.sys.amiga
Subject: Re: DKB-Trace Problems
Summary: x-modem problems?
Message-ID: <2670@dsacg3.dsac.dla.mil>
Date: 29 Oct 90 14:14:32 GMT
References: <41254@cc.usu.edu> <90301.112031UH2@psuvm.psu.edu>
Organization: Defense Logistics Agency Systems Automation Center, Columbus
Lines: 30

In article <90301.112031UH2@psuvm.psu.edu>, UH2@psuvm.psu.edu (Lee Sailer) writes:
> In article <41254@cc.usu.edu>, SL9QW@cc.usu.edu (Amiga IS Multimedia. An apple
> is a fruit.) says:
> 
> >on my Amiga 1000/w 2.5 megs.  I have FTP'd it several times (binary) and then
> >downloaded it to my computer Via X-modem, and when I try to run it, I get a
> 
> Try some other transfer protocol instead of Xmodem.  Xmodem adds (I seem
> to recall) NULL bytes at the end of the file to pad it out to 128 or 256
> byte blocks, or some such.  This doesn't matter to MSDOS, but makes
> AmigaDos ill. 
> 
>             lee


I've heard of this problem before of something padding the end block of a 
file with NULL bytes, but I don't think it is x-modem that is doing it. I've 
been using x-modem for close to 4 years now and never had any problem with
it and have never seen anything like this. Would like more information on what
this NULL byte padding problem is/was though.


---Mike,


-- 
 --------       o       A herd of bagels      | Michael Figg  DSAC-FSD
 |      |  --  oo o o   escaping from a deli. | DLA Systems Automation Center
 |      |  -- ooo oo    Looking for Lox in    | Cols, Ohio mfigg@dsac.dla.mil
 --------      o o      all the wrong places  | CIS: 73777,360