 |
 |
Cannot copy to folder: same name in caps-lock gives error?
|
|
|
|
|
Mac Elite
Join Date: Feb 2001
Location: France
Status:
Offline
|
|
Maybe this is a known bug or error, or even one which is logical but I never saw it.
For what ever reason I have a folder in my Documents folder which has the name WORK.
I made a new folder on the desktop named Work. I then wanted to copy it to my documents folder, just to find out it didn't ask for replacement or cancel, but instead gave the following:
Sorry, the opration could not be completedbecause an unexpected error occurred (Error code -8065)
It looks very OS before X-ish, but besides that it doesn't really give a clue of what is happening.
Silly.
Sorry if this is mentioned before or known.
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Aug 2005
Location: Delray Beach, FL
Status:
Offline
|
|
HFS+ in OS X thinks WORK and Work are the same file, and you can't copy a file onto itself. HFS+ is not case sensitive.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2001
Location: France
Status:
Offline
|
|
Originally Posted by Barry
HFS+ in OS X thinks WORK and Work are the same file, and you can't copy a file onto itself. HFS+ is not case sensitive.
I understand that. Now try to copy the folder (or file) with the same name, it does give you a canccel <-> replace option, so at least you know what you are dealing with.
What I try to say is that actually the OS makes a difference between capitals or not. That in itself is strange. For lesser gods, this makes no sense 
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Feb 2005
Location: 888500128
Status:
Offline
|
|
It's case-aware and case-preserving, but not case-sensitive.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2001
Location: France
Status:
Offline
|
|
Originally Posted by analogika
It's case-aware and case-preserving, but not case-sensitive.
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Aug 2005
Location: Delray Beach, FL
Status:
Offline
|
|
its not the OS, but the hard disk format. The common format is HFS+(journaled). IF you format the drive as a UFS (Unix File System) drive instead, you could do this with OS X (work, Work, WOrk, WORk,WORK would all be allowed in the same folder)
|
|
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status:
Offline
|
|
Yes, I can reproduce the issue.
If you try to copy onto an object with the same name and the same capitalization, then it asks for replacement.
If you try to copy onto an object with the same name and different capitalization it gives you the error message. It should ask for replacement here too (since HFS+ is not case-sensitive).
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2001
Location: France
Status:
Offline
|
|
OK, I understand the differences. Still, I think it's a bad way of telling the user this can't be done.
|
|
|
| |
|
|
|
|
|
|
|
Moderator  Join Date: May 2001
Location: Hilbert space
Status:
Online
|
|
BTW, contrary to what many of you think, HFS+ is case-sensitive if you tell it to be. If you use OS X Server, I think Panther was the first to introduce that. If you run Tiger, open Disk Utility and check it out 
However, most installations are HFS+ case-preserving.
|
|
I don't suffer from insanity, I enjoy every minute of it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
