delorie.com/archives/browse.cgi | search |
From: | "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: cwsdpr0.exe 4/15/99 |
Date: | Thu, 15 Apr 1999 21:41:20 |
Organization: | Aspen Technology, Inc. |
Lines: | 9 |
Message-ID: | <37165d00.sandmann@clio.rice.edu> |
References: | <F554E1189472D21198D000805F654BFE59FFE3 AT ntxchangerend DOT engr DOT rendition DOT com> |
NNTP-Posting-Host: | dmcap2.aco.aspentech.com |
X-NewsEditor: | ED-1.5.8 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> So. May I make a bold conclusion that, in cwsdpmi.exe, the linear address > will always equal the physical address even after going through the page > directory and page table stuff (as you guys put it: it is the way set up by > the dpmi host)? No, the pages get re-arranged all over the place when demand paging happens. And the base load point is typically at 0x10000000 for the base of memory. If you really want to understand what's going on, you have to look at the page tables themselves, which you can get to under cwsdpmi.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |