From: Niklas <d95-nlu AT nada DOT kth DOT se>
Newsgroups: comp.os.msdos.djgpp,comp.graphics.algorithms
Subject: Re: VESA 2.0 and NEAR PTR
Date: Mon, 10 Mar 1997 11:05:30 +0100
Organization: Solace Computer Society
Lines: 27
Message-ID: <3323DCEA.3B21@nada.kth.se>
References: <33232BE7 DOT 2F3D AT nada DOT kth DOT se> <3323C8DB DOT 308F AT eps DOT agfa DOT be>
NNTP-Posting-Host: mastermind.nada.kth.se
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> [Snip]
> 
> >
> >   int mode = 0x4101;
> >
> >   VBE_getmodeinfo(mode, &modeinfo);
> >   if(modeinfo.ModeAttributes & 0x8)
> >     printf("Linear frame buffer found\n");
> >   else {
> >     printf("Linear frame buffer not found\n");
> >     exit(1);
> >   }
> >
> 
> [Snip]
> 
> The problem might be that you're assuming mode 640x480 is 0x4101. While
> this was usually true for Vesa 1.2, this is not at all guaranteed in Vesa
> 2.0. The correct way to get the modenumber of the mode you're looking for
> is requesting the mode-table, and scanning that for the desired
> resolution & bits per pixel, thus giving you the right modenumber.
> 

no, I disagree. Have a look at VESA's information on 2.0. It should
always be the same mode-numbers to use.

d95-nlu AT nada DOT kth DOT se