These are all old packers. Make SURE you keep a backup. Most, but not all are designed to pack absolute code files, very few support relocs. Even less crunch things with >1 hunk. It's here that I want to point something out. Since version 1.0 of the Amiga operating system, the DOS loader has supported in it's file-loading routine, LoadSeg(), the possibility of relocs. What does this mean? It means that if you write this kind of instruction in assembler: move.l #$50,mylabel rts mylabel dc.l 0 that the assembler has to write a reloc for that instruction. This goes into a seperate hunk, usually reloc32 but could be reloc16 or reloc8 if needed. This reloc hunk (which you can have many of) goes something like this (as our example): Hunk 0 offset $00000002 - write reloc to hunk 0 offset $00000008 .... other relocs for this hunk... Anyway, when the code is loaded in memory it looks like this: $0120422: MOVE.L #$50,$012042A $0120428: RTS $012042A: DC.L 0 The loader has created an absolute address for the instruction. This means you can use absolute addressed commands and expect the computer to relocate them wherever you are loaded into memory! Cool! However, the problem is this : the SEKA assembler was/still is complete shit. It could not be bothered to support the hunk format, and said this: "Either you code for a single hunk entirely PC-relative, or you let SEKA save a binary image. This binary image contains correct-calculated addresses, but you must load it at the right address or it won't work". Because of this, for years we got absolute-addressed demos, a plague from the days of the C64. These demos, if written in any other assembler except SEKA, would have not needed absolute addresses. Meanwhile, at exactly the same time, the C compilers were not yet able to generate binary code direct from their sources. They generated assembly language files, which were then passed to an assembler. Which assembler? AS, CAPE, Devpac, ADAPT. All supported relocs. People with sense bought or pirated Devpac, the choice assembler for assembler coders. However, the idiocy of swappers hyped SEKA, making it sound cool when it was complete shite really. Now here is the part where I embarrass some shitheads. Quotes ripped from the code of MegaCruncher: "All coding in pure Assembler by Hans Bergstedt." not very pure assembler is it! "This is a tool for all Assembler programmers." wrong, it's a tool for all SEKA cøderz "You can crunch either Object files or Absolute-address files." wrong, you can crunch SEKA's object output or absolute output. "For best resaults use "SEKA" and no link- or includefiles..." *excuse* me? No include files? You complete wanker, do you enjoy typing out all the custom-register names for each source you write? Or do you prefer to write them as addresses instead, which you then get a mistake in and never find the bug.... "The Object-loader can NOT handle too many or strange "Hunk"-codes !" there is nothing strange about data and bss hunks! "Thats why this cruncher is not compatibel with most "C"-programs and "Pascal"-programs..." no, that's why the cruncher is not compatible with anything but SEKA cøde. And from the start of the (absolute coded) file.... "---------------- Hello CRACKERS ---------------- What are you looking for ??????? It is Illegal to CRACK or CHANGE others work !!!! Make your own routines... ----------------" Right then. 1) I am not a cracker, I'm just trying to get your stupid cruncher to WORK! 2) Crunching a file hides nothing! Have you ever heard of monam? 3) I'm looking for fairies. Care to join me? 4) It is not illegal to crack anything unless you specifically deny it, which you didn't. 5) I *do* make my own routines, mainly because your ones are complete shit. Here's a little excerpt of crapness, the keyboard decode routine.... $0 cmp.b #$10,d0 bne $1 move.b #'Q',d0 rts $1 cmp.b #$11,d0 bne $2 move.b #'W',d0 rts $2 [this shit is repeated for every key on the keyboard] I dunno, but had you perhaps ever considered something like: and.w #255,d0 move.b table(pc,d0.w),d0 rts table dc.b "'1234567890-=\ QWERTZUIOP[] 123ASDFGHJKL;#" [repeat for the rest of the keys...] I mean, it is several 100 times faster to type in, and probably 100 times faster executing too..... Anyway - enough of this rubbish! The cruncher "TitanPack" is the opposite of MegaCruncher. It is absolutely stunning. It came in a few years after MegaCruncher, and because it is coded so well, it is still in heavy demand today! It crunches any kind of executable file, into an overlayed file which will unpack into memory as it loads from disk. It runs on an intuition screen, and does nothing naughty at all! Let this be a testament to you, coders! Don't make bad utils!