CompuServe Messages

But practically all software uses MEMF_PUBLIC already, which means the virtual memory mapper would not be winning much. Also I imagine there are a sufficient number of interrupt things which do not use MEMF_PUBLIC as to make it practially unimplementable, without throwing out a lot of code, which won't be obvious until until somebody actually tries to implement virtual memory. Simple enough to say "but those programs are breaking the rules!!!", but that won't get you very far when you try to boot your system and it hangs. As a simple example, what should LoadSeg do with memory allocations? There are hunk-definitions for memory type, but it has never mattered if something threw in the "public" bit or not.