| |
Trap
Registered: Jul 2010
Posts: 223 |
Packing anno 2015
Hi guys,
It's been a few days since I wrote Sledgehammer 2 and I am pretty sure the scene has evolved somewhat since then. So, I wonder what's the latest and greatest in terms of packers? Specifically I am looking for a solution I can use to pack/unpack parts of memory. Not loading - just in-memory.
In this wonderful open-source world I think sharing is caring and there really is no reason to write a packer/depacker myself if somebody else already did :)
cheers and a merry Christmas!
Trap |
|
... 5 posts hidden. Click here to view all posts....
|
| |
Burglar
Registered: Dec 2004
Posts: 1101 |
cresh's stuff seems quite useful, when you're making a onefiled demo. if your stuff is going to get bigger and you want to load stuff fast, check out Spindle 2.1, Bitfire 0.4 and Krill's Loader, repository version 146. crunching is built in in each.
when choosing crunchers, exomizer yields best result, but also depacks the slowest by far.
also, quite a lot of info in this thread: Release id #139503 : Spindle 2.0 |
| |
Trap
Registered: Jul 2010
Posts: 223 |
Yes, I'm already using Spindle - lightyears ahead of the competition. So easy to use, which is a good thing for an old confused man like me :)
Thanks for all your kind responses fellow 8-bit aficionados.
/Trap |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
Spindle is already loading and on the fly depacking with lz in any case. But other depackers yield better results in size, not necessarily in speed however. Did i just state somewhen, that it is great to have loadraw with later depack capabilities? Didn't spindle have also the enhanced linking that allows to load data whenever possible beforehand by keeping track of the used memory? |
| |
Martin Piper
Registered: Nov 2007
Posts: 722 |
Depends if you're after packers that are native only, or cross platform tools. I think someone posted a comparison table here recently? |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
Trap, your best bet is depack WHILE loading, because it uses up the idle times in loading for maximum effect. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
exactly, roughly as a rule of thumb around a third faster, but depending on loader/depacker combo. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
It really depends on your requirements. Single file demo compo and parallel depacking's not an option; same with pulling data off a cartridge.
Must admit though, even for a single file I could have done with Spindle's level of automation when I was putting Reutastic together; spent a while chasing a bug because I'd run some init code for the second page before I'd decrunched the data it required. (As it happens I used Nucrunch because I had the source to hand, but last time there was a comparison post it lagged a little behind the competition) |
| |
Trap
Registered: Jul 2010
Posts: 223 |
Now I'm using the Exomizer in the plugin for KickAss. Works great.
However, when I crunch a section in memory. The crunched data is located at its destination address already. How can I decrunch data at a different destination address? |
| |
TheRyk
Registered: Mar 2009
Posts: 2244 |
It's possible, for expample
exomizer sfx $XXXX foo-in.prg -o foo-out.prg -n -Di_load_addr=$YYYY
will decrunch your data to $YYYY which is also the address you jump to for decrunching. After decrunching it will jump to $XXXX
See here for more Info:
https://www.c64-wiki.de/index.php/Exomizer
German, but code is code and I guess you as a Dane will get the message :) |
| |
Trap
Registered: Jul 2010
Posts: 223 |
Thanks Ryk. sfx was the wonderbutton I was looking for. I hadn't thought that I could just use the commandline cruncher to prepack the files :) |
| Previous - 1 | 2 - Next |
