Supported Hardware/Video cards

From ReactOS Wiki
Revision as of 04:32, 30 April 2013 by SomeGuy (talk | contribs) (Undo revision 33686 by SomeGuy (talk))
Jump to: navigation, search

Please update this page with the status of each Video card that is tested. Please add a link to the site where the driver was obtained, driver version and OS version. AS YOU CAN SEE, ITS LISTED ALPHABETICALLY, SO PLEASE COMPLY TO THIS ORDER.

Driver types

  • VBE driver (vbemp.sys)
    • Supports only graphic cards supporting VESA BIOS version v2.0 and higher.
    • Supports all available resolutions (640x480 and higher)
    • Supports all available color resolutions (8, 16, 24, 32 bits)
  • VGA driver (vgamp.sys)
    • Supports a standard resolution of 640x480x4 (4 bit = 16 colors)
    • Its presence is necessary at all times, for emergency debug fallback.
  • Native driver
    • This is Video Adapter's own Windows driver.

Possible statuses

Status Description
Works Works without any major problems
Not tested No test has been performed
Failed Fails to work or crashes ReactOS
Run w/o result Run without fundamental functionality

Known issues

  • VESA Driver accepts only VESA 2.0 compatible adapters.
  • Some INF files have both Windows 2000 and Windows XP sections, with separate drivers for both. When trying to install the Windows 2000 driver version ReactOS is being detected as Windows XP, thus the Windows XP driver is attempted to be installed, even though its driver file may be missing in the Windows 2000 driver directory. As ReactOS does not fail when copying nonexistent file, successful installation is reported, alas driver file is not copied to system32\driver directory. This will cause "Successful install, please restart" window to appear at every boot.
  • Original drivers (VGA/VESA) are hardcoded, so the native ones are not really used #2286.
  • VirtualBox 3.1.0 Video driver is no longer providing 3d acceleration in ReactOS, due to missing Mm functionality #4996. Silencing the UNIMPLEMENTED macro in both functions in question is a possible workaround.
  • Windows XP/Windows Server 2003 drivers should be used, as earlier ones are very likely to fail.

See Also