uzun@sdsu.UUCP (william uzun) (12/21/87)
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 a single character) and try and run it. It has yet to work. Am I doing something wrong? (The last time I tried to do this was on the Virus 1.2 program) Thanks -Roger
mike@ronin.cc.umich.edu (Michael Nowak) (12/21/87)
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 >a single character) and try and run it. It has yet to work. Am I >doing something wrong? (The last time I tried to do this was on the >Virus 1.2 program) > >Thanks >-Roger I find that you have much better luck if you send the .uu file to your Amiga and then use the Amiga version of uudecode. Then you won't have any problem with extra characterss in the Amiga file. ------------------------------------------------------------------------------ In Real Life: Michael Nowak Via Internet: mike@ronin.cc.umich.edu Via UUCP: uunet!umix!ronin.cc.umich.edu!mike Working for but in no way representing the University of Michigan. ------------------------------------------------------------------------------
ain@s.cc.purdue.edu (Patrick White) (12/22/87)
[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 >a single character) and try and run it. It has yet to work. Am I >doing something wrong? (The last time I tried to do this was on the >Virus 1.2 program) 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 shar file and unshar it on the Amiga -- but more about that in a separate posting. (BTW, we at moderator's anonymous guarantee that any shar file posted to the moderated groups can be unshared on the Amiga -- not necessarily so for the stuff posted directly to comp.sys.amiga.) For those of you who are new to downloading stuff to the Amiga and what to do with it to make it useable, stay tuned for another posting on specifically that -- going to post it in about an hour. -- Pat White (co-moderator comp.sources/binaries.amiga) UUCP: j.cc.purdue.edu!ain BITNET: PATWHITE@PURCCVM PHONE: (317) 743-8421 U.S. Mail: 320 Brown St. apt. 406, West Lafayette, IN 47906
bill@cbmvax.UUCP (Bill Koester CATS) (12/23/87)
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 >a single character) and try and run it. It has yet to work. Am I >doing something wrong? (The last time I tried to do this was on the >Virus 1.2 program) > >Thanks >-Roger XCHOP is used to remove the padding added in by xmodem transfers. If you are using kermit you should not need to chop the file. Otherwise get the uuencoded version onto the amiga and use the Amiga version of uudecode to decode it. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Bill Koester -- CBM >>Amiga Technical Support<< UUCP ...{allegra|burdvax|rutgers|ihnp4}!cbmvax!bill PHONE (215) 431-9355 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pleese desrigard eny spealing airors!!!!!!!!!!! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
stever@videovax.Tek.COM (Steven E. Rice, P.E.) (12/23/87)
In article <2873@sdsu.UUCP>, Roger (?william uzun?, uzun@sdsu.UUCP) 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 > a single character) and try and run it. It has yet to work. Am I > doing something wrong? (The last time I tried to do this was on the > Virus 1.2 program) Two possible fixes. First, you can tell Kermit "Set File Type Binary" at both ends (the sender controls; if you tell them both, you're bound to be listened to, right?). Don't use XCHOP. Unlike XMODEM, Kermit doesn't add extra characters to the end of a file. Even better, transfer the uuencoded file and then uudecode it on the Amiga (uudecode is available on Fish Disk #53, I think). I transfer the uuencoded binary and then uudecode on the Amiga. It takes an extra minute for a large binary. And it works. Steve Rice ----------------------------------------------------------------------------- * JESUS Is The REASON For The SEASON! (Merry Christmas and Happy New Year) * new: stever@videovax.tv.Tek.com old: {decvax | hplabs | ihnp4 | uw-beaver}!tektronix!videovax!stever
louie@trantor.umd.edu (Louis A. Mamakos) (12/23/87)
I kermit binary files from a 4.3 BSD UNIX host to my amiga all the time. On the unix side, I put my kermit into server/binary mode with: kermit -x -i and then I put the Amiga/VT100 kermit into binary mode. I have yet had this fail to work. In fact, I even do this while I am logged into the machine over an rlogin TCP connection. Just make sure that both ends are in binary mode. This works all the time, even when transferring text files since the UNIX idea of newline is the same as the Amiga's idea of a newline. Try it, you'll like it. Louis A. Mamakos WA3YMH Internet: louie@TRANTOR.UMD.EDU University of Maryland, Computer Science Center - Systems Programming
hamilton@uxc.cso.uiuc.edu (12/23/87)
uzun@sdsu says: > .... I kermit that module over to my amiga using VT100 V2.7. > I then run XCHOP on it (which typically removes a single character) > and try and run it. It has yet to work. Am I doing something wrong? be sure to select "image mode" from the vt100 menu and your unix's kermit ("-i" or "set file type binary"). don't run "xchop". wayne hamilton U of Il and US Army Corps of Engineers CERL UUCP: {ihnp4,seismo,pur-ee,convex}!uiucuxc!hamilton ARPA: hamilton@uxc.cso.uiuc.edu USMail: Box 476, Urbana, IL 61801 CSNET: hamilton%uxc@uiuc.csnet Phone: (217)333-8703 CIS: [73047,544] PLink: w hamilton
spencer@eris.BERKELEY.EDU (Randy Spencer) (12/24/87)
In article <2158@umd5.umd.edu> louie@trantor.umd.edu (Louis A. Mamakos) writes: >I kermit binary files from a 4.3 BSD UNIX host to my amiga all the time. On >the unix side, I put my kermit into server/binary mode with: > > kermit -x -i > >and then I put the Amiga/VT100 kermit into binary mode. I have yet had this >fail to work. >Louis A. Mamakos WA3YMH Internet: louie@TRANTOR.UMD.EDU Oh.... That may be the hook that I have been missing all these years... I read the Kermit Protocol Manual and it says that the sending kermit will send a packet that says: "I know about the following protocol specifics:" and then go on to list things like compression, packet-length, and BINARY. The receiving Kermit will then send back a packet that says: "Of those specifics I can only handle the following:" and then will list the ones it knows, which should include BINARY if it can do binary. There is no reason for it not to switch to binary mode if it has been told to... Tony Sumerall (sp?): This is an important part of Kermit compatibility, if you Kermit doesn't automatically switch than that explains almost every failure that I have ever experienced with VT100. I just Ass_U_Me'd that it was switching. Lesson is, Set Your Kermit to BINARY when downloading files from here. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Randy Spencer P.O. Box 4542 Berkeley CA 94704 (415)222-7595 spencer@mica.berkeley.edu I N F I N I T Y BBS: (415)222-9416 ..ucbvax!mica!spencer s o f t w a r e AAA-WH1M -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
papa@pollux.usc.edu (Marco Papa) (12/24/87)
In article <6383@jade.BERKELEY.EDU> spencer@eris.BERKELEY.EDU (Randy Spencer) writes: >In article <2158@umd5.umd.edu> louie@trantor.umd.edu (Louis A. Mamakos) writes: >>I kermit binary files from a 4.3 BSD UNIX host to my amiga all the time. On >>the unix side, I put my kermit into server/binary mode with: >> >> kermit -x -i >> >>and then I put the Amiga/VT100 kermit into binary mode. I have yet had this >>fail to work. >Oh.... That may be the hook that I have been missing all these years... >I read the Kermit Protocol Manual and it says that the sending kermit >will send a packet that says: > >"I know about the following protocol specifics:" > and then go on to list things like compression, packet-length, and BINARY. > >The receiving Kermit will then send back a packet that says: > >"Of those specifics I can only handle the following:" > and then will list the ones it knows, which should include BINARY if it > can do binary. There is no reason for it not to switch to binary mode > if it has been told to... > >Tony Sumerall (sp?): > > This is an important part of Kermit compatibility, if you Kermit doesn't >automatically switch than that explains almost every failure that I have ^^^^^^^^^^^^^^^^^^^^ >ever experienced with VT100. I just Ass_U_Me'd that it was switching. >Lesson is, Set Your Kermit to BINARY when downloading files from here. Randy, you misunderstood the Kermit manual. The information that is sent out includes whether the kermit supports 8 and 7 bit lines, and quoting (that is, encoding BINARY files on 7-bit lines). NO packet is sent out with the information about the TYPE (TEXT or BINARY) of the file(s) being sent. It is up to the user to set it up appropriately AT BOTH ENDS. When sending binary files, let's say between C-Kermit on a VAX and VT100 or A-Talk Plus on the Amiga one has to type: C-Kermit>set file type binary C-Kermit>send file on the VAX and then invoke the Binary Receive on VT100 or A-Talk Plus; and: C-kermit>set file type text (or ascii, I forgot) C-Kermit> send file on the VAX and then invoke the Text Receive on VT100 or A-Talk Plus. This has ALWAYS been the case for EVERY kermit. VT100, as A-Talk Plus, does it right. For more "in-depth" info, look in Frank Da Cruz's book, Kermit: A File Transfer Protocol", published by DEC press. The problem in many cases is due to the fact that the default state of the file type is text not binary. -- Marco Papa Felsina Software (ex C-Kermit developer -- see Acknowledgement in Frank's book)
jck@ncsuvx.ncsu.edu (Chuck Kesler) (01/02/88)
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.
dykimber@phoenix.Princeton.EDU (Daniel Yaron Kimberg) (04/22/88)
If anyone can give me a clue as to how to download binary files from UNIX
machines to the amiga, I'd be very grateful. I've been using handshake and
VT100, and I've tried 8 bits, 7 bits, even or none parity, etc., and the
various transfer options, with little luck. Nothing I do seems to leave me
with an amiga binary that's usable. This means that while it's easy to
transfer uuencoded files, anything that's zooed, arced, or just plain binary
is useless. If anyone has any ideas, or magic options, I'd be grateful.
Thanks,
-Dan