New compression method: Exomizer 2

Humm... when I try this
C:\>exoopt.exe TILESETF.BIN out.opt 0xC000 f0
it halts in an endless wait
Same if I use C000 instead of 0xC000 as address of the buffer
TILESETF.BIN is a 9k binary file to be compressed
Where is the problem ?

The optimizer still just optimizes the output of exomizer itself, so you must first compress TILESETF.BIN with something like:
exomizer raw -o TILESETF.temp TILESETF.BIN

and then follow it with:
exoopt.exe TILESETF.temp 0xC000 f0

I'm sure Antonio will soon update the optimizer to exit with an error message when the input stream isn't valid, instead of crashing or hanging.

PD: There's a mistake in the help, the "output_file" parameter doesn't exist now. The output files will be the same as input, adding ".opt". In our example, it will become "TILESETF.temp.opt".

Why not integrating it with the compressor?

Exomizer 2, it's in the first post:
http://hem.bredband.net/magli143/exo/

A bit lazy, aren't we? ;)

I'll check it with Antonio, as I'm not sure if the exomizer executable can be redistributed, if it would have to include the whole source...

PD: I see Antonio already updated to v1.04 including the executable (and changing a bit the parameters order):
http://retrolandia.net/foro/showthread.php?tid=48&pid=285#pi...

ARTRAG, can you list the parts you're using from the Exomizer package, and how are they working? I looked at it briefly and I think the "raw" version is the one I should use. I tested the compression briefly on some ArkosTracker binary files, and it beats my current simple LZSS compressor by a fair marging. I haven't tested the Z80 decompressor yet because it requires translating the source to as-z80 syntax first.