Implementing KbFilter_IoCtl

The DriverEntry routine of the kbfiltr example states:

//
// If you are planning on using this function, you must create another
// device object to send the requests to. Please see the considerations
// comments for KbFilter_DispatchPassThrough for implementation details.
//
// DriverObject->MajorFunction [IRP_MJ_DEVICE_CONTROL] = KbFilter_IoCtl;

Is there a working example that implements a device object from within a
filter driver that is accessible via user-mode IOCTLs?

Does the auxiliary device need to be referenced in the inf file?

If you are creating an NT4 style device object, no INF is needed since
there is no pnp enumeration of that device object. You still need an
INF to install the filter in the pnp stack though.

In terms of creating the device object and how to fix up your dispatch
handlers, read the following KB article:

HOWTO: Send IOCTLs to a Filter Driver
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q262305

D

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bob White
Sent: Wednesday, June 18, 2003 8:56 AM
To: NT Developers Interest List
Subject: [ntdev] Implementing KbFilter_IoCtl

The DriverEntry routine of the kbfiltr example states:

//
// If you are planning on using this function, you must create another
// device object to send the requests to. Please see the considerations
// comments for KbFilter_DispatchPassThrough for implementation details.
//
// DriverObject->MajorFunction [IRP_MJ_DEVICE_CONTROL] = KbFilter_IoCtl;
=== Is there a working example that implements a device object from
within a filter driver that is accessible via user-mode IOCTLs?

Does the auxiliary device need to be referenced in the inf file?


You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Doran,

Thanks for the pointer to the KB article. Comparison to my code
revealed the absence of the line

device->Flags &= ~DO_DEVICE_INITIALIZING;

in my control device initialization. Everything seems to work now.

Thanks again.

Bob

If you are creating an NT4 style device object, no INF is needed
since
there is no pnp enumeration of that device object. You still need an
INF to install the filter in the pnp stack though.

In terms of creating the device object and how to fix up your dispatch
handlers, read the following KB article:

HOWTO: Send IOCTLs to a Filter Driver
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q262305

D

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bob White
Sent: Wednesday, June 18, 2003 8:56 AM
To: NT Developers Interest List
Subject: [ntdev] Implementing KbFilter_IoCtl

The DriverEntry routine of the kbfiltr example states:

//
// If you are planning on using this function, you must create another
// device object to send the requests to. Please see the considerations
// comments for KbFilter_DispatchPassThrough for implementation details.
//
// DriverObject->MajorFunction [IRP_MJ_DEVICE_CONTROL] = KbFilter_IoCtl;
=== Is there a working example that implements a device object from
within a filter driver that is accessible via user-mode IOCTLs?

Does the auxiliary device need to be referenced in the inf file?


You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@perigee.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Bob

Robert B. White Perigee, LLC
Senior Software Engineer 135 Old Cove Rd, Suite 213
TEL: 315.453.7842x29 Liverpool, NY 13090
FAX: 315.453.7917 www.Perigee.com