Exomizer - Revision history

Ervin: /* Links */

2017-08-31T02:50:12Z

‎Links

Ervin: /* Links */

2017-08-31T02:49:34Z

‎Links

Ervin: /* Bugs */

2017-08-31T02:48:04Z

‎Bugs

Ervin: /* Bugs */

2017-08-31T02:47:26Z

‎Bugs

MiguelSky: /* Decompression */

2014-10-15T00:28:01Z

‎Decompression

MiguelSky: /* Decompression */

2014-10-15T00:27:24Z

‎Decompression

Nich: Added 'Bugs' section

2011-10-16T18:20:02Z

Added 'Bugs' section

Arnoldemu: /* Installing Exomizer */

2011-10-12T20:47:49Z

‎Installing Exomizer

Arnoldemu: /* Installing Exomizer */

2011-10-12T20:47:32Z

‎Installing Exomizer

Nich: Added CrossDev category

2011-10-11T20:17:29Z

Added CrossDev category

@@ Line 111: / Line 111: @@
 == Links ==
-* [http://hem.bredband.net/magli143/exo/ Old ''Exomizer'' home page]
+* [https://bitbucket.org/magli143/exomizer/wiki/Home/ ''Exomizer'' home page]
-* [https://bitbucket.org/magli143/exomizer/wiki/Home/ New ''Exomizer'' home page]
 [[Category:CrossDev]]

@@ Line 111: / Line 111: @@
 == Links ==
-* [http://hem.bredband.net/magli143/exo/ ''Exomizer'' home page]
+* [http://hem.bredband.net/magli143/exo/ Old ''Exomizer'' home page]
 [[Category:CrossDev]]

@@ Line 107: / Line 107: @@
 ''Exomizer'' can sometimes fail to decompress files correctly for no apparent reason, causing the CPC to crash. Unfortunately there is no known way to overcome this problem, other than to use a different compressor.
-[31-August-2017] The above claim is questionable. The *only* times I've ever encountered such Exomizer crashes were due to errors on my part (for example, an incorrect data type for an array in C). In my experience, Exomizer itself has never caused any problems.
+[Added 31-August-2017 by ervin] The above claim is questionable. The *only* times I've ever encountered such Exomizer crashes were due to errors on my part (for example, an incorrect data type for an array in C). In my experience, Exomizer itself has never caused any problems.
 == Links ==

← Older revision		Revision as of 02:47, 31 August 2017
Line 106:		Line 106:

	''Exomizer'' can sometimes fail to decompress files correctly for no apparent reason, causing the CPC to crash. Unfortunately there is no known way to overcome this problem, other than to use a different compressor.		''Exomizer'' can sometimes fail to decompress files correctly for no apparent reason, causing the CPC to crash. Unfortunately there is no known way to overcome this problem, other than to use a different compressor.
		+
		+	[31-August-2017] The above claim is questionable. The only times I've ever encountered such Exomizer crashes were due to errors on my part (for example, an incorrect data type for an array in C). In my experience, Exomizer itself has never caused any problems.

	== Links ==		== Links ==

@@ Line 80: / Line 80: @@
 <pre>load_file:
 		ld hl,filename		;HL = file name address
-		ld de,&4C4A             ;DE = start address to load file to
+		ld de,&4c4a             ;DE = start address to load file to
 		ld b,12			;B = length of file name
 		call &bc77		;Open the file header

@@ Line 3: / Line 3: @@
 == Tutorial ==
-=== Installing Exomizer ===
+=== Installing ''Exomizer'' ===
 Firstly, download ''Exomizer'' from the home page; the link is at the bottom of this article.
@@ Line 74: / Line 74: @@
 Remember the safety offset that was mentioned earlier? The game code starts at &200 and is &7520 bytes long, so the final byte is located at address &200 + &7520 - 1 = &771F. As the safety offset for <tt>BOULDERC.BIN</tt> is 2 bytes, this means that the final byte of this file can be located at any address from &771F + 2 = &7721 or above. This means that the lowest start address that the file can be loaded to is &7721 - &2AD8 + 1 = &4C4A (or 0x4C4A), so enter this value as the start address. The entry point should be left at 0x0000.
-The Z80 assembler source code for decompressing files is located in the <tt>rawdecrs\z80</tt> subfolder, and the file name is <tt>deexo.asm</tt>. The decompression routine is 198 bytes long, and it also requires a buffer of 156 bytes. The buffer is labelled <code>exo_mapbasebits</code>, and it is located immediately after the decompression routine, but you can alter it (by adding the line <code>exo_mapbasebits equ &xxxx</code>) so that it is located anywhere in memory - as long as it doesn't overwrite the compressed file or the decompressed data! Assemble the decompression routine to a suitable address in memory using an assembler of your choice (e.g. ''Pasmo'' or ''WinAPE'''s built-in assembler); again, ensure that it doesn't overwrite the compressed file or the decompressed data. The code supplied with ''Exomizer'' may need to be edited to suit the syntax of your assembler.
+The Z80 assembler source code for decompressing files is located in the <tt>rawdecrs\z80\</tt> subfolder, and the file name is <tt>deexo.asm</tt>. The decompression routine is 198 bytes long, and it also requires a buffer of 156 bytes. The buffer is labelled <code>exo_mapbasebits</code>, and it is located immediately after the decompression routine, but you can alter it (by adding the line <code>exo_mapbasebits equ &xxxx</code>) so that it is located anywhere in memory - as long as it doesn't overwrite the compressed file or the decompressed data! Assemble the decompression routine to a suitable address in memory using an assembler of your choice (e.g. ''[[Pasmo]]'' or ''[[WinAPE]]'''s built-in assembler); again, ensure that it doesn't overwrite the compressed file or the decompressed data. The code supplied with ''Exomizer'' may need to be edited to suit the syntax of your assembler.
 Now you will need to add some code to load <tt>BOULDERC.BIN</tt> into memory and decompress it. Add the following code before the decompression routine:
@@ Line 102: / Line 102: @@
 Finally, run this code, and if you have done everything correctly, you should see the ''Boulder Dash'' title screen!
 == Links ==

@@ Line 17: / Line 17: @@
 You need to download the zip, extract it and build it from source. You will gnu C installed.
-<tt>unzip exomizer202.zip</tt>
+ <tt>unzip exomizer202.zip</tt>
-<tt>cd exomizer202/src</tt>
+ <tt>cd exomizer202/src</tt>
-<tt>make</tt>
+ <tt>make</tt>
 When you are done you will have b2membuf, exobasic, exomizer and exoraw in the same directory as the source.

@@ Line 5: / Line 5: @@
 === Installing Exomizer ===
-Firstly, download ''Exomizer'' from the home page; the link is at the bottom of this article. Unzip the ZIP file to a folder of your choice (e.g. <tt>C:\exomizer</tt>). The Windows binaries are located in the <tt>win32\</tt> subfolder. For ease of use, copy the <tt>exomizer.exe</tt> file in this subfolder to the main folder (i.e. <tt>C:\exomizer</tt>).
+Firstly, download ''Exomizer'' from the home page; the link is at the bottom of this article.
 This tutorial also assumes that ''[[ManageDsk]]'' (a Windows utility for manipulating DSK files) is installed on your PC.
 === Compression ===

← Older revision		Revision as of 20:17, 11 October 2011
Line 92:		Line 92:

	* [http://hem.bredband.net/magli143/exo/ ''Exomizer'' home page]		* [http://hem.bredband.net/magli143/exo/ ''Exomizer'' home page]
		+
		+	[[Category:CrossDev]]