![]() ![]() when the target is FAT32 and it has too many small files on it. My guess is: something suboptimal about the way the program copies the files. I just waited it out and did spot checks to make sure the files were readable, and I think it's OK, just slow. It compared the two directories quickly, but then was glacially slow doing the actual file copies themselves-took an hour to copy about 1 gig. ![]() The drive currently has about 12 gig on it. I used a 16 gig thumb drive to back up all my scanned documents, using a file synchronizing utility. There are likely to be minor glitches on both systems due to its not being the "preferred" format for either.Īctually I may have run just such a glitch yesterday. ![]() The disadvantage of this format is that there are some things you can't do, such as make the partition bootable on a Mac, and there are minor issues, mostly cosmetic, such as the resource forks of Mac files being visible on a PC. I haven't used exFAT yet myself but it should be OK with recent versions of Mac OS X and with Windows 7 or later. FAT32 is reasonably compatible with Mac OS X and a very wide range of Windows OS versions, Windows 95 through Windows 8 I believe. ![]() Should I do NTFS for the Windows partition?Yes.Īnother option is to use FAT32 or exFAT. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |