Problem with USB Flash Memory (FAT32)
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, I need help using my USB flash memory using both on Mac and Windows.
To use on both Mac and Win, I formatted my USB flash memory drive (I call it USB from now on) with FAT on Disc Utility. I believe Disc Utility formats as FAT32.
I named the USB very simple way. I named it BLUE to avoid any mess caused by file names.
That's good is't it? It should work on both Mac and Windows? Right?
But it doesn't.
I have tried with 3 USBs I have. (2x 8GB and 1x 16GB) They are all less than a year old, and made by SanDisc and TDK, good manufactures. So it's not problem of actual USB, it's problem caused by my OS X I think.
When I plugged USB to Windows, it says I have to format the USB to use on Windows.
The same error occurs both Vista and XP.
So I decided to format as FAT on Windows but I could not format correctly. Whatever I do, Windows formats only 200MB out of 8GB or 16GB of the USB. And back to Mac again, I pugged these USB formatted on Windows and they comes up as 2 partitioned drive, one formatted on Mac and the other formatted on Win (200MB)
Does anybody have any idea about this?
I'M NOT SURE but it seems like this thing happened after I upgraded my OS X from 10.6.1 to 10.6.2.
Thanks in advance.
15 replies
Sign in or join Beachball Help to reply.
- 0
Kappy ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It's not just formatting. You also must partition the device correctly. Try the following:
1. Open Disk Utility.
2. Select the device from the list (the entry with the mfgr.'s ID) then click on the Partition tab in the DU main window.
3. Select One partition from the Partition drop down menu.
4. Click on the Options button and select MBR then click on the OK button.
5. Set the Format type to MSDOS and change the name to BLUE.
6. Click on the Partition button.Test the device on each platform.
- 0
SHINFRANK ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Kappy thanks for your replay.
I tried the post you wrote me, and it still doesn't work.
I've got another error that I forgot to write in previous post.I cannot copy folders from Mac to USB.
Error occurs. Error says,
The Finder can't complete the operation because some data in 'folder name" can't be read or written.
(Error code -36)
But I can still create a new folder or copy files(such as PDF, JPG etc), but not copying folders. (By the way the USB is formatted as FAT. Also everything works fine when USB is formatted as Mac partition systems such as Mac OS Extended.) - 0
Kappy ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
You may actually have a corrupted file in the folder or a file/folder with a name containing characters that are illegal on a FAT32 filesystem or a file/folder name that's too long, or a file that's larger than 2 GBs. All of these can generate the -36 error.
- 0
SHINFRANK ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
@Kappy
I thought same thing, but all the files and folders I tired to move from Mac worked fine on the previous FAT32 USB I had. Also I can copy them one by one, but not as a folder.
Names are correct, files are no bigger than 1GB. Everything is FAT32 standard.
Thanks
- 0
Kappy ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can only suggest trying a Google search on error 36 to see if you can find additional information. The error often occurs because of one or more of the reasons i mentioned previously. And, it does not seem uncommon that the files can be copied individually but not a folder of files. I don't know why this happens unless it's a problem with the way in which the drive has been prepared.
I usually prep my USB flash drives initially for OS X as follows:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the
Partition tab in the DU main window.3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the
Options button, set the partition scheme to GUID, then click on the
OK button. Click on the
Partition button and wait until the process has completed.4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the
Erase tab in the DU main window.5. Set the format type to Mac OS Extended (Journaled.) Click on the
Options button, check the button for Zero Data and click on
OK to return to the Erase window.6. Click on the
Erase button. The format process can take up to several hours depending upon the drive size.Then in the Erase panel of DU select MSDOS from the Format drop down menu and click on the Erase button. The device should work on both platforms if the Windows machine is running Vista or Win7. Not sure about XP. if it's running XP you may need to partition the device using MBR instead of GUID.
- 0
SHINFRANK ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have done what you have written and it didn't work on Vista. I tried bothMBR and GUID.
But I did same thing (format) on Mac OS X which I booted from Leopard Installation DVD and the I could open FAT32 USB. Yes it worked.
I could see the files I copied from Vista on Mac.But I'm still having trouble copying folders from Mac to the FAT32 USB.
Also cannot format USB on Disc Utility on Mac OS X on internal hard drive.It seems like my Mac OS X has problem with Finder and Disc Utility...
- 0
Kappy ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm sorry, but I don't have a fix for you. It's possible that the problem is a defective OS X system, but to test that would require erasing the drive and reinstalling from scratch.
I would suggest you search the forums for "error 36" since this issue has been raised many times. You may find a solution in another thread.
Message was edited by: Kappy
- 0
SHINFRANK ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Kappy
One more thing I would like to ask you. You might know.
Will it work if I make a copy of my data using Time Machine (TM) now, then clean the hard drive, install Mac OS X from scratch from the DVD, then update to 10.6.2 then put data back from the TM?If there is chance solving the problem by doing this I would try, but if the TM puts same PROBLEM data as now into the new OS it would not solve the problem I have at the moment.
Thanks again
- 0
Dick Dastardly ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Have you got a U3 partition on the pen drive? See http://u3.com/support/default.aspx#CQ3 for information on how to delete the partition. Once deleted you should be able to format it FAT 32 without any problems.
- 0
Txau-me ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
In my opinion the problem you describe is a bug with Snow Leopard. I have been through exactly the same problems with two different USB pendrives (A 2Gb TDK and a 4Gb Kingston), both brand new.
The problem vanished when I plugged them into another mac that had Leopard 10.5.8 as operating system. I can format it as DOS(FAT) I can copy all folders inside withouth a glitch and they are recognized by PCs.
Conclusion, either someone can come with a walkaround or we'll have to wait for 10.6.3
Regards
- 0
NickS ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm having the exact same problems too. It started with an OCZ Rally2 4GB flash drive giving 2 errors: "The operation can't be completed because an item with the name "Thunderbird" already exists" (even though it wasn't already on the drive). Also error code -36.
Reformatted in FAT32, same problem, tried another identical drive, same problem again. It has also started happening with my Western Digital 250GB USB hard drive formatted in FAT32. In fact, it's happening with every FAT32 drive I try now. So I've had to temporarily format the flash drive with 2 partitions in Mac Journaled and FAT32. No problems at all using the Mac formatted partition.
- 0
SHINFRANK ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hey I just found way to fix it.
I downloaded 10.6.2 update from Apple website manually and re-updated my Mac again.
And it just works fine.Give it a try.
You don't have to go back to 10.6.1. Just download the file not, and re-update.
- 0
Stalflare ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi everybody, there is a solution to the copy problem, but not to the formatting problem...
The solution is to run a TERMINAL session, go to the folder that contains the items (or the folders) that one wants to copy and type:
dot_clean nameofdir/
or
dot_clean namefile.extensionThe problems seems to be with the hidden files that Mac Os creates and with the fact that they are hidden. after this step you can copy no problem.
As for the formatting thing, it's an issue that I also have and really do not know where to bang my head as FAT 32 is needed to R/W in Windows and Mac..
- 0
Theodorre Micceri ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Yes - I have been having the same problem - Unfortunately, as a Professional Statistician, I am forced to use Windows for SAS.
I have been unable to copy Folders to my Fat32 USB transfer drives, although I can copy the contents of the folders easily once the folders are created on the drive.
This apparently is a bug in Snow Leopard.
Does anyone know if 10.6.3 will solve it?
- 0
uhu ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have exactly the same problem (error -36 while copying a folder or folders) with a new SanDisk USB-memorystick. Even worse it can happen that when copying files or ejecting the drive the Finder freezes!
I never have seen such a dramatic behaviour of the finder for a long time. Unfortunately all my Macs (3) are upgraded to SL and I can't test this issue with another OS version. And I need the USB-drive as FAT32 because it is for transfer files between Windows-PCs and Macs.
I really hope that this will be fixed with 10.6.3