COMPILING NOTES
===============

	The included file compile.bat should work if you have a properly
installed and configured copy of Borland C++ 3.1.  I have no idea if it
works with any other version of Borland C, but the file is simple enough
that you can modify it to suit your compiler.
	All .c and .h files inclided in this .zip are required.  Here's a list
of them:

	wadcomp.c -- source for wadcomp.exe
	extract.c -- source for extract.exe
	list.c    -- source for list.exe
	wads.c    -- a collection of functions used in all of the above
	mylib.c   -- a collection of functions that perform error checking
		     (you can modify wads.h so that mylib.c is not required
		      -- see mylib.h for details)
	wads.h
	mylib.h

The suggested memory models are:
	compact for extract.exe and wadcomp.exe;
	tiny fo list.exe.
The only reason extract.exe and compile.exe require the compact model is that
they can create WAD files, so they need enough memory for the wad directory.
For small files the directory is at most a few K, but for IWADS (2000-3000
entries) the directory size may approach 64K.  However, there's no point in
using a DOS extender, since 64K is enough for 4096 entries, and even DOO2.WAD
does not have that many.


These programs were written to work under DOS.  Wadcomp uses functions from
<dir.h>, and thus may not compile on other systems.  Extract will probably
compile fine, but using it under Unix poses two problems.  First, it assumes
that back slashes ('\') are used in directory names.  Second, one of extract's
parameters can contain wildcards, which are processed by the program.  If
these get processed by the shell, the program will likely get confused.  List
also has this problem.
