MacBinary: Difference between revisions
m Reverted 1 edit by 2804:7F3:8880:8C61:0:0:0:4 identified as test/vandalism using STiki |
No edit summary |
||
| (15 intermediate revisions by 12 users not shown) | |||
| Line 1: | Line 1: | ||
{{Essay|date=October 2009}} |
|||
{{Infobox file format |
{{Infobox file format |
||
| name = MacBinary |
| name = MacBinary |
||
| Line 15: | Line 14: | ||
| standard = |
| standard = |
||
}} |
}} |
||
'''MacBinary''' is a [[file format]] that combines the data fork and the [[resource fork]] of a [[classic Mac OS]] file into a single file, along with [[Hierarchical File System (Apple)|HFS's]] extended [[metadata]]. The resulting file is suitable for transmission over [[File Transfer Protocol|FTP]], the [[World Wide Web]], and [[electronic mail]]. The documents can also be stored on computers that run operating systems with no HFS support, such as [[Unix]] or [[Microsoft Windows|Windows]]. |
|||
MacBinary was widely supported on the [[Macintosh]] and was built into most communications programs on that platform. Similar solutions were built into most [[data compression]] applications on the Mac, and although these did not require MacBinary to survive transmission across non-Mac systems, MacBinary was often added in these cases to preserve longer filenames and other features. |
|||
The dual-fork nature of the HFS system was not used on [[Mac OS X]], and MacBinary has largely disappeared. |
|||
==Description== |
==Description== |
||
In contrast to other computers of the era, [[Macintosh]] applications included both computer code as well as a large number of ''resources'' that were used by the [[operating system]] (OS) itself. These resources were also widely used in documents to store [[rich media]] like sounds and images. However, the resource system had the significant limitation that the maximum size of any single resource was only 32 kB, far too small for storing document data. To address this, Apple introduced the concept of ''forks'', allowing any file in the filesystem to have both a resource fork and a data fork. Physically these were separate files, but the OS would ensure the two separate files were always treated as a single object, so dragging it to a [[floppy disk]] in the [[Finder (software)|Finder]] would copy both forks. |
|||
| ⚫ | Files encoded with MacBinary, regardless of the version, usually have a '''.bin''' or '''.macbin''' [[file extension]] appended to the ends of their filenames. E-mail programs such as [[Eudora (e-mail client)|Eudora]] can extract and decode MacBinary mail messages. Most dedicated FTP programs for the Mac, such as [[Fetch (FTP client)|Fetch]] and [[Transmit (FTP client)|Transmit]], transparently decode MacBinary files they download. |
||
This presented a serious problem when the file had to be stored on other computer systems. Those systems, unaware of the fork concept, would have to store the two forks as separate files. This presented the possibility that the two would be separated at some point, or not properly recombined when they were transmitted back to the Mac. This problem led to a number of solutions that combined the two forks together into a single file, and then automatically pulling them back apart when they reached another Mac. MacBinary was one of the most popular solutions, although [[BinHex]] was also used on [[UseNet]], where data transfer was not [[8-bit clean]]. Apple's own solutions, [[AppleSingle and AppleDouble formats| AppleSingle and AppleDouble]], were never widely adopted in the user community. |
|||
| ⚫ | |||
| ⚫ | Files encoded with MacBinary, regardless of the version, usually have a '''.bin''' or '''.macbin''' [[file extension]] appended to the ends of their filenames. E-mail programs such as [[Eudora (e-mail client)|Eudora]] can extract and decode MacBinary mail messages. Most dedicated FTP programs for the Mac, such as [[Fetch (FTP client)|Fetch]] and [[Transmit (FTP client)|Transmit]], transparently decode MacBinary files they download. |
||
| ⚫ | |||
For [[Mac OS X]], the MacBinary (and BinHex) format has been largely superseded by the [[tar.gz]], [[ZIP archive]] and [[.dmg]] [[disk image]] format which is mounted as a volume after it has been double-clicked. |
|||
==History== |
==History== |
||
The first incarnation of MacBinary was released in 1985. The standard was originally specified by Dennis Brothers (author of the terminal program MacTEP and later an Apple employee), BinHex author Yves Lempereur, [[PackIt]] author Harry Chesley, et al. |
The first incarnation of MacBinary was released in 1985. The standard was originally specified by Dennis Brothers (author of the terminal program MacTEP and later an Apple employee), BinHex author Yves Lempereur, [[PackIt]] author Harry Chesley, et al. then added support for MacBinary into BinHex 5.0, using MacBinary to combine the forks instead of his own methods. Most [[terminal program]]s and [[internet]] utilities added built-in MacBinary support during this period as well. |
||
Two years later it was updated to '''MacBinary II''', to accommodate changes in Mac OS. MacBinary II remained compatible with subsequent updates of the operating system for some time. This changed with the release of [[Mac OS 8]], which necessitated the release of '''MacBinary III''' in 1996. In the meantime, Apple itself had released the |
Two years later it was updated to '''MacBinary II''', to accommodate changes in Mac OS. MacBinary II remained compatible with subsequent updates of the operating system for some time. This changed with the release of [[Mac OS 8]], which necessitated the release of '''MacBinary III''' in 1996. In the meantime, Apple itself had released the AppleSingle and AppleDouble formats, which serve the same purpose as MacBinary, but correct some problems with it. |
||
==References== |
==References== |
||
* Dennis Brothers, "Macintosh Binary Transfer Format 'MacBinary' Standard (Proposal)", Micro-networked Apple User's Group (CompuServe), 1985 |
* Dennis Brothers, [https://www.cryer.co.uk/file-types/b/bin_/original_mac_binary_format_proposal.htm "Macintosh Binary Transfer Format 'MacBinary' Standard (Proposal)"], Micro-networked Apple User's Group (CompuServe), 1985 |
||
* Adam Engst, [http://db.tidbits.com/article/5066 "Macintosh Internet File Format Primer"], ''TidBits'', 31 August 1991 |
* Adam Engst, [http://db.tidbits.com/article/5066 "Macintosh Internet File Format Primer"], ''TidBits'', 31 August 1991 |
||
* [http://www.faqs.org/faqs/macintosh/comm-faq/part1/ "comp.sys.mac.comm FAQ"] |
* [http://www.faqs.org/faqs/macintosh/comm-faq/part1/ "comp.sys.mac.comm FAQ"] |
||
| Line 42: | Line 47: | ||
[[Category:Archive formats]] |
[[Category:Archive formats]] |
||
[[Category: |
[[Category:Computer-related introductions in 1985]] |
||
Latest revision as of 19:07, 25 December 2023
| Filename extension |
.bin |
|---|---|
| Internet media type |
application/macbinary application/x-macbinary |
| Uniform Type Identifier (UTI) | com.apple.macbinary-archive |
MacBinary is a file format that combines the data fork and the resource fork of a classic Mac OS file into a single file, along with HFS's extended metadata. The resulting file is suitable for transmission over FTP, the World Wide Web, and electronic mail. The documents can also be stored on computers that run operating systems with no HFS support, such as Unix or Windows.
MacBinary was widely supported on the Macintosh and was built into most communications programs on that platform. Similar solutions were built into most data compression applications on the Mac, and although these did not require MacBinary to survive transmission across non-Mac systems, MacBinary was often added in these cases to preserve longer filenames and other features.
The dual-fork nature of the HFS system was not used on Mac OS X, and MacBinary has largely disappeared.
Description[edit]
In contrast to other computers of the era, Macintosh applications included both computer code as well as a large number of resources that were used by the operating system (OS) itself. These resources were also widely used in documents to store rich media like sounds and images. However, the resource system had the significant limitation that the maximum size of any single resource was only 32 kB, far too small for storing document data. To address this, Apple introduced the concept of forks, allowing any file in the filesystem to have both a resource fork and a data fork. Physically these were separate files, but the OS would ensure the two separate files were always treated as a single object, so dragging it to a floppy disk in the Finder would copy both forks.
This presented a serious problem when the file had to be stored on other computer systems. Those systems, unaware of the fork concept, would have to store the two forks as separate files. This presented the possibility that the two would be separated at some point, or not properly recombined when they were transmitted back to the Mac. This problem led to a number of solutions that combined the two forks together into a single file, and then automatically pulling them back apart when they reached another Mac. MacBinary was one of the most popular solutions, although BinHex was also used on UseNet, where data transfer was not 8-bit clean. Apple's own solutions, AppleSingle and AppleDouble, were never widely adopted in the user community.
Files encoded with MacBinary, regardless of the version, usually have a .bin or .macbin file extension appended to the ends of their filenames. E-mail programs such as Eudora can extract and decode MacBinary mail messages. Most dedicated FTP programs for the Mac, such as Fetch and Transmit, transparently decode MacBinary files they download.
MacBinary is similar to BinHex, but MacBinary produces binary files as opposed to ASCII text. Thus, MacBinary files are smaller than BinHex files, but older applications and servers are more likely to corrupt them.
History[edit]
The first incarnation of MacBinary was released in 1985. The standard was originally specified by Dennis Brothers (author of the terminal program MacTEP and later an Apple employee), BinHex author Yves Lempereur, PackIt author Harry Chesley, et al. then added support for MacBinary into BinHex 5.0, using MacBinary to combine the forks instead of his own methods. Most terminal programs and internet utilities added built-in MacBinary support during this period as well.
Two years later it was updated to MacBinary II, to accommodate changes in Mac OS. MacBinary II remained compatible with subsequent updates of the operating system for some time. This changed with the release of Mac OS 8, which necessitated the release of MacBinary III in 1996. In the meantime, Apple itself had released the AppleSingle and AppleDouble formats, which serve the same purpose as MacBinary, but correct some problems with it.
References[edit]
- Dennis Brothers, "Macintosh Binary Transfer Format 'MacBinary' Standard (Proposal)", Micro-networked Apple User's Group (CompuServe), 1985
- Adam Engst, "Macintosh Internet File Format Primer", TidBits, 31 August 1991
- "comp.sys.mac.comm FAQ"
External links[edit]
- Mac Binary Converter, an open source tool for converting between different Macintosh file encodings.
- macutils, converts between different Macintosh file encodings
- MacBinary II Spec
- MacBinary II+ Spec, a proposed enhancement to MacBinary to incorporate a directory tree, never widely adopted.