Posted By
Csabo
on 2010-05-24
21:57:42
|  Re: Exomizer & load address
That should already be pretty clear, but I'll chime in since I was wondering about this myself just last month and asked Magnus directly. My question was:
> [...] Exomizer displays something like this:
>
> Memory layout:
> Data covers $0FFE to $4830.
> Decrunch table is located at $0334 to $03D0.
>
> In the above example, the data should start at $1000 [...]
His reply:
"I should probably document this somewhere too  The "data covers" interval is not only for the decrunched data but *also* for the crunched data. If it prints $0ffe for a file that starts at $1000 then it means that two bytes is the minimum overlap that allows for correct decrunching. The decruncher will make sure that the crunched data starts at $0ffe by copying all or parts of it before beginning the actual decrunch.
So together with the target file itself, the stack area and a few zero page locations, the "data covers" and "decrunch table" memory intervals should be the only areas that are overwritten by the decrunch process.
I hope this explains it."
|
