Path: utzoo!mnetor!uunet!husc6!rutgers!mcnc!ncsuvx!jck
From: jck@ncsuvx.ncsu.edu (Chuck Kesler)
Newsgroups: comp.sys.amiga
Subject: Re: Downloading Binaries
Message-ID: <1348@ncsuvx.ncsu.edu>
Date: 2 Jan 88 06:57:32 GMT
References: <2873@sdsu.UUCP> <1803@s.cc.purdue.edu>
Reply-To: jck@ncsuvx.UUCP (Chuck Kesler)
Organization: NCSU Computing Center, Raleigh, NC
Lines: 45
Keywords: UUDECODE DOWNLOAD
Summary: make sure binaries are downloaded as *binaries*

In article <1803@s.cc.purdue.edu> ain@s.cc.purdue.edu.UUCP (Patrick White) writes:
>[I'm posting this because we seem to get the same question over and over]
>
>In article <2873@sdsu.UUCP> uzun@sdsu.UUCP (william uzun) writes:
> >Every time I try and download a binary and run it I get an amigados
> >"File is not an object module" error.  What I do is write the file to 
> >my space, cut off the stuff up to and including the ----cut here---
> >line, and run /bin/sh on it.  I then usually get a doc file and a .uu
> >file.  I then do a uudecode on the file which gives me what I think
>	   ^^^^^^^^^^^^^^^^^^
> >is the object module.  I kermit that module over to my amiga
>			 ^^^^^^^^^^^^^^^^^^^^
> >using VT100 V2.7.   I then run XCHOP on it (which typically removes
>
>   Yes, you are doing something wrong.  Namely, you are kermiting the
>*executable*.  It should work, but dosen't.
>   I suggest you dounload the .uu files and uudecode them on the Amiga --
>that is what I do and it works every time.  You could also download the
>
Uudecoding the file on the Amiga side definitely makes a lot of sense,
but I hardly *ever* find myself doing this.  :-)  Never had any problems
with uudecoding on the unix side first, assuming the uuencoded file wasn't
screwed up to begin with.  

    If you want to uudecode before downloading, I'd say go for it.  
The only thing you MUST remember to do is to make sure of the following:

	1)  In Vt100, make sure you're downloading the file in IMAGE
	    mode, not text.                     
	2)  On the unix end, make sure your kermit program knows that 
	    you're sending a binary, either by doing a 'set file type bin'
	    from the kermit prompt or using the -i flag.

    Perhaps you're already doing this, but I don't recall you specifically
mentioning it.  But it you'll the the ol' "not an object module" from now 
until eternity unless this is done....

Hope this helps...

-chuck    jck@ncsu.ncsuvx.edu  -or-  chuck@ncsuvm.BITNET

p.s.  oh yeah..one argument for downloading executables instead of 
      uuencoded files:  the coded files are in the neighborhood of 
      35% larger than the executable-- that can translate into big 
      time savings.