Additional conditions:
On my test computer Windows 2000 SP2 is installed.
My FSD works over FILE_DEVICE_CD_ROM and
has type FILE_DEVICE_CD_ROM_FILE_SYSTEM.
I found that this situation happens only if I have
non zero ReferenceCounts field in this filter driver
object after I try to stop the underlying device.
— Al Shatilo wrote:
> From Al Shatilo Wed Oct 23 08:20:02 2002
> Received: from [213.144.12.8] by web20703.mail.yahoo.com via HTTP; Wed, 23 Oct 2002 08:20:02 PDT
> Date: Wed, 23 Oct 2002 08:20:02 -0700 (PDT)
> From: Al Shatilo
> Subject: About FSCTL_INVALIDATE_VOLUMES
> To: File Systems Developers
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Length: 874
>
>
> I work with the file system driver and after processing the PnP request
> IRP_MN_QUERY_REMOVE_DEVICE which completes with STATUS_SUCCESS - I receive
> a FSCTL_INVALIDATE_VOLUMES request, in Handle parameter, as supposed all file
> systems, must be contained FILE_OBJECT which points to class device object,
> but instead this FILE_OBJECT points to upper level filter driver.
>
> The routine, which process this request, by default must create new VPB
> in class device object, rescan all VCB related to this class device object,
> mark all Fcb as bad and try to free VPB structure, which was linked to this
> class device object.
>
> Why don’t I receive class device object? Has someone else had it before and knows
> the reason of this?
>
>
>
>
>
> Do you Yahoo!?
> Y! Web Hosting - Let the expert host your web site
> http://webhosting.yahoo.com/
>
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/