www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/12/07/10:06:45

Date: Wed, 7 Dec 94 00:10:30 -0500
From: dj AT stealth DOT ctron DOT com (DJ Delorie)
To: UCKO AT VAX1 DOT ROCKHURST DOT EDU
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: V2 and commercial level programs

> >> PPS: any detail about the way you'll access video memory with V2 ?
> >
> >Depends on the card.  For normal SVGA, through the 0xa0000 window.
> 
> Whoa...I thought you said that sort of thing didn't work with DPMI...
> which is the only extender interface supported by V2, n'est-ce pas?
> AFAIK (although I'm not really involved in this, so my opinions should
> be taken with at least one grain of salt...) the only real way to
> handle graphics in V2 involves messing with BIOS routines (some of which,
> of course, can be replaced/supplanted with port i/o) and/or page frames
> in DOS memory.  Microsoft can be _so_ irritating at times... :-)

The part that doesn't work in DPMI currently is go32's automatic page
frame based graphics memory window moving routines, which give you a
virtual frame buffer.

You've always been able to write to the graphics window yourself,
provided you knew how to move the vram window.  In V2, this is how you
have to do it.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019