On 9/25/2014 2:52 PM, Dave Botsch wrote: > Hi, Jeff. > > Thanks for the reply. > > Additional questions... > > > > >>> What's the story with case insensitivity or sensitivity with the Windows >>> OAFS client? >> >> File and directory name searches are performed: >> >> 1. case sensitive first >> 2. case insensitive second >> >> Ambiguous case insensitive matches are failed. > > Can you clarify what you mean by "ambiguous case insenstivie match" ?
Two or more objects match the case the insensitive search. > Would hardcoding the file system filter driver somehow cause the "case > insitivie second #2" above to not happen/match? I was very careful with my wording. "File and directory name searches". The failure you are experiencing is neither of these. > Should there be something in the fs trace output indicating which type > of match it is or isn't doing and the result? Or does that require > additional debugging (ie paid support)? > > thanks. The application issuing the request in all CAPS is a symptom. It is not the root cause of the problem. Additional debugging is absolutely required by Corel, Microsoft or the Windows kernel expert of your choice. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
