Xref:	news-dnh.mv.net comp.os.msdos.djgpp:402
Path:	news-dnh.mv.net!mv!news.sprintlink.net!europa.chnt.gtegsc.com!cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!news.sesqui.net!rice!news!sandmann
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Graphics mapping for V 2.0
Date:	Fri, 16 Jun 1995 12:10:08 CDT
Organization:	Rice University, Houston, Texas
Lines:	7
References:	<3rs5ds$fip AT newsbf02 DOT news DOT aol DOT com>
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

>   I have been told that under v 2.0 the mapping of memory to 0xd0000000
> will not work.  Could someone tell me how this is going to be done under v2.0?

The same way you have to do it under DPMI with V1.x - with far pointers and
setting up the frame yourself.  GRX 2.0 (in beta) does this when calling it's
routines.  We are also working on a way to write to the buffer with near 
pointers - but you still would not have the page fault based video drivers in V2

- Raw text -