Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Upcoming OSR Seminars:

Writing WDF Drivers I: Core Concepts, Nashua, NH 15-19 May, 2017
Writing WDF Drivers II: Advanced Implementation Tech., Nashua, NH 23-26 May, 2017
Kernel Debugging and Crash Analysis, Dulles, VA 26-30 June, 2017
Windows Internals & Software Driver Development, Nashua, NH 24-28 July, 2017


Go Back   OSR Online Lists > ntfsd
Welcome, Guest
You must login to post to this list
  Message 1 of 5  
29 Jun 05 08:22
Baja Mani
xxxxxx@hotmail.com
Join Date: 18 Aug 2004
Posts To This List: 136
Volume Open & FO_VOLUME_OPEN

For Volume Open 1. (FileObject->Flags & FO_VOLUME_OPEN) = TRUE OR 2. (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject = NULL) in the filter i always see the 2nd condition. when does 1st condition occur. --
  Message 2 of 5  
01 Jul 05 03:10
ntfsd member 1661
xxxxxx@windows.microsoft.com
Join Date:
Posts To This List: 608
Volume Open & FO_VOLUME_OPEN

For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER = the create has completed. This means it will be set for all other = operations (besides create) to this file object. I was so tired of dealing with this I modified the filter manager to set = this flag before it sends pre-create operations to minifilters. This = means a minifilter will see it correctly set for ALL operations. Neal Christiansen Microsoft File System Filter Group Lead This posting is provided "AS IS" with no warranties, and confers no = Rights ________________________________________ From: xxxxx@lists.osr.com = [mailto:xxxxx@lists.osr.com] On Behalf Of Mani Sent: Wednesday, June 29, 2005 5:25 AM To: Windows File Systems Devs Interest List Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN For Volume Open 1. (FileObject->Flags & FO_VOLUME_OPEN) =3D TRUE OR 2. (FileObject->FileName.Length =3D 0) AND = (FileObject->RelatedFileObject =3D NULL)=20 =A0 =A0 in the filter i always see the 2nd condition. when does 1st condition = occur. ---=20 Questions? First check the IFS FAQ at = https://www.osronline.com/article.cfm?id=3D17=20 You are currently subscribed to ntfsd as: unknown lmsubst tag argument: = ''=20 To unsubscribe send a blank email to xxxxx@lists.osr.com=20
  Message 3 of 5  
01 Jul 05 09:09
Baja Mani
xxxxxx@hotmail.com
Join Date: 18 Aug 2004
Posts To This List: 136
Volume Open & FO_VOLUME_OPEN

Thank you. By saying "AFTER the create has completed" you mean to say the flag is not set even in "Post-Create"? "Neal Christiansen" <xxxxx@windows.microsoft.com> wrote in message news:63240@ntfsd... For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER the create has completed. This means it will be set for all other operations (besides create) to this file object. I was so tired of dealing with this I modified the filter manager to set this flag before it sends pre-create operations to minifilters. This means a minifilter will see it correctly set for ALL operations. Neal Christiansen Microsoft File System Filter Group Lead This posting is provided "AS IS" with no warranties, and confers no Rights ________________________________________ From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mani Sent: Wednesday, June 29, 2005 5:25 AM To: Windows File Systems Devs Interest List Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN For Volume Open 1. (FileObject->Flags & FO_VOLUME_OPEN) = TRUE OR 2. (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject = NULL) in the filter i always see the 2nd condition. when does 1st condition occur. --- 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
  Message 4 of 5  
01 Jul 05 11:25
ntfsd member 8
xxxxxx@osr.com
Join Date:
Posts To This List: 2736
Volume Open & FO_VOLUME_OPEN

How about "after the create has been completed by the underlying file system driver". It wouldn't be set after completion by a driver BELOW the file system driver (if such a call is made) but would be set after completion by the file system driver. If you are a file system filter, you would observe the bit set. Regards, Tony Tony Mason Consulting Partner OSR Open Systems Resources, Inc. http://www.osr.com =20 -----Original Message----- From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mani Sent: Friday, July 01, 2005 9:12 AM To: ntfsd redirect Subject: Re:[ntfsd] Volume Open & FO_VOLUME_OPEN Thank you. By saying "AFTER the create has completed" you mean to say the flag is not set even in "Post-Create"? "Neal Christiansen" <xxxxx@windows.microsoft.com> wrote in message news:63240@ntfsd... For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER the create has completed. This means it will be set for all other operations (besides create) to this file object. I was so tired of dealing with this I modified the filter manager to set this flag before it sends pre-create operations to minifilters. This means a minifilter will see it correctly set for ALL operations. Neal Christiansen Microsoft File System Filter Group Lead This posting is provided "AS IS" with no warranties, and confers no Rights ________________________________________ From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mani Sent: Wednesday, June 29, 2005 5:25 AM To: Windows File Systems Devs Interest List Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN For Volume Open 1. (FileObject->Flags & FO_VOLUME_OPEN) =3D TRUE OR 2. (FileObject->FileName.Length =3D 0) AND = (FileObject->RelatedFileObject =3D NULL) in the filter i always see the 2nd condition. when does 1st condition occur. --- Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=3D17 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=3D17 You are currently subscribed to ntfsd as: xxxxx@osr.com To unsubscribe send a blank email to xxxxx@lists.osr.com
  Message 5 of 5  
08 Jul 05 03:27
Baja Mani
xxxxxx@hotmail.com
Join Date: 18 Aug 2004
Posts To This List: 136
Volume Open & FO_VOLUME_OPEN

I am not seeing the bit set in Post Create. "Tony Mason" <xxxxx@osr.com> wrote in message news:63244@ntfsd... How about "after the create has been completed by the underlying file system driver". It wouldn't be set after completion by a driver BELOW the file system driver (if such a call is made) but would be set after completion by the file system driver. If you are a file system filter, you would observe the bit set. Regards, Tony Tony Mason Consulting Partner OSR Open Systems Resources, Inc. http://www.osr.com -----Original Message----- From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mani Sent: Friday, July 01, 2005 9:12 AM To: ntfsd redirect Subject: Re:[ntfsd] Volume Open & FO_VOLUME_OPEN Thank you. By saying "AFTER the create has completed" you mean to say the flag is not set even in "Post-Create"? "Neal Christiansen" <xxxxx@windows.microsoft.com> wrote in message news:63240@ntfsd... For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER the create has completed. This means it will be set for all other operations (besides create) to this file object. I was so tired of dealing with this I modified the filter manager to set this flag before it sends pre-create operations to minifilters. This means a minifilter will see it correctly set for ALL operations. Neal Christiansen Microsoft File System Filter Group Lead This posting is provided "AS IS" with no warranties, and confers no Rights ________________________________________ From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mani Sent: Wednesday, June 29, 2005 5:25 AM To: Windows File Systems Devs Interest List Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN For Volume Open 1. (FileObject->Flags & FO_VOLUME_OPEN) = TRUE OR 2. (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject = NULL) in the filter i always see the 2nd condition. when does 1st condition occur. --- 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: xxxxx@osr.com To unsubscribe send a blank email to xxxxx@lists.osr.com
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntfsd list to be able to post.

All times are GMT -5. The time now is 04:50.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license