Attacing mini-filter to a newly created device after the minifilter has already loaded.

NTFSD
2

>I tried IoRegisterFsRegistrationChange() routine

You should not do this in minifilters, FltMgr does this for you.

–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

3

If your instance callback returns 0 (STATUS_SUCCESS) it should already be happening. Depending on what your instance call back returns your driver is being attached to the new volume or not.

/Daniel

“ganesh pashupathi” wrote in message news:xxxxx@ntfsd…
Hi all,

I am developing a mini-filter driver using sample nullfilter from IFS kit. In the INF file Instance flag (Instance1.Flags = 0x0) is 0 i.e automatic attachments (and in my code I have the InstanceSetUp fucntion as well which merely return 0). After loading my sample filter, if a new device object is created by some driver, how should i attach my sample mini-filter to that device object to receive the calls directed to the new device.

I tried IoRegisterFsRegistrationChange() routine, but it doesn’t seem to be useful as no notifications are done after new device object is created for this device. Is it recommended to use the routine IoRegisterFsRegistrationChange in minifilter (using this routine in minifilter resulted in my filter being shown as a legacy filter as well when fltmc was run)?

Thanks & Regards
Ganesh

4

Ganesh

I am not convinced that in your case there is - or is not - a new volume.
You can use devictree still to assist you with that point and you can also
enumerate the volumes of course - you can even use filter manager there :slight_smile:

Good luck
Lyndon

“ganesh pashupathi” wrote in message
news:xxxxx@ntfsd…
Hi all,

I am developing a mini-filter driver using sample nullfilter from IFS kit.
In the INF file Instance flag (Instance1.Flags = 0x0) is 0 i.e automatic
attachments (and in my code I have the InstanceSetUp fucntion as well which
merely return 0). After loading my sample filter, if a new device object is
created by some driver, how should i attach my sample mini-filter to that
device object to receive the calls directed to the new device.

I tried IoRegisterFsRegistrationChange() routine, but it doesn’t seem to be
useful as no notifications are done after new device object is created for
this device. Is it recommended to use the routine
IoRegisterFsRegistrationChange in minifilter (using this routine in
minifilter resulted in my filter being shown as a legacy filter as well when
fltmc was run)?

Thanks & Regards
Ganesh

5

Does the new device show up in the command:

fltmc volumes

Those are the volumes that FltMgr knows about.

Ken

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of ganesh pashupathi
Sent: Wednesday, May 09, 2007 2:56 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] Attacing mini-filter to a newly created device after
the minifilter has already loaded.

Hi Maxim,

Many thanks for your reply.

But I have this case where a new device is created / attached after my
mini-filter is already loaded. But my filter does not get attached to this
device.

I can see the new device getting attached in the DeviceTree utility. What
could be the reason for Filter manager not getting attached to the device.
If however my filter is loaded after the device is already attached my
mini-filter filter does get attached to that device (thorugh Fltmgr).

Any inputs will be really helpful.

Thanks a lot,
~ganesh

On Wed, 09 May 2007 ganesh pashupathi wrote :

Hi all,

I am developing a mini-filter driver using sample nullfilter from IFS kit.
In the INF file Instance flag (Instance1.Flags = 0x0) is 0 i.e automatic
attachments (and in my code I have the InstanceSetUp fucntion as well which
merely return 0). After loading my sample filter, if a new device object is
created by some driver, how should i attach my sample mini-filter to that
device object to receive the calls directed to the new device.

I tried IoRegisterFsRegistrationChange() routine, but it doesn’t seem to be
useful as no notifications are done after new device object is created for
this device. Is it recommended to use the routine
IoRegisterFsRegistrationChange in minifilter (using this routine in
minifilter resulted in my filter being shown as a legacy filter as well when
fltmc was run)?

Thanks & Regards
Ganesh

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

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

imagine
http:e-home.htm/xxxxx@Middle5/1176518_1170507/1175624/1?PARTNER=3&OAS_QUERY=
null target=new>
— Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17 You are currently subscribed to
ntfsd as: unknown lmsubst tag argument: ‘’ To unsubscribe send a blank email
to xxxxx@lists.osr.com</http:>