Acrobat cannot be installed on case sensitive formated mac

Any bug fixes available to get the acrobat installed on a Mac with case sensitive formatted hard disk? I formatted my mac withaout case sensitive but when I get the backup with my data from time capsule the original version comes back. Any help to this problem?

No, it's not possible. At this point Adobe programs do not support case sensitive volumes at all.
Mylenium

Similar Messages

It says it can't install on case sensitive volumes and i have no idea what that means

It says it can't install on case sensitive volumes and i have no idea what that means

I didn't save a link, but I think I've read a similar message in the past month or so... are you on a Mac, and what is the volume name of your hard drive?
Link for Download & Install & Setup & Activation problems may help
-Chat http://www.adobe.com/support/download-install/supportinfo/

Hi, I want to format my macbook pro and i don't know what to choose from this list---: Mac OS Extended (Journaled) Mac OS Extended Mac OS Extended (Case-sensitive, Journaled) Mac OS Extended (Case-sensitive)

Hi, I want to format my macbook pro and i don't know what to choose from this lis
Mac OS Extended (Journaled)
Mac OS Extended
Mac OS Extended (Case-sensitive, Journaled)
Mac OS Extended (Case-sensitive)

MAC OS Extended (Journaled)

Acrobat Reader 8, problems on case-sensitive HFS+

Hi,
I hope this is the right forum. I have formatted my Macbook to use case-sensitive HFS+ volumes, because I regularly use Unix programs (many of which have a built-in assumption that file names are case-sensitive) and now some functions of Adobe Acrobat Reader 8 don't work properly (e.g. printing and Updater). Since above formatting is the only change from my older installation, I assume it's because of the different HFS+ format. So I propose you test Adobe Reader on a Mac with case-sensitive volumes sometime.
Regards, Thomas Jahns

This forum is for FULL Acrobat - Reader forum is
http://www.adobeforums.com/webx?13@@.3bbf42f7

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.
ch

That 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'.

Software won't run/install on case sensitive volumes

I have found out the hard way that quite a few games will not install or will not run on a case-sensitive HFS+ formatted volume.

I didn't save a link, but I think I've read a similar message in the past month or so... are you on a Mac, and what is the volume name of your hard drive?
Link for Download & Install & Setup & Activation problems may help
-Chat http://www.adobe.com/support/download-install/supportinfo/

FaceTime cannot be installed because the version of Mac OS X is too new.

The Mac App Store program is telling me I can install FaceTime. I already have it installed, but the version in the App Store is dated last April, whereas my installed version is dated 2013, so it seems like the app store version should be an update.
However, when I try to install it, I get a message saying "FaceTime cannot be installed because the version of OS X is too new".
Is this just the Mac App Store program being stupid?
My installed version says version 3.0, but the app store version is 1.05. This is a huge difference that needs explanation. Especially since it does not tell me that I have a newer version of the program already installed.

The App Store version of FaceTime is only for OS X 10.6. All later versions of OS X have it built in.

Cannot run a a case sensitive drive? that is crap, lazy programmers, shoddy!

I am certainly not going to make my Mac case insensitive just to run Photoshop!

What Chris has resisted saying (cause well, after all these years he's learned to be PC) is that it ain't Adobe's fault...they've bent over backwards to deal with the issue and the bottom line is that Apple's own tools fail to provide a solution for an application the size of Photoshop (and other Adobe apps).
Photoshop ain't an App Store application....it's a real big time, heavy duty app that still (sadly) must use the system level APIs and OS services...sometimes those tools are somewhat South of optimal...(both Apple and MSFT suffer from this but often in frustratingly different ways).
But yapping at Adobe like their engineers are a subspecies doesn't help...and if the OP had half a clue he/she/it should have known that.

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 f

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

I recent la format the drive and create a case sensitive jornal and put a password. How I undo it if I just see the whole drive as the recovery disk

I want to format my computer and I start to do that but I fondo a copy of the boot folder on the drive, not the recovery drive. I formated and make it case sensitive jornal with a password. Then I put a password in main too. So the drive the entre drive become my recovery drive.So I have two recovery drive I think.I learn almost all the diskutil comando and I don know how to fin it. The disks are not showing the one with the passwords.

Hi Kappy,
Just wondering if you had any advice for my situation . . .
My time machine backup was backing up to a drive that was "Mac OS X Enteded Journaled, Case Sensitive." I had no idea what this meant, or that it would even cause issues.
I took my computer to the Apple store yesterday, and they wiped it clean. When they tried to restore it from the Time Machine backup drive, it would not work. Their guess is that Time Machine cannot restore from a drive that is "case sensitive."
Any thoughts on how I can convert my time machine backup data from a "case sensitive" state, to a "non-case sensitive" state? I've tried to just drag and drop the files from the case sensitive formatted drive to a new drive that I have that is formatted non case sensitive, but I get the following error message:
"The volume has the wrong case sensitivity for a backup"
I just really want my data back - I thought TimeMachine was the way to go (and was supposed to work) but unfortunately it is not.
Any help you can provide would be greatly appreciated.
Thanks,

Case-Sensitive volume issue installing Creative Suite 6 on mac

Trying to install Creative Suite 6 on MacBook Air but an error message "Case-Sensitive volume is not supported" come up.
How can I solve this problem and start using Creative Suite?
Can I install Creative Suite 6 on case-sensitive volume?
If not, how can I change my volume to non case-sensitive one?
I am a graphic designer and not a developer who is not so savvy about tech.

Tks_tks you will want to install Creative Suite 6 on a non-Case sensitive formatted drive. You can find more details at Error "Case-sensitive drives not supported" or similar install error | Mac OS.

How to convert case-sensitive to extended journal format

I have two apple computers (extended journal format) that have been backed up via a time capsule. I have just noticed that the TC is formatted as case-sensitive. I do not know why case-sensitive. In an effort to ensure consistency of file format then I seek to somehow remove case-sensitive formatting. I presume no/minimal underlying case-sensitivity issues within file names as source data is not formatted in case-sensitive manner.
I have tried SuperDuper to clone the TC to an external HDD but the application cloned the formatting in addition to the data.
I have attempted use of Disk Utility to copy content from source (TC) to destination (HDD) but this yielded error messages that noted different file format types.
It there a way to convert/remove case sensitive formatting from TC?
I appreciate that I could simply reformat TC to extended journal format but this would presumably erase all my backup data.
Any guidance most welcomed.

RossM wrote:
So I guess my choice is to "leave well alone" as Pondini suggests and accept the fact that cloning TC onto HDD has now formatted my new HDD as case-sensititive.
Actually, you may have two choices, depending on how you're going to be backing-up to the new HD:
Your best bet, by far, is to back up to it directly, rather than connecting it to the TC. That's much faster and more reliable. If so:
* Leave the TC backups alone. Reformat the HD as case-ignorant and let Time Machine start fresh on it. You can always see and restore from the old ones via the Browse... option, per Time Machine - Frequently Asked Question #17.
* Format the HD as case-sensitive and copy the backups from the TC to it. But don't copy the whole sparse bundle; copy the Backups.backupdb folder from the sparse bundle to the top level of the HD. (Sparse bundles are used only for network backups.) See #18 in the FAQ; you'll need the 4th procedure (copy network backups to be used locally.
But if you're going to connect the HD to the TC and back up to it that way, it doesn't matter how you format the HD, since the backups must be in a sparse bundle, that has its own format. Two choices for that:
* Leave the TC backups alone. Connect the HD to the TC and select it as the TM destination, and Let Time Machine start fresh on it. You can always see and restore from the old ones via the Browse... option, as above.   (There is a way to speed up the first backup; see the blue box in #Q2 of Using Time Machine with a Time Capsule.)
* Copy ("Archive") the TC's internal disk to the external HD, per the green box in #Q6 of the same article. Then select the external as your Time Machine destination via Time Machine Preferences.
Is this simply deferring a problem issue to another time (aagh)? Or to somehow try and remove this inconsistency and remove case-sensitive formatting from all tech items, even if this might mean reformatting and losing old backup data?
No. There's not really a problem, unless you change the case of file/folder names and try to restore the old ones to the same place via the TM browser, per the link in my earlier post. That's the only possible downside.
Does Time Machine require case-sensitive formatting on its destination drive?
No. It's the default, but case-ignorant is fine, unless you ever want to add a case-sensitive volume. Then you're in a pickle.
Or does Time Capsule only function witih case-sensitive formatting?
No. The TC's actual disk is case-ignorant; it's only the Time Machine sparse bundle that's case-sensitive by default.
The benefit of case-sensitive formatting as Apple default seems rather unclear to me
It's the default only for Time Machine backups. Everything else defaults to case-ignorant.
The advantage is, once you've been backing-up your internal HD for weeks, months, or years, and want to add a case-sensitive external HD to be backed-up, you can.   If the backups are case-ignorant, you can't.

Not able to install adobe due to Mac OS Extended (Case-sensitive, Journaled)?

My harddisk is Mac OS Extended (Case-sensitive, Journaled) and this does not support adobe aplications. Is there a way of changing the format?

No, not easily.
How and why is it case-sensitive? Macs are case-ignorant by default, but a few 3rd-party apps require it. Do you have another app that requires it?
Assuming you already have data on your Mac that you want to keep, you'll need to start with at least two full backups on two separate external HDs, because you'll have to erase the internal, reinstall OSX, and put your data back (that may be rather tedious).
What version of OSX is your Mac running?

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,,,

How do I convert a case sensitive drive to a case insensitive drive?

I have recently purchased a MacMini Server, and installed the 2 internal hard drives in a RAID 0 configuration to obtain the speed and 1 TB capacity, but unfortunately (rather stupidly in retrospect) formatted the drive in case sensitive mode.
On installing the operating system and multiple applications, everything seemed to work well until I tried to install Adobe Acrobat X Pro. This application refuses to install on a case sensitive formatted drive, which I now understand is a common problem.
The question is how can I convert to a case insensitive format without reinstalling all of the software from scratch?
I have a Time Machine backup, and the easiest thing for me would be to reformat the drive, and then restore from the Time Machine backup.
Will this process work? Or will there be some complications and files that will not function if they were originally installed on a case sensitive drive?
Any help is appreciated....

iPartition can do it ( http://www.coriolis-systems.com/iPartition.php ).
from iPartition Help:
Make Case Sensitive/Case Insensitive
HFS+ now supports a case sensitive format as well as the usual case insensitive format. On a case sensitive volume, the names “Readme”, “README” and “ReadMe” would all represent different files, even if they were in the same folder.
This option allows you to non-destructively change a case sensitive volume into a case insensitive one, and vice-versa. If you are going from a case sensitive volume to a case insensitive volume, some of your files may be renamed automatically by iPartition so that they do not clash. If all of the files in the table below were in the same directory, the right hand column shows the new names iPartition would choose for them:
Old name New name
README.txt README.txt
ReadMe.txt ReadMe 1.txt
Readme.txt Readme 2.txt
README README
ReadMe ReadMe 1
Readme Readme 2
Notice that iPartition puts the number before any file extension.
N.B. iPartition does not transform filenames with numbers on the end back into their original forms. There is no way to tell which files were renamed by the user and which were renamed by the conversion process.

Acrobat cannot be installed on case sensitive formated mac

Similar Messages

Maybe you are looking for