Ho to reformat to a non  case sensitive file

How to reformat to a non  case sensitive file

If you want quotes around all the fields, and you currently
have quotes around
none of the fields, you could probably do this using
find-and-replace in a word processor.
Open up the CSV file with 'word' or a similar word processor.
The important thing is that the word processor must be able to do a
find and replace on 'special' characters, like 'return'.
Use find and replace to:
Replace all 'comma' characters with the sequence: quote comma
quote
Replace all 'return' characters with the sequence: quote
return quote
You should then find that your CSV text has quotes around
every record, but you'll have an extra quote character at the very
start and very end of the file (on separate lines), which you'll
need to delete by hand.
Of course, make a backup of your data first - and this won't
work if some of your columns already have quotes, or if some of
your fields actually use the 'comma' character inside the field
data.
- Ben

Similar Messages

  • Case-Sensitive File System?

    I downloaded the trial for Flash CS4 pro and it won't install on my computer.
    It says:
    System Requirements Error
    This software cannot be installed because the file system of the OS volume is not supported. The OS volume should be local , writable and should have non case-sensitive file system
    Anything I can do to get it to work? I have a MBP running Leopard on an intel processor.
    Message was edited by: guynjoan

    guynjoan wrote:
    The hard drive is internal. And Adobe tech doesn't work on the weekends. I checked the "get info" on my hd and it said it is case-sensitive,
    that's your problem. Lots of apps have problems with case sensitive drives so you should never use case sensitive file system unless you have a compelling reason to do so. Your only recourse now is to move your data to a non case sensitive drive. Clone your hard drive to an external drive, boot from the leopard install DVD, reformat the drive non case sensitive and install leopard on it. then use migration assistant to migrate your data from the external.

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

  • Copying folders & files from case-sensitive to non-case-sensitive volume

    I'm trying to copy a rather large (60+ GB), folder and all its enclosed items from a volume that is has case sensitive file names to one that does not. The copy operation always stops when it comes across a duplicate file/folder name differing only in the case of some of the characters. The folders/files in question are actually not duplicates, so I would like to change the file name of the duplicate by appending anything to the filename.
    The copy operation does not provide any choice but to abort the operation when it finds the first identical file or folder name differing only in case..
    Any suggestions?

    Unfortunately, that is not a viable solution, as I am tring to convert a case sensitive volume to a non-case sensitive volume.
    What I would like is a method to copy files and when a duplicate occurs it asks me what to do like rename the second duplicate. However this problem is now moot, as I painstakingly renamed each offending file/folder as each error occured, and then restarted the copy.
    While the question is not answered, I am marking it as such because I am now past the problem.
    Thanks for your response.

  • Making search non case sensitive

    Hi,
    I have implemented a search help which I have copied from standard help ‘PREM’. I have created a Database view, taking that View I have created an Elementary search help and I have assign the elementary search help in the collective search help ‘ZPREM’ which is copied from ‘PREM’.  In the search help I have two fields (NACHN, VORNA), which are case sensitive fields.
    How to make it Non Case Sensitive?
    Regards,
    Jitendra

    Hi ,
    without checking  "Lower Case" ,  any  case(upper/lower)  u are entering will be  converted to upper case internally and the respective data will be displayed .
    With checking the lower case check box in domain  , u will get the  exact  case  data  in which u have entered .
    but if ur requirement  is like ,   if u enter   a*  in VORNA  FIELD  and it should display
    a*
    A*     - ie. all the names starting with the both 'a'  or  'A'   ,   then
    You can go for Search Help Exit . Inside the function module catch the  entered  name and select  required records from DB as per ur requirement and insert  result  into  RECORD_TAB[]  internal table  , having  standard search help result  list .
    Regards
    DJ

  • BI BEx & WAD F4 Search: How to search non-case sensitive

    Dear Colleagues,
    is there meanwhile a better and comfortable solution for this problem, or have'nt changed anything since "How to... Search non-case sensitive" paper from 2003.
    Thanks and regards,
    Wolfgang
    Edited by: Wolfgang Taag on Aug 4, 2008 1:40 PM

    Hi Gerhard,
    I quote from OSS note 914303 :
    The BI search requires the TREX Server as of 7.0 Support Package 06 or higher. If the search engine is not fully installed, you can still use the standard search that the system carries out in the database. However, as a result, the search takes longer, <u>it is case-sensitive</u> and it does not support the search for attributes.
    Hope this helps,
    Best regards,
    Olav

  • Can i make the database passwords non case-sensitive ??

    Can i make the database passwords non case-sensitive ??

    Yes: set instance parameter SEC_CASE_SENSITIVE_LOGON to FALSE ( http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/initparams220.htm#I1010299).

  • How to ... Search non-case sensitive?

    Hello,
    prior to SAP NetWeaver 2004s we implemented the How to Guide "How to ... Search non-case sensitive" in SAP BW 3.5.
    This solution is no longer valid in BI 7.
    Does anybody know how to implement a non-case sensitive search in SAP NetWeaver 2004s BI?
    Regards,
    Gerhard

    Hi Gerhard,
    I quote from OSS note 914303 :
    The BI search requires the TREX Server as of 7.0 Support Package 06 or higher. If the search engine is not fully installed, you can still use the standard search that the system carries out in the database. However, as a result, the search takes longer, <u>it is case-sensitive</u> and it does not support the search for attributes.
    Hope this helps,
    Best regards,
    Olav

  • Would like for URLs to be non-case sensitive

    How can Contribute 6.5 make URLs to be non-case sensitive?

    What do you mean exactly? What are you trying to accomplish?

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

  • CS5.5 Master Collection on Case-Sensitive File System

    Hello,
    The first thing I'll say is that I already know it's not possible to install on a case-sensitive file system.
    So, on to my question.  I have been tasked to find out a way to get this installed on our 30-35 Macs with case-sensitive file systems (required for other courses/tasks, so not an option to format.)  I was trying to think of a work-around that would let me install and use the CS5.5 Master Collection, but have not been successful yet.  Please note, I am not looking for a hack or extensive renaming of a bunch of files or other half-solutions I've found.
    Basically, what I was wondering is, if I go into Disk Utility and create a 35GB "Disk Image", mount that, and then try to install, why doesn't that work?  I mean, I am technically trying to install to a case-insensitive file system at that point, but CS5.5 still pops up with an error.  Has anyone gotten this type of solution to work, or any other for that matter?  Luckily my college hasn't bought the licenses for all these systems yet, but when a solution is found, they're jumping on it right away.  The main reason I don't want a "hacky" solution is that being deployed on 30-35 systems, this has to be a simple solution, not something that takes hours per system.
    Any insight is greatly appreciated.
    Jeffrey Simmons

    Thank you for the information, I had a hunch it was installing stuff elsewhere too, but wasn't 100% sure.  As for the problem, I ended up just converting to a case-insensitive boot partition.  To others who may want to do this, I used iPartition without a problem.  The only catch is, you can't just run it from the OS drive, you either have to burn a iPartition Boot DVD (requires you have your OS dvd as well), or do what I did and just install OSX to an external drive, install iPartition, then convert the file system on the regular OS drive.  A bit of a hassle, but you don't have to format your system. 
    CS5.5 Master Collection then installed fine, with no problems.  Unfortunately, Photoshop keeps repeatedly crashing.  It's fine for hours, then crashes 4+ times within an hour.  Repeats this over and over unfortunately.  Adobe support hasn't been helpful at all, so I'm just going to return this software and continue using Gimp.  It has always done everything I wanted, but I wanted the "name brand" software.  In the end, it's not worth the hassle, and definitely not worth losing my work over and over, so back to the store it goes.  Thanks again for taking the time to help out though.
    Jeffrey Simmons

  • CS4 and Case Sensitive File Systems

    Does anyone know if CS4 will support case sensitive file systems?

    While I do wish all software companies including Apple completely
    supported the case-sensitive file system. Many don't. I cannot pull up
    an article, but I remember reading that Apple only recommended the use
    of the case-sensitive file system for OS X server and if memory serves
    even for that it only recommended it for the attached hard drives.
    We can lament the lack of support but if you really want to change the
    status quo for Adobe products then the only useful way to do so is:
    ...Mike

  • ColdFusion Builder with case sensitive file system on Mac?

    Hi there,
    I tried to install CF Builder on my MacBook Pro (Intel), OS-X 10.5.7 with case sensitive file system. Installation went smoothly, but, when I try to launch CF Builder, I get an error saying that the "architecture is not supported". Is it just nor possible to have CF Builder on a case sensitive fs?
    Thank you
    Chris

    I am having the same issue and logged in here to see what the deal is.
    After I installed cfbuilder my flex builder crapped out as well.
    The cfbuilder logs (which were conveniently scattered throughout my system for no reason) report that I am running:
    java.vm.version               == 1.5.0_19-137
    But if I run "java -version" in terminal I get:
    daves-macbook-pro-2:~ Dave$ java -version
    java version "1.6.0_13"
    Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
    Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)
    "Is JDK 1.5 available in the system"
    Definale "available"...
    Does it exist? yes
    Is it set to default? no

  • What is HFS case sensitive file system

    What is HFS case sensitive file system?

    FlowerChick,
    a HFS case-sensitive filesystem would allow you to have files that differ only by case in the same folder; for example, you could have different files named “FlowerChick” and “flowerchick” in the same folder. On a case-insensitive filesystem, that wouldn’t be allowed.

  • Time Machine suddenly refuses to backup to non case-sensitive drive

    There is another thread on this which for some reason is marked as resolved, so I thought I'd post a new thread. Suddenly after months of no complaints I get the following error:
    *+Time Machine Error+*
    +A volume you are backing up is case-sensitive, but the backup volume is not.+
    +To Select a different backup volume, or to choose not to back up the case-sensitive volume, open the System Preferences and choose Time Machine.+
    The only thing I've changed is that yesterday I ran Software Update. Unfortunately I can't remember exactly what was updated, but I suspect Quicktime was one of them since I needed to reboot. So now I'm at 7.4.5 in Quicktime.
    Time Machine refuses to backup my drives now complaining about the case sensitive filesystem. The thing is, *NONE of my drives are case sensitive.* Looking at the Change Drive window in Time Machine, I see that most of the drives on my system say "reforat required" if I am to use them with Time Machine. All drives on my system are *Mac OS Extended (Journaled)*. The fact that some drives are not requiring a reformat and some are, even though they all are the same format is quite puzzling.
    I took a spare drive and allowed Time Machine to reformat it for it's use. It has now reformatted the drive as Mac OS Extended (Journaled, Case-Sensitive).
    Can anyone shed any light as to why TM would suddenly require my backup drive to be case sensitive when none of my drives are?
    This make no sense...
    -K

    Ok - Running Disk Utility Verify on both the system disk and the TM disk seems to have magically stopped this error. Note that Disk Utility didn't actually find or fix any problems with either disk. The problem just went away....
    It doesn't make any sense.
    -K

Maybe you are looking for

  • Image adjustments variables is missing in my PS CS5 Extended

    Hi, I'm working with PS CS5 extended, and I'm missing the option image>adjustments>variables. According to the information on the internet it should be there at the very same place that I'm used to finding it, but it seems to be missing at my version

  • Missing the entry "BI Document Repository" in KM

    Hi, I installed an nw2004s java with ep7.0. Later I deployed the components for BI via JSPM and patched all to the sp5. I want to integrate BI into the Portal to run Bex-Reports on Portal. At step "Install Repository-Manager for BI-Documents and BI-M

  • Java Add-in System Copy - same Java Support Package levels ?

    Hi, I'm looking at performing a standard SAP Netweaver 04 SAP Web Application Server system "refresh" procedure. I plan to copy the production system ( SAP WAS 640 ABAP+Java addin )to an already installed QA system that was installed originally exact

  • Unicode literal for '\' (Backslash)

    Hi there! I've got a problem with the Java compiler. I think he is cheating me! Just the simple command: System.out.println('\u005c'); causes the error: Import.java:171: unclosed character literal System.out.println('\u005c'); ^ The unicode character

  • Javascript-actionscript problems

    I am trying to set up a test app to get a grip on communications between javascript and action script. I have successfully registered a call back function with action script to be called by javascript, But a second registered function is not getting