Xref:	news-dnh.mv.net comp.os.msdos.djgpp:3979
Path:	news-dnh.mv.net!mv!news.sprintlink.net!datalytics!news.ahc.ameritech.com!ddsw1!news.mcs.net!van-bc!news.mindlink.net!agate!howland.reston.ans.net!newsfeed.internetmci.com!chi-news.cic.net!nntp.coast.net!harbinger.cc.monash.edu.au!newshost.anu.edu.au!newshost.pcug.org.au!e5.pcug.org.au!eyal
From:	eyal AT ise DOT canberra DOT edu DOT au (Eyal Lebedinsky)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Graphics in V2
Date:	19 Dec 1995 20:28:39 GMT
Organization:	Eyal at home
Lines:	22
Sender:	eyal AT e5 DOT pcug DOT org DOT au (Eyal Lebedinsky)
Message-ID:	<4b779n$3rk@supreme.pcug.org.au>
References:	<DJ4M4F DOT Fq3 AT jade DOT mv DOT net>
NNTP-Posting-Host:	ts97.pcug.org.au
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <DJ4M4F DOT Fq3 AT jade DOT mv DOT net>, wroberts AT aug DOT com writes:
|> >What address is the VGA buffer mapped to in V2 ?
|> >
|> >I've tried writing to 0xD0000000, 0xD1000000, and 0xA0000000 - all 
|> >the r/w video address mentioned in the docs.
|> >
|> Here's a snippet of code that uses the _farpokeb() function to plot a pixel:
[snippet deleted]

The example given gains access to the real-mode VGA frame memory. This is not what
the original poster was asking (and not what I, too, am looking for).

Go32 had a feature where the full video memory was mapped into a known virtual
address (it was 0xd0000000). You simply wrote to it, and if you hit a bank which
was not mapped then go32 (using the current video driver) will take care of it.

With v2 this virtual address gives a memory protection fault.

Anyone knows how to set up the same feature with v2?

--
Eyal Lebedinsky		(eyal AT ise DOT canberra DOT edu DOT au, eyal AT pcug DOT org DOT au)

- Raw text -