Xref:	news-dnh.mv.net comp.os.msdos.djgpp:4010
Path:	news-dnh.mv.net!mv!news.sprintlink.net!howland.reston.ans.net!newsfeed.internetmci.com!news.mel.aone.net.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:	22 Dec 1995 22:06:43 GMT
Organization:	Eyal at home
Lines:	23
Sender:	eyal AT e5 DOT pcug DOT org DOT au (Eyal Lebedinsky)
Message-ID:	<4bfa5j$e1u@supreme.pcug.org.au>
References:	<DJq0vw DOT 8K2 AT jade DOT mv DOT net>
NNTP-Posting-Host:	ts92.pcug.org.au
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Fri, 8 Dec 1995, Christopher Chlap wrote:

> >If your video card has the capabilities of mapping a linear buffer in
> >extended memory, there is a VBE.ZIP example floating around which shows
> >how to turn this on and directly write to the card with both near pointers
> >and far pointers.
> Where is this file and what is its exact name ?

*Please* can someone answer the original question: how to access the full
(NOT linear) video memory as it was done in v1?

In v1 you could access 0xb0000000 which was where your full video memory was.
When your card would not support linear memory, go32 will bank switch as
required (transparently, in response to page faults) so that it would
appear to the user as if the full video memory is there.

Now with v2 the above address is not mapped, Where is it?

Thanks.


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

- Raw text -