Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement our own
dxdiag.exe program?
This seems like it
On Sunday 28 December 2008 03:02:34 am Roderick Colenbrander wrote:
On Windows the main task of dxdiag is to show some diagnostic info and to
run some very basic network, sound and 3d tests. In case of Wine 3D testing
would be the most important feature but I'm not sure if it is that useful.
Chris Robinson chris.kcat at gmail.com writes:
I think such a thing could still be useful. It'll help figure out what kind
of
info apps are getting from a given system, and help determine if problems are
app-specific or more general system/wine-related. It can also serve as a
basic
2008/12/28 Dan Kegel d...@kegel.com:
Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement our own
On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet hverb...@gmail.com 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
2008/12/28 Dan Kegel d...@kegel.com:
On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet hverb...@gmail.com 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
On Sa, 2008-12-27 at 23:20 -0800, Dan Kegel wrote:
Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement
On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet hverb...@gmail.com 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
On Sun, Dec 28, 2008 at 7:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
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
On Sun, Dec 28, 2008 at 7:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
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
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?
I don't know, but if I were to guess I'd say it probably doesn't get
that information from d3d, but
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?
I don't know, but if I were to guess I'd say it probably doesn't get
that information from
On Sun, Dec 28, 2008 at 8:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
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
I think we should stay as close to the way the windows tools work and avoid
inventing too much wine-specific things. This is how I understand the
windows tools:
* dxdiag.exe: Prints DLL information, has very simple tests for ddraw, d3d,
dsound, dmusic, dplay. The tests just show that a device can
On Sun, Dec 28, 2008 at 8:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
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
On Sunday 28 December 2008 07:43:57 am Roderick Colenbrander wrote:
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
I can't imagine that being inaccessible by X apps.. and I believe I've
seen
some apps report this info. It's something gdi32/user32 can then get
for a
particular screen/adapter by calling into winex11.drv (if not also
something
wined3d can use), instead of reporting X Windows for the card
On Sunday 28 December 2008 07:43:57 am Roderick Colenbrander wrote:
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
Louis wrote:
Wine needs a dxdiag.exe as some apps expect it to be present,
like for example GameShadow. I once gave it a shot already, see
http://bugs.winehq.org/show_bug.cgi?id=14118
Thanks for the link.
I refreshed your patch, and also added in the parsing
for the commandline options used by
Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement our own
dxdiag.exe program?
This seems like it might be
20 matches
Mail list logo
