From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: VBE 2.0
Date: Sun, 13 Jul 1997 09:40:27 +0100
Organization: None
Distribution: world
Message-ID: <BsBD$DA7RJyzEwWQ@talula.demon.co.uk>
References: <01bc8f12$46ef4340$LocalHost AT nop44597>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 28
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Silent Dreamer writes:
>I'm making a VBE 2.0 lib, i getting an hard time at:
>
>Deciding the best method of accesing the video memory.
>What functions should i use ?
>Should i create a descriptor, and set its base to create an offset of 0 ?

That's how I do it in Allegro. But use whatever works best for you...

>Also. Are the video mode numbers fixed.
>From univbe 5.1 to univbe 5.3, i think the 320*200*8 changed from 153 to
>163. (I THINK)
>
>Should we trust the numbers, or should we shearch for mode that suits our
>needs ?

*Don't* trust that they will stay the same! The VESA spec is very clear
on this:

    Starting with VBE version 2.0 VESA will no longer define new VESA 
    mode numbers and it will not longer be mandatory to support these 
    old mode numbers.  VBE 2.0 aware applications should follow the 
    guidelines in the sample code above for setting a desired mode.


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
Beauty is a French phonetic corruption of a short cloth neck ornament.