On an NTFS file system configured with:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive=0
(see https://cygwin.com/cygwin-ug-net/using-specialnames.html "Case sensitive filenames")
- When I want copy a file "a" where a file "A" exists, TC detect a collision.
[EDIT]
[WRONG] - If folder "f" and "F" exist, only one is displayed.
- If folder "f" and "F" exist, both give the same contents.
[EDIT]
TC Version: 8.51a x64
TC on NTFS filename case sensitive
Moderators: Hacker, petermad, Stefan2, white
TC on NTFS filename case sensitive
Last edited by Alcolo47 on 2014-08-29, 07:31 UTC, edited 1 time in total.
Sorry I worked for large Companies which made havy use of Cygwin but we never came to that strange idea.
Its still Windows and you get in a lot of troubles with such a setting,
for example with missing files in backups and other funny things.
I guess Christion will never try to support such seetings as normal Windows APIs dont support it.
Its still Windows and you get in a lot of troubles with such a setting,
for example with missing files in backups and other funny things.
I guess Christion will never try to support such seetings as normal Windows APIs dont support it.
Indeed.Horst.Epp wrote:as normal Windows APIs dont support it.
A simple search finds an interesting article about that setting.
Windows is case-insensitive, and will probably be like that for the next years.
Such features like the mentioned registry settings are special cases, and I don't think you can expect any support for it.
TC plugins: PCREsearch and RegXtract
It still a possible configuration of windows.
It's a normal windows feature: useful for unix world interaction (with cygwin for instance), but it still a 100% Microsoft windows feature.
To support it, it's not very difficult: just call NtOpenSymbolicLinkObject(“\SYSTEMROOT”) to know if the system is case sensitive or not. (see milo1012 article)
PS:
With both 'd' and 'D' directories, windows explorer have the same bug: be better than windows
It's a normal windows feature: useful for unix world interaction (with cygwin for instance), but it still a 100% Microsoft windows feature.
To support it, it's not very difficult: just call NtOpenSymbolicLinkObject(“\SYSTEMROOT”) to know if the system is case sensitive or not. (see milo1012 article)
PS:
With both 'd' and 'D' directories, windows explorer have the same bug: be better than windows
It would require to call unofficial kernel function (I don't think reqular apps should do it) and to modify all case-insensitive code (and it is much bigger problem)... Even Explorer doesn't see any sense in having both 'd' and 'D' directories in one folder. Just like any other pure-Windows program.
Non official ? http://msdn.microsoft.com/en-us/library/bb470234%28v=vs.85%29.aspxMVV wrote:It would require to call unofficial kernel function
You can object me: [This function may be altered or unavailable in the future.]
But enclose code into windows version control, api availabity check ...
No, it just Windows (another) bug! I didn't think of this earlier, I will fight against microsoft with this.MVV wrote:Even Explorer doesn't see any sense in having both 'd' and 'D' directories in one folder. Just like any other pure-Windows program.
Alcolo47 wrote:Non official ? http://msdn.microsoft.com/en-us/library/bb470234%28v=vs.85%29.aspx
Regardshttp://msdn.microsoft.com/en-us/library/hh529126%28v=vs.85%29.aspx wrote:This section of the Library contains archived articles. Some articles cover deprecated or superseded technologies, and some cover niche subject areas that you may still find interesting.
Holger