
    A few notes on this version of ZenNode:

 1) This programs does NOT check to see if you have a valid .WAD file to
    begin with.  If you don't, ZenNode will dutifully build it's data
    structures for the .WAD file, but DOOM may behave unpredictably.
				  
 2) If you don't specify an output filename, the results will be written
    to a .WAD with the orignal filename in the current directory.  If the
    .WAD you specified as the source is in the current directory, your
    ORIGINAL .WAD WILL BE OVERWRITTEN.

 3) This version will not extract a single level from a .WAD file. ie:
    If you specify a level on the command line, that level will rebuilt
    and the entire .WAD file will be rewritten.

 4) If the ZenNode detects that the new resources ( NODES, SEGS, BLOCKMAP, 
    etc. ) are the same as those in the original file, the file is not 
    rewritten.  That is, if you run the program twice on the same .WAD 
    file, the second time, after generating the resources, it will not 
    update the file.  ( No big deal, just thought you might like to know. )

 5) Since ZenNode only builds resources ( ie: NODES and related structures ),
    it WILL rebuild levels E1M1 - E1M9.  By id Software's request, you are
    asked not to distribute custom levels below E2M1 for DOOM/Heretic.

 6) At any time while building a .WAD, file pressing <ESC> will stop ZenNode
    from rebuilding any further levels in the .WAD file.  However, it will
    continue rebuilding the level it is currently on.  Any levels that have
    been rebuilt will be written to the .WAD file before exiting.

 7) This version does not preserve any .EA's associated with a .WAD file.
    In general, this isn't a problem since the current version of DOOM only
    runs under DOS ( well actually a DOS extender under DOS ) and can't make
    use of EA's anyway.

 8) ZenNode stores any new data for a level in memory until the .WAD file is
    rewritten.  This means that if you rebuild a large .WAD file with lots of
    levels ( id's IWADs for example ), ZenNode may need a lot of memory.  If
    you run into memory problems ( usually indicated by an 'Abnormal program
    termination' message ), use the level selection option and do a few at a
    time. For example:

        C:\> ZenNode DOOM2 map01+map02+map03+map+04+map05 
        C:\> ZenNode DOOM2 map06+map07+map08+map+09+map10
        ...

 9) I haven't verified that this version works properly with PolyObjects (
    the moving sectors in HEXEN ).  Since there aren't many editors for 
    HEXEN out yet, this shouldn't be a major problem.
