Aug 05, '04 10:27:00AM • Contributed by: arloguthrie
While we wait for Apple to update Safari and fix this, there is a workaround. After Safari unzips the archive, it puts the original archive in the trash. Simply drag this original archive out of the trash and decompress the archive through the Finder.
[robg adds: I haven't seen this issue, but I don't use Safari much, and do very little with resource fork files any more. If someone can confirm/deny this one in the commnets, I'd appreciate it...]
