by Does anyone know a trick to bar WIN386.EXE from loading itself into
conventional memory, after using available upper memory? On some
machines WIN386.EXE uses only a very small amount of conventional
memory, even if there isn't that much upper memory available, loading
itself in extended memory (I assume). On other machines, it uses a very
large chunk of conventional memory.
I have applications running on the network that need expanded memory
support and the use of VLM instead of NETX. I can configure most
computers to enter Windows with about 570,000 bytes available
conventional memory, having all the network drivers loaded and expanded
memory support. On some computers though, WIN386.EXE brings down
available conventional memory to about 480,000, which makes those
computers to be very unstable in both Windows and DOS applications.
I would appreciate very, very much if somebody knows a solution to this
problem!!