There are a few other dangers to be aware of. So don't move around Mac files on non-Mac file systems, right? It's not quite that simple. So say if you moved a Mac application to a Windows hard drive and then back again, it wouldn't open because the resource fork was stripped in the process. But for applications, Disk Copy images, and font files, this was a big problem because their resource forks contained data necessary for their operation. png's this wasn't a problem because whatever was in their resource forks (custom icons?) wasn't required to open them. So each file had two forks, only one of which (the data fork) would be recognized on non-Mac systems. Resource forks are mostly a relic from the classic Mac OS, though they also exist in OS X, that stored data on a file apart from the data fork. So I thought I'd put up a little reminder that when transferring or backing up files with resource forks, you need to take steps to preserve them.įirst a little background. And when resource forks get destroyed, sometimes the whole file is rendered unusable. And when resource forks aren't supported in file transfer applications like Cyberduck, they get destroyed when transferring between computers. You see, I have files with resource forks on my various computers and hard drives. I will disappear sooner or later anyway, and well, I should just go die already. "Resource forks are deprecated anyway and they will sooner or later disappear alltogether." "Sorry, this is deprecated."
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |