Is the Adobe ID (email) case-sensitive?

I recently borrowed a book from my library, downloaded it with Adobe Digital Editions (and was able to open it on the PC) and transferred it to my (Adobe authorized) Kobo Mini reader. Unfortunately the reader refused to open the book because “it is not currently authorized for use with your Adobe ID”. I reset the reader, signed in with my Kobo account, authorized it again with Adobe Digital Editions, but got the same error.
I use one and the same email address as my account ID for Adobe and Kobo but noticed that the one for Kobo is spelled with lowercase letters while the one for Adobe has its first letter capitalized. Is this a problem?
I tried changing my Adobe ID to lowercase on the Abobe's website but got error “That Adobe ID is not available. Please try another address.”
This is the first DRM book I am trying to access on my Kobo.
Thank you.

I don't think that the Kobo account is relevant at all.
Also, email address capitalization is usually ignored; though maybe there is some bit of ADE (Adobe Digital Editions) or the Kobo that does not ignore it.
When you say my (Adobe authorized) Kobo Mini reader I assume you mean that you authorized it using 'Authorize Device' from ADE?
It might be worth trying ADE1.7.2, though I am not at all sure it will help.
ADE 2.0 has some peculiar bugs: for example it won't work at all with most Sony eReaders for reading library books.
Yours is clearly a little better than that, in that it works enough to get the book to the eReader, which is why I am a little pessimistic.
However, using 1.7.2 has proved a success for many different issues with 2.0 on this forum, so worth a go.
There are lots of bugs in ADE2.0 (and 2.0.1). Try replacing ADE2.0 with the older but more reliable v1.7.2.
(You can have them both installed at once if you like.)
Version 1.7.2, it is a little difficult to find, available on Adobe site for Windows and for Mac.
http://helpx.adobe.com/digital-editions/kb/cant-install-digital-editions.html
The forum software is sometimes corrupting the link above. There shouldn't be a blank in 'editio ns.html'. The following redirects to the same page: http://tinyurl.com/diged172
Some people have found ADE trying to upgrade automatically.
It appears (not 100% sure) that if you install ADE2.0 as a new install (not as an upgrade) that your 1.7.2 will continue to run.
Probably best to say no if 2.0.x installation asks if you want to migrate your library.

Similar Messages

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

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 do I change the Mac OS Extended (Case-sensitive, Journaled) Format of my Verbatim External Hard Drive

Good evening.
I have a Verbatim External Hard Drive, currently being used for my Time Machine back-up on my MacBook (Running Mac OS X Version 10.6.8).
I also frequently use a normal Windows laptop (Normal 32-bit OS).
The Hard Drive was formatted to Mac OS Extended (Case-sensitive, Journaled) in order for the MacBook to do the Time Machine back-up.
How do I change the fromat of the Hard Drive, as i do not need the Time Machine back-up to be done on the Hard Drive anymore, and I NEED to use the external in both PC's.
Your assistance will be greatly apreciated.

Open Disk Utility, select the external hard drive, select erase, and format it as FAT32. You'll be able to use it with both Mac and Windows.

The query screens are case sensitive I want to remove the case sensitivity

The current query screens are case sensitive ,I want to remove the case sensitivity is there a setting somewhere to remove this or how else can this be done.
Example:In the restrict value range of the query screen.If we give for a particular field anything in capital letters/small it should take.
Please let me know ASAP
Thanks

Hi pavan,
generally case sensivity is related to InfoObject Master Data.
Take a look via Tcode RSD1 to the master data of your InfoObject and check in first screen if flag for capitol letters has been marked.
If this is the situation it is a problem, because MAster Data in cube have been saved as different if are written like "Letter" or "LETTER".
Ciao.
Riccardo.
Message was edited by:
Riccardo Venturini

Tip: the iWeb server is case sensitive

the server is case sensitive.
<web.mac.com/yourname/iWeb> will work but
<web.mac.com/yourname/iweb> will return the 404 missing page error.
I've filled out a feedback form asking that Apple make the server non-sensitive. others might want to do the same to make accessing the iWeb server more user friendly.

Actually this is the case on the whole Internet.
http://www.apple.com/ilife/
and
http://www.apple.com/iLife/
Those two URL's are refferencing two different pages. If you go visit the second one you will also get a Page not Found error. The reason is because ilife and iLife might be two different pages / folders on the apple website.
In general :
Not Case Sensitive Case Sensitive
http://www.apple.com/ilife/
The part which indicates the web server adress ( http;//www.myisp.com ) isn't case sensitive. Anything which comes behind that IS case sensitive.
There is nothing Apple will be able to do about that, because that is how the whole Web World Works
Regards,
Stefaan

Renaming filenames and case-sensitivity: a race condition in the OS?

There appears to be a curious set of circumstances where the OS doesn't allow you to rename a file where the only changes are case-sensitive. For example, "foo.JPG" to "foo.jpg". You can see an example using the command-shell "tcsh". Start this shell (type "tcsh" at any command prompt), and then type:
% touch foo.JPG
% mv foo.JPG foo.jpg
overwrite foo.jpg? (y/n [n])
Now, you may think it's no problem because few people use tcsh, but the problem is more systemic that should be addressed because I'm finding the problem at a programming level as well. The simplistic tcsh example illustrates the problem: the internals of tcsh call the OS-layer library function rename(2) to move or rename a file. However, something in the OS that reports back that the new filename exists (even though it doesn't) Because it sees foo.JPG, and it doesn't differentiate letter case, it thinks foo.jpg exists, so it returns an error to the calling program. In this case, it's tcsh, which is what prompts the user to overwrite. It doesn't matter what you answer, the result is the same. If you say yesthe OS doesn't see them as different, so it doesn't do anything.
If you're a programmer, you can see this happen for yourself by writing a small program that does the same thing:
#!/usr/bin/perl
if (!rename "foo.JPG", "foo.jpg") {
print "Error: $!\n";
This simple perl script just calls the rename(2) library call, which is part of the OS.
What I don't understand is why this error happens, when, and how to get around it. Obviously, other programs that rename files don't have this problem. The default shell, bash, doesn't have a problem either--even though tcsh (also a similar command-line shell) does. In fact, most programs don't have this problem. But as a programmer, I'm not sure what I should be doing. This exact same perl script (and correlating C programs) work perfectly well on all other unix platforms I've tried.
G5 Mac OS X (10.4.5)

It's not at the os layer, it's at the filesystem
layer. The filesystem you have is not case sensitive.
well, the filesystem is part of the operating system, although it's clearly only one component of it. In fact, one of the primary defining characteristics of unix is how the filesystem works, albeit there are variations of implementation. But this is a nit=picking point.
As to the issue of whether the filesystem truly is case-insensitive, that isn't so clear. I can rename a file from foo.JPG to foo.jpg easily in the Finder (just click and edit a file to change it's name from upper to lower, or mixed), and the new name you give it DOES change. similarly, I can do this with virtually any other app that has a file-finder style dialog box. Why I can't do it with the shell (or at an API level) is the real mystery, and there is no doc on the subject that I'm aware of. Clearly, the OS is preserving the change somewhere, somehow. the question is, who's doing it? (and if it's not part of the filesystem, why?)
It could be that some other layer is sitting on top of the filesystem that is overseeing such actions, and is preserving the case of the filenames, but this is such a huge waste of time and work, all for a "feature" whose value is still as yet unclear to me.
If it is, as you say, that "my version" of the filesystem happens to be case-insensitive, I'd love to know where that came from, and what the rationale was behind it. And, of course, how to get some version of the filesystem that doesn't have this feature. I've been working with unix systems at every layer since 1983, and have never run into such a thing before.
dan

My Time Machine backup keeps failing. I get a message the "Volume has the wrong case sensitivity for a backup". Please advise.

My Time Machine backup keeps failing. I get a message the "Volume has the wrong case sensitivity for a backup". Please advise.
Thanks, Howard

You can change the case sensitivity of the sparsebundle.. but I really doubt the error is real.
See A8 here.
http://pondini.org/TM/Troubleshooting.html
The sparsebundle should have case sensitivity turned on.
I cannot even fathom how it could have changed.
Let me recommend before you start fooling around with the sparsebundle.
Do a full network start.
Power everything off.. start up modem.. wait 2min.. power up the TC.. wait 2min.. power up any other network gear like switches.. wait..
Now power up the computer and try it.
If the error is the same.. I would do a factory reset of the TC.. give it all short names, no spaces and pure alphanumeric. Then reset TM .. see A4 in the same reference as above.. and do a verify of the backups.. A5 above and try the backup again..
No luck..
Then erase the TC and start over.. it is sometimes necessary as TM does get itself in a knot.

Create directory / object name must NOT be case sensitive

SQL Dev. 2.1 - the wizard, chosen from the left side navigator, submits a wrong create statement in which the object name becomes case-sensitive. This should not be so! Even if you write the new object name in small letters , the object name must end up in the data dictionary with capitals. kind regards Inger ([email protected])

Which wizard? If I use a create table wizard, for example, and enter the table in lower case, this is indeed stored in the DB as upper case, as you require.
Please provide more detail for your problem.
Sue

Problem with the Adobe Acrobat version 10.1.4 (Review Tracker)

Friends!:
I have a big problem, just a few days ago we installed the Adobe Acrobat version 10.1.4
The next version this is creating problems for the users, because normally we use the review (Track Review) to comment online, but this began to fail, because that is not saving posted by the users in the documents and is generating problems.
HELP PLEASE, THANKS
ps: We using the Windows XP
ps2: Sorry for my "bad" english, but im native from Southamerica
Regards!

I have a wild guess, that's all. Do you perhaps have the disk formatted as "case sensitive"?

Installing to a case-sensitive fs

When I did my original 10.4 install, I opted
for a case-sensitive boot disk. I come from a
UNX background, and am using UNIX utilities
from darwin ports and my own UNIX files in
a cvs tree. It seemed natural to use a case-
sensiticve fs, since I would be using a lot
of files ad applications that are case
sensitive.
Enter my girlfriend's graphics applications.
After fighting with Adobe CS2 for hours, I
cloned my data drive and re-partitioned it
to have a 50 GB case-insensitive partition,
just for applications. All was good with the
world again.
Enter the next of her applications, Macromedia
Flash Pro. One of the same two errors as
the Adobe suite was getting [ 1008:17, -4 in
thie case ]. Looks like Flash writes to /Users,
not just /Applications, so I think I am
getting case-sensitive issues again.
I attempted to symlink the dir onto my
case-sensitive drive, but the installer
did not recognized the symlink as a
directory and prompted me to delete it.
I've learned two things from this experience:
1. A case-sensitive boot drive is near-useless
for commercial applications.
2. The people who write Mac installers are
very, very poor progrsmmers. Cavalier
attitude towards case, refusal to handle
symlinks ... someone spent too much time in
the primitive world of OS 9.
OK, on to the question...
I've repaired permissions, googled the error code,
verified the hdd, even sampled the installed to find
out it errored out during a file read.
I am not going to clone my boot drive and reinstall
onto a case-insensitive partition.
Is there any sane way of fixing this? Maybe a
wrapper daemon for crippled programs that are
incapable of handling a case-sensitive fs?

heya,
Yeah, I was afraid of that. Kinda hoping there would be
some crazy kext hack like you'd find in the linux/bsd
world. Hmm, could be an interesting project actually,
a case-insensitizer with an application white-list.
Well, I got most everything installed after some
trickery. Had to symlink /Users/Shared into a
case-insensitive partition, which fooled the
installer long enough for it to crash later
on the example files, then changed it back to
a dir.
Kept the error dialog open and copied what had
managed to install, hit ok on the error, and
let it clean up after itself. I now have
incomplete but functional installations of
flash pro and dreamweaver.
Now trying to find a way to pull the files
out of macromedia's installer. Looks like a
typical archive; has the unusual header SVCT,
which I cannot find documentation for [yet],
and file(1) identifies it only as 'data'. If I
can find some docs describing the file format I'm
golden.
Hard not to knock the developers though. In the
month I've been using OS X apps, I've seen many
things that would be a firing offense where I
work

Why is CS6 not in my Account after Adobe upgrade email

I purchased Adobe CS6 under the cs 5.5 upgrade program. Adobe was slow to respond to my upgrade request and a case number was opened. On May 30 I received an email from the Adobe store stating that I should log into my account using my Adobe ID and locate my order under the My Orders page. It states that after I download CS6 my serial number will appear. Several days latter I received notification that my case was closed. CS6 still does not appear in my account as stated in the email. It has been 30 days waiting for Adobe to comply with the email to me but Adobe has done nothing. I would like to get the CS6 software that I purchased. How do I get Adobe to complete the terms of the purchase as outlined in the Adobe Store email to me?

Thanks for the response. I created another case number and was provided an alternative download location to access the serial number and file. All seems to be ok now. The Adobe Customer Service Rep stated the problem that I was having accessing the upgraded CS6 via download was a "known" problem. It seems to me that getting the software to people who buy it should be the first thing that Adobe would get right rather than providing incorrect download instructions to customers attempting to download the software. Excusing the problems caused for the customer as a "known problem" is really unacceptable for so basic a function; especially since this upgrade program from CS5.5 started over 2 1/2 months ago.

Bugs due to case sensitivity of objects?!

Hi,
When migrating from MSAccess 97 to Oracle
8i, it seems that there are many problems
during the migration due to case sensitivity
of Oracle objects. Specifically, the usage
of the double quoted is not always correct
resulting in JET/DAO 3011 messages. I dont
know in which part of the chain is the
problem though (Access, ODBC or Workbench).
Is it possible, using Workbench wizard to
create and reference all objects in a non-
case sensitive manner (tablespace,
tables ...) to avoid these problems.
If not, any suggestion will be welcome,
-Eric Giguere
[email protected]
null

If you use SSO, then the passwords are case sensitive. If you are not using SSO, then you may need to create table that contains case sensitive passwords and associate them to database passwords.

Still need help with case sensitive strings

Hello guy! Sorry to trouble you with the same problem again,
but i still need help!
"I am trying to create a scrypt that will compare a String
with an editable text that the user should type to match that
String. I was able to do that, but the problem is that is not case
sensitive, even with the adobe help telling me that strings are
case sensitive. Do you guys know how to make that comparison match
only if all the field has the right upper and lower case letters?
on exitframe
if field "t:texto1" = "Residencial Serra Verde"then
go to next
end if
end
|----> thats the one Im using!"
There were 2 replys but both of them didnt work, and the
second one even made the director crash, corrupting even previously
files that had nothing to do with the initial problem..
first solution given --
If you put each item that you are comparing into a list, it
magically
makes it case sensitive. Just put list brackets around each
item.
on exitframe
if [field "t:texto1"] = ["Residencial Serra Verde"] then
go to next
end if
end
Second solution given--
The = operator is not case-sensitive when used on strings,
but the < and > operators are case-sensitive.
So another way to do this is to check if the string is
neither greater than nor less than the target string:
vExpected = "Residencial Serra Verde"
vInput = field "t:texto 1"
if vExpected < vInput then
-- ignore
else if vExpected > vInput then
-- ignore
else
-- vExpected is a case-sensitive match for vInput
go next
end if
So any new solutions??
Thanks in advance!!
joao rsm

The first solution does in fact work and is probably the most
efficient way
of doing it. You can verify that it works by starting with a
new director
movie and adding a field named "t:texto1" into the cast with
the text
"Residencial Serra Verde" in the field. Next type the
following command in
the message window and press Enter
put [field "t:texto1"] = ["Residencial Serra Verde"]
You will see it return 1 which means True. Next, make the R
in the field
lower case and execute the command in the message window, it
will return 0
(true).
Now that you know this works, you need to dig deeper in your
code to find
what the problem is. Any more info you can supply?

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

Is the Adobe ID (email) case-sensitive?

Similar Messages

Maybe you are looking for