Imploder

[mai]

Which tool is needed to pack an exexutable file with Imploder.
I have unpacked an executable (Imploder packed) with xfd, i have made some changes and want to pack it back with Imploder.

[Galahad/FLT]

Originally Posted by mai

Which tool is needed to pack an exexutable file with Imploder.
I have unpacked an executable (Imploder packed) with xfd, i have made some changes and want to pack it back with Imploder.

imploder spookily enough!

Theres two types, theres a command line data packer, and theres the rather famous Imploder with music by Paul Van Der Valk (he of Hybris and Battle Squadron fame).

http://aminet.net/util/pack/imploder-4.0.lzh

[mai]

ok, thanks for the link.

Had a quick test, why do i need external explode library, the file should unpack itself.

[BarryB]

Sounds like the 'library' button is enabled when you crunched the file, click it so it's out then try again!!

[Dr.Venom]

Originally Posted by Galahad/FLT

imploder spookily enough!

Theres two types, theres a command line data packer, and theres the rather famous Imploder with music by Paul Van Der Valk (he of Hybris and Battle Squadron fame).

OT, but still: Paul van der Valk is only of Hybris fame, Ron Klaren was responsible for the Battle Squadron music. Both really great tunes though

[mai]

Originally Posted by BarryB

Sounds like the 'library' button is enabled when you crunched the file, click it so it's out then try again!!

Thanks, it works now.
I wonder, if it is possible to get the the packed file to its original size?

[BarryB]

Galahad will be able to answer that better but I think if the cruncher messes with the hunk table or other code then it might not unpack to the same size as the original.

[StingRay]

Originally Posted by mai

Thanks, it works now.
I wonder, if it is possible to get the the packed file to its original size?

Not sure if I understand the question correctly but if you simply unpack the file you'll have the original size of the file.

If you mean crunching the file again then you'd need to use the exact same parameters for crunching. Chances are that the size will differ tho since you change the data.

Originally Posted by BarryB

Galahad will be able to answer that better but I think if the cruncher messes with the hunk table or other code then it might not unpack to the same size as the original.

Imploder does not "mess" with any code. If the crunched file hasn't been tampered with (as some sort of protection f.e.), the uncrunched file will be 100% identical to the original file.

[Toni Wilen]

"Merge" option enabled? It will change size of executable, permanently. (if it finds hunks that can be merged)

[KONEY]

Is anyone aware of a way to check if an executable has been imploded? without executing it? (Excluding the options of physically open the file within Imploder and of using snoopdos to check if imploder.library is being loaded.)

Thanks!

[Cylon]

Originally Posted by KONEY

Is anyone aware of a way to check if an executable has been imploded? without executing it? (Excluding the options of physically open the file within Imploder and of using snoopdos to check if imploder.library is being loaded.)

Thanks!

Xfdlist <file>.

[mark_k]

Originally Posted by StingRay

Imploder does not "mess" with any code. If the crunched file hasn't been tampered with (as some sort of protection f.e.), the uncrunched file will be 100% identical to the original file.

It might be effectively the same as the original when executed, but after compressing and unpacking the resulting file may well differ from the original. For example, the reloc tables are likely to be sorted.

[KONEY]

Originally Posted by Cylon

Xfdlist <file>.

PERFECT!! thanks!