2002.08.21 11:48 "Re: OT: large memory allocation in Windows", by Peter Nielsen
How about a memory mapped file? Could that possibly give you a linear "pointer space" of 2GB or maybe even more? Of course the file would not be completely mapped at all times, but maybe it would do the trick... (Just a crazy idea. I don't know if it would work at all...)
- stop all services not needed
- try to allocate memory before starting anything else
- a last (awful) solution is to write a memory-class, which maps chunks
on some virtual contiguous memory. (looks a hell of a job to me). Memory allocated by this class could only be accessed through this class, not by pointer aritmatic like "x = *p + 35".
--- Roger Bedell <email@example.com> wrote:
I am also confused about memory allocation. For the life of me, I cannot get Windows to allocate more memory than is contiguous in physical memory. In other words, if I do a GlobalAlloc for a fairly large chunk (perhaps 1GB or so), it always fails, even though I have lots of virtual memory. Anyone suggestions?