DeviceIoControl to mini-filter

I know that FilterConnectCommunicationPort etc is the recommended way for a
Win32 app to talk to a mini-filter. But is there any reason why I should not
create my own device object in the mini-filter and use DeviceIoControl to
talk to it instead?

This technique would allow me a choice of driver implementations (VxD,
legacy NT, or mini-filter) but still keep a single Win32 interface library
across all platforms (as I already do now for W9x or NT).

Brian

Brian,

There is no such reason which prevents you from creating your own device
object and using that for communication. The filter manager communication
interface provides a generic communication mechanism.between user and kernel
mode. You are more than welcome to design one which meets your needs.

Thanks
Ravinder

“Brian Collins” wrote in message
news:xxxxx@ntfsd…
> I know that FilterConnectCommunicationPort etc is the recommended way for
a
> Win32 app to talk to a mini-filter. But is there any reason why I should
not
> create my own device object in the mini-filter and use DeviceIoControl to
> talk to it instead?
>
> This technique would allow me a choice of driver implementations (VxD,
> legacy NT, or mini-filter) but still keep a single Win32 interface library
> across all platforms (as I already do now for W9x or NT).
>
> Brian
>
>
>

Brian,

For the exact reason that you describe some of our internal mini-filters
have a control device object. The only limitation from using a private
CDO is unloading. You will not be able to unload your filter if someone
has your CDO open. This is up to the mini-filter to manage.

This has become enough of an issue that I have already filed a feature
request for filter manager to design a formal mechanism to allow
mini-filter to have a CDO.

Neal Christiansen
Microsoft File System Filter Group Lead
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 Ravinder Thind
Sent: Friday, April 02, 2004 11:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] DeviceIoControl to mini-filter

Brian,

There is no such reason which prevents you from creating your own device
object and using that for communication. The filter manager
communication
interface provides a generic communication mechanism.between user and
kernel
mode. You are more than welcome to design one which meets your needs.

Thanks
Ravinder

“Brian Collins” wrote in message
news:xxxxx@ntfsd…
> I know that FilterConnectCommunicationPort etc is the recommended way
for
a
> Win32 app to talk to a mini-filter. But is there any reason why I
should
not
> create my own device object in the mini-filter and use DeviceIoControl
to
> talk to it instead?
>
> This technique would allow me a choice of driver implementations (VxD,
> legacy NT, or mini-filter) but still keep a single Win32 interface
library
> across all platforms (as I already do now for W9x or NT).
>
> Brian
>
>
>


Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

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