At 12:59 -0500 2/1/09, Steve R wrote: >"sonofagun" -- it worked. I got the 'this file may be corrupt' >message but it still mounted. Thanks, I'll have to try to remember >that trick.
The .bin extension was once used to identify single files that were really a combination of resource fork, data fork, and metainformation like date, type, and creator. The name of the format is MacBinary. It's also the MIME type AppleSingle which was for efficient email transfer between Macs. AppleDouble which used two separate files was for doing the same thing with Windows or UNIX users. Stuffit handled .bin as did a lot of e-mail clients. I have seen implementations of MacBinary that work on OS neXt. .bin.hex was used as a further expansion to support communication channels that handled only 7 bit ASCII characters. That has been replaced by mode64. It's possible that your download lost a resource fork. In the world of OS neXt that probably doesn't matter much. *.dmg - disk image - probably doesn't use resources. -- --> A fair tax is one that you pay but I don't <-- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed Low End Mac's G3-5 List, a group for those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs. The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/g3-5-list?hl=en Low End Mac RSS feed at feed://lowendmac.com/feed.xml -~----------~----~----~----~------~----~------~--~---
