| |
The Human Code Machine
Registered: Sep 2005
Posts: 112 |
Cross rle or equal char packer
I'm looking for a Windows commandline rle or equal char packer with at least these specs:
Memory range from $0200 to $ffff
Should create a runnable executeable with sysline
Anyone know one? I searched the net, but didn't find anything except pack64.exe included with Tass, but it didn't work here.
|
|
... 11 posts hidden. Click here to view all posts....
|
| |
iAN CooG
Registered: May 2002
Posts: 3194 |
Injecting a prg in vice would work only if the prg has a sysline, if it's starting from $0200 you can forget about it.
Give a try to Cadaver's packprg, full source included so you can build on any platform I think.
http://cadaver.homeftp.net/tools/c64tools.zip
Requires dasm to compile on the fly the depack.s, just set the depack address to $0100 and it depacks $0200-fffe (yes, it seems to have a bug with last byte setting it always to 0, just make sure you have 1 byte more than needed in the unpacked file)
I never used it because not only for the last-byte-bug, it does more than RLE (some sort of sequence packing) and the result when recrunched is worse than using an RLEpacker (or exomizer 2 alone) but it can be handy anyway if you only need to make a fast 0200-ffff program into a $0801-cfff 202 blocks runnable prg.
I have made my own semiautomatic(!) charpacker wrapper, that calls vice after injecting a charpacker and the unpacked prg in a d64, packs it and after exiting vice (alt-x/alt-f4) it extracts the packed version. Of course is not what you want but still it's better than having to do everyting manually ;)
http://iancoog.altervista.org/C/multipack_2.13_%285_packers%29... |
| |
Graham
Account closed
Registered: Dec 2002
Posts: 990 |
I am currently coding a cross version of this one: G-Packer V1.0. Fastes RLE depacking since it uses a packing scheme similar to CmpByteRun1 but introduces an end marker. This way you don't need to compare for packbyte and you don't need to compare for end address for every data byte.
|
| |
The Human Code Machine
Registered: Sep 2005
Posts: 112 |
Thx for all the suggestions. I think I'll wait until Graham comes around with hie RLE-Packer ;) |
| |
Shadow
Account closed
Registered: Apr 2002
Posts: 355 |
If you just want to test some cross-compiled code, can't you generate a Vice snapshot (vfs or whatever they are called)?
That way you can inject the complete memory without problems.
That's what I did when developing for C64DTV to avoid having to generate a D64 and emulate the complete loading process when I wanted to test something. |
| |
The Human Code Machine
Registered: Sep 2005
Posts: 112 |
@Shadow Also a nice idea. I'll take a look at the snapshot format. |
| |
Bacchus
Registered: Jan 2002
Posts: 156 |
Can I wake this thread up again.
I would want to have a full toolchain on the PC for cracking old C64 games and the normal way to do it is to RLE/Charpack the game, add the intro and then crunch the result. The RLC step is typically needed as the game is too big to add the intro without packing the game first. |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
You can try the rle option of cld here: cbmtools 0.6.
It does full 64K if required. |
| |
Burglar
Registered: Dec 2004
Posts: 1101 |
Quoting Bacchus...the normal way to do it is to RLE/Charpack the game, add the intro and then crunch the result.
For large singlefile games yes, but for multifile, Id say the best way is to keep the intro+bootfile as short as possible. and that fits easily in memory so u can just exo that.
but, for large singlefile things, I believe someone put a KickAssembler-based RLE packer on codebase or maybe in a thread here. Maybe it was Pantaloon or cruzer?
what I would do is just code an own RLE commandline tool. it's not hard ;) |
| |
Fungus
Registered: Sep 2002
Posts: 686 |
Exo skips non compressable data so crunching it works fine and rle is not needed. |
| |
Stainless Steel
Registered: Mar 2003
Posts: 966 |
is this Rle.exe or this RLEpack v0.1 any help? |
| Previous - 1 | 2 | 3 - Next |
