Skip to main content
Participant
July 7, 2010
Question

CS5 install on case-sensitive file system - can't choose different drive (Mac OS)

  • July 7, 2010
  • 11 replies
  • 35485 views

I just upgraded my macbook pro to a new drive and 10.6, and chose 'case sensitive' HFSX, 'cause I'm a heavy command line user and wanted the maximum BASH experience.

I'm trying to install the CS5 demo to try some web design tools, and the installer immediately says "Installation to case-sensitive drives is not supported. Please choose a different drive location to install." So case-sensitive drives aren't supported; crappy but fair enough.

The error message leads me to think that I can just choose a non-case-sensitive drive to install to, but I never get a chance to pick one - I click on the installer and it goes straight to the error message.

So - how do I pick a different drive to install to? Am I just an idoit, is there no way to select a different drive, or will it not install on a system that even BOOTS from a c.s. drive, regardless of the format of the drive that CS5 is installed to?

I called the support number, and the poor fellow on the other end suggested I re-download the demo, and if the new download fails call Apple support to report my 'drive error'.

I'm hoping to avoid an entire backup-reformat-restore and lose CLI compatibility just to try some demo software.

ch

    This topic has been closed for replies.

    11 replies

    Participant
    April 22, 2018

    Here is the problem.  Adobe did this way back when and had 'FlashUpdater' along with"flashupdater" in their code.  These were supposed to be two identical lines of code, but on a case sensitive system, they were treated differently so it did not work.

    The advantage with a case-sensitive system is that each file/variable is treated as separate;

    Awesome

    aWesome

    awEsome

    AweSome

    Each of those variables are considered unique under a case sensitive system.  They are the same under a case-insensitive system.  Sloppy variable tracking will work under case-insensitive, but not under case-sensitive.  Other than sloppy variables, I can fathom no reason why case sensitivity should be an issue.

    (And it is not just Adobe that has done this to me)

    maaz1017v
    Participant
    February 16, 2017

    Date is 16 February 2017.  People were surprised they didn't have this fixed in 2012.  Its been 5 years and still, we are not able to download adobe products on case sensitive drives.  Fix [it] adobe.

    [Inappropriate language edited by moderator]

    christig41548918
    Participant
    December 22, 2016

    Haven't been able to use my adobe apps or the past three years because of this issue. Thought they'd have resolved it by now. Nope. Still broke. New versions have the same issue (CC 2017) -- ridiculous. No other app I've used has ever had this problem. I guess I have to permanently switch over to affinity product line.

    Participating Frequently
    March 10, 2015

    Worst thing about this is the sheer number of developers now who work on OSX then deploy web content to linux servers and can't figure out why something's broken or why the unit tests are failing in CI.

    November 10, 2014

    I am glad I found this thread since I was pondering upgrading to CS6 but slammed into this issue when first trying to put my old copy of CS5 on my new Yosemite install.  But this really gives me pause regarding further investing in Adobe products.

    Though what I find perplexing is that I have been using CS5 for a number of years now, moving it from machine to machine as I tend to wear though my laptops disturbingly quickly, and I have never encountered this install problem till now.   I guess it never even occurred to me that Apple initialized drives defaulted to case insensitive, I always assumed it was some kind of backward compatibility option for legacy software that no one in their right mind used.

    This thread did give me some possibilities for how to get around the issue at least, so gratz to people with good advice.  And although it is a curiosity that will probably forever go unsated, I would be REALLY curious to see what issue Adobe is encountering.  The only toolchain issues I am familiar with in OSX are the exact opposite, you have to fix your FS and set it to case sensitive for the tools to work and they are known broken if you try to run them on a case insensitive drive.

    station_two
    Inspiring
    November 11, 2014

    neeneko wrote:


    …some kind of backward compatibility option for legacy software that no one in their right mind used…

    I've been using Macs for thirty years, I think I'm in my right mind, and yet I have never used case-sensitive drives for the simple reason that I have never had a reason to do so.

    So, be careful about your pronouncements.

    November 11, 2014

    Sorry about that.  It was intended to be humorous but tone gets lot in text.

    It do find it rather perplexing though.  Case insensitive filesystems are kinda like the 8:3 pre vfat setups or the ones that could not handle spaces or special characters.  People instinctively work around it, but part of the point is there is not a 'reason' to use case sensitive, any more then there is a reason to allow file names longer than 8 characters.  Why would one actually want their filesystem to be unable to tell the difference between two different characters?  As I said, I was always under the impression that the case insensitivity was there as a backwards compatibility thing.  I am also unsure why they defaulted journaling on but case sensitivity off since both updates were introduced around the same time.  In a way they are rather similar, things mac users had been accustomed to working without for a long time and there were die hard defenders not wanting them switched on, but one became 'you can not turn this off' and the other 'you have to take extra steps to turn on'

    Though now I am getting flashbacks to a project where it was decided that users were too easily confused by characters that 'look' the same so we made things like '1' == 'l'.  I guess people never really needed a reason for having both (among other reductions) and got along fine without them.

    skw33k
    Participant
    August 3, 2014

    Is there any update on this bug? I just purchased a license for this, and I can't install this software. My network admin doesn't support case in-sensitive file systems.

    station_two
    Inspiring
    August 3, 2014

    It's not a bug, i.e. not a programming error; it's a limitation imposed by Apple's OS.

    If there are news from Apple, it's not public knowledge.

    If you just bought the license, you can get your money back in the first 30 days after the purchase.

    skw33k
    Participant
    August 3, 2014

    I guess that's what I'll need to do. 

    https://bitbucket.org/al45tair/libstupid

    Participant
    August 13, 2012

    Never, ever have I encountered such a major mistake by such a big company (no not even MSFT) in my 15 years as a software developer. There really is no excuse possible for this. There is always a workaround, be it ugly, or a redesign of the code that so desperately needs case insensitivity. Gladly I first tried to install the trial and concluded after that, that if the install fails that hard then the rest will probably even fail harder.

    Participant
    January 7, 2012

    In 2012, adobe does not support case sensitive file systems? wow.

    Participant
    January 7, 2012

    I had my credit card ready, fortunately I downloaded the trial first, and discovered the case sensitive install issue.

    There is no exuse to not have fixed this by 2012!

    Another adobe fail

    I am not going to reformat my drive just because of you.

    My deployment enviroment are linux servers, so my development machine (mac) requires case sensitivity!

    Will start looking for an alternative.

    Chris Cox
    Legend
    January 8, 2012

    Please note that the tool chain in question, is supplied by Apple.

    Not all issues are in the developer's control.

    Participant
    December 20, 2010

    I guess I can be happy that I actually first downloaded the trial version despite having tested the software on other computers already. Having it completely fail to install on a case sensitive file system sadly needs to turn my choice from a "definitely buy" to a "too buggy to spend money on".

    All the "good" reasons given for case insensitivity still don't render void all the good reasons other people have to use exactly that. And I find it quite "interesting" to be told as a (potential) customer that it's my fault when a customer makes the perfectly valid request, that the product should run on the system it is advertised to work with...

    Chris Cox
    Legend
    December 20, 2010

    Photoshop clearly states that it can't be installed on a case sensitive file system.

    We are still working with Apple to resolve the tool chain problems that prevent us from doing so.

    Participating Frequently
    December 20, 2010

    it however does NOT clearly state the "boot" volume must be case insensitive. cause otherwise you could just throw in a extra drive or sparse bundle and you would be good to go.

     

    I mean seriously requiring a complete re-install of the OS to run an application is crazy.

     

    well I moved on and abandoned flash / flex for HTML5.  so long adobe and good riddance.

    July 9, 2010

    Another reason to NOT buy this crappy software.

    Participating Frequently
    July 23, 2010

    i can only aggree... crappy software!! I just blew couple of hunred euro on a eclipse plugin from adobe!! stupid company policy.Cause last version worked flawless on case sensitive drive.