Differences

This shows you the differences between two versions of the page.

--- base:exomizer_level_compress_decompression_for_beginners [2020-10-01 14:15] – [Using Exomizer's Decruncher on a Cross Assembler] richard
+++ base:exomizer_level_compress_decompression_for_beginners [2020-10-01 14:15] – [Using Exomizer's Decruncher on a Native C64] richard
@@ Line 37: / Line 37: @@
 </code>
 Please take note that there can be cases where running the decruncher, sometimes it might crash. This is normally if a zero byte has been read while depacking from reverse memory. Or the crash will occur if you are decrunching from the incorrect end address. Sometimes you may need to set the $01 value to #$35, #$36 or #$37 before/after calling the decrunch code, depending on which memory address you wish to decrunch from/to.
-====Using Exomizer's Decruncher on a Native C64====
+====An Example of Using Exomizer's Decruncher on a Native C64====
 What about if you wanted to use Exomizer when using a native C64 instead of a cross-assembler. It is quite easy. Exomizer's level decrunch is very flexible when it comes to areas to place the crunched data (Providing the crunched data is NOT loaded on to the memory that is being used for something else. A machine code monitor, such as the Action / Retro Replay fast load is helpful. Where there is spare memory in your program, you load the crunched data to a chosen address. Take note of the END address where the program lies. Then use the end address as a LOW/HI BYTE target. Then call the Exomizer to decrunch from that address. You can also load in the next crunched file one byte AFTER the END address of the previous file. Note down the end address and so on.