delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:3853 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!cs.utexas.edu!academ!news.sesqui.net!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Getting the physical address of allocated virtual memory |
Date: | Thu, 14 Dec 1995 10:32:22 CST |
Organization: | Rice University, Houston, Texas |
Lines: | 10 |
Message-ID: | <30d05196.sandmann@clio.rice.edu> |
References: | <DJJpC6 DOT 2C5 AT jade DOT mv DOT net> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
[Nice solution to DMA buffer above 640K using XMS snipped] Cool. A nice piece of code to keep as an example. It does depend on XMS memory being free, so you must be running under a memory manager. If you are running under XMS alone (no emm) with CWSDPMI, it would allocate it all. Under some other DPMI environments, I don't know what they would do either. This will also mess up the perceived free memory in CWSDPMI (but this normally shouldn't matter). This is a nice solution to big DMA buffer requirements, thanks!
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |