Using mft from QEMM tells me that after 640K there is 2K of "Extended BIOS Area". When i try to remove it with "Enable BIOS remap" feature (or smth. simmilar. I do not remember exact naming)? QEMM fails to boot on last stage. Playing whith memory caching in VMware's BIOS didn't get me anything.
On top of what Continuum said.. This is a VIRTUAL machine. I don't understand why people continue to be in denial that SOFTWARE virtualization is NOT NOT hardware.
You CANNOT manipulate the mapping, extended memory or ANY other CPU video related functions, because you do NOT have access to the hardware, it's SOFTWARE emulation, which means that the Virtual machine is an emulation, it's fake, it's not REAL, ANY semblance of real its completely imaginary and it's RANDOM, the other part that people fail to realize. I say it's random because the hypervisor grabs whatever block of memory it can get at the TIME the VM is booted, it's not the same block. And since a VM cannot get access to the Hyper-V, then it's impossible to achieve this.
QEMM was designed for HARDWARE, not software based machines, it was written a long LONG time ago and you will never get this to work, because that architecture has changed a hundred times since then, but now it's not even Intel, its a software rewrite.
So DOS, QEMM, upper memory blocks, video pages, memory paging.. NONE of this can you edit. It's VIRTUAL, which means you can't manipulated it..
UNLESS you write your OWN OS, that's why PARAVIRTUALIZATION was invented.. to do this, conventional OS in a VIRTUAL world is JUST basic, no real bit swapping or even low level assembler can be done.
