From: James MacDonald <trill AT netbook DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Vesa 2.0 is slower than 1.2 on my video card !!!!!
Date: Sun, 27 Jul 1997 20:37:00 +0100
Organization: Trills and Technologies
Distribution: world
Message-ID: <GAsjkBAcN62zEwFF@netbook.demon.co.uk>
References: <199707221500 DOT IAA26318 AT adit DOT ap DOT net>
 <h9b6bEAOrn1zEwLf AT netbook DOT demon DOT co DOT uk> <33d79d82 DOT 403618 AT news1 DOT telepac DOT pt>
 <xmerm05 DOT 3 DOT 33D8702E AT vse DOT cz> <33d8d7a0 DOT 2209688 AT news1 DOT telepac DOT pt>
 <q07JZBAD6R2zEwTj AT talula DOT demon DOT co DOT uk> <33da53b7 DOT 2937881 AT news1 DOT telepac DOT pt>
 <n78bqBAfsx2zEwSk AT netbook DOT demon DOT co DOT uk> <33db759d DOT 717585 AT news1 DOT telepac DOT pt>
NNTP-Posting-Host: netbook.demon.co.uk
MIME-Version: 1.0
Lines: 39
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <33db759d DOT 717585 AT news1 DOT telepac DOT pt>, Ricardo Cunha
<Myke AT cyberdude DOT com> scribbled :
>Dasse...
>
>Maybe it's my fault, i'm not so good at english :)
>
>It's better to start from the begin.
>
>Someone tould us that is vesa 2.0 (using linear memory) was slower
>that it Vesa 1.2
>So, i think that maybe, maybe the emulator that he was running didn't
>support directly is board. In that cases if the emulator (Vesa 2.0)
>detects Vesa 1.2 it redirects Vesa 2.0 calls to board by using Vesa
>1.2 calls. This process it's much slower than using Vesa 1.2 calls
>because he must "convert" Vesa 2.0 to Vesa 1.2
>I don't know the details of the process i only know how this can be
>done.

STOOOOOOOOOOOOOOOOOOOOOP!!!!!
I have an ATI mach64 which has VBE 1.2, which is slower than 2.0, and
the SECOND that I load UniVBE, that buggy VBE 1.2 is gone for ever more.
Will you please get it through your thick head that VESA is a >software<
API, and that it can be replaced by >software<. UniVBE is NOT an
emulator, it >IS< VBE 2.0, and it never shall be an emulator.

The whole point of VBE 2.0 is to have a protect mode API, and allow more
flexible and FASTER video modes. UniVBE and all VESA implementations
convert VESA calls to direct hardware writes. UniVBE knows your video
card better than you do. It knows which registers to peek, poke, push
and pop, and it does pure direct hardware writes only.

If UniVBE does not support your video card, it will not load. Period.
I know, because I can try it with UniVBE 5.1 - it doesn't work. UniVBE
5.2 works perfectly.
-- 
Revised anti-spam in use : remove X to reply - 
'Xnetbook' becomes 'netbook'

Anti-spam thermonuclear warheads cheap at only $300!