ioctl in a bus filter driver

I have a bus filter driver in which I am registering an interface for a
special IOCTL call (I want to return status information on a PCI-Express
switch) I am able to get the device interface details using the setupDI
calls and it looks good, but when I call CreateFile I get an invalid handle
and the last error code is 2 (file does not exist). I have breakpoints in
the Create/close routine and IOCTL dispatch routine, but the driver does not
appear to be getting called.

Doron
Tue Feb 05 15:07:01 CST 2008

if there is an FDO above you, i would bet that it is blocking creates.
instead, use wmi since the upper device objects in the stack cannot fail the
requests.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Brian" <Brian@discussions.microsoft.com> wrote in message
news:A52F3596-2D85-468C-BD54-5A0ACAB0FEC8@microsoft.com...
>I have a bus filter driver in which I am registering an interface for a
> special IOCTL call (I want to return status information on a PCI-Express
> switch) I am able to get the device interface details using the setupDI
> calls and it looks good, but when I call CreateFile I get an invalid
> handle
> and the last error code is 2 (file does not exist). I have breakpoints in
> the Create/close routine and IOCTL dispatch routine, but the driver does
> not
> appear to be getting called.