Re: Desperately want GDIINFO, how can I obtain this structure?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: lucy (losemind_at_yahoo.com)
Date: 08/14/04 

Date: Fri, 13 Aug 2004 22:30:24 -0700

"Brian Catlin" <brianc@sannas.org.bad> wrote in message
news:OdGYhVPgEHA.3964@TK2MSFTNGP12.phx.gbl...
> "lucy" <losemind@yahoo.com> wrote in message
> news:%23xXOTfOgEHA.2536@TK2MSFTNGP09.phx.gbl...
> >
> > "Brian Catlin" <brianc@sannas.org.bad> wrote in message
> > news:O9G26XJgEHA.1344@TK2MSFTNGP11.phx.gbl...
> >> "lucy" <losemind@yahoo.com> wrote in message
> >> news:OWIT5kCgEHA.644@tk2msftngp13.phx.gbl...
> >> > Dear all,
> >> >
> >> > I am mad about this...
> >> >
> >> > GDIINFO is a Windows System structure, and it is global...
> >> >
> >> > But I just don't know where to access it...
> >> >
> >> > I searched many places but cannot find how to read its field out...
> >> >
> >> > Any thoughts? Please help me! Thank you so much!
> >>
> >> What information in the GDIINFO structure are you looking for? The
Win32
> > API
> >> GetDeviceCaps will return pretty much everything in the GDIINFO
structure
> >>
> >> -Brian
> >>
> >> Brian Catlin, Sannas Consulting 310-944-9492
> >> Windows Network, Video, WDM Device Driver Training & Consulting
> >> See WWW.AZIUS.COM.bad for courses and scheduling
> >> REMOVE .BAD FROM EMAIL AND WEB ADDRESS
> >>
> >>
> >
> > Hi Brian,
> >
> > thank you very much for your help. I am in need of this field ULONG
> > ulPhysicalPixelCharacteristics;
> >
> > from the GDIINFO desperately...
> >
> > I did not see this from GetDeviceCaps... do you have a way to get it?
>
> 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.

Hi Brian,

Thank you very much for your help! At the first glance I feel very happy and
thought the good approach of obtaining the info I want has been discovered.
After some digestion I found that you meant that this method is no longer
available in current or newer OS.... :=) since I am developing on Windows XP
and hope that I can find a (almost) universal way to handle Windows family
together(at least Windows 2000 to Windows XP...) so this method does not
work, I guess? If I finally cannot find a universal way, then I guess I'd
better come back to this one...

>
> If this is too much of a hack for you, then you'll have to write what I
call an
> "intermediate display driver" (some people may refer to this as a filter
driver,
> but since I wrote the very first one, I get to name it). This is a
display
> driver that sits between GDI and the real display driver, allowing you to
see
> everything being sent to and from the display driver.
>

Yeah, many people have suggested KM GDI filter, but how to really write one?
Novice programmer always love the tutorials. Are there any tutorials and
sample codes for doing this? Since I just need to read the information, not
changing the information, I guess my GDI filter driver should be reasonably
simple? However, I have searched google many times, frankly I haven't see
any place for tutorial or sample codes... Please do give me some pointers!
Thank you so much!

Best,

-Lucy

Quantcast