CS5 + Yosemite + Case Sensitive
I know this is a similar question to one that has come up many times before for previous versions of OSX but I think I might have hit a new variation on the problem. I am also aware that this is not an officially supported install configuration but since it comes up so often I am hoping someone has run into this same block.
So I just set up a new machine, fresh install of Yosemite on a bare drive with a fresh copy of CS5 from original (legally purchased) install media. I used the recommended trick of booting to a case-insensitive drive, installing, copying the resulting install to the normal boot drive, then running scripts to correct the framework names. However Photoshop will still not start up.
The message I get is:
An unexpected and unrecoverable problem has occurred. Photoshop will now exit.
Nothing is contained in either /Users/<username>/Library/Logs/Adobe or /Users/<username>/Library/Logs/CrashReporter.
/tmp/amt3.log does have stuff in it, but nothing is leaping out as 'wrong':
2014-11-17 14:02:10 [6779] AMT: START SESSION, library version 3.0.0.64,3.0
2014-11-17 14:02:10 [6779] AMT: Initializing /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/
2014-11-17 14:02:10 [6779] AMT: Adobe License Manager version 3.2 (build 64.0) RELEASE
2014-11-17 14:02:10 [6779] ServiceLoader: looking for library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/amtservices.framework/adobe_caps.framework/adobe_caps
2014-11-17 14:02:10 [6779] ServiceLoader: looking for library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/adobe_caps.framework/adobe_caps
2014-11-17 14:02:10 [6779] ServiceLoader: Found library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/adobe_caps.framework/adobe_caps
2014-11-17 14:02:10 [6779] PCDService: PCD Service in threaded mode
2014-11-17 14:02:10 [6779] performance: AMTPreObtainProductLicense took 5.332000 ms
2014-11-17 14:02:10 [6779] PCD thread: PCD thread started
2014-11-17 14:02:10 [6779] ServiceLoader: looking for library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/amtservices.framework/Adobe_OOBE_Launcher.framework/Adobe_OOB E_
Launcher
2014-11-17 14:02:10 [6779] ServiceLoader: looking for library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/Adobe_OOBE_Launcher.framework/Adobe_OOBE_Launcher
2014-11-17 14:02:10 [6779] ServiceLoader: Found library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/adobe_oobe_launcher.framework/adobe_oobe_launcher
2014-11-17 14:02:10 [6779] AMT: App Product Locale [0] = en_US
2014-11-17 14:02:10 [6779] config: Loading configuration for /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Resources/AMT/application.xml
2014-11-17 14:02:10 [6779] config: Found payload code {7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}
2014-11-17 14:02:10 [6779] PCDService: found driver code {CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}
2014-11-17 14:02:10 [6779] config: config: Host app was installed, using installed license configuration.
2014-11-17 14:02:10 [6779] PCDService: No value for key [FLMap] in hive [Photoshop-CS5-Mac-GM{|}ALL] in cache.
2014-11-17 14:02:10 [6779] config: Setting current license to the driver at startup because no mapping was found.
2014-11-17 14:02:10 [6779] config: Setting current license to DesignSuitePremium-CS5-Mac-GM [ALL]
2014-11-17 14:02:10 [6779] config: payload code: {7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}
2014-11-17 14:02:10 [6779] config: driver payload code: {CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}
2014-11-17 14:02:10 [6779] config: driver licensing code: DesignSuitePremium-CS5-Mac-GM
2014-11-17 14:02:10 [6779] config: current licensing code: DesignSuitePremium-CS5-Mac-GM
2014-11-17 14:02:10 [6779] config: current locale code: ALL
2014-11-17 14:02:10 [6779] config: Done loading configuration
2014-11-17 14:02:10 [6779] AMT: Locale from PCD [0] = en_US
2014-11-17 14:02:10 [6779] AMT: Reordered Installed App Product Locale [0] = en_US
2014-11-17 14:02:10 [6779] config: Setting insalled locales
2014-11-17 14:02:10 [6779] config: Changing locale to "en_US" because old locale "" is not in the new list of installed languages
2014-11-17 14:02:10 [6779] ServiceLoader: looking for library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/amtservices.framework/asneu.framework/asneu
2014-11-17 14:02:10 [6779] ServiceLoader: looking for library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/asneu.framework/asneu
2014-11-17 14:02:10 [6779] ServiceLoader: Found library /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/asneu.framework/asneu
2014-11-17 14:02:10 [6779] PCDService: No value for key [ReLaunchMode] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [ReLaunchMode] in hive [{7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}] in master.
2014-11-17 14:02:10 [6779] AMT: App's last known config file is: /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Resources/AMT/application.xml
2014-11-17 14:02:10 [6779] apf: current config file path is: /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Resources/AMT/application.xml
2014-11-17 14:02:10 [6779] apf: current config file path is: /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Resources/AMT/application.xml
2014-11-17 14:02:10 [6779] AMT: config: Finding license info for payload: {CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}
2014-11-17 14:02:10 [6779] AMT: config: PayloadCode: {7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}
2014-11-17 14:02:10 [6779] AMT: config: Driver PayloadCode: {CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}
2014-11-17 14:02:10 [6779] AMT: config: Installed LicensingCode: DesignSuitePremium-CS5-Mac-GM
2014-11-17 14:02:10 [6779] PCDService: No value for key [AdobeUpdaterCodeV2] in hive [{7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [AdobeUpdaterCodeV2] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [BridgeTalkCode] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [ISO_TAGGING_DISABLED] in hive [Photoshop-CS5-Mac-GM] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [EULA] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Registration] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Registration] in hive [{7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Updates] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Updates] in hive [{7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}] in master.
2014-11-17 14:02:10 [6779] AMT: Application can be serialized (sif file found).
2014-11-17 14:02:10 [6779] config: Setting current license to DesignSuitePremium-CS5-Mac-GM [en_US]
2014-11-17 14:02:10 [6779] PCDService: No value for key [AMTConfigPath] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [ExpirationDate] in hive [Photoshop-CS5-Mac-GM] in master.
2014-11-17 14:02:10 [6779] AMT: Subsequent launch (serial [95459259782253172931]).
2014-11-17 14:02:10 [6779] AMT: Application state initialized. Obtaining Product License.
2014-11-17 14:02:10 [6779] AMT: Obtaining client features from cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [AMT_ALLOW_DRAGDROP_INSTALL_3.0] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [AMT_REQUEST_NO_TAMPERPROOFING_3.3] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Photoshop_Premium_12.0] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Photoshop_Base_12.0] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Bridge_Base_4.0] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [Bridge_CameraRaw_4.0] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [MobileCenter_Base_3.0] in hive [DesignSuitePremium-CS5-Mac-GM{|}en_US] in cache.
2014-11-17 14:02:10 [6779] AMT: Obtaining client product info from cache.
2014-11-17 14:02:10 [6779] PCDService: No value for key [ExpirationDate] in hive [Photoshop-CS5-Mac-GM] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [ExpirationDate] in hive [Photoshop-CS5-Mac-GM] in master.
2014-11-17 14:02:10 [6779] AMT: Running in PROV_APP
2014-11-17 14:02:10 [6779] PCDService: No value for key [EULADelay] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [EULADelay] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] PCDService: No value for key [MediaTag] in hive [{CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}] in master.
2014-11-17 14:02:10 [6779] config: No media tag found for payload {CDC977A9-B3BA-4320-BD28-96F2CC91B9E9}
2014-11-17 14:02:10 [6779] config: Using default media policy RET
2014-11-17 14:02:10 [6779] uiswitch: EULA has already been accepted.
2014-11-17 14:02:10 [6779] AMT: This is a subsequent launch. Deferring services.
2014-11-17 14:02:10 [6779] performance: AMTObtainProductLicense took 28.857000 ms
There is something interesting in /var/log/system.log though:
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: DebugAssert: Adobe Crash Reporter: logTransportBundle != NULL err TransportCallInitialize: Couldn't create the Adobe Crash Reporter.app bundle[/Users/vsagar/work/CrashReporter/CR3.0Daemon/CrashReporter/Mac/AdobeCrashReporterF ramework/main.cpp:265]
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 0 CarbonCore 0x00007fff95743dc3 ___Gestalt_SystemVersion_block_invoke + 113
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 1 libdispatch.dylib 0x00007fff95425c13 _dispatch_client_callout + 8
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 2 libdispatch.dylib 0x00007fff95425b26 dispatch_once_f + 117
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 3 CarbonCore 0x00007fff956ec4da _Gestalt_SystemVersion + 987
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 4 CarbonCore 0x00007fff956ec0c7 Gestalt + 144
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 5 Adobe Photoshop CS5 0x00000001000a1dd5 Adobe Photoshop CS5 + 662997
Nov 17 14:02:10 xxx Adobe Photoshop CS5[6779]: 6 Adobe Photoshop CS5 0x00000001000a1f58 Adobe Photoshop CS5 + 663384
Nov 17 14:02:14 xxx Adobe Photoshop CS5[6779]: GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framework/Versions/Current/A ppKit,_NSCreateAppKitServicesMenu) failed.
Has anyone else encountered this? Does anything jump out that I missed?
Thanks.
I'll try and help as much as I know.
Have you also installed the 12.0.4 update?
Adobe - Photoshop : For Macintosh : Adobe Photoshop 12.0.4 update for Adobe Photoshop CS5
Also the 10.10.1 Yosemite update is now available. (I need more coffee )
Gene
Similar Messages
-
CS5.5 Master Collection on Case-Sensitive File System
Hello,
The first thing I'll say is that I already know it's not possible to install on a case-sensitive file system.
So, on to my question. I have been tasked to find out a way to get this installed on our 30-35 Macs with case-sensitive file systems (required for other courses/tasks, so not an option to format.) I was trying to think of a work-around that would let me install and use the CS5.5 Master Collection, but have not been successful yet. Please note, I am not looking for a hack or extensive renaming of a bunch of files or other half-solutions I've found.
Basically, what I was wondering is, if I go into Disk Utility and create a 35GB "Disk Image", mount that, and then try to install, why doesn't that work? I mean, I am technically trying to install to a case-insensitive file system at that point, but CS5.5 still pops up with an error. Has anyone gotten this type of solution to work, or any other for that matter? Luckily my college hasn't bought the licenses for all these systems yet, but when a solution is found, they're jumping on it right away. The main reason I don't want a "hacky" solution is that being deployed on 30-35 systems, this has to be a simple solution, not something that takes hours per system.
Any insight is greatly appreciated.
Jeffrey SimmonsThank you for the information, I had a hunch it was installing stuff elsewhere too, but wasn't 100% sure. As for the problem, I ended up just converting to a case-insensitive boot partition. To others who may want to do this, I used iPartition without a problem. The only catch is, you can't just run it from the OS drive, you either have to burn a iPartition Boot DVD (requires you have your OS dvd as well), or do what I did and just install OSX to an external drive, install iPartition, then convert the file system on the regular OS drive. A bit of a hassle, but you don't have to format your system.
CS5.5 Master Collection then installed fine, with no problems. Unfortunately, Photoshop keeps repeatedly crashing. It's fine for hours, then crashes 4+ times within an hour. Repeats this over and over unfortunately. Adobe support hasn't been helpful at all, so I'm just going to return this software and continue using Gimp. It has always done everything I wanted, but I wanted the "name brand" software. In the end, it's not worth the hassle, and definitely not worth losing my work over and over, so back to the store it goes. Thanks again for taking the time to help out though.
Jeffrey Simmons -
How do I determine if my file system is case-sensitive before I buy Photoshop CS5?
How do I determine if my file system is case-sensitive before I buy Photoshop CS5? I currently have Mac OSX 10.5.8 with an Intel Core 2 Duo Processor and 4GB of Memory.. Adobe says the following requirements are needed..
2GB of available hard-disk space for installation; additional free space required during installation (cannot install on a volume that uses a case-sensitive file system or on removable flash storage devices)
1024x768 display (1280x800 recommended) with qualified hardware-accelerated OpenGL graphics card, 16-bit color, and 256MB of VRAM
Some GPU-accelerated features require graphics support for Shader Model 3.0 and OpenGL 2.0
I don't know if I have a "hardware-accelerated OpenGL graphics card" or "256MB or VRAM".. I've never heard of "VRAM" before and the last bullet points is just as confusing. The last thing I want to do is buy this program and discover my Mac Book is just a tad bit to old for it, I've already done that once with a video game.Disk Utility highlighting the drive or partition & clicking the blue Info icon may report it, but since I don't have Case Sensitive I can't tell for sure.
A simple test would be to save a small txt doc as...
test
Then save to the place same as...
TEST
If both show on the Disk, then it is, if it asks to replace test with TEST then it isn't. -
CS5 install on case-sensitive file system - can't choose different drive (Mac OS)
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.
chThat is part of why I would prefer case sensitive by default. I know some server packages do the folding for you, same as some web servers do not differentiate between 'htm' and 'html' when people type in requests, but most of the time the backend server is going to be case sensitive and it is not safe to assume (or hope) that the service will fix things. Compensating for mistakes is fine, but allowing such silent corruption is not a terribly laudable things and it encourage people be careless.
Every once in a while I do encounter someone submitting some work where their configuration values and file names do not match, and 'well my laptop silently fixes it for me since it does not care' is a poor excuse. And if I sent broken filenames upstream or even worse commit them to be used on a server, that is a pretty significant professional failure.
Back to Adobe specifically, I have been trying the suggestion on poster mentioned in where one installs the Adobe applications to a case insensitive drive then copy over the installed files. This does not quite work out of the box, but for reasons I would be hard pressed to believe are Apple's fault.
For instance the first error I encounter is the inability of Bridge to load:
"@executable_path/../Frameworks/WRServices.framework/Versions/A/WRServices"
When I go look inside the app directories I can see that in Bridge the file has been named 'awrservices', but in Illustrator it is correctly named AWRServices. So it looks more like a problem in whatever version control they are using. The only way I can picture (which my adminitialy limited knowledge of what I am sure is a large and complex project with all sorts of legacy issues) that the installer toolchain factors in as a problem is if they have mismatches in their own scripts/packaging and have been depending on HFS's bad behavior to hide the problem. I can understand not wanting to invest the time to pay down the technical debt on such an issue, but having such errors in your configuration causes long term headaches.
And I say this as someone who worked on just such a project, moving a software suite that had legacy code stretching back longer than Adobe has existed as a company. This conversion included moving from a case insenstive filesystem to a case sensitive one and yeah, there were lots of problems that the old FAT32 system hid from us, but it really paid off over the long run to fix them rather than try to twist the code to compensate.
Having said that, if the problem is really that they do not want to go update their filenames (in version control or config files), then you can always add folding to your loaders. I have had to do that a few times due to upstream people developing on case insensitive systems and sending data files with incorrect file names. This is an old class of problem, and while I can empathize with the struggles project managers have trying to get approval for paying down technical debt, the problem never gets better on its own and usually gets worse.
Which is why I responded with so much grump to the 'I never needed it' argument since that is exactly the type of customer comment that marketing tends to point to in order to push such things off the schedule. This is the type of thing where the customer does not really know what they want because they are already accustomed to broken behavior and most of the problems are hidden from their immediate view. It is easy to cover up the limitations since modern UI (and their search capabilities) can handle this.
It is not just arcane developers stuff, and it is the same transition that people have made with things like spaces, quotes, and parentheses, where years ago users believed they had no need for them since they were not using them, but they were only not using them because they did not work. Today try to tell a modern user they can not put (, ", ) or even ' ' in their filenames and they would rightly question why this piece of obvious functionality is not working since today they are used to it working and no longer automatically compensate for it.
I also find it ironic that by default OSX hides a number of file extensions, so from the user's perspective you can have multiple files with the exact same name displayed to them, so you can get display issues where 'foo' is the same as 'foO' if both have .txt, but 'foo' and 'foO' are not the same if one has .txt while the other is .pdf. Add to this confusion cases like 'foo.txt' and 'foo.pdf" both being shortened to 'foo'. -
Search for subject in Mail is case sensitive
I'm hoping this is the right place to ask questions about Apple Mail as the organisation of this forum is mind baffling.
Am I right in thinking that a search on the subject in Apple Mail is case sensitive. If so, how do I change this behaviour ?HD wrote:
Hi and welcome to Apple Discussions.
I agree it's silly that there doesn't appear to be a separate topic heading for questions about Mail. I think perhaps they want you to post under the version of the system software you're using. But what do I know?
As far as I can see, subject searches in Mail (at least under Yosemite) are not case sensitive. I searched for "your" (all lower case) in the subject and found, among others:
Searching for "Your" (upper case "Y") finds exactly the same messages.
Hope this helps,
H
Strange this, because that's what I thought, having used Apple Mail for years. Tried it again and you are right, it is not case sensitive, but earlier today I did a search that definitely returned a different set of results when I changed the word "hours" to "Hours". I wonder if somehow I inadvertently triggered a case sensitive option. -
Installation of Photoshop CS6 (Extended) on Case-Sensitive Drives
I understand that under the "system requirements" the Adobe website says that you can't install PS CS6 (Extended) on case-sensitive drives (I'm using a MacBook Pro, OS X v. 10.7.4). This seems to have been the case at least since CS5.
I didn't see this, and I bought (quite excitedly) the update from CS PS5 (Extended) to PS6. I had NO PROBLEM installing PS5 on this drive.
Of course, as other users have indicated, the installer refuses to let you install on a case-sensitive drive (e.g., no options to install on another disk). There is also no mention that CS6 must be installed on the boot drive.
Requiring installation on the boot drive has serious implications for those of us who require case-sensitive drives for other work; I don't want to have to reboot from another drive when I use PS, and switch back and forth -- that's simply foolish.
From my point of view (as a user, granted), this is lazy programming, and this needs to be fixed ASAP. At least in my case, I have a $400 lump of software just taking up space, when I want to be up to my eyeballs enjoying PS6 in all it's glory.
Outside an Adobe fix, I don't see a solution to this problem. If I wipe my drive, format it as not case-sensitive, then I lose functionality for other critical work. Further, I'm not sure that the process of wiping the drive, formating it as non case-sensitive, and restoring everything from TimeMachine would even work (since the backup material is coming from a case-senstive drive and trying to go to a drive that is not case-sensitive).
The REALLY frustrating part is that I've installed Photoshop 3, 4, and 5 (and from much, much further back) on case-sensitive disks -- all with no problems. It's only now that the issue smacks me in the face.
There's got to be a work-around, if not a "real" solution.
Whatever help you might be able to offer would be greatly appreciated; details can be sent to cdretk at gmail dot com.
I have hope, and I thank you in advance.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
systems.
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.
Respectfully,
Sherwood of Sherwood's Forests -
The volume has the wrong case sensitivity for a backup
Updated to OS X Yosemite 10.10.1 and when trying to restore my backup (using TM) into my iMac (27-inch, Mid 2011) get the following message: "The volume has the wrong case sensitivity for a backup."
Any help would be appreciated!That's not how you restore.
Move your data to a new Mac - Apple Support
OS X Yosemite: Recover your entire system -
[MacOSX] Case sensitive filesystem no support ?
I would like to know why it's still not possible to install Photoshop on a case sensitive filesystem on Mac OSX ?
I would have expected that this new version would have get rid of this old limitation.Although I have not tried it with CS6 yet, Bridge CS5 on Win 7 is case sensitive for file names when decoding the path to the file. Supposedly, win7 does not have a case sensitive file naming system. For example:
\\MyNetworkDrive/directory/pic.jpg
and
\\mynetworkdrive/directory/pic.jpg
will generate two distinct entries in the bridge cache system - one each for the upper and lower case "mynetworkdrive" - probably how the file hash code is generated. This can get awkward if you provide the file names as a parameter to the execution of bridge. This case sensitivity only seems to happen on network drives. -
In ALV Report Filter selection should be case sensitive
Dear All,
since one field is case sensitive in database table , i have to fetch that in alv report , but when i am applying filter on that field its is simply fetching data with case description. if its in caps it should fetch caps data but in smaal case report showing no data
Regards,
Pankaj VashistaHi,
All text datas are case sensitive.
To make it work perfectly You have to Use the Keyword translate to Upper Case than display
Now filter can work.
Without Transalation to Upper Case filter will not work.
Regards
Arbind -
How do I install PSE8 on MAC with case sensitive drive?
I tried to install PSE8 for mac and i get an error saying it cannot be installed on a case sensitive drive.
Is there a fix for this?What is the purpose of this?
I have my drive formatted case sensitive on purpose for more security and stability.
Why on earth would y'all choose to do this? -
Is a Full Text Index search case sensitive or not in SQL Server 2012?
I setup full text index on my contact table and am attempting to run a search on it using the following query:
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName, 'Test')
OR CONTAINS(C.LastName, 'Test')
The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
Case sensitivity
Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
is not supported.
1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
Full-text queries are
not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
(Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
Thank you for your time and help,
HananWhats the collation setting for the columns? try using a case insensitive collation as below
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs -
I am unable to reinstall Photoshop CS6 (I do have the serial number) on my Macbook Pro 10.9.5 (Mavericks os). and am getting the message "Installation on case-sensitive volumes is not supported. Please choose a different volume for installation." I am further told that "Adobe apps cannot be installed on case-sensitive drives, you need to Install the product onto an HFS+ or HFSJ non-case-sensitive drive."
What I don't understand is this: I originally bought and installed Photoshop CS6 back in March 2013, and it worked fine. Yesterday my hard drive had to be replaced and my computer person salvaged as much of what was on it as he could, but now I have to reinstall Photoshop. 1) Why did it work before and it's not working now? 2) Is there anything I can do that does not involve reformatting the hard drive?It means what it says. The "computer person" formatted it wrongly/ unsuitably. it needs to be formatted again.
Error "Case-sensitive drives not supported" or similar install error | Mac OS
Mylenium -
Print dialog options in case sensitive file system
Since changing the file system running Lion and Mountain Lion from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled), certain features in print dialogs have disappeared.
Particularly the option to print notes with slides in Microsoft Powerpoint are gone. Also, when choosing to print only 1 (or more, but not all) of multiple pages in Microsoft Word, the printer will nevertheless print all pages.
This problem occurs on printers of different brands, i.e. HP, Lexmark, Brother.
I was able to determine this problem by reproducing the issue on a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Case-sensitive, Journaled) vs a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Journaled), not Case-sensitive.
Has anyone else had the same problem and maybe a solution?I just fixed this on my Mac. It is a bug in Microsoft Office... the Printer Dialog Extension (PDE) for Powerpoint is located in a directory named "Plugins", but PowerPoint is looking for it in "PlugIns". This obviously does not work in a case-sensitive filesystem.
Here are the steps to fix the issue:
http://apple.stackexchange.com/a/119974/69562 -
How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?
The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,, -
I am trying to install MasterCollection_CS6_LS16. When I double click the install file I get this error message: We've encountered the following issues. Installation on case-sensitive volumes is not supported. Please choose a different volume for installation. What does that mean? How should I proceed?
Hey iraravitz,
Could you please let me know what version of OS are working on.
You might receive this error when you attempt to install on a drive with the HFS+ Case Sensitive file system, which is not supported for installation of Adobe Creative Suite 6.
So, please try installing on a drive that has been formatted with a supported file system.
You might refer the KB doc link mentioned below for the same:
Error "Case-sensitive drives not supported" or similar install error | Mac OS
Let me know if this helps.
Regards,
Anubha
Maybe you are looking for
-
When I try to open some pictures in finder with preview I get a message that I do not have permission to open it. It tells me to go to file - info. Don't know what to do from there.
-
i am trying to reset my brothers ipod touch to factory settings and to delete all of the data so that we can sell the ipod, but we were originally using an old apple id account that now no longer exists, our email was with a company (optus) that we w
-
How do I make a custom bookmark in Safari?
Hello, When I click "Add a Bookmark" from the Bookmarks bar, it will only let me edit the name of the bookmark, but not the html address. How do I put in my own addresses without actually being on a particular page? Thank you
-
Multiple process start with terminal?
How do I open multiple programs at one? I need it to open an executable, leave it running, open another executable. I'm not sure how to do this branch thing in the terminal I want to use this for an .sh script Last edited by caelestis (2009-04-29 22:
-
sxmb_moni shows error message when ever the transaction is processed. SYSTEM ERROR OCCURED DURING PERSIST. this is the error message.This happens when i try to execute monitor for processed xml messages and it stops in that page.