[Bug 1429] Getting dxdiag to work perfectly
http://bugs.winehq.org/show_bug.cgi?id=1429 Dmitry Timoshkov <dmitry(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|1424 | Luke Benstead <kazade(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kazade(a)gmail.com --- Comment #7 from Luke Benstead <kazade(a)gmail.com> 2009-01-06 08:04:00 --- I stumbled across this bug yesterday and while bored at work I had a bit of a play to see if I could figure it out. Just before the "DXDIAGN.DLL is out of date" message there is the following warning: warn:dxdiag:IDxDiagProviderImpl_QueryInterface (0x131650)->({7d0f462f-4064-4862-bc7f-933e5058c10e},0x1036ff4),not found The weird thing about this is the GUID it is passing in, is almost exactly the same as IID_IDxDiagContainer except for the last character. IID_IDxDiagContainer -> 7D0F462F-4064-4862-BC7F-933E5058C10F DxDiag.exe passes in -> 7d0f462f-4064-4862-bc7f-933e5058c10e This is weird for a couple of reasons: 1. The DxDiagProvider doesn't support the container interface, so it doesn't make sense to be a typo 2. Googling "933E5058C10E" returns no results so I don't have a clue what this GUID relates to and I don't think any one else does 3. Aren't GUIDs usually autogenerated, this one isn't! Now it could of course be a mistake in dxdiag.exe so I guess the next step would be to write a little test that makes the same call on Windows and find out what the Windows dxdiagn.dll does with this GUID. P.S. I knew nothing about COM yesterday morning so if the answer is obvious please ignore me :) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org