Required files:

Filename	Where
voldir.exe	current directory or a directory in the PATH
cygwin1.dll	C:\WINDOWS\SYSTEM or same directory as VOLDIR.EXE
vtextract.exe	current directory or a directory in the PATH
                (optional, used for running the batch files)

Usage:
voldir volfile.vol [extractor.bat]

volfile.vol is the name of the .vol file to get a file listing for.
extractor.bat (optional) is the name of the batch file to store extract
              commands into. The batch file will require that vtextract.exe
              be in the current directory or the path.


So if you just type (for example)

"voldir male2.vol"
you will get the directory of the male2.vol file, one file per line

"voldir male2.vol > male2.vol.list"
you will get the directory of the male2.vol file, one file per line,
stored into the male2.vol.list file. Note: the carriage returns in the
resulting .list file are incomplete. Some text editors (like Notepad)
may not display the .list file properly. A program like WordPad will, so
you can copy out of there and paste into Notepad in order to fix it.

"voldir male2.vol male2.vol.bat"
you will get a batch file which extracts every file of male2.vol, using
Dynamix's vtextract program. You can then simply enter
"male2.vol.bat"
and every file in male2.vol will be extracted

A note:
You may occasionally get a "voldir.dbg" file. This file is created
for debugging purposes. If all goes will, it gets deleted. If something
goes wrong (or you don't specify a .vol file on the command line), it
sticks around. It's perfectly safe to delete this file.

Thanks to LabRat for the hints on the .vol file format

This program was developed under Unix (FreeBSD 2.2.5) using LE (a text editor),
gdb (the GNU debugger), and gcc (GNU C compiler). On FreeBSD, the compiled voldir
executable is only 15k.

The Windows executable was compiled using Cygnus' Win32 GCC port. The Win32 executable
ballooned to 304k because M$ is a crappy operating system to program ANSI C on.

This program took much longer to write than I would have liked (something like 5 hours,
including debugging and documentation and finding a free Windows C compiler).
