Xref: news2.mv.net comp.os.msdos.djgpp:2819
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Transition from DJGPP1 to DJGPP 2.0
Date: Wed, 17 Apr 1996 14:58:27 CDT
Organization: Rice University, Houston, Texas
Lines: 19
Message-ID: <31754d63.sandmann@clio.rice.edu>
References: <4kqabd$lo9 AT freenet-news DOT carleton DOT ca>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> In DJGPP 2.0, the 0xD0000000 address for video memory was removed.

Not really true - this functionality didn't exist uniformly in V1.x either.
It was only available if not running with DPMI, so you could never run
these sorts of programs under Windows, QDPMI, OS/2, etc.  And you couldn't
use this functionality unless someone took the time to write a driver for
the particular video card.

There are ways to make this type of thing work, but it's much easier to
just use univbe to get a VBE 2.0 linear frame buffer.

> This will break virtually all my already written programs, requiring me to
> rewrite all their video functions to use the slower libgr that routines,
> and requiring me to completely rewrite programs that use a blitting
> function I wrote.

You can continue to run under V1.12 for these programs and migrate to V2
if you ever need to work with an advanced environment, in which case you
need to re-write it anyway.