Re: Re:Re: Re:Attacing mini-filter to a newly created device after the minifilter has alread

This is a clearcase drive right, did you ask the rational rose people ?

/Daniel

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

I was using Device Tree utility to look at this driver \FileSystem\mvfs.
There are 3 devices created by this driver (as the devices are seem under
the \FileSystem\mvfs node).

One is identified as a volume by Fltmgr (name is \device\mvfs).
One of the devices is of type FILE_DEVICE_NETWORK_FILE_SYSTEM (unnamed
device).
The third device is not created when the machine starts and user logs-in.

There is a mapped drive on my machine e.g. Z:. When the machine starts this
drive is shown as a disconnected network drive. If I right click to view the
properties then it’s file system is shown as Raw. For C: if I do the same
then I can see the file system is shown as Ntfs and type is shown as Local
disk.

Only when I access the Z: drive and then refresh the device tree view I can
see the 3rd device. The device type is FILE_DEVICE_DISK_FILE_SYSTEM and this
device is also unnamed. Also if I now right click Z: and view its properties
I can see the file system as mvfs (Its a Rational Clearcase view drive) and
type is a network drive.

When this device is seen in Device Tree utility, in the file spy or filemon
I cannot see a new volume being mounted. Nor does Fltmgr (e.g. Fltmc volumes
does not report this device as a volume and FltEnumerateVolumes also does
not return this device).

Also, if this device is already created and then if I load my mini filter
then Fltmgr gets attached to this device. However if the device is created
after my filter is loaded then fltmgr does not get attached to this device.

So I am not sure as to what / where I should look more to answer your
question correctly. Please provide some pointers. This will be really
helpful.

Thanks a lot,
~ganesh

On Sat, 12 May 2007 Daniel Terhell wrote :
>Did you say to what device you want to attach, it is a storage volume right
>and not a RAW device ?
>
>/Daniel
> “ganesh pashupathi” wrote in message
> news:xxxxx@ntfsd…
> Hi,
>
> Is there something pretty obvious that I am missing? Kindly provide any
> inputs.
>
> Thanks a lot,
> ~ganesh
>
>
> On Thu, 10 May 2007 ganesh pashupathi wrote :
> >Hi All,
> >
> >Thanks for your replies.
> >
> >As you say there may not be a new volume. Fltmc volumes does not show
> that device. Also in the very useful DeviceTree utility no volume
> information is shown for this device and the Vpb is 0. But this is true
> also for another device create by the same driver which is however shown
> in the output of Fltmc volumes.
> >
> >How should I attach to this newly created device then? Is there a
> notification mechanism to which I can hook? Or should I poll for the
> device creation (does not sound good)? What api should I use to attach to
> this device?
> >
> >Another work around could be performing the task that results in this
> device creation and then load my filter. (does not sound good though).
> >
> >~ganesh
> >
> >
> >On Thu, 10 May 2007 Lyndon J Clarke wrote :
> > >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
> > >
> > >
> > >
> > >—
> > >Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
> > >
> > >You are currently subscribed to ntfsd as:
> xxxxx@rediffmail.com
> > >To unsubscribe send a blank email to
> xxxxx@lists.osr.com
> >
> >—
> >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
>
>
>
>
>
>
>—
>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