Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!lll-lcc!ames!ucbcad!ucbvax!decvax!tektronix!tekcrl!tekfdi!videovax!stever
From: stever@videovax.Tek.COM (Steven E. Rice, P.E.)
Newsgroups: comp.sys.amiga
Subject: Re: How to go slowly nuts- moving object to Amiga
Message-ID: <4499@videovax.Tek.COM>
Date: Thu, 16-Jul-87 13:12:16 EDT
Article-I.D.: videovax.4499
Posted: Thu Jul 16 13:12:16 1987
Date-Received: Sat, 18-Jul-87 11:10:16 EDT
References: <357@louie.udel.EDU>
Reply-To: stever@videovax.Tek.COM (Steven E. Rice, P.E.)
Organization: Tektronix Television Systems, Beaverton, Oregon
Lines: 49
Keywords: invalid object file
Summary: Some things to try

In article <357@louie.udel.EDU>, Ron Minnich (rminnich@udel.EDU) writes:

> OK. I am cracking up. I ftp the uudecode.Z program from asc.purdue.edu.
> I set binary mode to do this. It looks like:
> -rw-r--r--  1 rminnich     8109 uudecode
> -rw-r--r--  1 rminnich     5709 uudecode.Z
>    The uncompressed one was created from the 'shar' file in ~ftp/pub
> at purdue. Now i load uudecode down over kermit, after 
> set file type binary
> and on the amiga it is still 8109 bytes. ADos (v1.2) starts to read
> it and crunches it for a few seconds, then
> cant load uudecode: not an object file 
>    I am going slowly nuts. Has anyone else had this problem?
> When i dump the file on the amiga it looks just fine.
> When i load C source down it gets there with no errors at all.
> HEEEEEEELLLLLLLP!

[ I apologize for replying via comp.sys.amiga, but when I ask "pathto"
  how to get to "udel.EDU", I get an extremely non-committal reply. . . ]

The first step is to try again.  In addition to "set file type binary",
also enter "set block-check 3", which causes Kermit to use a CRC on the
transmission (if you're not doing this already).  Upload the file to
your Amiga just as you have before.  Then try to run the file (just for
information. . .).

The second step is to reverse the process -- download the object file
to the VAX (or whatever), using the same procedure that you used to
upload it to your Amiga.  Then use diff (or another file comparison
program) to compare the two files.  If they are not equal, you have a
suspect in your sights.

If the file from the Amiga is identical with the original, then check to
see that what you are downloading is really a binary for the Amiga!

Finally, you should be able to end-run the problem by getting a copy of
uudecode on an Amiga floppy.  Uudecode appears several times on the
Fish Disks (#53 is one place, I believe).  Certainly someone in Delaware
(udel is in Delaware, right?) should have a copy of uudecode.  

If you can't find a copy of uudecode anywhere, send me email, I'll send
you my snail mail address, you can send me a disk and a SASM, and I'll
make a copy of uudecode for you.  (There's gotta be a better way, right?)

					Steve Rice

-----------------------------------------------------------------------------
new: stever@videovax.tv.Tek.com
old: {decvax | hplabs | ihnp4 | uw-beaver | cae780}!tektronix!videovax!stever