From:	Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: WIn95 - DPMI Memory problems
Date:	Tue, 3 Feb 1998 22:08:17 +0000
Organization:	None
Distribution:	world
Message-ID:	<F8MCrAARV510Ewzo@talula.demon.co.uk>
References:	<6b80m7$mqq AT news DOT or DOT intel DOT com>
NNTP-Posting-Host:	talula.demon.co.uk
MIME-Version:	1.0
Lines:	26
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Sivakumar Radhakrishnan writes:
>       Perhaps this question has been raised by someone else 
>regarding DMPI and win95. We are currently having run time errors
>when executing "__dpmi_map_physcial_memory() in WIn95.

I presume you mean the __djgpp_map_physical_memory() function, and
saying dpmi is just a typo?

Bad news, I'm afraid. This routine uses a DPMI 1.0 function call, but
win95 only supports DPMI 0.9, so it will always fail. There is no way to
do that kind of memory mapping under Windows.

>The question is how can we fix this problem and if possible where can 
>one get the DMPI v 1.0.

You can't. CWSDPMI supports several of the DPMI 1.0 functions, so this
code will work fine when using that under DOS, but it is impossible to
replace the operating system DPMI when you are running under a protected
mode system like win95. I think it is very unlikely that Microsoft will
ever bother to support DPMI 1.0, so I'm afraid your only solutions are
not to use win95, or not to use these functions...


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
"Pigs use it for a tambourine" - Frank Zappa

- Raw text -