This would be trivial (and fun) to implement with Wasm.
Wasm also supports multimemories, https://github.com/WebAssembly/multi-memory
https://github.com/WebAssembly/multi-memory/blob/main/propos...
The scaling point is what I was thinking of.
"As long as Wasm memories are limited to 32 bit address space, there is no way to scale out of 4 GB memory efficiently. Multiple memories at least provide an efficient workaround until 64 bit memories become available (which may still take a while)."
So pretty similar to launching several processes on 32 bit NT or Linux, each having their own memory space.
One program (com) I wrote with it back then is still being used by at least one person. I talked to them a couple of months ago and they said they still use it.
I used it for Empire, and for my text editor. When moving to Linux, it was easy to convert to using TTY sequences.
Phillipe Kahn is a marketing genius, and I am not.
(VCM's overlays could be loaded anywhere, the relocation happened at runtime.)
It works like a virtual memory system, except that the compiler emitted the necessary code rather than the CPU doing it in microcode.
https://www.digitalmars.com/ctg/handle-pointers.html
Similarly, Zortech C++ had the "VCM" memory model, which worked like virtual memory. Your code pages would be swapped in an out of memory as needed.
https://digitalmars.com/ctg/vcm.html