Sorry, but that's just a bunch of crap, and some of of it may have been true 2 years ago.
First, the standard Mac OS X 10.5 (Leopard) which has been out for ~1.5 years has the case sensitive option available to all users on, not just server, via the standard installer. Clearly this shows that Apple has said it's OK to use the case sensitive file system.
Second, both my home and work Macs have been running the case sensitive file system for well over a year and I have 104 applications installed on my Mac at home and 57 on my Mac at work and EVERY single app works fine on the case sensitive file system EXCPET Adobe Reader. That's my only Adobe product. Doesn't that tell you something?
Third, a case sensitive file system is what we should all be using, that's what we use in real language, and we should not still be restricting ourselves to design decisions of the 1980s where memory and disk space was so expensive that it was saved by using case insensitive filesystems. It's just not right that the file named "you must read me" is the same as the file "You MUST READ me".
Lastly, do you know how easy it is to write software that works with a case sensitive file system? Actually it requires ZERO extra effort. There is no support. All you need to do is actually TEST your software properly. Think about it. If software doesn't work with a case sensitive file system it is because the software is looking for a file with a different case name the the file actually exists on the disk. For example, the software looks for "MyPreferncesFile" and on the disk it is "mypreferencesfile". This is a programming mistake!
There is really nothing to do to support a case sensitive file system other than properly developing your software. So, I can rephrase my question if you like and ask for the software to be properly written and debugged instead.
I know that Adobe is always way behind, but this is ridiculous.
I know that Apple has made the case sensitive file system available in
Leopard, but that did not change Apple's recommendations. Adobe has made
it pretty clear that they do not support the case sensitive file system.
I wish they would. It is a safer system to be running, but my or your
wishing doesn't make it so.
If you want it supported get you, your friends, and all acquaintances to
place a request at:
Then maybe, just maybe it might get supported in Reader 11.
Adobe is just wrong on this. It's a huge failure on their part to require a case-insensitive drive. I feel cheated and ripped off. It's lazy poor programmers who program without strict adherence to case in filenames and variables. Shameful, and not that hard to fix.
I have hours invested in getting the software setup on my various Mac OSX Servers. Case sensitive filesystems are the default for the system disks, and something I choose routinely for all other drives. This is the proper filesystem. It's the RIGHT way do do things. All of my other software works EXCEPT Adobe products. I do not have the time or inclination to rebuild my system disk from scratch. It's cheaper for me to buy a new machine.
Wake up Adobe. WAKE UP! This is not a new issue. Support your users.
> Even Apple doesn't recommend it for anything but their server product and they do not recommend its use on the boot driver of OS X server.
Not true, my brand new 2015 MBP Retina shipped with a case-sensitive file system.
This has been going on for YEARS, time to fix it already!
And from what I can tell: the problem is that they don't use properly cased names for file resources in the application bundles. There's Perl scripts out there that will rip through and update the resource bundle names to correct them.
TIME TO FIX IT ADOBE