Disapearing pictures - case sensitive?

Hi all,
I create my website using iweb on my mac mini at home, then upload it from my mac at work to a university hosted webpage.
The last time I updated, I noticed that some of my pictures were missing. After a bit of fiddling, I found that the missing picture had file names ending in .JPG, and that if I changed the name to .jpg the picture reappered.
Has anyone had this problem, and does anyone know how I can stop it happening? I also found that some of the names refused to be changed back to .jpg ( "a file with this name and extension already exists" - not anywhere I can find it!), leaving me with slideshows which won't run.
This is one of the pages with missing images: http://www.maths.soton.ac.uk/~gh/Stage%20Costumes.html
Thanks for you help, Gemma

ok - is there an easy/quick way of doing this? Or a way of telling iweb not to use capitals in the file names automatically? Cos when you have over 100 images causing problems, changing each one individually is a pain!
Thanks, Gemma

Similar Messages

How can I transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive?

Community,
Every time I try to transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive, I receive the attached message: "You can't copy 'iPhoto Library' because it has the same name as another ideon on the destination volume, and that volume doesn't destinguish between upper- and lowercase letters in filenames."
My theory is, if I am able to unpackage my iphoto library, I can transfer each folder one at a time so that I can trouble shoot any "duplicates." Will this work?
Let's say that works. How can I repackage the library so iphoto recognizes it?
Is there a better way?
Thank you,
Jonathan

Can we assume that I don't have any naming conflicts? Clearly there are or else I wouldn't get the error I'm getting.
The error doesn't mean you have name conflicts. It means that the Finder won't take the chance that you might have them.
You're suggesting that all I would need to do would be to use Carbon Copy Cloner to transfer the files from the case-sensative harddrive to my Extended Journaled harddrive?
Yes. But I would just use the built-in rsync shell command. First, back up all data if you haven't already done so. Launch the Terminal application by entering the first few letters of its name into a Spotlight search. Copy or drag -- do not type -- the line below into the Terminal window, then press the space bar:
rsync -aE --delete
Now drag the iPhoto library you want to copy into the window. You should have something like this:
rsync -aE --delete /Users/you/Pictures/iPhoto\ Library
Drag the Pictures folder on the destination volume into the window. Now you have this (line will wrap on the page):
rsync -aE --delete /Users/you/Pictures/iPhoto\ Library /Volumes/something/Users/you/Pictures
Press return. The copying operation will start. When it finishes, you'll see a new dollar-sign ("$") prompt below what you entered. If there were no errors, you're done.

Problems retrieving backup from Time Machine, Case-sensitive HD

Hello.
I'm trying to manually retrieve the information I got in a Time Machine, but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way. After checking a couple of things I noticed that, somehow, the external HD was Case-sensitive, so I'm assuming that, instead of +File, File 01 File 02+ it's sorted out like +File, file, filE+, and since the computer's HD is normal it's having a conflict with those file names.
That being said, is there a way to fix this? What I'm trying to move is an iTunes and iPhoto Library, "probably" iTunes could be done manually, but in iPhoto there's over 10 GB of pictures and I'd probably take a looooong while to fix it manually.
Any work around?
Thanks!

Hi Adrian ...
Let me see if I can help ...
I'm trying to manually retrieve the information I got in a Time Machine, ...
How? With the TM App or from the Finder?
but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way.
It's just letting you know that the original file, on the System HD, still exists and wants your permission to over write the original file with the TM file. Backing up your System HD to TM should not have changed any of the original file names. If TM had changed the Case when backing up from your System then TM Restore would have duplicate these files/folders without even asking you.
That being said, is there a way to fix this?
Yes. After you have restored the files/folders that you want to keep you can reformat the TM HD. Or try one of my tricks which is to just reformat the free space. Use the Mac OS X Extended (Journaled).
Good Luck.
Buzz

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

Hello. I keep my IPhoto library (about 90GB) on an external HD and am trying to back it up to another external drive. Both are formatted Mac OS Extended (Case-sensitive, Journaled). Recently, backup has failed from the start due to error 36. Howtoresolve?

Hello. I keep my iPhoto library (about 90GB) on an external HD and am trying to back it up to another external drive. Both are formatted Mac OS Extended (Case-sensitive, Journaled) and both check out when scanned with Disk Utility. Recently, backup has failed from the start due to error 36. Any ideas how to resolve? Also, what's the maximum recommended size for an iPhoto library file? Thx!

Since you can't drag the library to the other EHD for the backup see if you can duplicate it (if you have enough room on the drive) by selecting it and typing Command+d (duplicate).
If you do rebuild the library without a backup and it goes awry you won't lose your photos but you may lose your orgnaizational efforts. So try the following:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Select the options identified in the screenshot.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library in the location of your choosing based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
NOTE: Fix 2 above might be the method you might want to try first with iPLM creating the new library on your second EHD. If it works that would get your backup copy on the second EHD at the same time as repairing it. If it does'nt work then go back to Fix 1.
OT

Case sensitive field in to_date function

update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input string
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.

Hi,
Welcome the the forum!
882431 wrote:
update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)It looks like you're missing a single-quote right before the last ')'.
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input stringThat error occurs when when you have characters in the 1st argument that do not correspond to anything in the 2nd argument. For example:
TO_DATE ( '30-Aug-2011 12:00'
, 'dd-Mon-yyyy'
)In this example, TO_DATE doesn;t know what to do with the ' 12:00' at the end of the 1st argument. According to the 2nd arguemnt, there's only supposed to be 11 characters in the string. So it raises the ORA-01830 error.
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.Case sensitive column names are a bad idea because they cause so amny problems, but I don't think this is one of those problems. It's more likely that you need to use SUBSTR (or some other string manipulation function) on "Order Date String" before using it in TO_DATE.
Whenever you have a problem, please post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) from all tables, so people can re-create the problem and test their ideas.
Also post the results you want from that data, and an explanation of how you get those results from that data, with specific examples.
Always say which version of Oracle you're using.

HT3275 Time Machine couldn't complete the backup to "My Passport Studio".. A disk you are backing up is case-sensitive, but the backup disk is not.

Hi,
Time Machine won't back up files on another external hard drive as it says it is case sensitive. The other drive contains mainly music and pictures.
Thanks for any suggestions,
Lisa

See pink box on this page:
http://pondini.org/TM/5.html

10.5.5 Update Now: A volume you are backing up is case-sensitive

Since the 10.5.5 patch, Time Machine will not backup. I get the following dialog:
A volume you are backing up is case-sensitive, but the backup volume is not.
To select a different backup volume, or to chose not to backup the case sensitive volume, open System Preferences and choose Time Machine.
Here is the problem. All my drives are formatted the same way including my backup drive.
Mac OS Extended (Journaled)
In fact, I can navigate through my older Time Machine backups (both in Finder and through the Time Machine UI) and see that previous to 10.5.5 backups were case sensitive. Or, at least they are showing proper case when I manually view the filenames.
A couple of days now without any backups has me very concerned about Time Machine. Thank goodness I have a Drobo as my primary storage.
Anyone have any recommendations?

Before I go on, I will say I'm not yelling at you - I'm venting in frustration. And, some of this is written tongue-in-cheek is it were, but perhaps you will get my meaning. All of it is factual.
I understand that much of Time Machine is smoke and mirrors until you are in the IT industry and understand what TM is doing. Trust me - it's not rocket science. Basically think of each file as your mailbox. When the file is altered, the operating system raises the mailbox flag to tell the postman (the backup application) "Hey - something is different here and this file needs to be copied". The backup application copies the modified file to a compressed file called an archive (or library) and then lowers the flag. The next time the backup application runs, it looks at all the files again to see if the archive bit (the flag) has been set (raised) and if it has ... you know the rest.
What is really frustrating is that we are growing more and more digitally dependent and we have no real reliable solution to data storage. It's not like I can send the drives back for warranty service, or even diagnostic - with all the digital information and continued identity theft. We were told that tapes were the solution, but they never work. Then CD-ROMs and DVDs were the rage and they were suppose to last a hundred years (cough cough) I mean months, (cough cough) I mean ....
And now we have TM.
Secondly, because digital data grows exponentially every year (those digital cameras aren't producing smaller images - for example) you have to grow your storage. Now Mr. Consumer is looking at 1 and 2 TB storage solutions for the home. So we need reliable storage and reliable backup. For example, I use Apple Aperture and am an amateur photographer. On my desk currently is nearly 6TB of storage. Now that may sound like a lot but I assure you it isn't. One disk is 1.5TB and is used to backup my 2TB primary disk (931GB used). A third disk was purchased as an emergency 3 weeks ago when the 2TB disk started to fail. Following instructions on Apples site, I used the DITTO command to transfer files from the original primary storage to the new storage. Unfortunately, the new storage unit had to be placed on a USB 1.0 chain. The transfer took WEEKS, yes WEEKS to complete and even then failed to apply proper user and group ownership. Just when I was about to try and clone the disk again, the latest patch came out and kicked two of the drives off the USB and placed the third into read only mode. Just like it does every time. And yes, I have turned auto update OFF and no, no one at Apple can tell my why it is automatically applying updates. They swear they are not doing a silent push.
As to the MS Windows approach of telling a user to "reinstall" their system frequently to resolve such problems - that is simply asshattery at the highest level. As an MCSE it is that kind of resolution which shifts the problem from the vendor to the client that I found unacceptable and why I moved from MS to Apple in the first place.
If I were to tell any of my customers that I'd quickly be without employment! We need to put pressure back on vendors to provide reliable solutions. I should not be expected to run verify and repair on each of my disks every time Apple comes out with a patch for some minor applications - which is what is happening.
Such actions (against TB drives) take hours to run and it's just plain unacceptable.
Luckily for me I use Drobo as my primary storage device. If it wasn't for Drobo - I would have lost all my data long ago. Through all of this, Drobo has continued to be (pretty) rock solid, despite the fact that I have to verify the volume every time there is a software patch and it takes all night. Oh, and by the way - before any of you run out and buy a Drobo for your users files (which I highly recommend) you should know that the folks over at Apple state that "the operating system does not support relocation of Users home directories" - which flies in the face of UNIX design.
In fact, the tech support rep who told me that directed me to relocate all my user files (all 931.45GB of them) back to the 150GB boot disk. I tried explaining to him that I had over 900GB of data, but he couldn't grasp that. I also explained that the reason my user directory was on an external drive was because some of the applications (when they were installed) required the files to be native in your home directory path, and my internal SATA disks were limted in size (apparently by architecture design) to 150GB. No one at Apple can explain this to me, the reasoning is also apparently quite a secret. But, I always understood that one of the reasons to migrate to SATA was that it reduced the need for the operating system to ... oh never-mind.
Now, I'm no math major but the last time I checked 931GB of data won't fit on a 150GB disk .... I could be wrong. If I am, I'm a big enough man to admit it so someone please explain it to me.
There, now that all of that is out of my system. I am truly a reasonable man. Please feel free to tell me why I'm wrong here or what I'm missing in the picture.
Message was edited by: Gilbert Blankenship1

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 Vashista

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

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

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

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

Disapearing pictures - case sensitive?

Similar Messages

Maybe you are looking for