Welcome Guest ( Log In | Register )
Digg this topic Add to my del.icio.us Submit to SlashDot 3 Pages V  < 1 2 3  
Reply to this topicStart new topic
> Universal Windows 9x/NT3/NT4/2K/XP/2003 video driver, VESA/VBE based Windows-family driver.
razvanz
post Jul 9 2007, 07:34 AM
Post #21


Newbie
*

Group: Members
Posts: 2
Thank(s): 0
Joined: 2-November 06
Member No.: 1,050



bearwindows,
I'm convinced that you can help me, you have the required VESA programming knowledge, it's easy stuff, only that I'm too much of a beginner in what programming is concerned.
I already have a driver for Cirrus5430.
http://rapidshare.com/files/41861616/Cirru...ic5430.rar.html

You can find the sources there.
What I need is either to turn that driver into a generic one or get one that initalises VESA instead of communicating directly with the display adapter.
I tried to binary patch the vendor ID and device ID in a compiled driver, but it didn't work that way.

Any help would be greatly appreciated.
Go to the top of the page
 
+Quote Post
bearwindows
post Jul 9 2007, 05:34 PM
Post #22


Advanced Member
***

Group: Developer
Posts: 37
Thank(s): 0
Joined: 5-June 07
Member No.: 8,262



QUOTE (razvanz @ Jul 9 2007, 07:34 AM) *

I see it. I don't understand what is all about. :)
References:
1) If you need VBE3 standard datasheet get it here: http://www.vesa.org/public/VBE/vbe3.pdf
2) SVGALib UNIX library http://www.svgalib.org/svgalib-1.4.3.tar.gz
3) original VBEMP.SYS: http://svn.reactos.org/svn/reactos/trunk/r...o/miniport/vbe/
4) WWW/Internet + Google.COM :) :) :)
5) 3 basic testing video platforms = intel/ati(amd)/nvidia chip based videocards. :)
6) lot of time.....

May be it is an interesting project, but:
a) many modern new cards are not FULLY VBE compatible (VBEMP has also problems with them).
b) calling INT10 in protected is a kinda complicated thing. you must discover a way to call it from your code in your case. I worked only with Windows (NT/legacy and WDM/PNP) driver model. This model uses Microsoft defined Int10CallBios() API (or Ke386CallBios() API) which is documented.



Regards, bearwindows.
Go to the top of the page
 
+Quote Post
MedEvil
post Jul 10 2007, 01:34 PM
Post #23


Advanced Member
***

Group: .script developer
Posts: 2,226
Thank(s): 15
Joined: 29-December 06
Member No.: 2,192



Hi bearwindow,
could you tell me what's the advantage of your driver over the default XP driver?

(IMG:http://www.boot-land.net/forums/style_emoticons/default/cheers.gif)
Go to the top of the page
 
+Quote Post
psc
post Jul 10 2007, 03:13 PM
Post #24


Guru
***

Group: .script developer
Posts: 4,592
Thank(s): 31
Joined: 14-July 06
From: Korschenbroich
Member No.: 3


Germany


QUOTE (MedEvil @ Jul 10 2007, 03:34 PM) *
Hi bearwindow,
could you tell me what's the advantage of your driver over the default XP driver?

(IMG:http://www.boot-land.net/forums/style_emoticons/default/cheers.gif)


Look here.

Peter
Go to the top of the page
 
+Quote Post
ktp
post Apr 29 2008, 04:12 AM
Post #25


Advanced Member
***

Group: Members
Posts: 287
Thank(s): 3
Joined: 16-February 07
Member No.: 3,365



@bearwindows

Thank you very much for your driver ! It works flawlessly on my Win98 SE. I desperately tried the Scitech driver without success, it did not recognize my graphic card chipset (ATI). Your VESA driver works really well !
Go to the top of the page
 
+Quote Post
« Next Oldest · bearwindows · Next Newest »
 

3 Pages V  < 1 2 3
Fast ReplyReply to this topicStart new topic

Members Who Viewed Topic Today ()

 

Display Mode: Standard · Switch to: Linear+ · Switch to: Outline


RSS Lo-Fi Version Time is now: 13th June 2008 - 07:18 AM

MKPortal ©2003-2008 mkportal.it