BS>    Are you suggesting that when I run a program on Warp 4 in a DOS
 BS> box, that normally requires the use of DOS4GW.EXE, I can configure
 BS> things so that DOS4GW is neither needed nor used?
No.  There are at least two separate things in DOS/4GW: client-side code to 
use a DPMI host to switch into protected mode and make memory requests to it 
once there, and a DPMI host.
When invoked on DOS, without an existing DPMI host present, the client-side 
code in DOS/4GW detects this and starts up its DPMI host, the "virtual memory 
manager" in the DOS/4GW documentation, for it to talk to.  When invoked on 
OS/2 in a VDM, there's already a DPMI host in existence : OS/2 itself.  So 
the client-side code in DOS/4GW doesn't try to start its built-in DPMI host.
You can eliminate the need for a separate _executable_, i.e. DOS4GW.EXE, if 
you are a developer who has a copy of DOS/4G, since that version of the 
product allows you to bind the DOS-extender code into the application EXE 
itself.  The normal operation of DOS/4GW programs is to have a "stub" program 
that does little more than search for DOS4GW.EXE, load it, and tell it to 
load and run the main program from the rest of the application executable. 
There's not much advantage in doing so, however, and several advantages in 
keeping the DOS extender and DPMI client in DOS4GW.EXE.  
 ¯ JdeBP ®
--- FleetStreet 1.16 NR
---------------