Quote - I think there's a little bit more to it than that, as you need some way to guarantee that application's memory is not grabbed by some other process (including OS) - and if you completely ignore the OS's memory management, as you seem to want to do, then you need some way to protect your app's memory from being ripped off by other running apps, which suggests to me you need to write a completely separate memory manager that the OS will use at a very low level.

That is why the idea is to use XP32 or Windows 98, neither of them have an idea what is 64 bits and the existence of the extra memory, so nobody will touch this memory (they don't know that it exist!). As for other applications, as they are 32 bit too, in the same way they don't know about the extra memory. The only problem can happen is if I try to run at the same time two applications made by me that use this special memory management, but for what I shall want to do two renderings at the same time!??
For the rendering process once all elements are loaded I need Windows for nothing. I only will need Windows memory management, once the rendering is complete, to copy the image from the render buffer to the video buffer.
A memory management to be used only by one active application is very simple and only has few lines of code (of course no virtual memory, for what I need the disk if I have a lot of RAM?).

Stupidity also evolves!