Can the GDI's DrvEnablePDEV call be intercepted?

[lucy]

Dear all drivers and GDI gurus,

I ask this question because I've been desperately searching for methods
that can give me the GDIINFO structure in the system. I was told that a
filter driver to filter the DrvEnablePDEV function of the display card may
help me solve this problem. I looked into the MS mirror driver sample and
compiled and installed it successfully. But changing it to call the old
display card' DrvEnablePDEV is no easy. After many days, I still get the
KERNEL_UNHANDLED_EXCEPTION_TRAP when calling the old DrvEnablePDEV from my
dummy DrvEnablePDEV. After so many days struggling, I decide to think not
to do the filter driver, as Caltin said, that's beyond my current
capability, althought all I need is just GDIINFO.

I decide to think the other way around: from the GDI point of view. I
heard many buzzwords about API hook or intercept. Can I just intercept the
DrvEnablePDEV and wait until it returns then I get that GDIINFO fields,
without writing a driver? Or are there any other easier way of getting the
GDIINFO?

Any suggestions/comments/advice/help would be greatly appreciated!

Thank you so much for your help!

 

[Tim Roberts]

Dear all drivers and GDI gurus,

I ask this question because I've been desperately searching for methods
that can give me the GDIINFO structure in the system. I was told that a
filter driver to filter the DrvEnablePDEV function of the display card may
help me solve this problem. I looked into the MS mirror driver sample and
compiled and installed it successfully.

A mirror driver is NOT a filter driver. You need a display filter driver.
That's NOT a class of driver that Microsoft supports, so there are no
samples in the DDK. You need to search the web or the newsgroups for
information about display filter drivers.