Poking unallocated memory

new topic     » topic index » view thread      » older message » newer message 

Greetings,

My application requires direct access to the top of memory space, near 
the 4 GB limit (where the BIOS resides). As one might expect, the 
CauseWay DOS extender does not allow this, and aborts with a protection 
fault.

If there was actually memory in this area, maybe I could find a way to 
allocate it first, and then poke it. But this is just memory "space", 
not actual memory. 

Any ideas?

Thanks,
-Ben

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu