Yes, I saw it discussed previously, but none of the discussions involved a case in which the user has sucessfully installed CS PS5 Extended on the case-sensitive drive in question.
Thanks for your suggestion, but I did do my "homework" before posting. I was hoping for an Adobe response that would be helpful.
I understand that you're still working on it - that's great. It does not explain why installation worked on this drive for CS5 and not for CS6. It turns out that this boot drive is NOT case-sensitive; it is "Journaled HFS+" directly from the System Information panel (Serial ATA tab) from "About this Mac."
This means that while the idea of installing on a case-sensitive drive may have been "discussed to death," this presents a different problem that is unresolved.
Based on the error message that was thrown (I have no logs or anything else), I'm not sure I could have stated it more clearly. Trying to install again, the specific error reads as follows:
[Red triangle with an exclamation point inside] We've encountered the following issues
Installation on case-sensitive volumes is not supported. Please chose a different volume for installation.
The only choice is "Quit" (that's the only button showing).
Now I've solved this (no thanks to Adobe, in whom I'm very disappointed).
In the past, when you wanted to install something on your Mac, you'd simply copy a folder to your Applications directory.
As Photoshop (among other programs) has gotten more complicated, it's decided that it needs to install things in the various system directories and potentially in your user directory.
Herein lies the issue (and the solution, in this case). My user directory is on the drive that is case-sensitive. I don't know what Adobe needs to install there (since Photoshop is, after installation, available to all users), but that was the key.
SOLUTION: Log in as another (administrator-enabled) user and install. Bang - it works with no problems.
Yes, I still had to copy all of my plug-ins, etc. from PS5 by hand (and sort out the ones PS6 doesn't like - again by hand), but at least it's working.
Good software engineering practices dictate that installed software should PREFER case-sensitive drives, and not case-insensitive drives (think about the data).
Good installation support (on the telephone) should at least suggest trying a different user account...
Adobe: You owe me for my time on this one. Where shall I send my bill?
I don't even get a "Helpful" for suggesting it might be an issue with another drive? LOL, don't worry about it, I'm just being a bit mischievous because it's the end of a long day.
Glad to hear you got to the bottom of that. I suppose since Apple is case-insensitive by default (not to mention Windows being case-insensitive), having a case-sensitive drive does mean you're kind of out of the mainstream.
...but not really out of the mainstream, right?
Software developers need case sensitivity (especially those who work in groups -- have you ever used "Subversion?").
Unix users need case sensitivity -- both developers and users (like me).
Web developers need case sensitivity (based on the servers they use).
There have been very long discussions about why case-sensitivity is "good" and "needed" (quick Google search will show you that), and, quite frankly, it's simply good software development practice.
I use Subversion in my business, where we develop on Windows machines. I do have one engineer with an Apple, but he develops in a VMware virtual machine using Windows 7. I'll have to ask him whether he ever retrieves files to his Mac outside the VM.
In any case , I don't find case insensitivity an issue. I don't know how that would map to Apple systems, but as long as you don't try to put two files in the same folder with the same name (using different case) I don't see it as a problem.
I'm not arguing with you - if you need case sensitivity that's fine, but perhaps you might want to separate your server needs from your workstation, because like it or not, in today's world you're in the minority with case sensitivity enabled.
I realize this is a stale discussion but...
...In the past, when you wanted to install something on your Mac, you'd simply copy a folder to your Applications directory.
As Photoshop (among other programs) has gotten more complicated, it's decided that it needs to install things in the various system directories...
How old is your perception of "in the past"?. Program installers from the early 1990s would drop stuff all over the system, especially in the Extensions folder.
...I don't know what Adobe needs to install there (since Photoshop is, after installation, available to all users), but that was the key...
Photoshop may be available to all users but each user has their own preferences that need to be written to their own user space. The fact that you don't know about this may give good cause for you to learn about your system prior to telling developers what they should do.
Where should we send the bill for educating you about your system?
From what I've read from this discussion, your issue involved a case sensitive drive being used for your main user account, even though your system drive was case-insensitive. If you created a fresh account for Photoshop, that account would have appeared on that case-insensitive system drive. So all that you have accomplished is a basic installation on a case-insensitive drive, as recommended by Adobe. Your "SOLUTION" was doing what Adobe requires and it is what every other Photoshop user does.
I find it stunning that case sensitive drives are not supported. They certainly were with CS5. Is Apple backing away from the case sensitive, journaled partition - maybe backwards to something like DOS. Hey - here's an idea how about 8.3 file names being required for CS7.
I also loved the blame on the Apple tools. I have a hard time believe XCode requires case insensitive drives. Sounds more like developer error to me. Adobe - how about you folks just cowboy up and fix this debacle?
Guess I'm staying on CS5. What a pathetic effort.
We are trying to use the correct cases, but there are situations where the dev tools get things more than a little confused.
We've been working with Apple on this for a long time. We find a few problems, Apple eventually fixes those, then a few new problems appear in the dev tools which we have to find and document, then wait for the tools to be fixed, etc.
Sorry I was having a bad day yesterday. Karma sucks - I got to work today and someone went off on me the same way about computer software my group builds. I thought of this thread and how I deserved it.
It's not an issue of using cases or not in the installation path. The part that sucks is I have to repartition my HDD to use CS6. That's going to take a number of hours to backup, partition, and restore the data. The installer won't run until I do this work. Yuck.
I'm not sure what you are doing wrong, but so far Adobe applications are the ONLY ones that I have a problem with.
Currently I have
Audio Book Builder
Chicken of the VNC
Microsoft Office 2003
Microsoft Office 2011
NONE of these have an issue with case sensitive file systems.
Why does Adobe?
For me this was user error in that I didn't understand what case sensitive meant. Case senstive is allow files with different capitalization patterns to exist on the HDD as different files. myFile and MyFile and myfile would be three different files. On a case insensitive file system there can only be one myfile file in a directory. Capitialization in the name is not considered so you can't have the myFile and MyFile files in the same directory.
Yeah that's what unix does but it's kind of a nightmare for the common user and now I can see why Adobe wouldn't want to support that option. I ended up backing up my system and reformatting to make the HDD case insensitive which is how it comes from Apple. Apple could certainly be more clear in the description of the various file systems and maybe even hide case sensitive under an advanced option.
Maybe not news to you and I'm sure it's not what you want to deal with but that's the deal. Sorry. E
Whether it is Apple or Adobe's work flow isn't the issue. Between the two
of them, if they are going to support both naming variants, then at both
Adobe and Apple:
1. You MUST use the same case file names. (E.g. FrameWorks and not
Frameworks) EVERY time. And refer to them in your programs and
configuration files the same way EVERY time.
2. You may NOT in your development code use different but case invariant
file names for different files.
3. Your libraries must do the Right Thing.
What gets me is that few others seem to have this problem. Perhaps Adobe
needs to abandon Apple development software, and roll their own outside the
standard system libaries.
Further searching shows that it is not a problem unique to Adobe. The
games BeJeweled, and BZFlag have this issue, as does the Steam game support
In every case I've run down to date, it has been a violation of #1.
Now there are workarounds: A script that creates appropriate symlinks on
case sensitive file systems would be fairly easy. It would impose some
minor amount of extra overhead.
I bought a copy of Adobe Creative Suite. I returned it unopened. You lost
a sale. Furthermore, until it is fixed, I will mention this at every
opportuity as an exampled of a combination of sloppy workmanship, and
customer indifference on the part of Adobe.
Tell your bosses, Chris, they need to fix this.
Sherwood of Sherwood's Forests
I Agree. For expensive software it is a disgrace not being able to install on a case sensitive volume. It is a bug and a big one at that. Adobe should apologise and refund accordingly or apologise and fix it quickly. Most developers ( the people most likely to use it ) would be using case sensitive volumes because the target systems they are developing for are usually Linux or Unix. Excuses about not being mainstream is absurd. I have encountered no problems with other software other than Adobe. Accept you have basically got it wrong and stop blaming apple or their customers. Why not open source it if you can't fix it. It might work then!
Got working it now, on Mac Mavericks 10.9.4 with a single SSD case sensitive HDD. What I did (from my mind, please correct if there are mistakes):
- make a new partition 20GB, formatted as "Mac OS Extended (Journaled)".
- Download Mavericks from the App Store and execute it.
- Destination is the new partition from step 1.
- Boot from the new partition (hold "ALT" key during boot).
- Copy Photoshop CS6 install files (containing "packages" folder, "payloads" folder, "Deployment" folder and Install.app) via Finder from the old main partition to the new Photoshop partition.
- Execute the installer. Register.. Started CS6 - it workes under the new partition.
- Shut down. Boot again, holding the "ALT" key to get the boot option menu. Hold the "CTRL" key and press the old partition to make it to the standard boot drive.
- Start Photoshop from the old partition via Finder. When the icon accours in the dock, you can say right mouse "options" -> keep in dock.
That works for me.