If I understand correctly...
(Almost) every process/application with Windows 10 x64 is referenced to Virtual (Logical) Memory and is interfaced to a File Mapping Object (in Physical Memory) which in turn is interfaced to the Physical Disk(s).
I am trying in QB64 to interface to RAM (Physical Memory) - initially the requirement is to READ ONLY (RAM), effectively doing a (RAM) MEMORY.DUMP. At present I can only do Memory dump with the Control Panel feature, however there is a very significant time delay between using QB64 and getting latest dump. Improvement is obtained by using a third party software which cannot be effected completely from within QB64 and ALL the RAM (in my case 32 Gbyte) is dumped to external drive.
Any way to access a contiguous section of Physical RAM in real-time using QB64?
Of course, any memory used by say MEM (in QB64) is referenced to Logical addresses which in reality is placed somewhere in Physical Memory by means of the File Mapping Object. My initial reading of Windows API System Services (Memory Management) indicates to me that any memory functions such as copy/move etc relates only to logical addresses.
