Ted,
No, I am not telling you that. If the system has been put into case
sensitive mode by installing one of these other applications then the
names returned are guaranteed to be case correct. When the machine is
NOT in case sensitive mode (controlled by a registry key) then we do not
guarantee the case correctness of names (though they are usually
correct).
Tony, would you email me off line and tell me what you have heard about
this and from whom? I would be very surprised if they were going to do
away with this for longhorn because of the impact on some products.
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 Tony Mason
Sent: Wednesday, November 02, 2005 1:18 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Strange result from FltGetFileNameInformation
Given how horribly difficult it is to turn on case sensitivity (and I’ve
been told by a reliable source that it won’t be an option in LH,
although like all prospective changes that’s subject to change) the
problem is that this doesn’t impact very many applications, so I can see
why they wouldn’t necessarily “fix” this (after all, fixing it means
walking through every directory component and picking out the right
case.)
But I think you’re analysis is right Ted - if you rely upon the case of
the file names, you’ll have to determine it and maintain it on your own.
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 Ted Hess
Sent: Wednesday, November 02, 2005 3:24 PM
To: ntfsd redirect
Subject: RE: [ntfsd] Strange result from FltGetFileNameInformation
Neal -
So, in short you are telling me that we are hosed if the machine is
running
SFU, Posix or some other case-sensitive application?
Do I now have to fall back to other, legacy, file name tracking
mechanisms
that forego the goodness of the FilterManager? Even with this problem
fixed
in LH, it doesn’t help me with all the W2K, XP and WS03 systems we need
to
support for the foreseeable future!
Gah!
/ted
-----Original Message-----
From: Neal Christiansen [mailto:xxxxx@windows.microsoft.com]
Sent: Monday, October 31, 2005 2:21 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Strange result from FltGetFileNameInformation
Ted,
The filter manager does not currently guarantee the case for names it
has
returned. This was by design. We are fixing this in longhorn.
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 Ted Hess
Sent: Wednesday, August 31, 2005 11:07 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Strange result from FltGetFileNameInformation
Has anyone seen this – is there a problem in fltmgr?
On rare occasions I get filename information returned with a directory
path
seqment in lower case that I know isn’t (“c:\program files” for
instance). I
always call with flags = (FLT_FILE_NAME_NORMALIZED |
FLT_FILE_NAME_QUERY_DEFAULT). Calls are usually made from either my
post-CREATE or post-SET_INFORMATION(FileRenameInformation) handler.
Under
certain unusual circumstances, I will make this call in my pre-CLOSE
handler.
Unfortunately, I have only seen this at a couple of customer sites and
have
no real data other than the systems were most likely running WS03 SP1.
Is it possible the filter manger name cache has the information cached
from
some other call using FLT_FILE_NAME_OPENED? I’m also trying to find out
if
operation had a ReleatedFileObject or not.
/ted
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
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
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