Is there an API call under win95 to get a block of memory<br>
that is actual ram on board, and not virutal (eligible to be<br>
paged out)? I have 64 meg and I would like to reserve <br>
a large block, say 15 or 20 meg that will stay FIXED to<br>
the motherboard ram (above the 1 meg line, of course),<br>
so that my program can have instant access to any byte<br>
within the block allocated, without fear of having to see my<br>
hard-drive light blinking while WIN95 pages in and out<br>
needlessly. For DOS programmer's, you know you can<br>
run real mode with the granularity bit set on for GS, FS, and<br>
even ES, and you can overrides to get acces to all the<br>
ram on your motherboard without having to experience<br>
hard drive "paging". This is very fast, but when I try this<br>
under win95, somehow it thinks it has to go wild paging<br>
in and out. What gives? It makes memory intensive<br>
computations take many times longer. Using DOS4g<br>
(that's what it is called) means you lose all the good<br>
benefits of win95, but then you lose fixed access to <br>
board ram with win95. How do windows programmers<br>
solve that problem? How do you get what we mainframers<br>
call VIRTUAL=REAL (non-pagealbe main memory)?<br>
Thanks, Jerry Burnett alcman@neto.com

You can call the MS extentions API to lock down the HD.<br>
While this of course, fails all writes to the HD, it also<br>
prevents paging to and from the HD. You can mail me for the <br>
code if you wish. However, it might not be useful due to<br>
the adverse affects on other programs. Many simply don't<br>
recover properly from a failed disk write.


URL:http://acheronx.resnet.tamu.edu/home/

You can call the MS extentions API to lock down the HD.<br>
While this of course, fails all writes to the HD, it also<br>
prevents paging to and from the HD. You can mail me for the <br>
code if you wish. However, it might not be useful due to<br>
the adverse affects on other programs. Many simply don't<br>
recover properly from a failed disk write.


URL:http://acheronx.resnet.tamu.edu/home/

User GlobalLock<br>
: Is there an API call under win95 to get a block of memory<br>
: that is actual ram on board, and not virutal (eligible to be<br>
: paged out)? I have 64 meg and I would like to reserve <br>
: a large block, say 15 or 20 meg that will stay FIXED to<br>
: the motherboard ram (above the 1 meg line, of course),<br>
: so that my program can have instant access to any byte<br>
: within the block allocated, without fear of having to see my<br>
: hard-drive light blinking while WIN95 pages in and out<br>
: needlessly. For DOS programmer's, you know you can<br>
: run real mode with the granularity bit set on for GS, FS, and<br>
: even ES, and you can overrides to get acces to all the<br>
: ram on your motherboard without having to experience<br>
: hard drive "paging". This is very fast, but when I try this<br>
: under win95, somehow it thinks it has to go wild paging<br>
: in and out. What gives? It makes memory intensive<br>
: computations take many times longer. Using DOS4g<br>
: (that's what it is called) means you lose all the good<br>
: benefits of win95, but then you lose fixed access to <br>
: board ram with win95. How do windows programmers<br>
: solve that problem? How do you get what we mainframers<br>
: call VIRTUAL=REAL (non-pagealbe main memory)?<br>
: Thanks, Jerry Burnett alcman@neto.com<br>
: <br>
<br>