Grr, I hit send before finishing writing this. I meant to write: "Then, check for existence of the uppercase or lowercase form of the path (choose appropriate casing based on the existing casing) with NtQueryAttributesFile ensuring, obviously, that the OBJ_CASE_INSENSITIVE flag is not set."
Cheers, Nick On Tue, Feb 21, 2012 at 8:59 AM, Nick Lowe <nick.l...@gmail.com> wrote: > Dear Cygwin Developers, > > shared_info::init_obcaseinsensitive in shared.cc has, in my opinion, > been implemented incorrectly. > > The value of the obcaseinsensitive value in the registry only > represents how the object manager will be on next reboot and not its > present state. Cygwin uses it as if it represents the present state, > however. This is likely to be true, but is not guaranteed to be. > > To determine the present state, first get the system root path via either: > > 1) Querying the %SystemRoot% environment variable via > RtlExpandEnvironmentStrings_U and change it with > RtlDosPathNameToNtPathName_U (alternatively > RtlDosPathNameToNtPathName_U_WithStatus in Vista and later). > > 2) Querying the symbolic link target of \SystemRoot via > NtQuerySymbolicLinkObject. (Requires administrative rights.) > > Then, check for existence of the uppercase form of the path with > NtQueryAttributesFile ensuring, obviously, that the > OBJ_CASE_INSENSITIVE flag is not set. > > If the the NTSTATUS value is successful, the object manager is running > with case insensitivity, if not its running with case sensitivity. > > With regards, > > Nick Lowe -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
