I am developing a driver which hooks the display dirver interrupt.
After finding the interrupt vector, line , IRQL, affinity and level of the installed
display driver, I called IoConnectInterrupt and it returns SUCCESS in my driver.
The interrupt service routine(ISR), however, does not work.
I guess the interrupt service routine of the original display driver preoccupies the
interrupt.
I wonder my guess is right and how my driver runs aheard among the sharing drivers.
ps. Are there any monitoring methods wether the ISR of the original display driver
is running or not.
Best Free e-Mail Site Orgio.net http://www.orgio.net
?Ŀ??? ??? ???, ???Ȯ??? ???
IoConnectInterrupt does not guarantee the order. Why do you want to hook the interrupt ? If you give us a reason we can find the correct answer.
–
Nar Ganapathy
Windows Core OS group
This posting is provided “AS IS” with no warranties, and confers no rights.
“?ӻ???” wrote in message news:xxxxx@ntdev…
I am developing a driver which hooks the display dirver interrupt.
After finding the interrupt vector, line , IRQL, affinity and level of the installed
display driver, I called IoConnectInterrupt and it returns SUCCESS in my driver.
The interrupt service routine(ISR), however, does not work.
I guess the interrupt service routine of the original display driver preoccupies the
interrupt.
I wonder my guess is right and how my driver runs aheard among the sharing drivers.
ps. Are there any monitoring methods wether the ISR of the original display driver
is running or not.
--------------------------------------------------------
Best Free e-Mail Site Orgio.net http://www.orgio.net
?Ŀ??? ??? ???, ???Ȯ??? ???