shithub: rgbds

Download patch

ref: 2eb748278b62f28ea5fb99c47bee9f12712e8982
parent: 5ee058f21718406ff4cd5cd3c0c4811512ed167a
author: Anthony J. Bentley <[email protected]>
date: Thu Feb 23 16:07:11 EST 2017

Move HTML docs to a different repo.

--- a/doc/asm.htm
+++ /dev/null
@@ -1,129 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm</title>
-	<link rel="stylesheet" type="text/css" href="./style.css">
-</head>
-<body>
-<h1>xAsm Documentation</h1>
-<h2>Table of Contents</h2>
-<h3>General stuff</h3>
-<ul>
-	<li><a href="asm/history.htm">History</a>
-	<li><a href="asm/usage.htm">Usage</a>
-	<li><a href="asm/opt.htm">Changing options while assembling</a>
-	<li><a href="asm/popo.htm">The option stack</a>
-	<li><a href="asm/syntax.htm">Syntax and comments</a>
-	<li><a href="asm/section.htm">Sections</a>
-</ul>
-
-<h3>Symbols</h3>
-<ul>
-	<li><a href="asm/symbols.htm">Symbols</a>
-	<li><a href="asm/export.htm">Exporting and importing symbols</a>
-	<li><a href="asm/purge.htm">Purging symbols</a>
-	<li><a href="asm/presym.htm">Predeclared symbols</a>
-</ul>
-
-<h3>The macrolanguage</h3>
-<ul>
-	<li><a href="asm/print.htm">Printing out things during assembling</a>
-	<li><a href="asm/rept.htm">Automatically repeating blocks of code</a>
-	<li><a href="asm/fail.htm">Aborting the assembly process</a>
-	<li><a href="asm/include.htm">Including other sourcefiles</a>
-	<li><a href="asm/if.htm">Conditional assembling</a>
-	<li><a href="asm/expr_int.htm">Integer and Boolean expressions</a>
-	<li><a href="asm/expr_fix.htm">Fixed-point expressions and functions</a>
-	<li><a href="asm/expr_str.htm">String expressions, functions and formatting</a>
-	<li><a href="asm/miscfunc.htm">Other functions</a>
-</ul>
-
-<h3>Other ways than mnemonics to define data</h3>
-<ul>
-	<li><a href="asm/db.htm">Defining constant data</a>
-	<li><a href="asm/ds.htm">Declaring variables in a RAM section</a>
-	<li><a href="asm/incbin.htm">Including binary files</a>
-</ul>
-
-<h3>Target specific information</h3>
-<ul>
-	<li><a href="asm/trg_gb.htm">The Gameboy</a>
-</ul>
-
-<h3>Alphabetical list of the macro-language instructions and functions</h3>
-<ul>
-	<li><a href="asm/presym.htm">@</a>
-	<li><a href="asm/presym.htm">__DATE__</a>
-	<li><a href="asm/presym.htm">__LINE__</a>
-	<li><a href="asm/presym.htm">__TIME__</a>
-	<li><a href="asm/presym.htm">_NARG</a>
-	<li><a href="asm/presym.htm">_PI</a>
-	<li><a href="asm/presym.htm">_RS</a>
-	<li><a href="asm/expr_fix.htm">ACOS</a>
-	<li><a href="asm/expr_fix.htm">ASIN</a>
-	<li><a href="asm/expr_fix.htm">ATAN</a>
-	<li><a href="asm/expr_fix.htm">ATAN2</a>
-	<li><a href="asm/miscfunc.htm">BANK</a>
-	<li><a href="asm/expr_fix.htm">COS</a>
-	<li><a href="asm/db.htm">DB</a>
-	<li><a href="asm/miscfunc.htm">DEF</a>
-	<li><a href="asm/expr_fix.htm">DIV</a>
-	<li><a href="asm/ds.htm">DS</a>
-	<li><a href="asm/db.htm">DW</a>
-	<li><a href="asm/if.htm">ELSE</a>
-	<li><a href="asm/if.htm">ENDC</a>
-	<li><a href="asm/macro.htm">ENDM</a>
-	<li><a href="asm/rept.htm">ENDR</a>
-	<li><a href="asm/equ.htm">EQU</a>
-	<li><a href="asm/equs.htm">EQUS</a>
-	<li><a href="asm/export.htm">EXPORT</a>
-	<li><a href="asm/fail.htm">FAIL</a>
-	<li><a href="asm/export.htm">GLOBAL</a>
-	<li><a href="asm/section.htm">HRAM</a>
-	<li><a href="asm/if.htm">IF</a>
-	<li><a href="asm/export.htm">IMPORT</a>
-	<li><a href="asm/incbin.htm">INCBIN</a>
-	<li><a href="asm/include.htm">INCLUDE</a>
-	<li><a href="asm/macro.htm">MACRO</a>
-	<li><a href="asm/expr_fix.htm">MUL</a>
-	<li><a href="asm/opt.htm">OPT</a>
-	<li><a href="asm/popo.htm">POPO</a>
-	<li><a href="asm/pops.htm">POPS</a>
-	<li><a href="asm/print.htm">PRINTF</a>
-	<li><a href="asm/print.htm">PRINTT</a>
-	<li><a href="asm/print.htm">PRINTV</a>
-	<li><a href="asm/purge.htm">PURGE</a>
-	<li><a href="asm/popo.htm">PUSHO</a>
-	<li><a href="asm/pops.htm">PUSHS</a>
-	<li><a href="asm/rept.htm">REPT</a>
-	<li><a href="asm/rs.htm">RB</a>
-	<li><a href="asm/section.htm">ROM0</a>
-	<li><a href="asm/section.htm">ROMX</a>
-	<li><a href="asm/rs.htm">RSRESET</a>
-	<li><a href="asm/rs.htm">RSSET</a>
-	<li><a href="asm/rs.htm">RW</a>
-	<li><a href="asm/section.htm">SECTION</a>
-	<li><a href="asm/set.htm">SET</a>
-	<li><a href="asm/shift.htm">SHIFT</a>
-	<li><a href="asm/expr_fix.htm">SIN</a>
-	<li><a href="asm/section.htm">SRAM</a>
-	<li><a href="asm/expr_str.htm">STRCAT</a>
-	<li><a href="asm/expr_str.htm">STRCMP</a>
-	<li><a href="asm/expr_str.htm">STRIN</a>
-	<li><a href="asm/expr_str.htm">STRLEN</a>
-	<li><a href="asm/expr_str.htm">STRLWR</a>
-	<li><a href="asm/expr_str.htm">STRSUB</a>
-	<li><a href="asm/expr_str.htm">STRUPR</a>
-	<li><a href="asm/expr_fix.htm">TAN</a>
-	<li><a href="asm/section.htm">VRAM</a>
-	<li><a href="asm/section.htm">WRAM0</a>
-	<li><a href="asm/section.htm">WRAMX</a>
-	<li><a href="asm/fail.htm">WARN</a>
-	<li><a href="asm/export.htm">XDEF</a>
-	<li><a href="asm/export.htm">XREF</a>
-</ul>
-
-<p>Last updated 20 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/db.htm
+++ /dev/null
@@ -1,26 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm DB, DW</title>
-	<link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>DB, DW</h1>
-<p><dfn>DB</dfn> defines a list of bytes that will be stored in the final image. Ideal for tables and text.</p>
-<pre>DB   1,2,3,4,"This is a string"</pre>
-<p>Alternatively you can use <dfn>DW</dfn> to store a list of words. Strings are not allowed as arguments to DW.</p>
-<p>You can also use DB and DW without arguments. This works exactly like “DS 1” and “DS 2” respectively. Consequently DB and DW can be used in a WRAM0/WRAMX/HRAM/VRAM/SRAM section.</p>
-<h1>See also:</h1>
-<ul>
-	<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-	<li><a href="expr_fix.htm">Fixed-point expressions and functions</a>
-	<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-	<li><a href="ds.htm">Declaring variables in a RAM section</a>
-	<li><a href="miscfunc.htm">Other functions</a>
-</ul>
-
-<hr>
-<p>Last updated 02 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/ds.htm
+++ /dev/null
@@ -1,20 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm DS</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>DS</h1>
-<p><dfn>DS</dfn> allocates a number of bytes. The content is undefined. This is the preferred method of allocationg space in a <a href="section.htm">RAM section</a>. You can however also use DB and DW without any arguments.</p>
-<pre>DS   str_SIZEOF     ;allocate str_SIZEOF bytes</pre>
-<h1>See also:</h1>
-<ul>
-	<li><a href="db.htm">Defining constant data (DB/DW)</a>
-	<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-</ul>
-<hr>
-<p>Last updated 02 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/equ.htm
+++ /dev/null
@@ -1,21 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm EQU</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>EQU</h1>
-<p>EQUates are constant symbols. They can for example be used for things such as bit-definitions of hardware-registers.</p>
-<pre>DONUT_ISGOOD   EQU  $01
-DONUT_ISBAD    EQU  $02</pre>          
-<p>Note that a colon (:) following the label-name is not allowed. EQUates can be <a href="export.htm">exported and imported</a>. They don't change their value during the link process.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/equs.htm
+++ /dev/null
@@ -1,27 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm EQUS</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>EQUS</h1>
-<p>EQUS is used to define string-symbols. Wherever the assembler meets a string symbol its name is replaced with its value. If you are familiar with C you can think of it as the same as #define.</p>
-<pre>COUNTREG EQUS "[hl+]"
-          
-         ld   a,COUNTREG</pre>
-<p>(Note that : following the label-name is not allowed.)</p>
-<p>This will be interpreted as:</p>
-<pre>         ld   a,[hl+]</pre>
-<p>String-symbols can also be used to define small one-line macros:</p>
-<pre>PUSHA    EQUS "push af\npush bc\npush de\npush hl\n"</pre>
-<p>Note that a colon (:) following the label-name is not allowed. String equates can't be exported or imported.</p>
-<h1>See also:</h1>
-<ul>
-	<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/export.htm
+++ /dev/null
@@ -1,35 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm EXPORT/XREF, IMPORT/XDEF, GLOBAL</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>EXPORT/XREF, IMPORT/XDEF, GLOBAL</h1>
-<p>Importing and exporting of symbols is a feature that is very useful when your project spans many source-files and for example you need to jump to a routine defined in another file.</p>
-<table>
-	<caption>Import/export commands</caption>
-<thead>
-<tr>
-	<th scope="col">Command</th>
-	<th scope="col">Meaning</th>
-</tr>
-</thead>
-<tr>
-	<td>IMPORT (or XREF) <i>label</i>[,<i>label</i>,...]</td>
-	<td>This  instructs the assembler to define label as if it were present
-                  in the current file but leave the address calculation to the linker.</td>
-</tr>
-<tr>
-	<td>EXPORT (or XDEF) <i>label</i>[,<i>label</i>,...]</td>
-	<td>The  assembler will make <i>label</i> accessible to other files during the link process.</td>
-</tr>
-<tr>
-	<td>GLOBAL <i>label</i>[,<i>label</i>,...]</td>
-	<td>If <i>label</i> is defined during the assembly it will be exported, if not it will be imported. Handy (very!) for include-files.</td>
-</tr>
-</table>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body></html>
--- a/doc/asm/expr_fix.htm
+++ /dev/null
@@ -1,76 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Fixed-point expression</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>Fixed‐point Expressions</h1>
-<p>Fixed point constants are basically normal 32-bit constants where the upper 16 bits are used for the integer part and the lower 16 bits are used for the fraction (65536ths). This means that you can use them in normal integer expression and indeed some integer operators like plus and minus don't care whether the operands are integer or fixed-point. You can easily convert a fixed-point number to an integer by shifting it right 16 bits. It follows that you can convert an integer to a fixed-point number by shifting it left.</p>
-<p>Some things are different for fixed-point math though. Which is why you have the following functions to use:</p>
-
-<table>
-<thead>
-<tr>
-	<th scope="col">Name</th>
-	<th scope="col">Operation</th>
-</tr>
-</thead>
-<tr>
-	<td>DIV(x,y)</td>
-	<td>x/y</td>
-</tr>
-<tr>
-	<td>MUL(x,y)</td>
-	<td>x*y</td>
-</tr>
-<tr>
-	<td>SIN(x)</td>
-	<td>sin(x)</td>
-</tr>
-<tr>
-	<td>COS(x)</td>
-	<td>cos(x)</td>
-</tr>
-<tr>
-	<td>TAN(x)</td>
-	<td>tan(x)</td>
-</tr>
-<tr>
-	<td>ASIN(x)</td>
-	<td>sin<SUP>-1</SUP>(x)</td>
-</tr>
-<tr>
-	<td>ACOS(x)</td>
-	<td>cos<SUP>-1</SUP>(x)</td>
-</tr>
-<tr>
-	<td>ATAN(x)</td>
-	<td>tan<SUP>-1</SUP>(x)</td>
-</tr>
-<tr>
-	<td>ATAN2(x,y)</td>
-	<td>(x,y) angle</td>
-</tr>
-</table>
-<p>These  functions are extremely useful for automatic generation of various tables. A circle has 65536.0 degrees. Sine values are between [-1.0;1.0]</p>
-<pre>; --
-; -- Generate a 256 byte sine table with values between 0 and 128
-; --
-ANGLE   SET     0.0
-        REPT    256
-        DB      (MUL(64.0,SIN(ANGLE))+64.0)>>16
-ANGLE   SET     ANGLE+256.0
-        ENDR</pre>
-<h1>See also:</h1>
-<ul>
-	<li><a href="symbols.htm">Symbols</a>
-	<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-	<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-	<li><a href="miscfunc.htm">Other functions</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/expr_int.htm
+++ /dev/null
@@ -1,92 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Integer/Boolean expressions</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>Integer and Boolean expressions</h1>
-<p>An expression can be composed of many things. Expressions are always evaluated using signed 32-bit math.</p>
-<p>The most basic expression is just a single number.</p>
-<h2>Numeric Formats</h2>
-<p>xAsm has a number of numeric formats.</p>
-<ul>
-	<li>Hexadecimal: $0123456789ABCDEF. Case-insensitive
-	<li>Decimal: 0123456789
-	<li>Octal: &01234567
-	<li>Binary: %01
-	<li>Fixedpoint (16.16): 01234.56789
-	<li>Character constant: "ABYZ"
-	<li>Gameboy graphics: `0123
-</ul>
-<p>The last one, Gameboy graphics, is quite interesting and useful. The values are actually pixel values and it converts the “chunky” data to “planar” data as used in the Gameboy.</p>
-<pre>DW   `01012323</pre>
-<p>Admittedly an expression with just a single number is quite boring. To spice things up a bit there’s a few operators you can use to perform calculations between numbers.</p>
-<h2>Operators</h2>
-<p>A great number of operators you can use in expressions are available (listed in order of precedence):</p>
-<table>
-	<caption>Operators</caption>
-<thead>
-<tr>
-	<th scope="col">Operator</th>
-	<th scope="col">Meaning</th>
-</tr>
-</thead>
-<tr>
-	<td>( )</td>
-	<td>Precedence override</td>
-</tr>
-<tr>
-	<td>FUNC()</td>
-	<td>Functioncall</td>
-</tr>
-<tr>
-	<td>~ + -</td>
-	<td>Unary not/plus/minus</td>
-</tr>
-<tr>
-	<td>* / %</td>
-	<td>Multiply/divide/modulo</td>
-</tr>
-<tr>
-	<td>&lt;&lt; &gt;&gt;</td>
-	<td>Shift left/right</td>
-</tr>
-<tr>
-	<td>&amp; | ^</td>
-	<td>Binary and/or/xor</td>
-</tr>
-<tr>
-	<td>+ -</td>
-	<td>Add/subtract</td>
-</tr>
-<tr>
-	<td>!= == &lt;= &gt;= &lt; &gt;</td>
-	<td>Boolean comparison</td>
-</tr>
-<tr>
-	<td>&amp;&amp; ||</td>
-	<td>Boolean and/or</td>
-</tr>
-<tr>
-	<td>!</td>
-	<td>Unary Boolean not</td>
-</tr>
-</table>     
-
-<p>The result of the boolean operators is zero if when FALSE and non-zero when TRUE. Thus it is legal to use an integer as the condition for <a href="if.htm">IF</a> blocks. You can use symbols instead of numbers in your expression if you wish.</p>
-
-<p>An expression is said to be constant when it doesn't change its value during linking. This basically means that you can't use labels in those expressions. The instructions in the macro-language all require expressions that are constant.</p>
-<h1>See also:</h1>
-<ul>
-	<li><a href="symbols.htm">Symbols</a>
-	<li><a href="expr_fix.htm">Fixed-point expressions and functions</a>
-	<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-	<li><a href="miscfunc.htm">Other functions</a>
-</ul>
-
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/expr_str.htm
+++ /dev/null
@@ -1,114 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm String expressions</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>String Expressions</h1>
-<p>The most basic string expression is any number of characters contained in double quotes ("for instance"). As in C the escape character is <b>\</b> and there is a number of commands you can use within a string:</p>
-<table>
-	<caption>Escape characters:</caption>
-<thead>
-<tr>
-	<th scope="col">Character sequence</th>
-	<th scope="col">Meaning</th>
-	<th scope="col">Notes</th>
-</tr>
-</thead>
-<tr>
-	<td>\\</td>
-	<td>Backslash</td>
-	<td></td>
-</tr>
-<tr>
-	<td>\"</td>
-	<td>Double-quote</td>
-	<td></td>
-</tr>
-<tr>
-	<td>\{</td>
-	<td>Curly bracket left</td>
-	<td></td>
-</tr>
-<tr>
-	<td>\}</td>
-	<td>Curly bracket right</td>
-	<td></td>
-</tr>
-<tr>
-	<td>\n</td>
-	<td>Newline ($0A)</td>
-	<td></td>
-</tr>
-<tr>
-	<td>\t</td>
-	<td>Tab ($09)</td>
-	<td></td>
-</tr>
-<tr>
-	<td>\1-\9</td>
-	<td>Macroargument</td>
-	<td>Only in macros</td>
-</tr>
-<tr>
-	<td>\@</td>
-	<td>Labelname suffix</td>
-	<td>Only in macros and repts</td>
-</tr>
-</table>
-
-<p>A funky feature is <b>{symbol}</b> withing a string. This will examine the type of the symbol and insert its value accordingly. If symbol is a string symbol the symbols value is simply copied. If it's a numeric symbol the value is converted to hexadecimal notation and inserted as a string.</p>
-<p><strong>HINT:</strong> The <b>{symbol}</b> construct can also be used outside strings. The symbols value is again inserted as a string. This is just a short way of doing &quot;{symbol}&quot;.</p>
-<p>Whenever the macro-language expects a string you can actually use a string expression. This consists of one or more of these function. Yes, you can nest them. Note that some of these functions actually return an integer and can be used as part of an integer expression!</p>
-<table>
-	<caption>String functions:</caption>
-<thead>
-<tr>
-	<th scope="col">Name</th>
-	<th scope="col">Operation</th>
-</tr>
-</thead>
-<tr>
-	<td>STRLEN(<i>stringexpr</i>)</td>
-	<td>Returns the number of characters in <i>string</i></td>
-</tr>
-<tr>
-	<td>STRCAT(<i>stringexpr1,stringexpr2</i>)</td>
-	<td>Appends <i>stringexpr2</i> to <i>stringexpr1</i>.</td>
-</tr>
-<tr>
-	<td>STRCMP(<i>stringexpr1,stringexpr2</i>)</td>
-	<td>Returns negative if <i>stringexpr1</i> is alphabetically less than <i>stringexpr2</i><BR>Zero if they match<BR>Positive if greater than</td>
-</tr>
-<tr>
-	<td>STRIN(<i>haystack,needle</i>)</td>
-	<td>Returns <i>needle</i>s position within <i>haystack</i> or zero if it's not present</td>
-</tr>
-<tr>
-	<td>STRSUB(<i>stringexpr,pos,count</i>)</td>
-	<td>Returns a substring of <i>stringexpr</i> starting at <i>pos</i> (first character is position 1) and with <i>count</i> characters</td>
-</tr>
-<tr>
-	<td>STRUPR(<i>stringexpr</i>)</td>
-	<td>Converts all characters in <i>string</i> to capitals and returns the new string</td>
-</tr>
-<tr>
-	<td>STRLWR(<i>string</i>)</td>
-	<td>Converts all characters in <i>string</i> to lower case and returns the new string</td>
-</tr>
-</table>
-
-<h1>See also:</h1>
-<ul>
-	<li><a href="symbols.htm">Symbols</a>
-	<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-	<li><a href="expr_fix.htm">Fixed-point expressions and functions</a>
-	<li><a href="miscfunc.htm">Other functions</a>
-</ul>
-
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/fail.htm
+++ /dev/null
@@ -1,20 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm FAIL, WARN</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>FAIL, WARN</h1>
-<p>FAIL and WARN can be used to terminate the assembling process if you wish to do so. This is especially useful for macros that get an invalid argument. FAIL and WARN take a string as the only argument and they will print this string out as a normal error with a linenumber.</p>
-<p>FAIL stops assembling immediately while WARN continues after printing the errormessage.</p>
-
-<h1>See also:</h1>
-<ul>
-<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/history.htm
+++ /dev/null
@@ -1,224 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm History</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>xAsm History</h1>
-<table>
-	<caption>The history of xAsm</caption>
-<thead>
-<tr>
-	<th scope="col">Version</th>
-	<th scope="col">Dated</th>
-	<th scope="col">Release notes</th>
-</tr>
-</thead>
-<tr>
-	<td>1.0</td>
-	<td>1 Oct. 96</td>
-	<td>First release</td>
-</tr>
-<tr>
-	<td>1.01</td>
-	<td>1 Dec. 96</td>
-	<td><ul>
-<li>Fixed  bug  in <a href="incbin.htm">INCBIN</a> (sometimes reported the section full)</li>
-                 <li>Added <a href="miscfunc.htm">DEF()</a> function
-</ul></td>
-</tr>
-<tr>
-	<td>1.02</td>
-	<td>12 Feb. 97</td>
-	<td><ul>
-<li>Added <a href="expr_str.htm">STRLEN(), STRCAT(), STRIN(), STRCMP(), STRSUB(), STRUPR() and STRLWR()</a> functions</li>
-	<li><a href="export.htm">IMPORT/EXPORT/GLOBAL</a> takes multiple arguments now</li>
-	<li><a href="section.htm">HRAM</a> sectiontype added</li>
-	<li>ORG like features added to <a href="section.htm">SECTION</a></li>
-	<li><a href="trg_gb.htm">LDIO</a> mnemonic added</li>
-</ul></td>
-</tr>
-<tr>
-	<td>1.03</td>
-	<td>23 Mar. 97</td>
-	<td><ul>
-<li>The <a href="section.htm">HRAM section</a> was 128 bytes long instead of 127. potentially thrashing the interrupt enable register if you filled the HRAM.</li>
-	<li>The <a href="miscfunc.htm">BANK() function</a>, when used on a symbol defined in the current sourcefile, returned the wrong bank ID. (reported by Harry P. Mulder)</li>
-	<li>The <a href="miscfunc.htm">BANK() function</a> didn't check whether the argument was a properly defined symbol. (reported by Harry P. Mulder)</li>
-	<li>Completely new lexical analyser module. This fixed several linenumber bugs and other macro/if/rept related bugs. Also fixed a bug which made it possible to have equated symbols with the same name as a reserved keyword (if you get a "parse error" with this release on some of your sources, this is probably what is going on)</li>
-	<li><a href="fail.htm">FAIL and WARN</a> commands.</li>
-	<li><a href="presym.htm">__LINE__, __FILE__, __TIME__, __DATE__</a> predefined symbols added.</li>
-</ul>
-</td>
-</tr>
-<tr>
-	<td>1.04</td>
-	<td>03 July 1997</td>
-	<td><ul><li>First ASMotor release</li>
-<li><a href="presym.htm">__TIME__ and __DATE__</a> give todays date instead of when the assembler was compiled.</li>
-<li>Sometimes the first line of a file wouldn't assemble correctly. Reported by Jeff Frohwein.</li>
-<li>Unrolling multiline <a href="equs.htm">string symbols</a> left the linecounter in a sorry state. Jeff Frohwein again.</li>
-<li><a href="db.htm">DB and DW</a> can now (officially ;-) be used in BSS/HRAM/VRAM sections without any arguments to reserve a byte or a word respectively. Reported/suggested/inspired by Mr. Frohwein.</li>
-<li>The character # can now be used as part of a <a href="symbols.htm">symbol name</A>. Jeff....</li>
-<li>The <a href="rs.htm">RS</a> counter "_RS" is now defined from the very start of the assembly process instead of after the first RSSET or RSRESET.</li>
-<li>Bug fixed: You couldn't use \0-\9 and \@ in <a href="expr_str.htm">{} constructs</a></li>
-<li><a href="purge.htm">PURGE</a> pseudo-op added. Purges a symbol from the symboltable and memory. Use with extreme caution! Inspired by Harry P. Mulder</li>
-<li><a href="macro.htm">MACRO</a> parameter passing method changed drastically. Read (and re-read) the manual for details. Suggested by Harry P. Mulder.</li>
-</ul>
-</td>
-<tr>
-	<td>1.05</td>
-	<td>20 July 1997</td>
-	<td><B>RGBDS fixes:</B><BR>
-	RGBAsm supports the LDD and LDI syntax plus [HLD] and [HLI]. LDH is
-	synonymous with LDIO.<BR>
-	<B>General fixes:</B><BR>
-There was a bug in the macro parameter passing. Any whitespace after the
-last parameter would be appended to the last parameter. Reported by Jeff Frohwein.<BR>
-A section stack has been implemented. Look up <a href="pops.htm">POPS and PUSHS</A>. Jeff Frohweins doing again.<BR>
-<a href="opt.htm">OPT</A> command added for defining and changing some options while assembling.<BR>
-You can now define which characters are used for the <a href="expr_int.htm">Gameboy graphics
-integer (`)</A> using the <a href="usage.htm">commandline</A> or the new <a href="opt.htm">OPT</A> command. Cool idea by (surprise surprise) Jeff Frohwein.<BR>
-Also, an option stack has been added. Look up <a href="popo.htm">POPO and PUSHO</A> in the
-manual.<BR>
-Fixed yet another line number bug reported by Jeff Frohwein (when will this guy leave me alone? ;)<BR>
-</td>
-<tr>
-	<td>1.06</td>
-	<td>22 July 1997</td>
-	<td><B>General fixes:</B><BR>
-The lamest typo bug of all time has been fixed. RGBAsm would output a word defined with DW as 4 bytes instead of 2. Jeff Frohwein reported this.<BR>
-The first line of an included file didn't assemble correctly.<BR>
-<a href="usage.htm">-b option</A> added for setting the characters used for binary constants.<BR>
-</td>
-</tr>
-<tr>
-	<td>1.08</td>
-	<td>21 September 1997</td>
-	<td><B>General fixes:</B><BR>
-A crash occured if you tried to use a macro symbol in an expression.
-(Jeff Frohwein)<BR>
-You couldn't use STRCMP, STRLEN and STRIN in relocatable expressions. (Harry
-P. Mulder)<BR>
-Relocatable symbols are no longer allowed as arguments to the DEF function.<BR>
-Bug fixed in the assembler where it would sometimes write out too many bytes
-for HRAM section definitions.<BR>
-</td>
-</tr>
-	<tr>
-		<td>1.08</td>
-		<td>02 July 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			DQ directive added for defining 32-bit data constants. See operation of DW &amp; DB.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>05 July 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Allow only a part of a binary file to be included instead of the whole thing.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>10 June 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Added output of file dependency information for each file included/assembled. Enabled with a command line option.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>?? ???? 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Added ORG directive to allow anonymous sections.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>?? ???? 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Added ability to output error information in either RGBDS or Microsoft Developer Studio format.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>?? ???? 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Added pseudo-instructions to handle NE (not equal), EQ (equal), and LT (less than) on JR/JP/CALL instructions
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>?? ???? 1999</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Added STRTRIM, STRLTRIM, STRRTRIM directives to allow trimming of white space from strings in macro arguments.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>?? ???? 1999</td>
-		<td>
-			<B>Bug Fix:</B>
-			<BR>
-			When an "unknown symbol" error was reported during the link phase the undefined symbol was not given.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.08</td>
-		<td>?? ???? 1999</td>
-		<td>
-			<B>Bug Fix:</B>
-			<BR>
-			Declaring a symbol as GLOBAL in a header file and then referencing it in code but never defining it would crash the linker.
-			<BR>
-		</td>
-	</tr>
-	<tr>
-		<td>1.09</td>
-		<td>08 February 2000</td>
-		<td>
-			<B>Feature:</B>
-			<BR>
-			Can now use a command line option to set the number format between a slightly tweaked Motorola/RGBDS format and Zilog.
-			<BR>
-			Hex numbers can now be represented as $FF or FFh.
-			<BR>
-			Octal as &amp;77 or 77o.
-			<BR>
-			Binary as %10010110 or 10010110b.
-			<BR>
-			Gameboy graphics numbers as `1001 or 1001g.
-			<BR>
-			Decimal numbers remain unchanged.
-			<BR>
-		</td>
-	</tr>
-
-</TABLE>
-
-<BR><HR>
-<FONT SIZE="-1"><I><P ALIGN=RIGHT>Last updated 21 September 1997 by <a href="mailto:[email protected]">Carsten Sorensen</A></P></I></FONT>
--- a/doc/asm/if.htm
+++ /dev/null
@@ -1,24 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm IF, ELSE, ENDC</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>IF, ELSE, ENDC</h1>
-<p>These three commands is used to conditionally assemble parts of your file. It is a powerful feature commonly used in macros.</p>
-<pre>IF   2+2==4
-PRINTT    "2+2==4\n"
-ELSE
-PRINTT    "2+2!=4\n"
-ENDC</pre>
-<p>The ELSE block is optional. IF/ELSE/ENDC-blocks can be nested.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/incbin.htm
+++ /dev/null
@@ -1,22 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm INCBIN</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>INCBIN</h1>
-<p>You  probably have some graphics you’d like to include. Use <dfn>INCBIN</dfn> to include a raw binary file as it is. If the file isn’t found in the current directory the <a href="usage.htm">include-path</a> list will be searched.</p>
-<pre>INCBIN    "titlepic.bin"
-INCBIN    "sprites\\hero.bin"</pre>
-<p>You can also include only part of a file with <b>INCBIN</b>. The example below includes 256 bytes from <i>data.bin</i> starting from position 78.</p>
-<pre>INCBIN    "data.bin",78,256</pre>
-<h1>See also:</h1>
-<ul>
-	<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/include.htm
+++ /dev/null
@@ -1,19 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm INCLUDE</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>INCLUDE</h1>
-<p>Use INCLUDE to process another assembler-file and then return to the current file when done. If the file isn't found in the current directory the <a href="usage.htm">include-path</a> list will be searched. You may nest <b>INCLUDE</b> calls infinitely (or until you run out of memory whichever comes first).</p>
-<pre>INCLUDE   "irq.inc"</pre>
-<h1>See also:</h1>
-<ul>
-<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/labels.htm
+++ /dev/null
@@ -1,22 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Labels</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>Labels</h1>
-<p>One of the assembler’s main tasks is to keep track of addresses for you so you dor’t have to remember obscure numbers but can make do with a meaningful name, a label.</p>
-<p>This can be done in a number of ways:</p>
-<pre>GlobalLabel
-AnotherGlobal:
-.locallabel
-.yet_a_local:
-ThisWillBeExported::        ;note the two colons</pre>
-<p>This  is very similar to other assemblers. Local labels are  only accessible within the scope they are defined. A scope starts after a global label and ends at the next global label. You  may  or  may not have seen the <b>::</b> feature  before. It declares a normal global label but does an <a href="export.htm">EXPORT</a> at the same time.</p>
-<p>Labels will normally change their value during the <a href="../link.htm">link process</a> and are thus <em>not</em> constant.</p>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/macro.htm
+++ /dev/null
@@ -1,60 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm MACRO/ENDM</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>MACRO, ENDM</h1>
-<p>One of the best features of an assembler is the ability to write macros for it. Macros also provide a method of passing arguments to them and they can then react to the input using IF-constructs.</p>
-<pre>MyMacro:  MACRO
-          ld   a,80
-          call MyFunc
-          ENDM</pre>
-<p>The above example is a very simple macro. You execute the macro by typing its name.</p>
-<pre>          add  a,b
-          ld   sp,hl
-          MyMacro        ;This will be expanded
-          sub  a,87</pre>
-<p>When the assembler meets MyMacro it will insert the macrodefinition (the text enclosed in <b>MACRO/ENDM</b>).</p>
-<p id="labelsuffix">Suppose your macro contains a loop.</p>
-<pre>LoopyMacro:    MACRO
-               xor  a,a
-.loop          ld   [hl+],a
-               dec  c
-               jr   nz,.loop
-               ENDM</pre>
-<p>This is fine. That is, if you only use the macro once per <a href="labels.htm">scope</a>. To get around this problem there is a special label string equate called <b>\@</b> that you can append to your labels and it will then expand to a unique string.</p>
-<p><b>\@</b> also works in <a href="rept.htm">REPT-blocks</a> should you have any loops there.</p>
-<pre>LoopyMacro:    MACRO
-               xor  a,a
-.loop\@        ld   [hl+],a
-               dec  c
-               jr   nz,.loop\@
-               ENDM</pre>
-<h2>Arguments</h2>
-<p>I’d like <i>LoopyMacro</i> a lot better if I didn’t have to pre-load the registers with values and <em>then</em> call it. What  I’d like is the ability to pass it arguments and it then loaded the registers itself.</p>
-<p>And I can do that. In macros you can get the arguments by using the special macro string equates <b>\1</b> through <b>\9</b>, <b>\1</b> being the first argument specified on the calling of the macro.</p>
-<pre>LoopyMacro:    MACRO
-               ld   hl,\1
-               ld   c,\2
-               xor  a,a
-.loop\@        ld   [hl+],a
-               dec  c
-               jr   nz,.loop\@
-               ENDM</pre>
-<p>Now I can call the macro specifying two arguments. The first being the address and the second being a bytecount. The macro will then reset all bytes in this range.</p>
-<pre>               LoopyMacro     MyVars,54</pre>
-<p>You can specify up to nine arguments when calling a macro. Arguments are passed as string equates. There’s no need to enclose them in quotes. Parameter passing has changed a bit since v1.03 in that an expression will not be evaluated first but passed directly. This means that it’s probably a very good idea to use brackets around \1–\9 if you perform further calculations on them. For instance if you pass 1+2 as the first argument and then do <code>    PRINTV  \1*2</code>
-you will get the value 5 on screen and not 6 as you might have expected.</p>
-<p>Note that a colon (:) following the macro-name is required. Macros can't be exported or imported. It's valid to call a macro from a macro (yes, even the same one).</p>
-
-<h1>See also:</h1>
-<ul>
-<li><a href="shift.htm">SHIFT</a>
-</ul>
-<hr>
-<p>Last updated 02 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/miscfunc.htm
+++ /dev/null
@@ -1,38 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Other functions</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>Other functions</h1>
-<p>There's a few other functions that do various useful things:</p>
-<table>
-	<caption>Other functions</caption>
-<thead>
-<tr>
-	<th scope="col">Name</th>
-	<th scope="col">Operation</th>
-</tr>
-</thead>
-<tr>
-	<td>BANK(<i>label</i>)</td>
-	<td>Gameboy ONLY: Returns the bank number <i>label</i> is in. The link will have to resolve this so it can't be used when the expression has to be constant</td>
-</tr>
-<tr>
-	<td>DEF(<i>label</i>)</td>
-	<td>Returns TRUE if <i>label</i> has been defined</td>
-</tr>
-</table>
-<h1>See alse:</h1>
-<ul>
-	<li><a href="section.htm">Sections</a>
-	<li><a href="symbols.htm">Symbols</a>
-	<li><a href="presym.htm">Predeclared symbols</a>
-	<li><a href="if.htm">Conditional assembling</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/opt.htm
+++ /dev/null
@@ -1,27 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm OPT</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>OPT</h1>
-<p>OPT can be used to change <I>some</I> of the options during assembling you source instead of defining them on the commandline.</p>
-<p>OPT takes a comma-seperated list of options as its argument:</p>
-
-<pre>    PUSHO
-    OPT   g.oOX    ;Set the GB graphics constants to use these characters
-    DW    `..ooOOXX
-    POPO
-    DW    `00112233</pre>
-<p>The options that OPT can modify are currently: <b>b, e and g</b></p>
-<h1>See also:</h1>
-<ul>
-<li><a href="usage.htm">Usage</a>
-<li><a href="popo.htm">The option stack</a>
-</ul>
-<hr>
-<p>Last updated 20 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/popo.htm
+++ /dev/null
@@ -1,18 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm POPO, PUSHO</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>POPO, PUSHO</h1>
-<p>POPO and PUSHO provide the interface to the option stack. PUSHO will push the current set of options on the option stack. POPO can then later be used to restore them. Useful if you want to change some options in an include file and you don't want to destroy the options set by the program that included your file. The stacks number of entries is limited only by the amount of memory in your machine.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="opt.htm">Changing options while assembling</a>
-</ul>
-<hr>
-<p>Last updated 20 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/pops.htm
+++ /dev/null
@@ -1,18 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm POPS, PUSHS</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>POPS, PUSHS</h1>
-<p>POPS and PUSHS provide the interface to the section stack. PUSHS will push the current section context on the section stack. POPS can then later be used to restore it. Useful for defining sections in included files when you don't want to destroy the section context for the program that included your file. The stacks number of entries is limited only by the amount of memory in your machine.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="section.htm">Sections</a>
-</ul>
-<hr>
-<p>Last updated 18 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/presym.htm
+++ /dev/null
@@ -1,63 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Predeclared symbols</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>Predeclared symbols</h1>
-<table>
-	<caption>Symbols</caption>
-<thead>
-<tr>
-	<th scope="col">Name</th>
-	<th scope="col">Contents</th>
-	<th scope="col">Type</th>
-</tr>
-</thead>
-<tr>
-	<td>@</td>
-	<td>PC value</td>
-	<td>EQU</td>
-</tr>
-<tr>
-	<td>_PI</td>
-	<td>Fixed point ¶</td>
-	<td>EQU</td>
-</tr>
-<tr>
-	<td>_RS</td>
-	<td>_RS counter</td>
-	<td>SET</td>
-</tr>
-<tr>
-	<td>_NARG</td>
-	<td>Number of arguments passed to macro</td>
-	<td>EQU</td>
-</tr>
-<tr>
-	<td>__LINE__</td>
-	<td>The current linenumber</td>
-	<td>EQU</td>
-</tr>
-<tr>
-	<td>__FILE__</td>
-	<td>The current filename</td>
-	<td>EQUS</td>
-</tr>
-<tr>
-	<td>__DATE__</td>
-	<td>Todays date</td>
-	<td>EQUS</td>
-</tr>
-<tr>
-	<td>__TIME__</td>
-	<td>The current time</td>
-	<td>EQUS</td>
-</tr>
-</table>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/print.htm
+++ /dev/null
@@ -1,29 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm PRINTT, PRINTV, PRINTF</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>PRINTT, PRINTV, PRINTF</h1>
-<p>These  three  instructions  type  text and  values  to stdout. Useful for debugging macros or wherever you may feel the need to tell yourself some important information.</p>
-<pre>PRINTT    "I'm the greatest programmer in the whole wide world\n"
-PRINTV    (2+3)/5
-PRINTF    MUL(3.14,3987.0)</pre>
-<ul>
-	<li><dfn>PRINTT</dfn> prints out a string</li>
-	<li><dfn>PRINTV</dfn> prints out an integer value or, as in the example, the result of a calculation. Unsurprisingly you can also print out a <a href="symbols.htm">constant symbols</a> value</li>
-	<li><dfn>PRINTF</dfn> prints out a fixed point value.</li>
-</ul>
-
-<h1>See also:</h1>
-<ul>
-	<li><a href="asm/expr_int.htm">Integer and Boolean expressions</a>
-	<li><a href="asm/expr_fix.htm">Fixed-point expressions and functions</a>
-	<li><a href="asm/expr_str.htm">String expressions, functions and formatting</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/purge.htm
+++ /dev/null
@@ -1,18 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm PURGE</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>PURGE</h1>
-<p>The PURGE command allows you to completely remove a symbol from the symbol table as if it had never existed. USE WITH EXTREME CAUTION!!! I can’t stress this enough but you <em>seriously</em> need to know what you are doing. DON’T purge symbol that you use in expressions the linker needs to calculate. In fact, it’s probably not even safe to purge anything other than string symbols and macros.</p>
-<pre>Kamikaze    EQUS    "I don't want to live anymore"
-AOLer       EQUS    "Me too"
-            PURGE   Kamikaze,AOLer</pre>
-<p>Note that string symbols that are part of a PURGE command WILL NOT BE EXPANDED as the ONLY exception to this rule.</p>
-<hr>
-<p>Last updated 02 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/rept.htm
+++ /dev/null
@@ -1,32 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm REPT, ENDR</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>REPT, ENDR</h1>
-<p>Suppose you’re feeling lazy and you want to unroll a time consuming loop. <dfn>REPT</dfn> is here for that purpose. Everything between REPT and ENDR will be repeated a number of times just as if you done a copy/paste operation yourself</p>
-<pre>REPT 4
-add  a,c
-ENDR</pre>
-<p>This will assemble <code>add a,c</code> four times.</p>
-<p>You can also use REPT to generate tables on the fly:</p>
-<pre>; --
-; -- Generate a 256 byte sine table with values between 0 and 128
-; --
-ANGLE   SET     0.0
-        REPT    256
-        DB      (MUL(64.0,SIN(ANGLE))+64.0)>>16
-ANGLE   SET     ANGLE+256.0
-        ENDR</pre>
-<p>REPT is also very useful in recursive macros and as in macros you can also use the special label operator \@. REPT-blocks can be nested.<p>
-<h1>See also:</h1>
-<ul>
-<li><a href="macro.htm#labelsuffix">\@</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/rs.htm
+++ /dev/null
@@ -1,76 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm RSSET, RSRESET, RB, RW</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>RSSET, RERESET, RB, RW</h1>
-<p>The <dfn>RS</dfn> group of commands is a handy way of defining structures:</p>
-<pre>              RSRESET
-str_pStuff    RW   1
-str_tData     RB   256
-str_bCount    RB   1
-str_SIZEOF    RB   0</pre>
-<p>The example defines four <a href="equ.htm">equated</a> symbols:</p>
-<table>
-	<caption>Defined symbols</caption>
-<thead>
-<tr>
-	<th scope="col">Name</th>
-	<th scope="col">Value</th>
-</tr>
-</thead>
-<tr>
-	<td>str_pStuff</td>
-	<td>0</td>
-</tr>
-<tr>
-	<td>str_tData</td>
-	<td>2</td>
-</tr>
-<tr>
-	<td>str_bCount</td>
-	<td>258</td>
-</tr>
-<tr>
-	<td>str_SIZEOF</td>
-	<td>259</td>
-</tr>
-</table>
-<p>There are four commands in the RS group of commands:</p>
-<table>
-	<caption>RS related commands</caption>
-<thead>
-<tr>
-	<th scope="col">Command</th>
-	<th scope="col">Meaning</th>
-</tr>
-</thead>
-<tr>
-	<td>RSRESET</td>
-	<td>Resets the <a href="presym.htm">_RS</a> counter to zero</td>
-</tr>
-<tr>
-	<td>RSSET <i>constexpr</i></td>
-	<td>Sets the <a href="presym.htm">_RS</a> counter to <i>constexpr</i></td>
-</tr>
-<tr>
-	<td>RB <i>constexpr</i></td>
-	<td>Sets the preceding symbol to <a href="presym.htm">_RS</a> and adds <i>constexpr</i> to _RS</td>
-</tr>
-<tr>
-	<td>RW <i>constexpr</i></td>
-	<td>Sets the preceding symbol to <a href="presym.htm">_RS</a> and adds <i>constexpr*2</i> to _RS</td>
-</tr>
-</table>
-<p>Note that a colon (:) following the symbol-name is not allowed. RS symbols can be exported and imported. They don't change their value during the link process.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/section.htm
+++ /dev/null
@@ -1,70 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm SECTION</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>SECTION</h1>
-<p>Before you can start writing code you must define a section. This tells the assembler what kind of data follows and if it is code where to put it.</p>
-<pre>SECTION   "CoolStuff",ROMX</pre>
-<p>This switches to the section called <b>"CoolStuff"</b> (or creates it if it doesn't already exits) and it defines it as a code section. All sections within a sourcefile must be identified by a <em>unique</em> name.</p>
-
-<p>Possible section types are as follows:
-
-<dl>
-	<dt>ROM0</dt>
-	<dd>A ROM section. Mapped to memory at $0000–$3fff.</dd>
-
-	<dt>ROMX</dt>
-	<dd>A banked ROM section. Mapped to memory at $4000–$7fff. Valid banks range from 1 to 511.</dd>
-
-	<dt>VRAM</dt>
-	<dd>A banked video RAM section. Mapped to memory at $8000–$9fff. Can only allocate memory, not fill it. Valid banks range from 0 to 1.</dd>
-
-	<dt>SRAM</dt>
-	<dd>A banked external (save) RAM section. Mapped to memory at $a000–$bfff. Can only allocate memory, not fill it. Valid banks range from 0 to 3.</dd>
-
-	<dt>WRAM0</dt>
-	<dd>A general-purpose RAM section. Mapped to memory at $c000–$cfff. Can only allocate memory, not fill it.</dd>
-
-	<dt>WRAMX</dt>
-	<dd>A banked general-purpose RAM section. Mapped to memory at $d000–$dfff. Can only allocate memory, not fill it. Valid banks range from 1 to 7.</dd>
-
-	<dt>HRAM</dt>
-	<dd>A high RAM section. Mapped to memory at $ff80–$fffe. Can only allocate memory, not fill it. NOTE WELL: if you use this method of allocating HRAM the assembler will NOT choose the short addressingmode in the LD instruction because the actual address calculation is done by the linker! If you find this undesirable you can use <a href="rs.htm">RSSET/RB/RW</a> instead or use the LDIO mnemonic. The address calculation is then done by the assembler.</dd>
-</dl>
-
-<p>The following deprecated section names are aliases for some of the above sections:
-
-<dl>
-	<dt>HOME</dt>
-	<dd>Alias for ROM0.</dd>
-
-	<dt>CODE</dt>
-	<dt>DATA</dt>
-	<dd>Alias for ROMX.</dd>
-
-	<dt>BSS</dt>
-	<dd>Alias for WRAM0.</dd>
-</dl>
-
-<p>Due to quite a lot of emails requesting an ORG directive you can now add an address to the sectiontype for the Gameboy:</p>
-<pre>SECTION   "CoolStuff",ROM0[$1234]</pre>
-<p>This will force the section to address $1234. This also works with the other sectiontypes. For ROMX sections the linker  will then place the section in any bank at the address you specify. If you also want to specify the bank you can do:</p>
-<pre>SECTION   "CoolStuff",ROMX[$4567],BANK[3]</pre>
-<p>And if you only want to force the section into a certain bank, and not it's position within the bank, that's also possible:</p>
-<pre>SECTION   "CoolStuff",ROMX,BANK[7]</pre>
-<p><strong>HINT:</strong> If you think this is a lot of typing for doing a simple ORG type thing you can quite easily write an intelligent macro (called ORG for example) that uses <a href="expr_str.htm">\@</a> for the sectionname and determines correct sectiontype etc as arguments for SECTION</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="../link.htm">xLink</a> documentation
-<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-<li><a href="expr_str.htm">String expressions, functions and formatting</a>
-<li><a href="pops.htm">POPS and PUSHS:</a> The section stack.
-</ul>
-<hr>
-<p>Last updated 18 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/set.htm
+++ /dev/null
@@ -1,22 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm SET</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>SET</h1>
-<p>SETs are like <a href="equ.htm">EQUates</a> also constant symbols in the sense that their values are defined during the assembly process. These symbols are normally used in macros.</p>
-<pre>KINKYCOUNT     SET  2
-KINKYCOUNT     SET  DONUT_ISGOOD+KINKYCOUNT</pre>
-<p>Note that a colon (:) following the label-name is not allowed. SETs can be exported and imported but the result is undefined and might change in a later release. Alternatively you can use = as a synonym for SET.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="expr_int.htm">Integer and Boolean expressions</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
-
--- a/doc/asm/shift.htm
+++ /dev/null
@@ -1,19 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm SHIFT</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>SHIFT</h1>
-<p><dfn>SHIFT</dfn> is a special command only available in <a href="macro.htm">macros</a>. Very useful in <a href="rept.htm">REPT-blocks</a>. It will "shift" the arguments by one "to the left". <b>\1</b> will get <b>\2</b>'s value, <b>\2</b> will get <b>\3</b>'s value and so forth.</p>
-<h1>See also:</h1>
-<ul>
-<li><a href="macro.htm">Macros</a>
-<li><a href="rept.htm">Automatically repeating blocks of code</a>
-</ul>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/symbols.htm
+++ /dev/null
@@ -1,31 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Symbols</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>xAsm Symbols</h1>
-<p>xAsm supports several types of symbols:</p>
-<ul>
-<li><a href="labels.htm">Label</a>. Used to assign a memory location with a name
-<li><a href="equ.htm">EQUate</a>. Give a constant a name.
-<li><a href="set.htm">SET</a>. Same as EQUate but with a subtle difference. You can change the value of a SET during assembling.
-<li><a href="rs.htm">Structures (the RS group)</a>. Define a structure easily.
-<li><a href="equs.htm">String equate (EQUS)</a>. Give an often used string a name. Can also be used as a mini-macro. Much like #define in C.
-<li><a href="macro.htm">MACROs</a>. A block of code or pseudo instructions that you invoke like any other mnemonic. You can give them arguments too! Life is good.
-</ul>
-
-<p><strong>A symbol cannot have the same name as a reserved keyword.</strong></p>
-
-<h1>See also:</h1>
-<ul>
-<li><a href="presym.htm">Predeclared symbols</a>
-<li><a href="export.htm">Importing and exporting symbols</a>
-<li><a href="purge.htm">Purging symbols</a>
-</ul>
-<hr>
-<p>Last updated 02 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/syntax.htm
+++ /dev/null
@@ -1,23 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Syntax</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-
-<body>
-<h1>xAsm Syntax</h1>
-<p>The syntax line‐based, just as in any other assembler. Meaning that you do one instruction or pseudo‐op per line:</p>
-<pre>[label] [instruction] [;comment]</pre>
-<p>Example:</p>
-<pre>John:          ld   a,87 ;Weee</pre>
-<p>A comment can also be an asterisk (*) followed by the comment if the asterisk is the first character on the line:</p>
-<pre>********************************
-* These are full line comments *
-********************************</pre>
-<p>All pseudo‐ops, mnemonics and registers (reserved keywords) are <em>case‐insensitive</em> and all labels are <em>case‐sensitive</em>.</p>
-<hr>
-<p>Last updated 21 June 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/trg_gb.htm
+++ /dev/null
@@ -1,102 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Gameboy</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>Gameboy</h1>
-<p>The full GB-Z80 instruction-set is implemented with a few modifications to the original Zilog syntax. This is due to a Bison problem but in my opinion the syntax is better than the original one.</p>
-<h2>Instructions</h2>
-<ul>
-    <li>ADC
-    <li>ADD
-    <li>AND
-    <li>BIT
-    <li>CALL
-    <li>CCF
-    <li>CP
-    <li>CPL
-    <li>DAA
-    <li>DEC
-    <li>DI
-    <li>EI
-    <li>EX
-    <li>HALT
-    <li>INC
-    <li>JP
-    <li>JR
-    <li>LD
-    <li>LDD
-    <li>LDI
-    <li>LDH/LDIO    (see note below)
-    <li>NOP
-    <li>OR
-    <li>POP
-    <li>PUSH
-    <li>RES
-    <li>RET
-    <li>RETI
-    <li>RL
-    <li>RLA
-    <li>RLC
-    <li>RLCA
-    <li>RR
-    <li>RRA
-    <li>RRC
-    <li>RRCA
-    <li>RST
-    <li>SBC
-    <li>SCF
-    <li>SET
-    <li>SLA
-    <li>SRA
-    <li>SRL
-    <li>STOP
-    <li>SUB
-    <li>SWAP
-    <li>XOR
-</ul>
-<p>Note that you can use both
-<pre>    OR   A,B
-    OR   B</pre>
-<h2>Addressingmodes</h2>
-<p>Indirect addressing has been changed to [ ] instead  of ( ):</p>
-<ul>
-   <li> A
-   <li> B
-   <li> C
-   <li> D
-   <li> E
-   <li> H
-   <li> L
-   <li> AF
-   <li> BC
-   <li> DE
-   <li> HL
-   <li> SP
-   <li> [BC]
-   <li> [DE]
-   <li> [HL]
-   <li> [HL-]/[HLI]
-   <li> [HL+]/[HLD]
-   <li> [SP]
-   <li> n8       (8 bit expression)
-   <li> n16      (16 bit expression)
-   <li> n3       (3 bit CONSTANT expression)
-   <li> [n16]/[$FF00+n8]
-   <li> [$FF00+C]/[C]
-</ul>
-<p>The  assembler will intelligently decide between  <b>[n16]</b> and  <b>[$FF00+n8]</b> in the LD instruction.  Note however  that  if  you  use  any <a href="symbols.htm">constant symbols</a> in the expression they had better  be defined before the instruction or your symbol-table may become mangled. Also worth noting is that it will only ever select the short $FF00 mode when you use constant symbols. NOT if you use symbols defined in a <a href="section.htm">HRAM section</a>. As this defies the whole point of implementing the HRAM sectiontype I've added the LDIO mnemonic. It works like the LD instruction but it will ALWAYS generate the $FF00+ form and it will also automatically logically AND the expression with $FF if it is relocatable. Which is what you want. Trust me ;)</p>
-<h2>Conditioncodes</h2>
-<ul>
-<li>    C
-<li>    NC
-<li>    Z
-<li>    NZ
-</ul>
-<hr>
-<p>Last updated 20 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/asm/usage.htm
+++ /dev/null
@@ -1,30 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xAsm Usage</title>
-        <link rel="stylesheet" type="text/css" href="../style.css">
-</head>
-<body>
-<h1>xAsm Usage</h1>
-<pre>C:\>xAsm [options] asmfile</pre>
-<p>Options are preceded by a hyphen (-) and go as follows:</p>
-<pre>    o<b>objectfile</b> : Write an <a href="../rgb0.htm">object-file</a> for <a href="../link.htm">xLink</a>
-    i<b>path</b>       : Add an extra include-path
-    h           : Short help text
-    e<b>(l|b)</b>      : Change endianness (CAUTION!)
-    g<b>ASCI</b>       : Change the four characters used for Gameboy graphics
-                  constants (default is <b>0123</b>)
-    b<b>AS</b>         : Change the two characters used for binary constants
-                  (default is <b>01</b>)
-    z<b>HX</b>         : Set the byte value (hex format) used for uninitialised data (default is ? for random)
-</pre>
-
-<h1>See also:</h1>
-<ul>
-<li><a href="opt.htm">Changing options while assembling</a>
-</ul>
-<hr>
-<p>Last updated 08 October 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/geninfo.htm
+++ /dev/null
@@ -1,116 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>General Information</title>
-	<link rel="stylesheet" type="text/css" href="./style.css">
-</head>
-<body>
-<h1><abbr title="Rednex Game Boy Development System">RGBDS</abbr>—ASMotor General Information</h1>
-<h2>Table of Contents</h2>
-<ul>
-	<li><a href="#license">License</a>
-	<li><a href="#Author">The Author</a>
-	<li><a href="#Introduction">Introduction</a>
-	<li><a href="#Installation">Installation</a>
-	<li><a href="#Documentation">The Documentation</a>
-	<li><a href="#History">History</a>
-</ul>
-<h2 id="license">License</h2>
-<p>The <dfn>ASMotor</dfn> package (<a href="asm.htm">xAsm</a>, <a href="link.htm">xLink</a>, <a href="fix.htm">RGBFix</a>, examples and <a href="#Documentation">documentation</a>) is freeware and distributed as is. The author retains his copyright and right to modify the specifications and operation of the software without notice.
-<p>In other words this means I encourage you to…
-<ul>
-	<li>use it for whatever purpose even professional work without me charging you a penny
-	<li>copy it to another person (wholly or in part, though I’m sure he’d appreciate the whole package) in
-whatever form you find suitable
-	<li>mass-distribute the ASMotor package if it is complete (<a href="asm.htm">xAsm</a>, <a href="link.htm">xLink</a>, <a href="fix.htm">RGBFix</a> and documentation).
-	<li>contact me if you have any problems
-</ul>
-<p>This also means you can’t…
-<ul>
-	<li>blame me for loss of profit, data, sleep, food or other nasty things through the use or distribution of ASMotor. If
-you choose to use ASMotor you do so at your own risk.
-	<li>expect me to be able to help you should you have a problem related or not to ASMotor.
-</ul>
-<h2 id="Author">The Author</h2>
-<p>Any questions? Write me!
-<h3>Address</h3>
-<p>
-Carsten Sorensen<br>
-1 Spring Court<br>
-Guildford<br>
-Surrey GU2 6QW<br>
-United Kingdom<br>
-<h3 id="Email">e-mail:</h3>
-<ul>
-	<li><a href="mailto:[email protected]">[email protected]</a> (private)
-	<li><a href="mailto:[email protected]">[email protected]</a> (work)
-</ul>
-<p>Get the latest version from my web page at <a href="http://www.matilde.demon.co.uk">http://www.matilde.demon.co.uk</a>
-<h2 id="History">History</h2>
-<table>
-	<caption>The history of ASMotor</caption>
-<thead>
-<tr>
-	<th>Version</th>
-	<th>Dated</th>
-	<th>Release notes</th>
-</tr>
-</thead>
-<tr>
-	<td>1.0</td>
-	<td>03 July 1997</td>
-	<td>First release</td>
-</tr>
-<tr>
-	<td>1.01</td>
-	<td>20 July 1997</td>
-	<td><p>RGBDS fixes:</p>
-<ul>
-	<li>RGBFix can now also truncate the ROM-images to a valid size.
-	<li>RGBAsm supports the LDD and LDI syntax plus [HLD] and [HLI]. LDH is synonymous with LDIO.
-	<li>Example filenames have been changed to adhere to Jeff Frohweins proposed standard.
-</ul>
-	<p>General fixes:</p>
-<ul>
-	<li>RGBLink knows about big and little endian. Plus it can do range checking on intermediate results in an expression. This is necessary to support
-different types of CPUs.
-	<li>RGBLink <em>didn’t</em> know about the special PC symbol “@” so if you used it more than once per sourcefile in an expression the linker had to resolve, things would go horribly wrong.
-	<li>There was a bug in the macro parameter passing. Any whitespace after the last parameter would be appended to the last parameter. Reported by Jeff Frohwein.
-	<li>A section stack has been implemented. Look up POPS and PUSHS in the
-manual. Jeff Frohwein’s doing again.
-	<li>OPT command added for defining and changing some options while assembling.
-	<li>You can now define which characters are used for the Gameboy graphics integer (`) using the commandline or the new OPT command. Cool idea by (surprise surprise) Jeff Frohwein.
-	<li>Also, an option stack has been added. Look up POPO and PUSHO in the manual.
-	<li>Fixed yet another line number bug reported by Jeff Frohwein (when will this guy leave me alone? ;)
-</ul>
-</td>
-<tr>
-	<td>1.02</td>
-	<td>22 July 1997</td>
-	<td><p>General fixes:</p>
-<ul>
-	<li>The lamest typo bug of all time has been fixed. RGBAsm would output a word defined with DW as 4 bytes instead of 2. Jeff Frohwein reported this.
-	<li>The first line of an included file didn’t assemble correctly.
-	<li>-b option added for setting the characters used for binary constants.
-</ul>
-</td>
-</tr>
-<tr>
-	<td>1.10</td>
-	<td>21 Sep 1997</td>
-	<td><p>General fixes:</p>
-<ul>
-	<li>The assembler would crash if you tried to use a macro symbol in an expression.  (Jeff Frohwein)
-	<li>You couldn’t use STRCMP, STRLEN and STRIN in relocatable expressions. (Harry P. Mulder)
-	<li>Relocatable symbols are no longer allowed as arguments to the DEF function.
-	<li>Finally! A librarian and smart linking has been added.
-	<li>Bug fixed in the assembler where it would sometimes write out too many bytes for HRAM section definitions.
-	<li>-z options (set fill value used for uninitialised data) added to the
-assembler and linker.
-	<li>The assembler will now read in any type of ASCII file on any type of OS.
-</ul>
-</table>
-<p>Last updated 08 October 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/index.htm
+++ /dev/null
@@ -1,20 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>RGBDS—ASMotor Documentation</title>
-	<link rel="stylesheet" type="text/css" href="./style.css">
-</head>
-<body>
-<h1><abbr title="Rednex Game Boy Development System">RGBDS</abbr>—ASMotor v1.10 Documentation</h1>
-<h2>Table of Contents</h2>
-<ul>
-	<li><a href="geninfo.htm">ASMotor General Information</a>
-	<li><a href="asm.htm">xASM Documentation</a>
-	<li><a href="link.htm">xLink Documentation</a>
-	<li><a href="fix.htm">RGBFix Documentation</a>
-	<li><a href="rgb0.htm">The RGB0-2 ObjectFileFormat</a>
-</ul>
-<p>Last updated 21 September 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/link.htm
+++ /dev/null
@@ -1,118 +1,0 @@
-<!DOCTYPE HTML PUBliC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>xLink</title>
-        <link rel="stylesheet" type="text/css" href="./style.css">
-</head>
-<body>
-<h1>xLink Documentation</h1>
-<h2>Table of Contents</h2>
-<ul>
-<li><a href="#history"> History</a>
-<li><a href="#usage"> Usage</a>
-<li><a href="#linkfile"> The Linkfile</a>
-<li><a href="#operationtg"> Operation for Gameboy</a>
-<li><a href="#smallmode"> Operation for Gameboy small mode</a>
-<li><a href="#psion2"> Operation for Psion2 relocatable modules</a>
-</ul>
-<hr>
-<h2 id="history">History</h2>
-<table>
-	<caption>The history of xLink</caption>
-<thead>
-<tr>
-	<th scope="col">Version</th>
-	<th scope="col">Dated</th>
-	<th scope="col">Release notes</th>
-</tr>
-</thead>
-<tr>
-	<td>1.0</td>
-	<td>1 Oct. 96</td>
-	<td>First release (RGBDS)</td>
-</tr>
-<tr>
-	<td>1.01</td>
-	<td>3 Dec. 96</td>
-	<td>
-<ul>
-	<li>BANK() didn't work. Fixed.</li>
-	<li>Sections were quite often output in the wrong order. Fixed.</li>
-</ul>
-</tr>
-<tr>
-	<td>1.02</td>
-	<td>12 Feb. 97</td>
-	<td><a href="#usage">-s switch and mapfile option</A> added</td>
-</tr>
-<tr>
-	<td>1.03</td>
-	<td>23 Mar. 97</td>
-	<td>
-<ul>
-	<li><a href="#usage">Mapfile</A> now shows BSS, VRAM and HRAM areas</li>
-	<li>There was a bug regarding <a href="#operation">fixed HOME sections.</a>
-</ul></td>
-</tr>
-<tr>
-	<td>1.04</td>
-	<td>03 July 1997</td>
-	<td>First ASMotor release. Supports big-endian CPUs as well. <a href="#usage">Usage</a> changed to allow for different 	output fileformats</td>
-</tr>
-<tr>
-	<td>1.05</td>
-	<td>20 July 1997</td>
-	<td>
-<ul>
-	<li>We can now do range checking on intermediate results in an expression. This is necessary to support different types of CPUs.</li>
-	<li>RGBLink DIDN’T know about the special PC symbol "@" so if you used it more than once per sourcefile in an expression the linker had to resolve, things would go horribly wrong.</li>
-</ul>
-</td>
-<tr>
-	<td>1.06</td>
-	<td>21 September 1997</td>
-	<td><ul><li>Smart linking and library support added
-	<li>Program renamed to xLink
-</ul>
-</td>
-</table>
-<h2 id="usage">Usage</h2>
-<pre>    xlink [options] linkfile</pre>
-<p>Options are preceded by a hyphen (-) and go as follows:
-<pre>    h         : Short help text
-    m<b>mapfile</b>  : Write a mapfile
-    t         : Output target:
-      tg      : Gameboy <a href="#operationtg">ROM image</a> (default)
-      ts      : Gameboy <a href="#smallmode">Small mode (32kB)</a> ROM image
-      tp      : <a href="#psion2">Psion2</a> relocatable module
-    z<b>HX</b>       : Set the byte value (hex format) used for uninitialised data (default is ? for random)
-</pre>
-<h2 id="linkfile">The Linkfile</h2>
-<p>A linkfile is used to tell <B>xLink</B> which objects to include and what the outputname should be. It is in plain ASCII-format.
-<pre>    # Linkfile for foobar.gb
-      
-    [Objects]
-    foo.obj
-    bar.obj
-      
-    [Libraries]
-    mylib.lib
-
-    [Output]
-    foobar.gb</pre>
-<p>A line starting with # is ignored.
-<p>If you use libraries they will only be included if one of the objects actually reference them. This works on a SECTION level and not on a module level. This means that when you write libraries you can put each subroutine in its own SECTION so only the relevant bits are included.
-<h2 id="operationtg">Operation for Gameboy (-tg)</h2>
-<p><a href="asm.htm#sections">Sections</a> created with <b>ROM0</b> in the assembler are placed in the GB bank #0 (the fixed bank $0000-$3FFF) in the order they are loaded from the objectfiles specified in the linkfile. So you want the first file in the linkfile to contain your header. <b>ROMX</b> sections are placed in <em>any bank other than #0</em>. This means you have absolutely <em>no</em> control over which sections goes where. This insures minimal slack (unused bytes) at the end of each bank in the image.
-<p>Currently  the linker doesn't calculate the GB checksums.
-You must use <a href="fix.htm">RGBFix</a> to do this.
-
-<h3 id="smallmode">Operation for Gameboy small mode (-ts)</h3>
-<p>Small mode forces all <b>ROMX</b> sections to be of type <b>ROM0</b> and increases the <b>ROM0</b> section size from 16kB to 32kB. This also means that <b>ROM0/ROMX</b> sections are written to the final image in the order you have specified on the command line.
-<p>Currently  the linker doesn't calculate the GB checksums. You must use <a href="fix.htm">RGBFix</a> to do this.
-
-<hr>
-<p>Last updated 08 October 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>
--- a/doc/rgb0.htm
+++ /dev/null
@@ -1,210 +1,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-	<title>RGB? Fileformat</title>
-        <link rel="stylesheet" type="text/css" href="./style.css">
-</head>
-<body>
-<h1>The RGB ObjectFileFormats</h1>
-<h2>Table of Contents</h2>
-<ul>
-	<li><a href="#background">Background</A>
-	<li><a href="#filestructure">FileStructure</A>
-	<li><a href="#rpn">Rpn Data</A>
-</ul>
-<h2 id="background">Background</h2>
-<p>I developed the RGB0 fileformat mainly because I needed a suitable dataformat to hold the output from <a href="asm.htm">xAsm</a> that was powerful to accomodate all the features I needed and also would make it easy for me to add new ones. The reason for documenting it is so people can write converters between it and other formats. Perhaps even develop other compilers for it?</p>
-<p>The RGB1 fileformat saw the light of day with the V1.02 of the old RGBDS release because of the addition of fixed sections.</p>
-<p>The RGB2 fileformat emerged because I needed to add support for big endian CPUs.</p>
-<h2 id="filestructure">FileStructure</h2>
-<ul>
-	<li><dfn>LONG</dfn> is a 32‐bit integer stored in little‐endian  format (Intel)
-	<li><dfn>BYTE</dfn> is an 8‐bit integer
-	<li><dfn>STRING</dfn> is a 0‐terminated string of <b>BYTE</b>
-</ul>
-<p>Down to business...</p>
-<pre>
-    ; There's a header...
-      
-    BYTE    ID[4]                      ;"RGB0", "RGB1", "RGB2"
-    LONG    NumberOfSymbols            ;The number of symbols used in this file
-    LONG    NumberOfSections           ;The number of sections used in this file
-      
-    ; Now for some symbols
-      
-    REPT    NumberOfSymbols            ;<b>NumberOfSymbols</b> symboldefs follow
-        STRING  Name                   ;The name of this symbol
-        BYTE    Type                   ;0 = LOCAL symbol only used in this file
-                                       ;1 = IMPORT this symbol from elsewhere
-                                       ;2 = EXPORT this symbol to other objects
-        IF      Type != 1
-            LONG    SectionID          ;The section number in which this symbol
-                                       ;is defined.  If -1 this symbol is an EQUate
-            LONG Value                 ;The symbols value. If SectionID!=-1 it's the
-                                       ;offset into that section
-        ENDC
-    ENDR
-      
-    ; And I'll be... Sections!
-      
-    REPT NumberOfSections
-        LONG    Size                   ;Size in bytes of this section
-        BYTE    Type                   ;0 = WRAM0
-                                       ;1 = VRAM
-                                       ;2 = ROMX
-                                       ;3 = ROM0
-                                       ;4 = HRAM
-        LONG    Org                    ;Only present in RGB1. Address to fix this
-                                       ;section at. -1 if the linker should
-                                       ;decide (normal operation)
-        LONG    Bank                   ;Only present in RGB1. Bank to load this
-                                       ;section into. -1 if the linker should
-                                       ;decide (normal operation). This field is
-                                       ;only valid for ROMX sections.
-        IF      Type==ROMX || Type==ROM0
-            BYTE Data[Size]
-            LONG NumberOfPatches
-               
-            ; These types of sections may have patches
-               
-            REPT NumberOfPatches
-                STRING    SourceFile   ;The name of the sourcefile (for
-                                       ;printing an errormessage)
-                LONG Line              ;The line of the sourcefile
-                LONG Offset            ;Offset into the section where patch
-                                       ;should be applied
-                BYTE Type              ;0 = BYTE patch
-                                       ;1 = little endian WORD patch
-                                       ;2 = little endianLONG patch
-                                       ;3 = big endian WORD patch (RGB2 and later)
-                                       ;4 = big endianLONG patch (RGB2 and later)
-                LONG RPNSize
-                BYTE RPN[RPNSize]      ;RPN definition below
-            ENDR
-        ENDC
-    ENDR</pre>
-<h2 id="rpn">Rpn Data</h2>
-<p>Expressions in the objectfile are stored as <abbr title="Reverse Polish Notation">RPN</abbr>. This is an expression of the form “2 5 +”. This will first push the value “2” to the stack. Then “5”. The “+” operator pops two arguments from the stack, adds them, and then pushes the result on the stack, effectively replacing the two top arguments with their sum. In the RGB format RPN expressions are stored as <b>BYTE</b>s with some bytes being special prefixes for integers and symbols.</p>
-<table>
-	<caption>RPN Expressions</caption>
-<thead>
-<tr>
-	<th scope="col">Byte value</th>
-	<th scope="col">Meaning</th>
-</tr>
-</thead>
-<tr>
-	<td>$00</td>
-	<td>+ operator</td>
-</tr>
-<tr>
-	<td>$01</td>
-	<td>- operator</td>
-</tr>
-<tr>
-	<td>$02</td>
-	<td>* operator</td>
-</tr>
-<tr>
-	<td>$03</td>
-	<td>/ operator</td>
-</tr>
-<tr>
-	<td>$04</td>
-	<td>% operator</td>
-</tr>
-<tr>
-	<td>$05</td>
-	<td>unary -</td>
-</tr>
-<tr>
-	<td>$06</td>
-	<td>| operator</td>
-</tr>
-<tr>
-	<td>$07</td>
-	<td>& operator</td>
-</tr>
-<tr>
-	<td>$08</td>
-	<td>^ operator</td>
-</tr>
-<tr>
-	<td>$09</td>
-	<td>unary ~</td>
-</tr>
-<tr>
-	<td>$0A</td>
-	<td>&& comparison</td>
-</tr>
-<tr>
-	<td>$0B</td>
-	<td>|| comparison</td>
-</tr>
-<tr>
-	<td>$0C</td>
-	<td>unary !</td>
-</tr>
-<tr>
-	<td>$0D</td>
-	<td>== comparison</td>
-</tr>
-<tr>
-	<td>$0E</td>
-	<td>!= comparison</td>
-</tr>
-<tr>
-	<td>$0F</td>
-	<td>&gt comparison</td>
-</tr>
-<tr>
-	<td>$10</td>
-	<td>&lt comparison</td>
-</tr>
-<tr>
-	<td>$11</td>
-	<td>&gt= comparison</td>
-</tr>
-<tr>
-	<td>$12</td>
-	<td>&lt= comparison</td>
-</tr>
-<tr>
-	<td>$13</td>
-	<td>&lt&lt operator</td>
-</tr>
-<tr>
-	<td>$14</td>
-	<td>&gt&gt operator</td>
-</tr>
-<tr>
-	<td>$15</td>
-	<td>BANK() function for Gameboy, a symbol ID follows</td>
-</tr>
-<tr>
-	<td>$16</td>
-	<td>HRAMCheck for Gameboy, check if value is in HRAM and logically and it with 0xFF</td>
-</tr>
-<tr>
-	<td>$17</td>
-	<td>ZeroPageCheck for PC-Engine, check if value is in ZP (0x2000-0x20FF) and logically and it with 0xFF</td>
-</tr>
-<tr>
-	<td>$18</td>
-	<td>RangeCheck. LOW and HIGH signed LONGs follow. Checks a value to see if within the range [LOW;HIGH]. If not, generate an error.
-</td>
-</tr>
-<tr>
-	<td>$80</td>
-	<td>LONG integer follows</td>
-</tr>
-<tr>
-	<td>$81</td>
-	<td>Symbol ID follows</td>
-</tr>
-</table>
-<hr>
-<p>Last updated 18 July 1997 by <a href="mailto:[email protected]">Carsten Sorensen</a></p>
-</body>
-</html>