Mail Archives: djgpp/1997/08/02/13:02:08
>I have a Cirrus Logic 5440. only supports Vesa 1.2 but with an
>emulator i can run Games (or others) that use Vesa 2.0.
>It's simple. One Tsr locks the interrupt used by Vesa 2.0 then when it
>gets a Call like putpixel(50,70,5). It calculates the bank (Vesa 1.2
>or native calls) where that pixel is then it allocates that bank and
>sends the pixel information. Theres more time spend using this metod
>that using direct Vesa 1.2 or board native calls
>----------------------------------------------
>Ricardo Cunha
>myke AT cyberdude DOT com
>http://www.geocities.com/Area51/Cavern/7471
>ICQ: 2217830
>----------------------------------------------
Good lord that is so wrong.. first of all Shawn H. is the most correct
in this entire thread. First off, VESA 1.2 nor 2.0 has API gateways
for accessing video memory. It will set up memory so your program can
access it, but it would do a putpixel(x,y). Second, VESA is a
standard, not this video god that empowers your system. Essentially
VESA just translates your int calls into native video calls. all
Scitech did was ask for every vendor for the specs of their cards and
then standardize all the calls into a buggy worthless environment ;)..
even the oldest of Hi-Color vid-cards supports linear buffers. You'd
just hafta know how to access the ports on you trident-1mb. Why is
VESA 2.0 slower. Well lets see. Of the top of my head i can think of
about 3 reasons. Give the thread your computer setup, the resolution,
color depth and mode of operation. Then we can answer you question
better. Just remember. SDD doesn't convert 2.0 calls to 1.2 and send
them to ROM. If that were true, then my Trident that supports VESA
1.02 wouldn't work.
mint- try linux. ;)
mint
- Raw text -