Trying To Switch To Case Sensitive

I'm trying to switch to a case sensitive file system. My install disks are at work and I'm lazy, so I tried to use the disks for my roommate's MacBook Pro (I have a white MacBook) and it didn't work -- it admonishes me that "Mac OS X can not be installed on this computer." What's the deal? Do certain Leopard disks only work with certain computers, or do I have a big problem?

This is correct. Only the retail version of the OS will work on all machines that meet the OS's system requirements.
Message was edited by: Sagesse

Similar Messages

Trying to install photoshop cs6 purchased last christmas for wife on a MAC and the redemption code is coming up invalid. Tried to enter it case sensitive as well with same result. Is there a timeline to install this after purchase?

Any help is appreciated thanks!

I'm not sure. It was from a dept store out the box.
Inside is a little black card with the redemption code.
Front of box says Adobe Photoshop CS6 MAC OS.

Acquiring case sensitive URL info from browser

In a Java filter am trying to acquire the case sensitive URL (hostname) from the app I'm filtering.
Normally, to get the whole URL, one would do something like:
String myurl = request.getServerName() + request.getRequestURI();getServerName returns an all lowercase server name from what I'm seeing...
Is it possible to get the case sensitive server name from the requested url....
For example:
http://mysErVer.cOm/myApp/
request.getServerName returns "*myserver.com*" whereas I want "*mysErVer.cOm*"
Any ideas? Am I missing anything obvious?

I may be wrong, but I'm pretty sure that when the request is sent by the browser, it's converted to lowercase, so if you want to know what the user typed into the address bar, you won't get it. Urls are defined as lowercase anyway, so what difference does it make how it's entered?
http://en.wikipedia.org/wiki/URL_normalization

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

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

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

Cannot change case-sensitivity of Time Machine sparse bundle (10.7.2)

Hi everyone, I'm trying to follow this excellent guide to Time Machine backups:
http://pondini.org/TM/A8.html
The site suggests that I make my TM backup case INsensitive, so after the network sparse bundle has been initially created on my Lion 10.7.2 TM backup, I cancelled the backup, then opened up the sparse bundle in Disk Utility as per the instructions provided.
I double clicked the sparse bundle to open the Time Machine Backups volume, and then in the Erase tab I changed the format from Mac OS Extended (Case-sensitive, Journaled), to Mac OS Extended (Journaled).
Then I clicked on "Erase" but it returned an error and said it could not do it. Sorry I don't have the exact error message on hand at the moment but it happened again with the same error message when I tried again.
Steps 6-8 in the guide tell me to Get Info on the Time Machine Backups volume and "Ignore ownership on this volume". However when I open the Info for the volume "Ignore ownership on this volume" is not there at all in the options? I've opened up every section of the Get Info window but it's definitely not present.
Has something changed in 10.7 Lion or is there another reason I'm getting this problem? The HDD is connected as an AirDisk on an AirPort Extreme Base Station (yes I realise this is an unsupported/not recommended Time Machine solution). I haven't yet tried directly plugging the drive in via USB which will be my next step when I regain access to my computer later.
Any help or advice would be appreciated. Many thanks.

owngoal wrote:
You say your "backups still turn up corrupted now and then" - how do you know? Is it only when you try to access them that you will know this?
Sometimes a backup will fail, sometimes you can't access them, sometimes you'll get this message:
See #C13 in Time Machine - Troubleshooting for details.
And by this stage is it too late to recover anything?
Sometimes. Sometimes they can be repaired by Disk Utility. Sometimes only a heavy-duty 3rd-party disk repair app like DiskWarrior ($100) can fix them. Sometimes nothing can. Sometimes you can restore some individual items, sometimes not. Sometimes you can do a full system restore from some backups, other times not.
does it help that I am using a Gigabit WIRED connection between iMac - 10/100/1000 switch - Airport Extreme Base Station?
Probably -- you won't have WIFI interference.
But if you have an iMac, why not just connect the external HD directly to your Mac? That's much faster and more reliable (and supported).
You'd need to erase the disk in that case, since Time Machine won't bother with a sparse bundle at all on a direct backup. Just format the disk as GUID, with Mac OS Extended (Journaled) and let 'er rip!

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?

How do I use switch and case statements to fill more than one other field?

Hi all,
I'm new to the community.
I'm trying to make an existing form more user friendly for my coworkers. I want to use a switch and case approach in a drop-down list field so that the selection fills two seperate other fields with different info related to the selection.
I can already do this with one field, but if I add a second target field under an existing case the text doesn't appear there when I make the selection from the dropdown.
Basically, I'm asking if I can do this:
switch
(sNewSel){
   case "1": // Selection 1    Row2.Field1
= "text for field 1";
    Row1.Field2 = "text for field 2";
    break;
etc.
It works if the "row1.field2" option isn't there, but not when it is present.
Any takers?

I'm not sure if I will be able to send you the form. There may be too much to redact.
Would this last bit of code in the cell affect anything?
if
(bEnableTextField)
{Row2.Field1.access
= "open"; // enable field
Row2.Field1.caption.font.fill.color.value= "0,0,0"; // set caption to black
That is, do I also need to repeat the same thing for the second target cell (Row1.Field2)?
What would be possible hang ups that would prevent it from working correctly?
Dave
By the way, I'm not sure if my other attachment posted. I am trying again.

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 can I deal with case-sensitive filenames referred to inconsistently inside other files?

I have downloaded into Dreamweaver an existing web site that I'll be taking over from someone else. The site was built with Microsoft Front Page and apparently now runs on a Windows web server. While redesigning the site, I'd like to upload it to a web server belonging to me, where I can maintain a work in progress that is accessible to others (so they can give me input as I go along). But my site is running on a Unix system, where filenames are case-sensitive.
In the site I've inherited, I've discovered at least one file that is referred to in other files sometimes with one character in upper case and other places in all lower-case. The actual filename contains the upper case character and locally, on my Windows system, it doesn't matter. But on the server the file is not found when it is referenced in all lower-case.
Of course, I can create an all lower-case symlink on my Unix server for the mixed-case file that I know about. But I don't want to look through every file on the site for other files which may vary, case-wise, in how they are referenced. Is there any way that Dreamweaver can help me; for example, by going through and changing all mixed-case filename references inside files, to be consistent with the actual filenames?
I know this is a lot to ask of Dreamweaver and I'm not optimistic. But if anyone knows of a solution, I'd appreciate it.

he means that if you use the file > find function
(on windows this can be called upoon using CTRL + F)
you will be able to go through all the files which are cauing you a problem and change their names so that they are all in the same case
be warned thou
if case sensitivity is your problem,
and
if some code references to your files are written in one case and some are written in the other case, simply changeing the case of the file names will not help.
what you are trying to do will only work if
> ALL of the file names are in one case
or
> ALL of the files names are the same case
bcause this will mean you can change the one which does not always match using CTRL + F
if there is a mix and match on both sides then you are in for a lot of work, if this problem involves multiple names then i would advise you to simply start over!

How do i reformat a case sensitive external hard drive without losing data

I know there are a lot of posts about this, and i have spent hours trying to find a soloution / understand what people have responded to others, but i can't work this out.
I also have a Buffalo HD (let's call it HD1) that stores my itunes library.
I have a WD My Passport for Mac (let's call it HD2) that backs up my Mac Book Pro.
I have an older WD that has older TM back ups on it from previous computers (let's call it HD3)
I have one spare completely 'clean' WD hard drive (let's call it HD4).
My laptop was really slow and full so i went to Genius bar, they sold me the Buffalo HD and they moved my itunes to it and set it up so it now has my itunes. I used this disk to run two TM Backups before i realised the drive was nearly full, so i bought the WD My Passport HD2.
I now use WD My Passprt HD2 for TM.
I want to MOVE the backups on HD1 to My Passport HD2 as there is lots of space on it. I also want to move my itunes library from HD2 as a back up.
But i can't!!!
After reading for hours, apparently this is because my HD1 is case sensitive, journaled. And it needs to be Journaled to work with TM/OSX or something very confusing. I have read lots of threads about re-formatting / partitioning and all things that are way over my head. But the one thing i do understand is if i reformat HD1, it erases the data.
This is NOT an option as it holds my WHOLE itunes. The Itunes is WAY too big to drag onto my mac book pro and then move it over to HD2 and make that my itunes folder.
HOW THE **** ARE YOU SUPPOSED TO BACK UP THE CASE SENSITIVE DRIVE BEFORE REFORMATTING IT IF IT'S TOO BIG TO FIT BACK ON YOUR COMPUTER? Surely that's the whole point of having an external drive... to back up AND give you more space?
I'm so mad that the apple store did this to me... they should know that case sensitve wouldn't work with a passport... that i would have problems. UGh.
I have options to move the files from HD1 as i have HD2 and HD3 and then also the completely unused HD4... but i can't move anything anywhere due to this case sensitive nightmare.
Someone PLEASE HELP ME.
thanks.

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,

Why Case-Sensitive while assigning tasks to other users??

I am trying to assign a task to another user through AdminUI.
While searching for users, I am supposed to provide case-sensitive search text to find actual users.
In previous installations it is not a problem. i.e only in production it happens.
Is there any place to modify this settings?
Please see the attached screenshot of the page.
Thanks,
Nith

Raghu,
thanks for the reply, you are right as per the audit .But suppose if it is for 200 users ,creating 200 CUP requests will be impractical right.
there should be some solution for this , because there will be many situations practically where we have to assign roles to N number of users.
Is this possible in GRC 10 ? any idea ?
Regards,
Jaags

Case Sensitive External Drive for iTunes

My iTunes Library is currently stored on a case sensitive external drive. I am moving it to another drive that I found out is formatted as a non-case sensitive (both areJournaled). When I tried to move my iTunes Library, it would not copy because there are apparently some duplications that are different in case and this causes a problem when duplication to a non-case sensitive drive.
I figure I have two options:
1) Reformat the new drive to be Journaled and Case Sensitive
2) Go through the tedious process of identifying which files in the iTunes Library would be duplicates in a non-case sensitive drive. There could be just a few or hundreds (or even thousands).
What is the disadvantage of using a Case Sensitive drive for iTunes (option #1)? I may also store some other files on this drive.
I noticed that all my other drives, on both my desktops and external are formatted as non-case sensitive.

If you can get to the two metadata files that iTunes keeps on the old PC, then you have several options. See: What are the iTunes Library files?
1) Use the 'iTunes Library.itl' file on the old PC to completely recreate your Library. You will have to place all the music files/folders in the exact same location on the new PC as they were on the old PC. That drive letter and directory path. Then copy the older ITL file over the current one on the new PC. Open iTunes and you'll have a clone of the old PC's Library. As you have been using an ExHD to store the music, this would be my preferred choice. It's easy to remap the drive letter of an ExHD, if needed.
2) The other way is to 'File=>Import' the XML file and recover the Playlists from there. They will not be in any folder structure as they were in the previous iTunes. Also, any playlists that depended on ratings, play counts and last played will be changed, as those attributes have not been carried over using this method.
Post back if you have questions.

When logging onto a web site with a log on name firefox is changing logon name from Kostas to kostas as the site is case sensitive it is not acceptable. how do I correct this? Thanks

I registered with a web site and used the name Kostas as the log on name. Entered a question and recieved replies
When I later tried to log onto the web site to say thankyou ,and enter Kostas in the log on box a reminder appears created by Firefox of kostas, I ignore this, move to the password box and firefox changes the log on name to kostas with small k. The register is case sensitive so for quite a while I could not understand what was going wrong? I eventually managed to log on by using a rival system
My previous experience is that if you use a different log on name it is recorded and then you choose the correct one to use? But in this case I am given no choice
How can I correct this please
Probably no connection but
I registerd with another site and recieved an e-mail in which I had to click on web address to confirm registration and came up with an error message, tried a few times and same thing happened?? The webmaster of this site had no record of my registration details?
Finally I had a phone call from a company called NERD-I.com
offering to solve various computor problems at a fee. I did not take up their offer, but hope they do not have anything to do with my current problems??
Many thanks

Hi Corel
Thank you for your reply
However I need the lower case version for some sites and the upper case version for the site in question? To make matters worse this site does not allow you to change your log on name unless it is in the form of an e-mail address
So what I need is Kostas for this site and kostas saved for other sites and allow me to choose which one I want to use
How do I do this please
I have no bother with this on Win Internet Explorer but I like Firefox
Mind it may be as simple as deleting The appropriate entry and resetting with Kostas instead of kostas?
But I would appreciate knowing the correct solution from an expert

Trying To Switch To Case Sensitive

Similar Messages

Maybe you are looking for