Re: DOS/UMBs: General Tips for Getting More Memory?

Helix applications work different to QEMM/EMM386 etc.

Instead of cramping everything into UMBs, Netroom for example will use a DOS VM to off-load heavy stuff like network software.

Or they may use pointers to point past 1 MB barrier (like Helix Multimedia Cloaking etc does).:
Here, small 1 KB stubs below 1 MB are working like a remote control to control the large, cloaking-enabled software running above 1 MB.

In simple words, I mean. I'm bad at wording, I'm afraid.

Anyway, those alternative ways of running memory heavy things may not cause the usual problems like QEMM/EMM386/386Max do.
So they're worth a try.

The Helix solutions also provide a DPMI host, which can be used if wished.
Using the DPMI host of QEMM instead is also a possibility.

Edited.

Has anyone dug into how EMM386 and friends determine which UMB address space is taken or not when told to scan automatically?
is it literally that if it's full of FF bytes it's free, and anything else, it's taken?
Is it possible that an Intel Atom system, not really being designed to run DOS, might fill unused UMBs with 00 bytes instead?
And as already established, there could be UMB space taken by option ROMs that aren't being used in your system and that you could forcibly overlay using an I= parameter for emm386.