Xref: news-dnh.mv.net comp.os.msdos.djgpp:1309
Path: news-dnh.mv.net!mv!news.sprintlink.net!howland.reston.ans.net!swrinde!news.uh.edu!uuneo.neosoft.com!news!sandmann
From: Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DPMI Graphics and DJGPP V2
Date: Tue, 01 Aug 1995 19:04:06 CDT
Organization: NeoSoft Internet Services +1 713 968 5800
Lines: 12
References: <DCnA0B DOT 2I1 AT jade DOT mv DOT net>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: praline.no.neosoft.com
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> was said to be easily portable to DJGPP version 2.  There are two things that
> I will need to know: is there an equivalent to _GO32_dpmi_simulate_int() and
> the _go32_dpmi_registers? and how can I use farptr.h to directly write to
> the VESA frame buffer window at 0xD0000000?

the _go32_dpmi_* functions are still available in V2

The frame window at 0xd0000000 is *NOT* available under any DPMI, V1.x or V2.0
and cannot be made available.  You can access the vidram at 0xa0000 or a
linear extended memory buffer via many different methods.  The farptr
routines will always work, memory mapping and/or near pointers may work 
depending on the DPMI provider.