Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!shelby!polya!gilham From: gilham@polya.Stanford.EDU (Fred Gilham) Newsgroups: comp.sys.amiga Subject: Re: File not an object module Message-ID: <9986@polya.Stanford.EDU> Date: 13 Jun 89 14:54:03 GMT References: <620@wn2.sci.kun.nl> Sender: Fred Gilham Reply-To: gilham@polya.Stanford.EDU (Fred Gilham) Organization: Stanford University Lines: 26 In article <620@wn2.sci.kun.nl> peterb@wn2.sci.kun.nl (Peter Beker ) writes: >I cannot use the source-files from comp.binaries.amiga. >The files in comp.binaries.amiga should be run through the /bin/sh. >I have to copy the files to an Atari 1040ST. At home i use Dos2Dos to >copy files to the Amiga. If i try to execute the files, i get the >error-message 'File not an object module'. Some people say, the binary- >files should be runned through /bin/sh and after that through UUDECODE. >Neither of them works. > >Is there anybody who can help me with this problem ? Possibly you are running into the old problem with hunks being padded, which is the same problem people used to have with doing xmodem transfers onto the amiga. There are programs to fix this (called "CHOP" or something) on old fish disks. The idea is that xmodem always filled out the binary to 128 byte boundaries, while the amiga loader would keep track of how long the hunks were, and notice that the last hunk was too long. This caused it to think the file was screwed up, and it would report the "error". Other than this you might be having trouble with the way you are doing the transfers. You might want to keep the files in shar format and run an unshar program and a uudecode program on the amiga. I do this all the time and it works fine. -Fred Gilham