From: Niklas Newsgroups: comp.os.msdos.djgpp,comp.graphics.algorithms Subject: Re: VESA 2.0 and NEAR PTR Date: Mon, 10 Mar 1997 11:10:43 +0100 Organization: Stockholm University Lines: 29 Distribution: world Message-ID: 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 In-Reply-To: <3323C8DB.308F@eps.agfa.be> 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. And I see that I've entered the correct mode, it's just the set-pixel-function that doesn't work. Niklas