tDocumentation updated and made properly HTML 4.01 Strict compliant - vaccinewars - be a doctor and try to vaccinate the world
(HTM) git clone git://src.adamsgaard.dk/vaccinewars
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) README
(DIR) LICENSE
---
(DIR) commit 33aa3c702c9ba3c42f18d2263d5e63e227028c13
(DIR) parent 63e0da7145c73373c9115dcd2e59097c3119a5b6
(HTM) Author: Ben Webb <ben@salilab.org>
Date: Sun, 13 May 2001 21:04:38 +0000
Documentation updated and made properly HTML 4.01 Strict compliant
Diffstat:
M doc/aiplayer.html | 23 +++++++++++++----------
M doc/clientplay.html | 135 ++++++++++++++++---------------
M doc/commandline.html | 46 +++++++++++++++++--------------
M doc/configfile.html | 57 ++++++++++++++++---------------
M doc/credits.html | 50 +++++++++++++++++--------------
M doc/developer.html | 17 ++++++++++-------
M doc/i18n.html | 84 ++++++++++++++++---------------
M doc/index.html | 22 ++++++++++++----------
M doc/installation.html | 91 ++++++++++++++++++-------------
M doc/metaserver.html | 79 ++++++++++++++++---------------
M doc/server.html | 49 ++++++++++++++++---------------
M doc/servercommands.html | 9 ++++++---
M doc/windows.html | 25 ++++++++++++++-----------
13 files changed, 371 insertions(+), 316 deletions(-)
---
(DIR) diff --git a/doc/aiplayer.html b/doc/aiplayer.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Adding computer-controlled players</title>
t@@ -6,16 +9,16 @@
<body>
<h1>Adding computer-controlled players</h1>
-Multiplayer games of dopewars can be made a little more interesting by
+<p>Multiplayer games of dopewars can be made a little more interesting by
introducing computer-controlled, or AI, players. These players will join
a dopewars server, and to all intents and purposes will behave like normal
human players - they will deal in drugs in an attempt to make a fortune,
they will encounter the cops, you can spy on them, and they will shoot at
-you if you give them the chance!<p>
+you if you give them the chance!</p>
-To start a computer-controlled player, all you need is the standard dopewars
+<p>To start a computer-controlled player, all you need is the standard dopewars
binary. Run it as<br>
-<b>dopewars -c</b><br>
+<tt><b>dopewars -c</b></tt><br>
and it will attempt to connect to the server and port specified in the
<a href="configfile.html">configuration files</a> (or the local host, if none
is specified). Alternatively, you can specify server and port with suitable
t@@ -23,9 +26,9 @@ is specified). Alternatively, you can specify server and port with suitable
takes its game settings from the server it connects to, no other options in
the configuration files will take effect, with the exception of the
<a href="configfile.html#AITurnPause">AITurnPause</a> option, which sets the
-pause in seconds between turns.<p>
+pause in seconds between turns.</p>
-Once started and connected to the server, the AI player will choose a
+<p>Once started and connected to the server, the AI player will choose a
suitable name for itself and start playing. It will continue to play until
its game finishes - i.e. it is killed or runs out of time - at which point
the program will finish and drop you back to the command prompt. The program
t@@ -35,21 +38,21 @@ whatever you have set AITurnPause to be) before jetting to a new location -
this is to simulate the time it takes a human player to choose which drugs
to buy and to press all the requisite keys; it also gives other players a
fighting chance of spotting the computer sitting still in any one location
-for a few seconds!<p>
+for a few seconds!</p>
-If a computer player is attacked by the cops or another player, it will
+<p>If a computer player is attacked by the cops or another player, it will
defend itself if it can, and attempt to run if necessary. During normal
play it will also attempt to "blend in" with the other players by hurling
rather pathetic insults at them... you are free to edit the code of the
AI player to give these insults a little more "punch", or
<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">email</a> them to me (preferably
without actually directing the insults themselves at me!) and I'll add them
-to the next dopewars release.
+to the next dopewars release.</p>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>30-9-99</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/clientplay.html b/doc/clientplay.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Playing the game: the dopewars client</title>
t@@ -6,23 +9,23 @@
<body>
<h1>Playing the game: the dopewars client</h1>
-The dopewars client is the part of dopewars which most users will
+<p>The dopewars client is the part of dopewars which most users will
encounter most frequently. If the dopewars binary is run without the
<b>-s</b> (server) or <b>-c</b> (computer player) options (see
<a href="commandline.html">command line options</a>) it defaults to running
in client mode. The dopewars client handles the interaction between a
human player and the dopewars server (but if a dopewars server is not
available, a "virtual" server will be run by the client to enable a
-single-player game to be played).<p>
+single-player game to be played).</p>
-A brief description of using the client and playing dopewars is given here.
+<p>A brief description of using the client and playing dopewars is given here.
These instructions apply to the old-style text-mode client, but the basic
game play is similar for the newer graphical client.
Bear in mind that both the client and the server you are connecting to can
be configured by means of the dopewars <a href="configfile.html">
configuration files</a>, and so the game may differ radically from what is
described here. It is suggested that you familiarise yourself with the game
-using the default settings before getting too adventurous!<p>
+using the default settings before getting too adventurous!</p>
<ul>
<li><a href="#startup">Starting the dopewars client</a>
t@@ -34,20 +37,20 @@ using the default settings before getting too adventurous!<p>
<li><a href="#multiplayer">Multiplayer: interacting with other players</a>
</ul>
-<a name="startup"><h2>Starting the dopewars client</h2></a>
+<h2><a name="startup">Starting the dopewars client</a></h2>
<ul>
<li>From the command prompt, run the dopewars client with the command<br>
-<b>dopewars</b><br>
+<tt><b>dopewars</b></tt><br>
or to run an <a href="commandline.html#antique">"antique"</a> mode game,<br>
-<b>dopewars -a</b>
+<tt><b>dopewars -a</b></tt>
<li>An introduction screen will appear, giving a brief description of the
game and version and licensing information. Press any key to clear this.
</ul>
-<a name="screen"><h2>The main game screen</h2></a>
+<h2><a name="screen">The main game screen</a></h2>
-The game screen is your interface with the dopewars world. At the top of the
+<p>The game screen is your interface with the dopewars world. At the top of the
screen, from left to right, is displayed the game date, the game location
(you start in the Bronx), the number of bitches working for you, and the
space you have available for drugs. Note that each drug uses up one "space",
t@@ -55,30 +58,30 @@ but some guns may take up more.
Your "bitches" are your subordinates - each bitch increases your "space"
by 10 (you yourself start with a space of 20) and can carry one gun (you can
carry two). Your bitches also take damage for you when in firefights, so it
-is advantageous to acquire extra bitches during the game.<p>
+is advantageous to acquire extra bitches during the game.</p>
-Below the top line of the screen are three large windows. The one in
+<p>Below the top line of the screen are three large windows. The one in
the top left lists your statistics - your finances, the health of yourself
or your bitches, and the number of guns you are carrying. Notice that you
start the game with a debt - this will increase, turn by turn, until you
pay it off to the Loan Shark. The top right window lists the drugs that you
are currently carrying (you start off with none). Below this is a window in
-which messages from other players (if any) will appear.<p>
+which messages from other players (if any) will appear.</p>
-Please note that if you are playing in <a href="commandline.html#antique">
+<p>Please note that if you are playing in <a href="commandline.html#antique">
"antique"</a> mode, you do not have "bitches" but instead have a large
trenchcoat which can carry 100 drugs. Antique mode also disables the
-messages window.<p>
+messages window.</p>
-<a name="server"><h2>Connecting to a dopewars server (or not)</h2></a>
+<h2><a name="server">Connecting to a dopewars server (or not)</a></h2>
-On starting a game of dopewars, the first thing you must do is give
+<p>On starting a game of dopewars, the first thing you must do is give
yourself a name. This identifies you to the server and to other players. If
you are running in <a href="commandline.html#singleplayer">single-player</a>
or <a href="commandline.html#antique">antique</a> mode, the client will
-then start an internal "virtual" server and immediately start the game.<p>
+then start an internal "virtual" server and immediately start the game.</p>
-In other cases, the client will attempt to connect to a dopewars server
+<p>In other cases, the client will attempt to connect to a dopewars server
specified in the <a href="configfile.html#Server">configuration file</a> or
on the <a href="commandline.html#server">command line</a> (if none is
specified, it defaults to the local host). If this connection is successful,
t@@ -87,19 +90,19 @@ choose a different server, obtain the server list from the metaserver and
choose one, play a single-player game, or quit, by pressing the
C, L, P, or Q keys respectively. If you don't want the client to attempt to
connect to a server, this can be set - full details are given in the section
-on <a href="configfile.html#Server">configuration files</a>.<p>
+on <a href="configfile.html#Server">configuration files</a>.</p>
-<a name="dealing"><h2>Dealing drugs and moving around</h2></a>
+<h2><a name="dealing">Dealing drugs and moving around</a></h2>
-The New York of dopewars is divided into 8 (6 in "antique" mode) locations.
+<p>The New York of dopewars is divided into 8 (6 in "antique" mode) locations.
At each of these locations, a variety of drugs, with fluctuating prices, are
on sale. Not all of the drugs are necessarily on sale at each location all
of the time, and the normally gentle fluctuations may be affected by such
events as other dealers flooding the market with drugs, or the cops making
a big drugs bust (which will drive the price up). On arriving at a new
-location, you will be told if any of these "special" events have occurred.<p>
+location, you will be told if any of these "special" events have occurred.</p>
-The main way to make money in dopewars is to buy and sell drugs, buying
+<p>The main way to make money in dopewars is to buy and sell drugs, buying
cheaply at one location, and then moving ("jetting") to a new location (a
process which uses up one "day" or turn), and then selling for a profit at
this new location. When you have arrived at a location, you will be told which
t@@ -108,16 +111,16 @@ key, then pressing the letter for the drug you wish to buy, and then entering
the number of this drug you require. Bear in mind that you may not be able
to afford or carry these drugs! Selling drugs is similar, on pressing the "S"
key. When you are done and wish to "jet" to a new location, press the "J" key
-and then choose the location number.<p>
+and then choose the location number.</p>
-If you are at a location where you cannot sell your drugs, you can drop them
+<p>If you are at a location where you cannot sell your drugs, you can drop them
to free up space in your inventory (with the "D" key). Of course, this does
not get you any money, and there is a chance that the cops may catch you in
-the act and attack you (see below).<p>
+the act and attack you (see below).</p>
-<a name="finance"><h2>Your finances: loans and banks</h2></a>
+<h2><a name="finance">Your finances: loans and banks</a></h2>
-Buying and selling drugs may make money, but unfortunately you start the game
+<p>Buying and selling drugs may make money, but unfortunately you start the game
with a debt to the loan shark of $5,000. Every turn this accumulates
interest, and counts against your total amount of money at the end of the
game (which is used as your high score, so it's quite possible to end with
t@@ -126,23 +129,23 @@ jetting to the Bronx. You will be asked if you wish to visit the loan shark -
respond by pressing the "Y" key - and then asked how much money you want to
give him. Respond by entering the amount of money, without the $ sign or
commas, and ended with "k" or "m" as shorthand for "thousand" or "million"
-if you like (i.e. entering "2.5k" is the same as "2000", which is $2,000).<p>
+if you like (i.e. entering "2.5k" is the same as "2000", which is $2,000).</p>
-You can also deposit or withdraw money from the bank, which is also located
+<p>You can also deposit or withdraw money from the bank, which is also located
in the Bronx. This is done in a similar way to paying the loan shark. Putting
your money in the bank lets you accumulate interest on it, and prevents it
from being stolen if you are mugged (which does occasionally happen). Money
-in the bank also contributes to your high score at the end of the game.<p>
+in the bank also contributes to your high score at the end of the game.</p>
-<a name="cops"><h2>Law enforcement and why it's a bad thing</h2></a>
+<h2><a name="cops">Law enforcement and why it's a bad thing</a></h2>
-When you jet to a new location, one or more "random events" may occur.
+<p>When you jet to a new location, one or more "random events" may occur.
Usually this is just something such as a drug bust which affects drug prices,
but there are a number of other beneficial, useless, or just plain annoying
random events. Perhaps the most annoying of these is an encounter with the
-cops, in the form of Officer Hardass or Bob and their deputies.<p>
+cops, in the form of Officer Hardass or Bob and their deputies.</p>
-When you meet Officer Hardass, you must decide what to do. If you don't have
+<p>When you meet Officer Hardass, you must decide what to do. If you don't have
any guns, you must answer Y (yes) or N (no) to the question "Do you run?"
If you are lucky, you'll get away - otherwise, the cops may shoot you. The
more deputies are accompanying Hardass, the worse the damage is likely to be.
t@@ -150,66 +153,66 @@ If you take enough damage for your health to drop to zero, you will lose a
bitch (and, possibly, some drugs and a gun, if the bitch was carrying them).
If you have no bitches, you will die, and the game will end! The more
successful your drug dealing is (i.e. the more money you have made) the
-more aggressive the cops will be.<p>
+more aggressive the cops will be.</p>
-If, on the other hand, you have acquired one or more guns, you can either run
+<p>If, on the other hand, you have acquired one or more guns, you can either run
("R" key) or fight ("F"). Guns may be offered to you at bargain prices
randomly, or you can visit the gun shop in the Ghetto and buy or sell them.
To beat the cops by fighting them, you must kill all the deputies, one by one,
and then finally Officer Hardass. Bear in mind that the more guns you have, the
more damage you will do to the cops! If you kill Officer Hardass, you can take
whatever money you find on his corpse, and if you are lucky a doctor will
-offer to "sew you up" (i.e. restore your health to 100) for a price.<p>
+offer to "sew you up" (i.e. restore your health to 100) for a price.</p>
-If, after killing Officer Hardass, you are unlucky enough to meet the cops
+<p>If, after killing Officer Hardass, you are unlucky enough to meet the cops
again later on, they will be lead by his replacement, Officer Bob, who is
tougher. If you then kill him too, you'll meet tougher opposition in future -
-so it's often wise to run from the cops!<p>
+so it's often wise to run from the cops!</p>
-If you lose bitches, or simply want to acquire more, you can visit the pub
+<p>If you lose bitches, or simply want to acquire more, you can visit the pub
in the Ghetto to hire them, or they may offer their services to you at
-bargain rates randomly.<p>
+bargain rates randomly.</p>
-Some locations are more heavily policed than others. In addition to being
+<p>Some locations are more heavily policed than others. In addition to being
attacked on your travels, you also run a high risk of being shot at by the
cops if you drop drugs (dispose of drugs that you can't get any cash for)
-or if you attack other players.<p>
+or if you attack other players.</p>
-<a name="multiplayer"><h2>Multiplayer: interacting with other players</h2></a>
+<h2><a name="multiplayer">Multiplayer: interacting with other players</a></h2>
-If you log on to a dopewars server, there is the possibility of meeting other
+<p>If you log on to a dopewars server, there is the possibility of meeting other
players, either human or computer-controlled. When joining a game which
already contains other players, they will be listed to you. Other players
which join or leave the game once you are playing will announce their
-presence to you automatically via. the "Messages" window.<p>
+presence to you automatically via. the "Messages" window.</p>
-When in multiplayer mode, you can send a message to all current players by
+<p>When in multiplayer mode, you can send a message to all current players by
pressing the "T" key from the main drug prices screen, and then typing in
your message. To send a private message, use the "P" key and select the
-player instead. These messages will appear in the Messages window also.<p>
+player instead. These messages will appear in the Messages window also.</p>
-Another new command in multiplayer mode is the list command ("L" key). This
+<p>Another new command in multiplayer mode is the list command ("L" key). This
will either list the other players in the game, or the list of high scores
-maintained by the server which you're connected to.<p>
+maintained by the server which you're connected to.</p>
-The "G" key activates the "give errand" command. With this you can sack one
+<p>The "G" key activates the "give errand" command. With this you can sack one
of your bitches (with the "G" key again), pay one to tip off the cops to one
of the other players, or pay one to leave your employment and to join another
player and spy on them for you. In any case, if you lose a bitch you may
also lose any drugs or guns which they were carrying (remember that each
bitch can carry one gun, and increases your inventory - your available space -
-by 10).<p>
+by 10).</p>
-A tip-off means that Officer Hardass or Bob will attack your chosen
+<p>A tip-off means that Officer Hardass or Bob will attack your chosen
enemy when they jet to their next location (and then you will get to hear
-the result of the encounter). A spy, on the other hand, will present himself to the enemy as
-a bargain bitch (in the same way as normal "bargain bitches" appear). If your
-enemy accepts the bitch, you will then be able to see everything about the
-enemy whenever you like, by pressing the "C" key from the main drug prices
-screen. Unfortunately, there is a chance that your spy may be discovered by
-your opponent later on...<p>
-
-If, in the course of normal play, you are carrying one or more guns, and you
+the result of the encounter). A spy, on the other hand, will present himself to
+the enemy as a bargain bitch (in the same way as normal "bargain bitches"
+appear). If your enemy accepts the bitch, you will then be able to see
+everything about the enemy whenever you like, by pressing the "C" key from the
+main drug prices screen. Unfortunately, there is a chance that your spy may be
+discovered by your opponent later on...</p>
+
+<p>If, in the course of normal play, you are carrying one or more guns, and you
jet to the a location where another player already is, you will be informed of
their presence. You can either ignore them completely (with the "E" key)
in which case they will never know you were there, or you can attack them
t@@ -218,9 +221,9 @@ you, the main screen which normally lists drug prices at the current location
is replaced by the fighting screen. You can switch back from this screen to
the drug price screen with the "D" key, but note that the "Jet" command is now
missing from the drug price screen - you must instead use the "F" key to
-return to the fight, and conclude it before continuing on your way.<p>
+return to the fight, and conclude it before continuing on your way.</p>
-When in a fight with another player, you can choose not to fire back with the
+<p>When in a fight with another player, you can choose not to fire back with the
"S" key, you can shoot back with the "F" key, or you can run from the fight
with the "R" key. Be aware that if you fail to shoot back at your enemy
within five seconds, they can fire at you again (otherwise, shots alternate
t@@ -229,12 +232,12 @@ are awarded a bounty from the cops for killing such a dangerous criminal; if
you kill an enemy player (after you've killed all of their bitches) you
receive their total assets - their cash and bank balance minus any debt. In
either case you can loot the body and pick up any guns or drugs which the
-bitch or player was carrying.<p>
+bitch or player was carrying.</p>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>29-04-2001</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/commandline.html b/doc/commandline.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>dopewars command line options</title>
t@@ -6,47 +9,48 @@
<body>
<h1>dopewars command line options</h1>
-Once you have <a href="installation.html">installed</a> dopewars, you should
+<p>Once you have <a href="installation.html">installed</a> dopewars, you should
be able to run the binary just by typing<br>
-<b>dopewars</b><br>
+<tt><b>dopewars</b></tt><br>
(unless you have installed the binary in a directory which is not in your
path, in which case precede it with the path). Run without any options,
-the dopewars binary runs as a dopewars client.<p>
+the dopewars binary runs as a dopewars client.</p>
-Command line options can be used to configure common aspects of dopewars.
+<p>Command line options can be used to configure common aspects of dopewars.
More exhaustive configuration is possible by editing the dopewars
<a href="configfile.html">configuration files</a>; note, however, that
command line options can be used to override some of these settings (also see
-the <b>-g</b> option below).<p>
+the <b>-g</b> option below).</p>
+
+<p>For a brief description of the command line options, specify the option
+<b>-h</b> with the command<br>
+<tt><b>dopewars -h</b></tt><br>
+A list of the other command line options is presented below.</p>
-For a brief description of
-the command line options, specify the option <b>-h</b> with the command<br>
-<b>dopewars -h</b><br>
-A list of the other command line options is presented below.
<dl>
<dt><b>-b</b>
<dd>"Black and white". This tells the dopewars client (if that is what
you're running) not to use coloured text (by default, colour is used if the
terminal and curses support it).
-<a name="singleplayer"><dt><b>-n</b></a>
+<dt><a name="singleplayer"><b>-n</b></a>
<dd>If running the client, run in single-player mode. Don't try to connect
to any available dopewars servers.
-<a name="antique"><dt><b>-a</b></a>
+<dt><a name="antique"><b>-a</b></a>
<dd>Puts the client into "antique" mode; dopewars is derived from the
earlier game for MS-DOS of the same name, which in turn was based on
"Drug Wars" by John E. Dell. "Antique" mode aims to follow the behaviour
of the MS-DOS dopewars closely, and consequently this entails single-player
mode also.
-<a name="hiscore"><dt><b>-f <i>file</i></b></a>
+<dt><a name="hiscore"><b>-f <i>file</i></b></a>
<dd>Specifies the path and name of the file used to store the dopewars
high scores in; this can alternatively be specified in the configuration file
with the <a href="configfile.html#HiScoreFile">HiScoreFile=<i>file</i></a>
option.
-<a name="server"><dt><b>-o <i>addr</i></b></a>
+<dt><a name="server"><b>-o <i>addr</i></b></a>
<dd>Gives the name of the machine running a dopewars server, in human
readable (e.g. "nowhere.com") or dotted quad (e.g. 127.0.0.1) form. When the
client is started, if not in single-player mode, it automatically attempts to
t@@ -54,15 +58,15 @@ connect to this server for a multiplayer game. This can also be specified with
the <a href="configfile.html#Server">Server=<i>addr</i></a> configuration file
option.
-<a name="port"><dt><b>-p <i>port</i></b></a>
+<dt><a name="port"><b>-p <i>port</i></b></a>
<dd>Specifies the numeric port number which the server uses. This is usually
7902, but some servers may use other port numbers to avoid conflicts with
other services running on the machine. If you are running the dopewars client,
it will search for a server on this port; if you are running the server, it
will bind to this port and wait for connections from clients (the clients
must also be instructed to use this port, of course). This is equivalent to
-setting the port number with the <a href="configfile.html#Port">Port=<i>port</i></a>
-configuration file option.
+setting the port number with the
+<a href="configfile.html#Port">Port=<i>port</i></a> configuration file option.
<dt><b>-s</b>
<dd>Runs the <a href="server.html">dopewars server</a>. This mediates
t@@ -75,7 +79,7 @@ status to the <a href="metaserver.html">metaserver</a>, unless it is set
otherwise in the <a href="configfile.html#MetaServerActive">configuration
file</a>.
-<a name="privateserver"><dt><b>-S</b></a>
+<dt><a name="privateserver"><b>-S</b></a>
<dd>Also runs a dopewars server, but in this case <b>does not</b> report its
status to the metaserver. This does not stop clients from connecting to your
server, of course (unless it is behind a firewall, or the
t@@ -99,13 +103,13 @@ that change these same settings, will then override them.
The file is a one-line text file, containing the process ID of the dopewars
server process, and is deleted when the server quits.
-<a name="computer"><dt><b>-c</b></a>
+<dt><a name="computer"><b>-c</b></a>
<dd>Runs a computerised player. This will connect to the specifed dopewars
server and join in the multiplayer game going on there. When the player
finishes the game (or is eliminated by the other players or the server) the
program finishes.
-<a name="gui-client"><dt><b>-w</b></a>
+<dt><a name="gui-client"><b>-w</b></a>
<dd>If running a dopewars client, then this forces the use of a graphical
user interface. Under Microsoft Windows, this is an "ordinary" window, while
under Unix, this uses GTK+. If a suitable environment is not present (e.g.
t@@ -114,7 +118,7 @@ you are not running X) then dopewars will quit with an error. By default,
if neither -w or -t are specified, then a graphical user interface will be
used where available, falling back to a text-mode client in case of error.
-<a name="text-client"><dt><b>-t</b></a>
+<dt><a name="text-client"><b>-t</b></a>
<dd>When running a dopewars client, forces the use of a text-mode (curses
or console mode) interface, even if graphics are available.
t@@ -131,6 +135,6 @@ contact details.
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>29-04-2001</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/configfile.html b/doc/configfile.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>dopewars configuration files</title>
t@@ -6,14 +9,14 @@
<body>
<h1>dopewars configuration files</h1>
-A dopewars <a href="server.html">server</a>, or a <a href="clientplay.html">
+<p>A dopewars <a href="server.html">server</a>, or a <a href="clientplay.html">
client</a> (in single-player mode) can be heavily configured by the means
of dopewars configuration files. Clients used to connect to multiplayer
servers can also be configured by the same means, but almost all of these
settings will be overridden on connecting to the server (although the server
-location settings <i>Port</i> and <i>Server</i> are still useful).<p>
+location settings <i>Port</i> and <i>Server</i> are still useful).</p>
-The order of making dopewars settings is as follows:-
+<p>The order of making dopewars settings is as follows:-</p>
<ol>
<li>The global configuration file (if present) <b>/etc/dopewars</b>
<li>The user-specific file (if present) <b>~/.dopewars</b>
t@@ -22,17 +25,17 @@ directory
<li>Options specified on the <a href="commandline.html">command line</a>
</ol>
-Settings in a configuration file can set numbers, strings or "string lists".
+<p>Settings in a configuration file can set numbers, strings or "string lists".
A numerical value is set with a command such as <b>Port=7902</b> (which sets
-the TCP port for mulitplayer connections to 7902).<p>
+the TCP port for mulitplayer connections to 7902).</p>
-String (text) values are set with commands such as <b>BankName='the bank'</b>
+<p>String (text) values are set with commands such as <b>BankName='the bank'</b>
(which sets the name of the bank). Notice that string values <b>must</b> be
enclosed in quotes. Strings in double quotes understand escapes such as "\t";
strings in single quotes do not treat backslash characters specially, and
-so should be used for Windows pathnames.<p>
+so should be used for Windows pathnames.</p>
-A string list is used for setting an array of strings; for example
+<p>A string list is used for setting an array of strings; for example
<b>SubwaySaying = { "Saying 1", "Saying 2", "Saying 3" }</b> sets up three
"subway sayings". A string list consists of a list of strings, separated by
commas and wrapped with braces - { and } characters. Single strings in a
t@@ -41,15 +44,15 @@ string list can be replaced individually - for example
previously "Saying 3"). The <i>number</i> of strings in the list
<i>"List"</i> can be set with the variable <i>NumList</i> - for example,
<b>NumSubwaySaying=4</b> dimensions the <b>SubwaySaying</b> list to contain
-four strings.<p>
+four strings.</p>
-Whitespace and line breaks are ignored in the configuration files; comments
+<p>Whitespace and line breaks are ignored in the configuration files; comments
can be used, and extend from a '#' character to the end of the current line,
or are enclosed by C-style /* and */ symbols. See the
<a href="example-cfg">example configuration file</a> for a demonstration.
Valid configuration file settings are listed below. The examples given
generally reproduce the default behaviour; obviously you are free to replace
-the parts in italics to customise your own server and client.<p>
+the parts in italics to customise your own server and client.</p>
<ul>
<li><a href="#fileloc">General configuration: file and server locations</a>
t@@ -60,16 +63,16 @@ the parts in italics to customise your own server and client.<p>
<li><a href="#advanced">Advanced configuration</a>
</ul>
-<a name="fileloc"><h2>General configuration: file and server locations</h2></a>
+<h2><a name="fileloc">General configuration: file and server locations</a></h2>
<dl>
-<a name="Port"><dt><b>Port=<i>7902</i></b></a>
+<dt><a name="Port"><b>Port=<i>7902</i></b></a>
<dd>Tells the dopewars client to look for a server on port <i>7902</i>, and
tells the dopewars server to bind to port <i>7902</i> and wait for connections.
This can be overridden with the -p <a href="commandline.html#port">
command line option</a>.
-<a name="Server"><dt><b>Server=<i>"localhost"</i></b></a>
+<dt><a name="Server"><b>Server=<i>"localhost"</i></b></a>
<dd>Tells the dopewars client to look for a server at the address
<i>localhost</i>. Dotted quad (e.g. 127.0.0.1) addresses may also be used here.
If this variable is set to one of the three "special" names
t@@ -81,7 +84,7 @@ This option can be overridden with the -o <a href="commandline.html#server">
command line option</a> (but be sure to protect the brackets from the shell
if you use one of the "special" names).
-<a name="HiScoreFile"><dt><b>HiScoreFile=<i>"/var/lib/dopewars.sco"</i></b></a>
+<dt><a name="HiScoreFile"><b>HiScoreFile=<i>"/var/lib/dopewars.sco"</i></b></a>
<dd>Tells the dopewars server (or the client, if running in single-player
mode, not connected to a server) to use the file <i>/var/lib/dopewars.sco</i>
to store high scores. This can be overridden with the -f
t@@ -97,9 +100,9 @@ to 1; this only takes affect, of course, after the ConfigVerbose variable is
set, and then remains in force until it is reset again.
</dl>
-<a name="metaserver"><h2>Metaserver configuration</h2></a>
+<h2><a name="metaserver">Metaserver configuration</a></h2>
<dl>
-<a name="MetaServerActive"><dt><b>MetaServer.Active=<i>1</i></b></a>
+<dt><a name="MetaServerActive"><b>MetaServer.Active=<i>1</i></b></a>
<dd>Tells the dopewars server to report its status to the
<a href="metaserver.html">metaserver</a>. If <i>1</i>
is replaced by <i>0</i> (zero) the server will not report to the metaserver.
t@@ -127,12 +130,12 @@ by the client due to its much lower overhead.
registration (server mode) or listing the available servers (client mode) is
<i>/~ben/cgi-bin/server.pl</i>.
-<a name="MetaServerComment"><dt><b>MetaServer.Comment=<i>"dopewars
+<dt><a name="MetaServerComment"><b>MetaServer.Comment=<i>"dopewars
server"</i></b></a>
<dd>Sets the comment for your server, which appears on the list of servers
maintained by the metaserver, to <i>dopewars server</i>.
-<dt><b>MetaServer.LocalName=<i>"dope-serv.com"</i></b></a>
+<dt><b>MetaServer.LocalName=<i>"dope-serv.com"</i></b>
<dd>Tells the metaserver that the preferred hostname of your dopewars server
machine is <i>dope-serv.com</i>. By default, the metaserver tries to ascertain
your domain name from the connection, and this can fail if you connect via.
t@@ -143,12 +146,12 @@ maintainer</a> for this to work. A blank LocalName can also be used with a
suitable password to identify "your" server, even if its IP changes.
See the <a href="metaserver.html">metaserver page</a> for more details.
-<dt><b>MetaServer.Password=<i>"auth"</i></b></a>
+<dt><b>MetaServer.Password=<i>"auth"</i></b>
<dd>Uses the password <i>auth</i> to authenticate your dopewars server's
hostname (see MetaServer.LocalName above) with the metaserver.
</dl>
-<a name="places"><h2>Basic configuration: places in the game</h2></a>
+<h2><a name="places">Basic configuration: places in the game</a></h2>
<dl>
<dt><b>NumLocation=<i>8</i></b>
t@@ -205,7 +208,7 @@ the game.
<dd>The pub is known by the name <i>"the pub"</i> during the game.
</dl>
-<a name="drugs"><h2>Basic configuration: drug prices</h2></a>
+<h2><a name="drugs">Basic configuration: drug prices</a></h2>
<dl>
<dt><b>NumDrug=<i>12</i></b>
<dd>Sets there to be <i>12</i> different types of drug in the game.
t@@ -256,7 +259,7 @@ normal price distribution (between Drug[x].MinPrice and Drug[x].MaxPrice) by
<i>4</i>.
</dl>
-<a name="combat"><h2>Basic configuration: guns and fighting</h2></a>
+<h2><a name="combat">Basic configuration: guns and fighting</a></h2>
<dl>
<dt><b>NumGun=<i>4</i></b>
<dd>Configures the game to have <i>4</i> guns available to players at the
t@@ -335,7 +338,7 @@ against a player.
<dd>The first cop's deputies will each carry <i>1</i> gun.
</dl>
-<a name="advanced"><h2>Advanced configuration</h2></a>
+<h2><a name="advanced">Advanced configuration</a></h2>
<dl>
<dt><b>NumTurns=<i>31</i></b>
<dd>Defines the game to end after <i>31</i> "days" or turns. If this is set
t@@ -372,11 +375,11 @@ server for <i>14400</i> seconds, he/she will be automatically disconnected.
of connecting or disconnecting to the server, the server will sever the
connection.
-<a name="MaxClients"><dt><b>MaxClients=<i>20</i></b></a>
+<dt><a name="MaxClients"><b>MaxClients=<i>20</i></b></a>
<dd>Prevents more than <i>20</i> clients from connecting to the server at
any one time.
-<a name="AITurnPause"><dt><b>AITurnPause=<i>5</i></b></a>
+<dt><a name="AITurnPause"><b>AITurnPause=<i>5</i></b></a>
<dd>Makes computer-controlled client players run from this machine (not
necessarily AI players that connect to a server run on this machine) wait
<i>5</i> seconds between moving from location to location - i.e. a turn
t@@ -481,6 +484,6 @@ any drugs, and clients will display this information if available.
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>29-04-2001</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/credits.html b/doc/credits.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Credits and acknowledgements</title>
t@@ -6,46 +9,47 @@
<body>
<h1>Credits and acknowledgements</h1>
-dopewars is derived from the MS-DOS game of the same name (author unknown).<p>
+<p>dopewars is derived from the MS-DOS game of the same name (author
+unknown).</p>
-This is turn was based upon the MS-DOS game "Drug Wars", by John E. Dell.<p>
+<p>This is turn was based upon the MS-DOS game "Drug Wars", by John E. Dell.</p>
-dopewars is written by and is copyright of
-<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">Ben Webb</a>.<p>
+<p>dopewars is written by and is copyright of
+<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">Ben Webb</a>.</p>
-Pivotal to the development of dopewars were and are the following:-<p>
+<p>Pivotal to the development of dopewars were and are the following:-</p>
-<b>Dan Wolf</b> for uncountable numbers of useful suggestions for the structure
-of the multiplayer game, drawing upon a disturbing knowledge of the drugs
-world. He also undertook scary amounts of research (i.e. playing the game) to
-assist with the re-engineering of the MS-DOS version, and plays the game to
-an unhealthy extent (as is witnessed by his high scores on many dopewars
-servers).<p>
+<p><b>Dan Wolf</b> for uncountable numbers of useful suggestions for the
+structure of the multiplayer game, drawing upon a disturbing knowledge of the
+drugs world. He also undertook scary amounts of research (i.e. playing the
+game) to assist with the re-engineering of the MS-DOS version, and plays the
+game to an unhealthy extent (as is witnessed by his high scores on many
+dopewars servers).</p>
-<b>Phil Davis, Caroline Moore, Katherine Holt</b> and <b>Andrea
+<p><b>Phil Davis, Caroline Moore, Katherine Holt</b> and <b>Andrea
Elliot-Smith</b> for extensive play testing of early versions of dopewars,
despite the large amounts of "real" work which they were supposed to be
doing, and despite the many dodgy bugs, as well as for providing
-suggestions, even if they were often rude. You know who you are.<p>
+suggestions, even if they were often rude. You know who you are.</p>
-<b>Owen Walsh</b> and <b>Pete Winn</b> for yet more play testing, and for
-consequently doing very little research in vastly more important fields...<p>
+<p><b>Owen Walsh</b> and <b>Pete Winn</b> for yet more play testing, and for
+consequently doing very little research in vastly more important fields...</p>
-<b>James Matthews</b> for providing absolutely no useful suggestions, but
-providing vital assistance with the Officer Bob code.<p>
+<p><b>James Matthews</b> for providing absolutely no useful suggestions, but
+providing vital assistance with the Officer Bob code.</p>
-<b>Mike Meyer</b> for providing several modifications to version 1.4.3,
-as well as spotting many of his own and my bugs...<p>
+<p><b>Mike Meyer</b> for providing several modifications to version 1.4.3,
+as well as spotting many of his own and my bugs...</p>
-<b>Matt Higgins</b> for a couple of patches to version 1.4.4.<p>
+<p><b>Matt Higgins</b> for a couple of patches to version 1.4.4.</p>
-<b>Tony Brown</b> for assistance with using dopewars via. enforced web
-proxies.<p>
+<p><b>Tony Brown</b> for assistance with using dopewars via. enforced web
+proxies.</p>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>11-10-1999</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/developer.html b/doc/developer.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Notes for developers</title>
t@@ -6,32 +9,32 @@
<body>
<h1>Notes for developers</h1>
-You are free to make whatever changes to the code you wish, as long as you
+<p>You are free to make whatever changes to the code you wish, as long as you
abide by the terms set out in the <a href="LICENCE">GNU General
Public License</a>. Obviously, I only have a limited amount of time to devote
to dopewars development, and so encourage discussion of the dopewars code,
-documentation and concept, and particularly welcome suggested improvements.<p>
+documentation and concept, and particularly welcome suggested improvements.</p>
-You are free to distribute modified versions of the code,
+<p>You are free to distribute modified versions of the code,
again subject to the licence, but I also welcome patches to the code at my
email address,
<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">ben@bellatrix.pcl.ox.ac.uk</a>.
If I choose to include these patches in a new dopewars version, you will of
course be credited in the changelog (unless, of course, you don't want to
-be).<p>
+be).</p>
-For information on the internal workings of the dopewars game code, and
+<p>For information on the internal workings of the dopewars game code, and
the client-server interface, the best documentation for the budding
developer is the source code itself. I have endeavoured to add sufficient
documentation to the source where necessary; any discussion here of the
internal workings, however, may be incomplete, out of date, and possibly
misleading. Feel free to email me at the address above with questions on this;
-I might possibly even know the answers!<p>
+I might possibly even know the answers!</p>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>30-9-1999</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/i18n.html b/doc/i18n.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Internationalization</title>
t@@ -6,13 +9,13 @@
<body>
<h1>Internationalization</h1>
-dopewars uses the <a href="http://www.gnu.org/manual/gettext/">GNU gettext</a>
-utilities for internationalization (i18n) support. This allows the software
-to be translated into the local language at runtime - run dopewars in the UK
-and it'll talk to you in English, but run it in Germany and it'll talk to you
-in German. This relies on translators to translate the program's output into
-each language beforehand, of course, and so native language speakers to carry
-out this task are always needed!
+<p>dopewars uses the <a href="http://www.gnu.org/manual/gettext/">GNU
+gettext</a> utilities for internationalization (i18n) support. This allows the
+software to be translated into the local language at runtime - run dopewars in
+the UK and it'll talk to you in English, but run it in Germany and it'll talk
+to you in German. This relies on translators to translate the program's output
+into each language beforehand, of course, and so native language speakers to
+carry out this task are always needed!</p>
<ul>
<li><a href="#running">Running dopewars with i18n support</a>
t@@ -22,18 +25,18 @@ out this task are always needed!
<li><a href="#current">Currently available translations</a>
</ul>
-<a name="running"><h2>Running dopewars with i18n support</h2></a>
-i18n is only included in versions of dopewars later than 1.4.8. By default,
+<h2><a name="running">Running dopewars with i18n support</a></h2>
+<p>i18n is only included in versions of dopewars later than 1.4.8. By default,
"Native Language Support" is compiled in; binary installations should be
already set up for i18n. When compiling dopewars from source code, the
<tt>configure</tt> script should detect whether your system can support
GNU gettext. If it can, but the gettext utilities themselves are not present,
an included copy in the <tt>intl/</tt> subdirectory is used. To disable i18n,
-pass the <tt>--disable-nls</tt> option to the <tt>configure</tt> script.<p>
+pass the <tt>--disable-nls</tt> option to the <tt>configure</tt> script.</p>
-When you run your installed copy of dopewars, it should detect your "locale"
+<p>When you run your installed copy of dopewars, it should detect your "locale"
automatically and talk to you in your native language. If this does not happen,
-the following are some possible explanations:-
+the following are some possible explanations:-</p>
<ul>
<li>dopewars cannot find the locale-specific language file - by default, stored
under /usr/local/share/locale/
t@@ -46,27 +49,27 @@ shell and want a German translation, the command "<tt>export LANG=de</tt>"
should fix the problem.
</ul>
-<a name="adding"><h2>Adding a new translation</h2></a>
-Translation files are kept in the subdirectory <tt>po/</tt> of the dopewars
+<h2><a name="adding">Adding a new translation</a></h2>
+<p>Translation files are kept in the subdirectory <tt>po/</tt> of the dopewars
source code distribution. They are named by
<a href="http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_639.html">
2-letter language codes</a> followed by the <tt>.po</tt> extension - for
example, the German translation is stored in the file <tt>po/de.po</tt>.
They are simple text files, consisting of lists of the original English string
(labelled by "msgid") followed by the translated string (labelled by
-"msgstr").<p>
-
-Adding a new translation is simply a matter of copying the reference file
-<tt>dopewars.pot</tt> to your language-specific <tt>.po</tt> file in the <tt>po/</tt> directory, and filling
-in the "msgstr" entries. Once this is done, edit the <tt>configure.in</tt>
-file in the top dopewars directory to add your language code to the
-<tt>ALL_LINGUAS</tt> variable. Then run <tt>autoconf</tt> to rebuild the
-<tt>configure</tt> script, before making and installing dopewars as usual. The
-new translation should now be available. Once this is complete, please
-<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">send</a> the translation to be
-included in the next dopewars version.<p>
-
-Please note that some strings are <b>format strings</b> containing the %
+"msgstr").</p>
+
+<p>Adding a new translation is simply a matter of copying the reference file
+<tt>dopewars.pot</tt> to your language-specific <tt>.po</tt> file in the
+<tt>po/</tt> directory, and filling in the "msgstr" entries. Once this is done,
+edit the <tt>configure.in</tt> file in the top dopewars directory to add your
+language code to the <tt>ALL_LINGUAS</tt> variable. Then run <tt>autoconf</tt>
+to rebuild the <tt>configure</tt> script, before making and installing dopewars
+as usual. The new translation should now be available. Once this is complete,
+please <a href="mailto:ben@bellatrix.pcl.ox.ac.uk">send</a> the translation to
+be included in the next dopewars version.</p>
+
+<p>Please note that some strings are <b>format strings</b> containing the %
character. These are used in the program code for substituting numbers and
other pieces of text into the string - these substitutions are are performed
using variables which are specified in the <b>same order</b> as the %
t@@ -81,9 +84,9 @@ Now the number and string are specified in the wrong order, and this will
probably crash the program on running! To fix this, use the special notation<br>
<tt>"%2$d Zeichen lang ist die Zeichenkette '%1$s'"</tt><br>
(i.e. replace <b>%x</b> with <b>%n$x</b> where <b>n</b> is the index that the
-format specifier "should" have, starting from 1.)<p>
+format specifier "should" have, starting from 1.)</p>
-<a name="dopespec"><h2>dopewars specifics</h2>
+<h2><a name="dopespec">dopewars specifics</a></h2>
<ul>
<li>When questions are asked in the curses (text mode) client, the keys that
you are allowed to press in reply are stored in a string. This should be
t@@ -109,7 +112,7 @@ free to translate <tt>%txx</tt> to use the most appropriate form of the word.
If you wish to capitalise the first letter of the word (as used in English for
titles, etc.) then use "<tt>%T</tt>" rather than "<tt>%t</tt>".<p>
-Obviously dopewars cannot guess what your "alternative forms" are; you must
+<p>Obviously dopewars cannot guess what your "alternative forms" are; you must
specify them yourself. Essentially, when setting a string in a dopewars
configuration file (or the defaults, which are set in dopewars.c) alternative
forms can be added by alternating two-letter codes and alternative forms after
t@@ -123,20 +126,21 @@ in the translation that you haven't given an alternative form for, the
default word ("bitch") will be used. In the original English, "<tt>%tde</tt>"
is used for this purpose, but there is nothing special about the "<tt>de</tt>"
code - you can use it yourself if you like, and you can use as many
-different two-letter codes as you want to.<p>
+different two-letter codes as you want to.</p>
-Additionally, prices in dopewars are automatically formatted into strings by
+<p>Additionally, prices in dopewars are automatically formatted into strings by
means of the %P notation, and comments can be introduced into format strings
by means of the %/.../ notation. Everything between the two / characters is
not printed. This is used to "qualify" some strings for translation, and the
%/.../ can be left out of the translated string if desired (the comment does
-not need to be translated).
+not need to be translated).</p>
</ul>
-<a name="updating"><h2>Updating a translation for a new dopewars
-version</h2></a>
-New versions of dopewars will often change what is printed to the user, and
+<h2><a name="updating">Updating a translation for a new dopewars
+version</a></h2>
+
+<p>New versions of dopewars will often change what is printed to the user, and
so may may require changes to the translation. To update an existing
translation, "<tt>make</tt>" the new version of dopewars. This will create
a <tt>dopewars.pot</tt> file listing the strings that need translating. Change
t@@ -150,9 +154,9 @@ translation with the new one:<br>
<tt>mv newfile de.po</tt><br>
Rebuild and reinstall dopewars, and the new translations should become
available. Again, it is deeply appreciated if such updated files are
-contributed to the main dopewars distribution!<p>
+contributed to the main dopewars distribution!</p>
-<a name="current"><h2>Currently available translations</h2></a>
+<h2><a name="current">Currently available translations</a></h2>
<ul>
<li>German (<tt>de.po</tt>)
t@@ -175,11 +179,11 @@ Molenda</a>
</ul>
</ul>
-<hr><br>
+<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>29-04-2001</b>
+<p>Last update: <b>29-04-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/index.html b/doc/index.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>dopewars 1.5.0: Main Index</title>
t@@ -24,31 +27,30 @@
</td>
<td>
-dopewars is a game simulating the life of a drug dealer in 1984 New York,
+<p>dopewars is a game simulating the life of a drug dealer in 1984 New York,
based upon the MS-DOS game of the same name, in turn derived from "Drug
Wars" by John E. Dell. The aim of the game is to make lots and lots of
money, but unfortunately you start the game with a hefty debt to the loan
shark (who charges equally hefty interest) and the cops take a rather dim
-view of drug dealing...<p>
+view of drug dealing...</p>
-dopewars expands upon the MS-DOS version by introducing multiplayer
+<p>dopewars expands upon the MS-DOS version by introducing multiplayer
functions. With the aid of dopewars servers, several players (computer or
human) can roam New York (or some other city, chosen by the operator of the
-server) and attempt to shoot other players and steal their lucrative drugs.<p>
+server) and attempt to shoot other players and steal their lucrative drugs.</p>
-dopewars is written on the RedHat Linux platform, and should run on most
+<p>dopewars is written on the RedHat Linux platform, and should run on most
varieties of Unix, as well as under Microsoft Windows. The source code is
-freely available under the <a href="LICENCE">GNU General Public License</a>.<p>
+freely available under the <a href="LICENCE">GNU General Public License</a>.</p>
-For more information on the current state of dopewars, check out the
-<a href="http://bellatrix.pcl.ox.ac.uk/~ben/dopewars/">webpage</a>.<p>
+<p>For more information on the current state of dopewars, check out the
+<a href="http://dopewars.sourceforge.net/">webpage</a>.</p>
</td>
</tr>
</table>
-<p>
<hr>
-Last update: <b>29-04-2001</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/installation.html b/doc/installation.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Obtaining and installing dopewars</title>
t@@ -6,7 +9,7 @@
<body>
<h1>Obtaining and installing dopewars</h1>
-The dopewars source code and precompiled binaries for Intel and Alpha
+<p>The dopewars source code and precompiled binaries for Intel and Alpha
systems (in RPM format) are available from the main dopewars web page,
at <a href="http://dopewars.sourceforge.net/">
http://dopewars.sourceforge.net/</a>. Just follow the link from
t@@ -15,15 +18,17 @@ for simplifying installation and upgrade of programs, and is part of the
RedHat Linux distribution. If you are using a different distribution, it
may be still be included, however. If you do not want to use "rpm", or the
installation fails, then you can obtain the source code tarball and recompile
-the code from scratch.<p>
+the code from scratch.</p>
-<b>Prerequisites:</b> dopewars relies on the screen library curses (or the
-equivalent, such as ncurses or cur_colr) but otherwise aims to be usable
-without modification on a wide variety of Unix variants. The
-<a href="#tarball">tarball</a> can also be compiled using the freely
-available <a href="http://sourceware.cygnus.com/cygwin/">Cygwin</a> suite for
-Win32 systems, to yield a Windows binary. dopewars is developed and tested on
-RedHat Linux systems.<p>
+<p><b>Prerequisites:</b> dopewars relies on the screen library curses (or the
+equivalent, such as ncurses or cur_colr, for the text-mode client), the GLib
+library, and the X toolkit <a href="http://www.gtk.org/">GTK+</a> (for the
+graphical client) but otherwise aims to be usable without modification on a
+wide variety of Unix variants. The <a href="#tarball">tarball</a> can also be
+compiled using the freely available
+<a href="http://sourceware.cygnus.com/cygwin/">Cygwin</a> suite for Win32
+systems, to yield a Windows binary. dopewars is developed and tested on RedHat
+Linux systems.</p>
<ul>
<li><a href="#rpmbinary">RPM binary installation</a>
t@@ -31,12 +36,12 @@ RedHat Linux systems.<p>
<li><a href="#tarball">Tarball installation</a>
</ul>
-<a name="rpmbinary"><h2>RPM binary installation</h2></a>
-The binary RPMs are built for Compaq (formerly DEC) Alpha systems running
+<h2><a name="rpmbinary">RPM binary installation</a></h2>
+<p>The binary RPMs are built for Compaq (formerly DEC) Alpha systems running
RedHat Linux 7.0, and Intel (also Intel compatibles, such as AMD, Cyrix, etc.)
systems running RedHat Linux 7.1. On other systems, these binary RPMs may
refuse to install, or may run but then crash with mysterious segmentation
-faults due to library conflicts.
+faults due to library conflicts.</p>
<ol>
<li>Download the
t@@ -46,57 +51,68 @@ Alpha</a> or
i386 (Intel)</a> RPM with your web browser. (If your browser is incorrectly set
up, it may try and display the file, in which case tell it explicitly to save
the file - Shift+Mouse button 1 in Netscape.)
+
<li>Become root on your Unix box (if you cannot become root, then you will
probably not be able to use RPM installation, depending on how "rpm" is set
up).
+
<li>Change to the directory containing the dopewars rpm, and install it with
-the command <br>
-<b>rpm -i dopewars-1.5.0-1.<i>xxx</i>.rpm</b><br>
-(where <b><i>xxx</i></b> is i386 or alpha). If you have a previous version
-of dopewars installed, upgrade it instead with<br>
-<b>rpm -U dopewars-1.5.0-1.<i>xxx</i>.rpm</b>
+the command<br>
+<tt><b>rpm -Uvh dopewars-1.5.0-1.<i>xxx</i>.rpm</b></tt><br>
+(where <b><i>xxx</i></b> is i386 or alpha). This will replace any
+already-installed earlier version.
</ol>
-<a name="rpmsource"><h2>RPM source installation</h2></a>
-This route is open to you if your system has "rpm", but the binary RPMs do
+<h2><a name="rpmsource">RPM source installation</a></h2>
+<p>This route is open to you if your system has "rpm", but the binary RPMs do
not work on your system, or your machine is not an Intel or Alpha (a PowerMac,
for example). It involves obtaining the RPM of the source code, and then
-building the binaries from it on your system.
+building the binaries from it on your system.</p>
<ol>
-<li>Download the <a href="http://dopewars.sourceforge.net/dopewars-1.5.0-1.src.rpm">source code RPM</a>.
+<li>Download the
+<a href="http://dopewars.sourceforge.net/dopewars-1.5.0-1.src.rpm">source code
+RPM</a>.
+
<li>Become root and change to the directory containing the new rpm.
+
<li>Build a binary rpm with the command<br>
-<b>rpm --rebuild dopewars-1.5.0-1.src.rpm</b>
+<tt><b>rpm --rebuild dopewars-1.5.0-1.src.rpm</b></tt>
+
<li>Change to the directory which the binary rpm has been written to (check
the output of the above - usually /usr/src/redhat/RPMS/<i>xxx</i>, where
<i>xxx</i> is your machine type - for example, "i386" on Intel machines,
"alpha" on Alphas)
+
<li>Install the binary rpm with the command<br>
-<b>rpm -i dopewars-1.5.0-1.<i>xxx</i>.rpm</b><br>
-or upgrade an existing version with<br>
-<b>rpm -U dopewars-1.5.0-1.<i>xxx</i>.rpm</b><br>
+<tt><b>rpm -Uvh dopewars-1.5.0-1.<i>xxx</i>.rpm</b></tt>
</ol>
-<a name="tarball"><h2>Tarball installation</h2></a>
-If you don't have, or don't want to use, RPM, you can obtain the source code in
-gzipped, tarred ("tarball") format and recompile and install it yourself. This
-is also usually a necessity if you cannot become root (the superuser) on your
-Unix box.
+<h2><a name="tarball">Tarball installation</a></h2>
+<p>If you don't have, or don't want to use, RPM, you can obtain the source code
+in gzipped, tarred ("tarball") format and recompile and install it yourself.
+This is also usually a necessity if you cannot become root (the superuser) on
+your Unix box.</p>
<ol>
-<li>Download the <a href="http://dopewars.sourceforge.net/dopewars-1.5.0.tar.gz">source code tarball</a>.
+<li>Download the
+<a href="http://dopewars.sourceforge.net/dopewars-1.5.0.tar.gz">source code
+tarball</a>.
+
<li>Change to the directory containing the tarball and extract the contents
with the command <br>
-<b>tar -xvzf dopewars-1.5.0.tar.gz</b><br>
+<tt><b>tar -xvzf dopewars-1.5.0.tar.gz</b></tt><br>
(or similar).
+
<li>Change into the dopewars-1.5.0 directory, and read all the important
documentation in there ;)
+
<li>Build the binary with the commands<br>
-<b>./configure</b><br>
-<b>make</b>
+<tt><b>./configure</b><br>
+<b>make</b></tt>
+
<li>Become root and install the dopewars files with<br>
-<b>make install</b><br>
+<tt><b>make install</b></tt><br>
The configure script will test your system and set up dopewars so that it
should compile cleanly. If you are running the Cygwin tools under Microsoft
Windows, the script should detect this and allow you to build a native
t@@ -107,13 +123,14 @@ more details, read the INSTALL file in the dopewars-1.5.0 directory.<p>
If you cannot become root, run the configure script specifying directories for
which you have write access for both the dopewars binary and high score file
with a command such as<br>
-<b>./configure --bindir=/home/user/dopewars --datadir=/home/user/dopewars</b>
+<tt><b>./configure --bindir=/home/user/dopewars
+--datadir=/home/user/dopewars</b></tt>
</ol>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>09-07-2000</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/metaserver.html b/doc/metaserver.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>The dopewars metaserver</title>
t@@ -6,12 +9,12 @@
<body>
<h1>The dopewars metaserver</h1>
-Every dopewars <a href="server.html">server</a> is different, due to their
+<p>Every dopewars <a href="server.html">server</a> is different, due to their
differing locations and configurations. Thus some centralised system for
listing the currently available servers and displaying some sort of comment
about the games running on them is necessary, to enable client players to
pick the game that most suits them. This is the function of the dopewars
-<b>metaserver</b>.<p>
+<b>metaserver</b>.</p>
<ul>
<li><a href="#location">Metaserver location</a>
t@@ -23,16 +26,16 @@ pick the game that most suits them. This is the function of the dopewars
</ul>
</ul>
-<a name="location"><h2>Metaserver location</h2></a>
-The metaserver has a CGI (web) interface for humans and dopewars clients to
+<h2><a name="location">Metaserver location</a></h2>
+<p>The metaserver has a CGI (web) interface for humans and dopewars clients to
read from, and a UDP interface for servers to report to. It lives at the
same place as the <a href="http://bellatrix.pcl.ox.ac.uk/~ben/dopewars/">
main dopewars page</a>; the CGI interface listens on TCP port 80, and the
UDP interface on port 7802. These are the default settings which all
-dopewars servers and clients use for metaserver communication.<p>
+dopewars servers and clients use for metaserver communication.</p>
-<a name="client"><h2>Using the metaserver from the client</h2></a>
-Players who want to use the metaserver to list the currently available
+<h2><a name="client">Using the metaserver from the client</a></h2>
+<p>Players who want to use the metaserver to list the currently available
servers should go to
<a href="http://bellatrix.pcl.ox.ac.uk/~ben/cgi-bin/serverlist.pl">this
link</a>, or just follow the "Servers" link from the main dopewars web page.
t@@ -40,9 +43,9 @@ It cannot be guaranteed that all the listed servers are functional - they
may, for example, have been registered in error, or a server may have crashed
since being added to the list - but the list is checked daily for service,
and so there is at least a good chance that the servers listed there will
-be working.<p>
+be working.</p>
-The metaserver, being a collection of CGI scripts, should work happily on
+<p>The metaserver, being a collection of CGI scripts, should work happily on
most machines which have web access. A problem occurs, however, if your
connection to the Web is via. an enforced proxy server (i.e. traffic on
port 80 from your machine is blocked by firewall). dopewars can be
t@@ -52,28 +55,28 @@ add the following lines to your dopewars <a href="configfile.html">
configuration file</a>:-<br>
<b>MetaServer.Name=proxy.com<br>
MetaServer.Port=8080<br>
-MetaServer.Path=http://bellatrix.pcl.ox.ac.uk/~ben/cgi-bin/server.pl</b><p>
+MetaServer.Path=http://bellatrix.pcl.ox.ac.uk/~ben/cgi-bin/server.pl</b></p>
-<a name="server"><h2>Using the metaserver from the server</h2></a>
-People running servers who <b>do not</b> want their details listed by the
+<h2><a name="server">Using the metaserver from the server</a></h2>
+<p>People running servers who <b>do not</b> want their details listed by the
metaserver should disable the metaserver comunication of the server with
the <a href="configfile.html#MetaServerActive">MetaServer.Active=0</a>
configuration file setting, or the <b>-S</b>
<a href="commandline.html#privateserver">command line option</a>. Servers
which <b>do</b> register their details can have their accompanying comment
set with the <a href="configfile.html#MetaServerComment">
-MetaServer.Comment</a> configuration file setting.<p>
+MetaServer.Comment</a> configuration file setting.</p>
-Each dopewars server notifies the metaserver of its current status, and
+<p>Each dopewars server notifies the metaserver of its current status, and
sends this data on startup and shutdown, and when players leave or join the
-game. See the <a href="server.html">server page</a> for more details.<p>
+game. See the <a href="server.html">server page</a> for more details.</p>
-<a name="wrongip"><h3>But it's displaying the wrong IP address!</h3></a>
-Once connected to the metaserver, you may find that it incorrectly
+<h3><a name="wrongip">But it's displaying the wrong IP address!</a></h3>
+<p>Once connected to the metaserver, you may find that it incorrectly
displays the domain name of your server machine. This is usually because the
-metaserver cannot resolve your IP address to a domain name.<p>
+metaserver cannot resolve your IP address to a domain name.</p>
-In this case, you will need to override the hostname that the metaserver
+<p>In this case, you will need to override the hostname that the metaserver
guesses for your machine with one you choose yourself. This is done by
specifying the hostname with the MetaServer.LocalName variable in your dopewars
<a href="configfile.html">configuration file</a>. In order to prevent abuse
t@@ -82,37 +85,37 @@ authenticate your chosen hostname.
<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">Email</a> the maintainer, giving
the exact hostname you want to use (be aware that this is case-sensitive) and
you will be given a password. Specify this password with the MetaServer.Password
-variable in the dopewars configuration file.<p>
+variable in the dopewars configuration file.</p>
-For example, if you wish your server to be known as <b>dope-serv.com</b> and
+<p>For example, if you wish your server to be known as <b>dope-serv.com</b> and
you have emailed the maintainer, receiving the password <b>Dope-Auth</b>, then
add the following to the dopewars configuration file:-<br>
<b>MetaServer.LocalName=dope-serv.com<br>
-MetaServer.Password=Dope-Auth</b><p>
+MetaServer.Password=Dope-Auth</b></p>
-Restart your dopewars server, or send it a SIGUSR1 signal, for the change to
+<p>Restart your dopewars server, or send it a SIGUSR1 signal, for the change to
take effect. Bear in mind that if you make up a non-existent or invalid domain
name, the metaserver will accept it, but the server will be removed from the
-metaserver's list when it is checked daily for service.<p>
+metaserver's list when it is checked daily for service.</p>
-<a name="dynamicip"><h3>But my server has a dynamic IP...</h3></a>
-Finally, your server's IP may be resolved happily, but you may have a connection
-to the internet which assigns you a dynamic IP. Consider what happens if your
-connection is broken before the dopewars server exits; the metaserver will
-list the IP of the "old" server, and you will now have no way of removing that
-entry when your connection comes back up, as your IP will be different. In
-this case, you can <a href="mailto:ben@bellatrix.pcl.ox.ac.uk">email</a> the
-metaserver maintainer, and specify a blank MetaServer.LocalName variable.
-You will again receive a MetaServer.Password variable (see
-<a href="#wrongip">above</a>), which the metaserver
-will use to identify "your" server; now, when your internet connection is
-restored, the server registration with the "new" IP will automatically replace
-the "old" one.
+<h3><a name="dynamicip">But my server has a dynamic IP...</a></h3>
+<p>Finally, your server's IP may be resolved happily, but you may have a
+connection to the internet which assigns you a dynamic IP. Consider what
+happens if your connection is broken before the dopewars server exits; the
+metaserver will list the IP of the "old" server, and you will now have no way
+of removing that entry when your connection comes back up, as your IP will be
+different. In this case, you can
+<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">email</a> the metaserver
+maintainer, and specify a blank MetaServer.LocalName variable. You will again
+receive a MetaServer.Password variable (see <a href="#wrongip">above</a>),
+which the metaserver will use to identify "your" server; now, when your
+internet connection is restored, the server registration with the "new" IP
+will automatically replace the "old" one.</p>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>09-07-2000</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/server.html b/doc/server.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Setting up and running a dopewars server</title>
t@@ -6,23 +9,23 @@
<body>
<h1>Setting up and running a dopewars server</h1>
-Multiplayer games of dopewars require a running dopewars server; this mediates
-the interactions between each player (each player runs a
+<p>Multiplayer games of dopewars require a running dopewars server; this
+mediates the interactions between each player (each player runs a
<a href="clientplay.html">client</a> which connects to this server). The server
runs the game, generating drug prices and the like, and instructs the clients
accordingly. The server can be run on any machine that can be reached over
the network by clients (so you don't have to run it on the same machine that
you run your client on, for example, unless your firewall blocks the dopewars
-port).<p>
+port).</p>
-Single player games do not require a server (although you can still connect
-to one if you like) as a "virtual server" is run by the dopewars client.<p>
+<p>Single player games do not require a server (although you can still connect
+to one if you like) as a "virtual server" is run by the dopewars client.</p>
-The dopewars server can be heavily customised by means of the
+<p>The dopewars server can be heavily customised by means of the
<a href="configfile.html">configuration files</a>. For example, you can
change the names of all the game locations so that the game is set in your
home city rather than New York. Any players that then connect to your
-customised server will play this customised game.<p>
+customised server will play this customised game.</p>
<ul>
<li><a href="#interactive">Running an interactive server</a>
t@@ -30,19 +33,19 @@ customised server will play this customised game.<p>
<li><a href="#metaserver">Private and public: the dopewars metaserver</a>
</ul>
-<a name="interactive"><h2>Running an interactive server</h2></a>
+<h2><a name="interactive">Running an interactive server</a></h2>
-All the code for the dopewars server is included in the same binary as the
+<p>All the code for the dopewars server is included in the same binary as the
standard client. To run the binary in server mode, specify the <b>-s</b> or
<b>-S</b> <a href="commandline.html">command line option</a>. By default,
this runs the server in "interactive" mode; that is to say that the server
functions as normal, but in addition responds to typed commands from you.
Click <a href="servercommands.html">here</a> for a list of the valid commands
-in interactive mode.<p>
+in interactive mode.</p>
-<a name="noninteractive"><h2>Non-interactive servers</h2></a>
+<h2><a name="noninteractive">Non-interactive servers</a></h2>
-Usually, however, you will not need to use server commands (most can be
+<p>Usually, however, you will not need to use server commands (most can be
specified in the <a href="configfile.html">configuration files</a> anyway)
and so will want a non-interactive server. This will sit in the background
and quietly deal with dopewars games without disturbing you, the user. To
t@@ -51,40 +54,40 @@ input and output, and use your shell's job control to put it in the background,
with a command similar to the following:-<br>
<b>dopewars -s < /dev/null >> /var/log/dopewars.log &</b><br>
(this writes server output to the logfile <i>/var/log/dopewars.log</i>.
-Alternatively you can redirect this output to <i>/dev/null</i>.)<p>
+Alternatively you can redirect this output to <i>/dev/null</i>.)</p>
-<a name="metaserver"><h2>Private and public: the dopewars metaserver</h2></a>
+<h2><a name="metaserver">Private and public: the dopewars metaserver</a></h2>
-By default, a server reports its status to the dopewars
+<p>By default, a server reports its status to the dopewars
<a href="metaserver.html">metaserver</a>. It does this on startup and
shutdown, and whenever players join or leave the game. In addition, you
can force a report (under Unix systems) by sending the dopewars server
process a SIGUSR1 signal. The server will "remind" the metaserver that it
exists by ensuring that a report is sent at least once every 20 minutes or so,
regardless. A "status report" comprises contact details for the server,
-a count of the number of active players, and current high scores.<p>
+a count of the number of active players, and current high scores.</p>
-The metaserver also has a web interface, which is used by dopewars clients to
+<p>The metaserver also has a web interface, which is used by dopewars clients to
obtain the list of servers, and can also be viewed with a web browser
-<a href="http://bellatrix.pcl.ox.ac.uk/~ben/cgi-bin/serverlist.pl">here</a>.<p>
+<a href="http://bellatrix.pcl.ox.ac.uk/~ben/cgi-bin/serverlist.pl">here</a>.</p>
-Whether your server connects to the metaserver can be configured with the
+<p>Whether your server connects to the metaserver can be configured with the
<a href="configfile.html#MetaServerActive">MetaServer.Active</a> configuration
file setting, or the <b>-s</b> and <b>-S</b> <a href="commandline.html">
-command line options</a>.<p>
+command line options</a>.</p>
-N.B. Your machine may have trouble connecting with
+<p>N.B. Your machine may have trouble connecting with
the metaserver in some circumstances, most notably if you are using an
enforced proxy server or your DNS does not correctly resolve your IP address
to your domain name. In such cases, you may be unable to connect to the
metaserver, or it may register your server with an incorrect name. For
information on getting round these difficulties, see the
-<a href="metaserver.html">metaserver</a> page.
+<a href="metaserver.html">metaserver</a> page.</p>
<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>09-07-2000</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/servercommands.html b/doc/servercommands.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>Interactive server commands</title>
t@@ -6,14 +9,14 @@
<body>
<h1>Interactive server commands</h1>
-Available commands are listed below. Please note also that any valid
+<p>Available commands are listed below. Please note also that any valid
line from a <a href="configfile.html">configuration file</a> can
be entered at the interactive server's prompt. Note, however, that game
options cannot be changed while players are connected. In addition, the
current value of any option from the configuration files can be displayed
by typing the name of the variable by itself. For example, entering
<i>MetaServer.Comment</i> at the prompt will display the comment that the
-server sends to the <a href="metaserver.html">metaserver</a>.
+server sends to the <a href="metaserver.html">metaserver</a>.</p>
<dl>
<dt><b>help</b>
t@@ -52,6 +55,6 @@ signal (i.e. pressing Ctrl-C or killing the process with the "kill" command).
<li><a href="server.html">Setting up and running a dopewars server</a>
</ul>
</ul>
-Last update: <b>28-9-99</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>
(DIR) diff --git a/doc/windows.html b/doc/windows.html
t@@ -1,3 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+
<html>
<head>
<title>dopewars and Microsoft Windows</title>
t@@ -6,26 +9,26 @@
<body>
<h1>dopewars and Microsoft Windows</h1>
-dopewars now runs natively on Win32 systems (95, 98, NT, 2000). It runs by
+<p>dopewars now runs natively on Win32 systems (95, 98, NT, 2000). It runs by
default as a dopewars client, using the familiar Windows interface. However,
if you prefer the "original look" text mode interface, this is still
available; just right click on a shortcut to dopewars, and add <tt>-t</tt> to
the end of the command line. To run a dopewars server, add <tt>-s</tt>
-instead.<p>
+instead.</p>
-Binaries can be obtained from the main
-<a href="http://bellatrix.pcl.ox.ac.uk/~ben/dopewars/download.html">download
-site</a>, or dopewars will compile with the free
+<p>Binaries can be obtained from the main
+<a href="http://dopewars.sourceforge.net/download.html">download site</a>, or
+dopewars will compile with the free
<a href="http://sourceware.cygnus.com/cygwin/">Cygwin</a> tools under Win32.
dopewars uses the <a href="http://www.gtk.org/">GLib</a> library, which can
be obtained for Windows from <a href="http://user.sgic.fi/~tml/gimp/win32/">
http://user.sgic.fi/~tml/gimp/win32/</a>. The installation procedure is the
same as <a href="installation.html">that for Unix systems</a> - download the
tarball, extract the files, change into the created directory, run the
-<b>configure</b> script, and then <b>make</b>. This builds a native Win32
-binary, which does not need the Cygwin libraries to run.<p>
+<tt><b>configure</b></tt> script, and then <b>make</b>. This builds a native
+Win32 binary, which does not need the Cygwin libraries to run.</p>
-In virtually all respects, the Unix and Win32 versions of dopewars should be
+<p>In virtually all respects, the Unix and Win32 versions of dopewars should be
identical. Both will accept the same command line parameters and configuration
options. However, since the standard Unix paths for the high score file and
configuration files do not translate well to Windows, by default the program
t@@ -34,13 +37,13 @@ high score file <b>dopewars.sco</b> in the current directory. (N.B. The
standard Unix-like configuration files \Etc\Dopewars and $HOME\.Dopewars will
be read before dopewars-config.txt if they are present, and if you build
the program by hand, you'll need to use --datadir="." as an option to
-configure in order to get this behaviour for the high score file.)<p>
+configure in order to get this behaviour for the high score file.)</p>
-<hr><br>
+<hr>
<ul>
<li><a href="index.html">Main index</a>
</ul>
-Last update: <b>29-04-2001</b>
+<p>Last update: <b>13-05-2001</b></p>
</body>
</html>