Used 3dfx driver, crashes with 0xB4 BSOD on videoport.sys, probably same issue as 3dfx voodoo 3 Used both last 3dfx reference driver for Windows 2000 and the same winxp driver from the archived result, reference driver crashes with 0xB4 BSOD, winxp driver aserts CORE-16009 Used FastVoodoo2 4.0 XP Gold Edition and tested some 3dfx-only games with a S3 2D card. If wglinfo runs and uses the video adapter as OpenGL renderer (doesn't fallback to ReactOS SW implementation/Mesa3D), then the OpenGL ICD works properly.To determine wether OpenGL ICD works, please use wglinfo. Video Adapter's own OpenGL ICD driver, usually supplied within native driver.This is the Video Adapter's own Windows driver.Its presence is necessary at all times, for emergency debug fallback.Supports a standard resolution of 640x480x4 (4 bit = 16 colors).Supports all available color resolutions (8, 16, 24, 32 bits).Supports all available resolutions (640x480 and higher).Supports only graphic cards supporting VESA BIOS version v2.0 and higher.OpenGL hardware acceleration in NVidia drivers has severe performance issues, even Mesa3D software rendering performs much better in many cases, see CORE-15959.OpenGL hardware acceleration in NVidia drivers has been fixed again since a8fa539.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |