Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Aovid copying problems on external FireWire hard drives System
I have an iMac running OS X, and an external Western Digital 120 Gbyte FireWire hard drive. I got the 120 gig instead of the 200 so I could share it between my PC and iMac (there's a 137 gig limit in that mode), particularly important when I was moving my flies to the iMac.

While the FW HD worked well for the move, I had major problems using it for backup of the iMac's files. When I dragged the folder to be copied to the external HD it would start, but then hit a problem with a file and stop the rest of the copy with an error code –36 or –50. The folders are in my home directory, so I have all the necessary permissions. This problem made the copy operation useless on all but the simplest folders. Using Tri-Backup helped in that it continued to copy other files after the problem occurred, but it still had errors on some files and could not copy them.

Thanks to some help from Alan Zisman (a poster on some Mac newsgroups), I've solved my problem, which had also plagued him earlier. Since I couldn't find the solution in a google search or in Apple's Knowledge Base I am posting it with Alan's permission. The problem only occurs when the FW HD is formatted for DOS/Windows, and disappears when it is reformatted as an OS X Extended volume. The problem is not unique to WD HD's, since Alan's is an Acom Data.

So you seem to have a choice: ease of transferring files from a PC to a Mac (but not the reverse) OR ease of use (really ability to use) with the Mac. Alan gets some of both by using the Mac formatting and making it a shared volume on his local network. But I've found that large file transfers over my local network are too slow to suit my taste, which is why I wanted to use the external drive for that purpose. While not a complete solution, it certainly helps to know the source of the problem and what you can and cannot do. It would be nice if Apple would fix the problem in a later update of the OS.

[robg adds: Another potential solution is listed in the Create HFS+ and FAT32 partitions on one external drive hint -- this explains how to have a bit of the best of both, though it requires use of the Terminal.]
    •    
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (1 vote cast)
 
[16,414 views]  

Aovid copying problems on external FireWire hard drives | 8 comments | Create New Account
Click here to return to the 'Aovid copying problems on external FireWire hard drives' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Aovid copying problems on external FireWire hard drives
Authored by: Fofer on Aug 07, '03 10:42:35AM

So, once it's formatted for Mac (Mac OS Extended) what do you use to mount the HD on a Windows XP desktop? That part was left out from the tip.

I just installed Mediafour's MacDrive 5 and it seems to do the job well. I'm able to move an external 160 GB drive (with a FW/USB 2 case) between my Mac and my PC without any problems.



[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: mclbruce on Aug 07, '03 10:58:49AM

DataViz makes a product called MacOpener that should allow Windows machines to read Mac formatted firewire disks. I haven't used it, but a business associate uses an older version and likes it:

http://www.dataviz.com/products/macopener/index.html

Anotherr Windows based Mac connectivity product worth looking into is PC MacLAN Connect by Miramar Systems. It comes with MacOpener:

http://www.miramar.com/MiramarWeb.nsf/web/prod_nav_nt_index



[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: af3556 on Aug 07, '03 10:59:21AM

I suspect the problem you have is due to the different ideas of valid file names for HFS+ and VFAT32/NTFS. UFS+ is pretty forgiving and allows any (7bit?) character in filenames except '/' (note the Finder hides ':' chars as '/', but this is for the GUI only); VFAT doesn't allow any of the following: '\/:*?"<>|'.

Any file with one or more of these invalid characters in its filename will fail to be copied to a VFAT32 or NTFS partition.

Also, I believe as UFS+ allows wide character filenames (i.e. accents, etc), and VFAT/NTFS does not, these will also cause an error.

As you noted, the Finder bails on the first error with a very unhelpful error code.

To find the culprit file(s), try the following from the command line (all on one line):
find . | grep -v "^[]\/.0-9ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz=\;_\#\+\(\) \'\&,\$\![-]*$"

(the grep character classes A-Za-z can't be used as they seem to include accented chars?)



[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: wlinder on Aug 07, '03 02:55:53PM

Actually, in our testing here at Iomega, we have found that when a file transfer chokes on an MSDOS volume, it is usually a problem with an Icon resource. Try this - look in the folder/volume you're copying and see if you have a folder with a special icon. Delete or move that icon and the folder/volume will copy.

Also, instead of partitioning the volume, try sharing it from the Windows machine and the 127GB limitation will be ignored.

Enjoy!

Wayne Linder



[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: claustrophonic on Jan 19, '04 09:58:43AM
Delete or move that icon...

How does one do this exactly? I have folders and folders of files that probably have icon info inside them somewhere... one in particular I have to click on "show package contents" then there are hundreds of files inside.



Thanks.

[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: reisschuessel on Aug 07, '03 01:17:20PM

A useful solution (to me) is to create a disk-image on a DOS formatted disc by using disc copy app. With this method you avoid error messages concerning illegal filenames. I use this method for creating backups of my mac-files on a fat32 fw-hdd.

reisschuessel



[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: gdsimms on Aug 07, '03 02:37:59PM

I do the reverse of this for transferring PalmOS data between USB-mounted Memory Sticks. I keep a small DOS formatted read/write .dmg around on my mac and I use it for intermediate storage of the files. There is something about the type and creator codes for PalmOS .prc and.pdb files that gets lost on HFS+ and UFS partitions.

Gosh, is this a hint in itself?



[ Reply to This | # ]
Aovid copying problems on external FireWire hard drives
Authored by: Potemkin on Jan 19, '04 04:34:40PM

For total portability, a simple solution is to format the Firewire drive as FAT32. I have one enclosure that is used to change files with Windows computers in many places where I cannot install any third party software.



[ Reply to This | # ]