JP>> Unfortunately, some of the client-side code is in 
 JP>> DOS4GW.EXE itself, I believe.
 DN> In the copy with Watcom C/C++ 10.6 this is hauled in automatically by
 DN> the stub module. You do need to have the DOS/4GW (i.e. Watcom)
 DN> directory along the path, but you don't need to use DOS4GW.EXE to
 DN> load the program.
Yes, but all that that means is that the stub program was augmented so that 
it went searching for DOS4GW.EXE along the path if the executable was invoked 
directly.  DOS4GW.EXE is still required.  
On a system with a DPMI host of its own (such as an OS/2 Virtual DOS 
Machine), the DPMI host built in to DOS4GW.EXE (i.e. "VMM") isn't required 
and won't be initialised by the DPMI client.  But that doesn't mean that 
DOS4GW.EXE itself is superfluous, because I believe that not all of the 
client side code is in the application executable itself.  At the very least, 
the loader for the LE format that brings the "real" program into memory seems 
to be in DOS4GW.EXE.  I suspect that that is not the only "necessary" DPMI 
client code that resides in DOS4GW.EXE instead of the application executable 
itself.
 ¯ JdeBP ®
--- FleetStreet 1.16 NR
---------------