BJ> And you are building on a Win32 system, correct?  I 
 BJ> don't remember what Scott said he last compiled the 
 BJ> code on.  

Probably a w2k box. The source docs says only the NT executables
compilation on Windows 2000 is supported, with some implicit instructions
for OS/2.

 ML> Dmake complains my version of WLIB can't support 
 ML> overlays but I'm using a full installation of Watcom 
 ML> 11c. So my guess is a failed / missing option or 
 ML> missing/incorrect environment variable set in the batch 
 ML> files I'm supposed to run (snt.bat, setwc.bat, 
 ML> setwc11.bat, varnt.bat var2nt.bat etc) .

 BJ> Very likely.....

It turns out that 16 bit DOS overlays were reinstated in the Open Watcom
linker since v1.4. 

I tried manually sending the wlink command as sent by dmake to compile the
failed object again, which still didn't work albeit the Watcom 11c linker
was used.

I then substituted the Open Watcom linker and it worked (without
modification of the make file or any batch variables).

So I concluded that the Watcom 11c linker doesn't do overlay.

 ML> The compile doesn't even get half as far when building 
 ML> the Win32 executables.

 BJ> Not supprised.  You may need to run the make scripts 
 BJ> more than once.  Some times libraries needed to link in 
 BJ> are compiled out of order and the first time through 
 BJ> you end up with a failed overall compile, but some of 
 BJ> the libraries are compiled that will then be found in 
 BJ> later attempts to recompile the code....

It appears the compilation process automatically creates missing lib files if it can.

[cut]

 BJ> Did you attempt multiple, repeated compiles using the 
 BJ> same set of compilation switches or the same master compile script?

Heaps of times. :)

--- Maximus/2 3.01