Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have been using Cygwin 32-bit on Windows 7 Professional 64-bit. I had the HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\ObCaseInsensitive registry key set and all has been good: I could get true case-sensitive filename handling, I could create FOO.txt and foo.txt in the same directory.

Now that Cygwin 64-bit is released, I want to try it on Windows 7 Professional 64-bit. It turns out that the ObCaseInsensitive registry key has no effect for Cygwin 64-bit because the key seems to be for the Win32 subsystem only. Subsystem for UNIX-based Applications (SUA) is also not available in Windows 7 Professional 64-bit (Enterprise or Ultimate is required). In fact, I don't even know if having SUA installed would help at all.

Does anybody know if it is possible to get case-sensitive filename handling with Cygwin 64-bit on Windows 7 Professional 64-bit?

share|improve this question

1 Answer 1

up vote 2 down vote accepted

Case sensitivity does work on x86_64-cygwin. Remember that on 64-bit Windows systems, there are effectively two registries, one for 32-bit processes and another for 64-bit processes. (In Cygwin, these are represented by /proc/registry32 and /proc/registry64.) Setting the key again with regtool -w and rebooting should fix this for you.

share|improve this answer
    
Mea culpa. Further tests confirm that the ObCaseInsensitive key does have an effect on Cygwin 64-bit: I could echo 'FOO' > FOO.txt; echo 'bar' > foo.txt and create two different files. The problem seems to be with git. git in Cygwin 64-bit doesn't seem to be patched to have correct case-sensitive filename handling, despite the ObCaseInsensitive registry key having been set. –  Kal Aug 16 '13 at 1:46

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.