When copying a large amount of files, if one file ever throws it off, the copying just stops. ends. thats it. Not only do you nnot know where to locate the problem file, but you also have no idea how much copying was done, what the last file that was copied or ANYTHING! It just gives you an error message and when you click ok, it stops. Worst thing about Mac ever! This one specific issue has given me so many problems over the years with mac. Does anyone know any way around this? Is there a unix command of some sort?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The one thing about OS X that SUCKS!
- Thread starter reykjavik
- Start date
- Sort by reaction score
Well does windows does it differently?
anyways, unix command is cp
cp /path/you/want/*.mov .
will copy all .mov files in the current directory keeping same name.
anyways, unix command is cp
cp /path/you/want/*.mov .
will copy all .mov files in the current directory keeping same name.
abhishekit said:
I do NOT recommend using cp, as it will obliterate any resource forks you have, only use cp if you KNOW that your file(s) don't have resource forks.
You can think of a file in OS X as a sandwich (Sort of)...reykjavik said:
Data Fork
------------- = File
Resource Fork
The resource fork will contain such things as icons and resource and creator codes. Since this is a Mac only thing, the Unix utilities that come with this do not respect the information contained within the resource fork (Although this should be a non-issue in Tiger according to Apple). It's kind of like making the duplicate of a sandwich and forgetting to add the mayo.
I haven't had that problem, everytime I copy files over and one is corrupt, it says "Continue...?" and I click OK and then it copies the other files over.
If you have lots of files that you need to copy, you could always use rsync. It seems to be much more reliable than the normal methods. It's slightly more complicated to use though.
Search for "Rsync X" on Versiontracker for a nice GUI.
(Disclamer: I don't know how rsync deal with resource forks. I've only used it to copy lots and lots of music to and from my FAT32 formatted portable player, where that is of no importance).
Search for "Rsync X" on Versiontracker for a nice GUI.
(Disclamer: I don't know how rsync deal with resource forks. I've only used it to copy lots and lots of music to and from my FAT32 formatted portable player, where that is of no importance).
On the developer site for Rsync X it says "Resource fork sent only when needed." So I assume that if it needs it then it will send it.
http://archive.macosxlabs.org/rsyncx/rsyncx.html#history
http://archive.macosxlabs.org/rsyncx/rsyncx.html#history
reykjavik said:
If one of your files (or target disk) is corrupt, then no amount of Finder or command line copying is going to function properly.
I don't know if you're comparing this to Windows, but...
It's not really that simple on Windows. The only easy way to do this is xcopy, which is command-line, and requires knowledge of the switches. And corrupt files can sometimes hang xcopy too, so I'm not sure what you're complaining about. AFAIK, copying groups of files when one is corrupted is always risky and usually problematic...
It's not really that simple on Windows. The only easy way to do this is xcopy, which is command-line, and requires knowledge of the switches. And corrupt files can sometimes hang xcopy too, so I'm not sure what you're complaining about. AFAIK, copying groups of files when one is corrupted is always risky and usually problematic...