I am desperately in need of the information from GDIINFO. Specifically, I
want the field ulPhysicalPixelCharacteristics and other related fields in
GDIINFO which is not exposed in GetDeviceCaps function...
I asked this question long time ago and got the following help from Guru Mr.
Catlin...
--------------------------------------------------------------
There is a kernel debugger extension DLL for display drivers called
GDIKDX.DLL,
and it has the ability to display just about anything you would like to know
regarding display and print drivers, including their data structures.
Unfortunately, the extension isn't supported after Win2K. >:-{
On the bright side, using that extension (specifically, the !dpdev command),
you
can look at the global list of PDEVs, and the GDIINFO structure in them.
Unfortunately, the extension DLL doesn't display the
ulPhysicalPixelCharacteristics, but that's OK, you can find it using the
debugger. There is a global linked list of PDEVs starting at
Win32K!gppdevlist.
With a little bit of effort, you should be able to find the offset of the
GDIINFO structure within the PDEV structure.
---------------------------------------------------------------
So anybody has the GDIKDX.DLL for Windows XP SP2? How do I automate the
above investigation process in order to get the pointer to the GDIINFO
structure that I can use in my MSVC program?
Thank you so much and have a great weekend~!
http://www.microsoft.com/whdc/devtools/tools/verifier.mspx
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q244/6/17.asp&NoWebContent=1
Both articles indicate that gdikdx.dll should be available for Windows XP to support the gdikdx.verifier command. Yet, since the
winxp\gdikdx.dll does not ship in the public debugger tools, it was probably pulled (or never fully released) for some reason. If I
had to guess, I would bet that there are problems with a dependency on private symbols or something. But maybe someone didn't
realize that there are pointers indicating it should be used (externally to Microsoft) for the verifier option.
If you *do* manage to get a copy of the DLL, you may not be able to get much support for anything other than the gdikdx.verifier
command.
BTW, note that the debugger.chm indicates that !gdikdx.verifier is only available on Windows 2000, but the above articles either
contradict the debugger help file or else neither document is making it clear that you should use the downlevel w2kfre\gdikdx.dll to
work with driver verifier on Windows XP.
"lucy" <lose...@yahoo.com> wrote in message news:%23$Z9pVJj...@TK2MSFTNGP12.phx.gbl...