DoomRun v0.1 14th April 1996
Copyright (c) 1996, Tom Lees <firstname.lastname@example.org> BETA release
DoomRun is a simple program which can automatically set up things in a WAD
to be used at Doom runtime, by intercepting the Doom command line. For
example, DeHackEd patches can automatically be loaded with WAD files.
Currently, it supports the following lumps and types:-
MSG* Any lump of this name is automatically displayed.
README* Any lump of this name can be displayed if the user
HACK* Will be passed to DeHackEd.
(Not many... well, this *IS* only version 0.1, and was written in about
Note that 'raw lump' files are NOT checked.
It can also be used to use a hacked Doom EXE in net games without needing to
do all sorts of renaming.
To install it, first rename your Doom/Doom2 EXE file:-
E:\DOOM\DOOM2>REN DOOM2.EXE RDOOM2.EXE
E:\DOOM\DOOM>REN DOOM.EXE RDOOM.EXE
Note that if you wish to use different names, you will either have to put
up with adding '-run <name>' to the command-line, or change the compiled in
defaults (either re-compile it, or hack the EXE).
Then, copy DOOMRUN.EXE to the either 'DOOM.EXE' or 'DOOM2.EXE':-
E:\DOOM\DOOM2>COPY \HOLD\DOOMRUN.EXE DOOM2.EXE
E:\DOOM\DOOM>COPY \HOLD\DOOMRUN.EXE DOOM.EXE
Edit your DeHackEd.INI file to use the new file as its standard DOOM EXE:-
Find the line 'doomexe = doom.exe' or 'doomexe = doom2.exe', and change
it to 'doomexe = rdoom.exe' or 'doomexe = rdoom2.exe'. Save your changes,
and exit. (You can use another editor if you want).
That's it! You have now installed DoomRun. Using it is very simple, it works
totally transparently*. It also interprets the following command-line
-run <name> Specify the name of the real Doom EXE to execute.
Can be used to execute a different doom executable in
net games! The default is to look for RDOOM.EXE, then
-hackrun <name> Specify the name of your DOOMHACK.EXE file created by
DeHackEd. This will be run instead of the normal
EXE if a WAD contains any DeHackEd patches. The
default is DOOMHACK.EXE.
-dehacked <name> Specifies the command to run DeHackEd. This does not
need the .EXE on the end, as '-run' and '-hackrun'
do, as it is interpretted by your shell (normally
COMMAND.COM). The default is 'dehacked'.
-pager <name> Specify the name of the pager used when viewing
README files. The default is 'more'. The pager must
accept the data on the standard input, i.e. be able
to be used in the syntax "xxx <xxx" or "... | xxx".
-debug Enables DEBUG mode, which will generate lots of
messages about what is happening. Only useful if
you want to see why the program is crashing.
-noexec Disables the execution of the DOOM EXE. Only useful
if you want to see output generated which is not
visible because DOOM clears the screen.
-keephack Stops DoomRun using the '-reload' option the first
time it executes DeHackEd - useful if you want to
play a WAD which has its own hack with another hack.
-batch Tells RunDoom to assume you don't want to read any
-file Specifies files to check. Only WAD files are looked
through - no raw lump files.
* Well, almost. It doesn't support response files yet, so files specified
in those will not be processed.
Feature list planned for version 0.2:-
+ Response file handling.
+ DeuTex IWAD 'merge' stuff.
+ Internal versions of DeHackEd, some kind of pager, and DeuTex (for
the 'merge' feature).
+ Support for configuration file, no more ugly compiled in defaults.
+ Pass all args to Doom as a response file.
+ Code to detect a 'WAD file template' within a readme file, and tell
you what the WAD file is called, and who wrote it, etc.
NOTE: The source code _IS_ available. I just don't want to have tp upload
as much to ftp.cdrom.com, which is why it's not in the archive. Email me
if you want it... but be warned, it's not very organized, and not commented
Tom Lees <email@example.com>