Implementing dxdiag as student project?

Roderick Colenbrander thunderbird2k at
Sun Dec 28 09:43:57 CST 2008

> On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet <hverbeet at> wrote:
> > ... I think the main use of such an application would be
> > dumping information like supported caps, texture formats, etc in case
> > of D3D and supported extensions, pixelformats, various limits, drivers
> > strings, etc. for OpenGL.
> OK.  Can you list the main Win32 API calls you'd like such
> an app to use to retrieve information?
> Also, isn't it annoying that native dxdiag always says
> the graphics card is X Windows?  Why is that, and
> should we change Wine so that the true card's info
> is reported by native dxdiag?

Native dxdiag is checking the name of the display driver which in our case winex11.drv and I guess this is just the identifier of Winex11.drv. Inside winex11.drv we don't really have the knowledge about the 3d hardware we are emulating. In the end we might need to duplicate some card detection code inside winex11.drv and show a real driver name like the Nvidia or ATI ones. It would be a lot of work and only be worth if apps really need it.

Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL 
für nur 16,37 Euro/mtl.!*

More information about the wine-devel mailing list