🚀 go-pugleaf

I am having problems getting enough memory when using VLMs with 
expanded memory, compared to EMSNETX.

MEM /C reports EMSNETX as using 10K of conventional memory and
no UMB memory.

With the VLMs it reports about 47K total.  This includes 'Data'
space of about 40K, which is the global segment reported by VLM /D.
I can force this data into UMBs by 
  Load low CONN = OFF
  Load low IPXNCP = OFF
which makes it run _very_ slow (indeed, VLM /D itself runs 
very slow when listing the modules) but even that doesn't really 
help as UMB space is very tight because of the EMS page table.
Using VLM /ME doesn't reduce memory use at all, I assume this is 
moving the VLM code itself from XMS to EMS which is no help.

So: for all the VLMs' claimed automatic and transparent use of 
EMS and XMS, the VLMs have a 47K conventional+UMB footprint 
compared to EMSNETX's 10K.  I know I can chip away tiny amounts
by disabling some VLM features but how I do I bring it down to 10K?