From: lonniem AT cs DOT utexas DOT edu (Lonnie McCullough) Newsgroups: comp.os.msdos.djgpp Subject: Re: Vesa 2.0 is slower than 1.2 on my video card !!!!! Date: Sun, 27 Jul 1997 05:16:58 GMT Message-ID: <33dad80e.4790417@news.nol.net> References: <199707221500 DOT IAA26318 AT adit DOT ap DOT net> <33d79d82 DOT 403618 AT news1 DOT telepac DOT pt> <33d8d7a0 DOT 2209688 AT news1 DOT telepac DOT pt> <33da53b7 DOT 2937881 AT news1 DOT telepac DOT pt> <33db5521 DOT 3300648 AT news1 DOT telepac DOT pt> NNTP-Posting-Host: ip38-47.nol.net Lines: 22 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk On Sat, 26 Jul 1997 19:52:33 GMT, Myke AT cyberdude DOT com (Ricardo Cunha) wrote: >P.S.: If what you said is true how can a board that doesn't supports >Vesa 1.2 support those calls simple by using UniBve? > UniVBE simply provides an interface to routines that implement the VESA VBE standard. Alot of video cards have Linear Frame Buffer capability (just like many have hardware blitting, line and circle drawing functionality) but the method to set an LFB mode (or any SVGA mode) is not standard across all cards because when the first SVGA's came out there was no standard everyone had to comply with as was the case with the first VGA clones. It was every hardware engineer for himself. This was a bad thing so VESA devised the VBE specs to make it standard. If UniVBE can figure out what card is in your system it can install a driver that will correctly implement all the features of the VBE just because it knows what registers to write to to get a desired effect. Sorry for the long winded explanation. Lonnie McCullough lonniem AT cs DOT utexas DOT edu