VOGONS


First post, by m1so

User metadata
Rank Member
Rank
Member

http://books.google.sk/books?id=4j4EAAAAMBAJ& … d%20vga&f=false
http://support2.microsoft.com/kb/83442

It appears that some early "VGA compatible" cards such as Everex EVGA and Quadram Quad VGA were not really truly VGA compatible, but only "BIOS compatible". It seems that all of these use the Chips and Technologies 441 chipset. Wikipedia states that the C&T were the first to offer a non-IBM VGA card, but it seems that these cards were not really "true VGA" and they weren't "enhanced EGA" either. Why is the Windows 3.1 driver for these cards states to be "VGA (version 3.0)"?" Some early C&T chip is mentioned here as the rock bottom score for Quake http://www.vgamuseum.info/index.php/benchmark … tware-rendering , but it seems to support VGA and be a later chip, Anyone owns this card or has any information please?

Reply 1 of 3, by NJRoadfan

User metadata
Rank Oldbie
Rank
Oldbie

"BIOS Compatible" likely means that the card only supports high-level functions that the official VGA BIOS made available to the machine via Int 10h. Anything that directly accesses the video card's registers and/or exploit non standard video modes will crash and burn. For that you need a "register compatible" card like the rest of the industry developed.

Performance will be horrible when the card does work since using Int 10h is slow compared to programming the hardware directly. This is even worse in protected mode as the application has to switch to real mode to access Int 10h services. Its likely there were "native" drivers later developed that supported the C&T chip's registers. Microsoft's tech note hints to that.

Reply 2 of 3, by m1so

User metadata
Rank Member
Rank
Member

Are there any DOS games that use BIOS-mode only?

Reply 3 of 3, by smeezekitty

User metadata
Rank Oldbie
Rank
Oldbie
NJRoadfan wrote:

"BIOS Compatible" likely means that the card only supports high-level functions that the official VGA BIOS made available to the machine via Int 10h. Anything that directly accesses the video card's registers and/or exploit non standard video modes will crash and burn. For that you need a "register compatible" card like the rest of the industry developed.

Performance will be horrible when the card does work since using Int 10h is slow compared to programming the hardware directly. This is even worse in protected mode as the application has to switch to real mode to access Int 10h services. Its likely there were "native" drivers later developed that supported the C&T chip's registers. Microsoft's tech note hints to that.

Well. There is a good chance it will still work by writing directly to video memory. I am betting only things like mode sets and palette changes
would require 0x10 which isn't THAT bad. Well hopefully it is atleast register compatible enough for plane changes in 640x480x16 mode