www.delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:1556 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!europa.chnt.gtegsc.com!cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!newsfeed.rice.edu!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: DPMI stuff |
Date: | Tue, 15 Aug 1995 10:24:13 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 6 |
References: | <DDC44A DOT 8sx AT jade DOT mv DOT net> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | clio.rice.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> weird number is with Windows. I get 0x80003000 under QDPMI.) It seems > to me that these values are quite obviously not right (I don't have 2 GIG These base values are correct. You are working with paging and virtual memory, so DPMI can put it anywhere it wants to. There are memory lock examples in src/go32/dpmiexcp.c in the v2 beta source.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |