Hi Metick,
First of all, thank you for this amazing DMA Library! It works flawlessly for native Windows processes.
I have a feature request regarding emulator memory mapping. I am currently working on a project involving the Gameloop 64-bit emulator (aow.exe). Since emulators run inside a nested virtualization layer, standard virtual-to-physical translation hooks don't easily catch the guest OS directory bases (dynamic CR3 / NPT Page Tables).
Would you consider adding a helper function or an extension to the DMALibrary that allows users to manually pass a custom Directory Base or handles nested page table parsing for emulators?
If you don't have plans to officially support this, could you point me to which part of your memory reading logic (VMMDLL calls) I should modify to implement a custom virtual-to-physical parser?
Thanks a lot for your time!
Hi Metick,
First of all, thank you for this amazing DMA Library! It works flawlessly for native Windows processes.
I have a feature request regarding emulator memory mapping. I am currently working on a project involving the Gameloop 64-bit emulator (aow.exe). Since emulators run inside a nested virtualization layer, standard virtual-to-physical translation hooks don't easily catch the guest OS directory bases (dynamic CR3 / NPT Page Tables).
Would you consider adding a helper function or an extension to the DMALibrary that allows users to manually pass a custom Directory Base or handles nested page table parsing for emulators?
If you don't have plans to officially support this, could you point me to which part of your memory reading logic (VMMDLL calls) I should modify to implement a custom virtual-to-physical parser?
Thanks a lot for your time!