
	Where results make sense

Topic: MacBinary

Related Topics

Eureka, Texas

Football in Israel

Radio Mast Thule

In the News (Thu 31 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Replacing the Batteries In Mac Portable
		MacBinary's purpose is to encapsulate all information (including the filename, creation and modification dates, file type and creator) contained in a Macintosh file for transport over a non-Macintosh medium.
		MacBinary II is the name given to the new MacBinary standard which everybody uses today; in common usage, MacBinary means MacBinary II.
		MacBinary III is an update to the vernerable c1987 format that supports the icon badge custom routing information finder flags that are part of MacOS 8.5.
	www.jagshouse.com /commFAQPt1.html (3656 words)

	MacBinary - Wikipedia, the free encyclopedia
		MacBinary was developed as a means of preserving this structure without sacrificing portability.
		MacBinary is similar to BinHex, but MacBinary produces binary files as opposed to ASCII text.
		For Mac OS X, the MacBinary format has been largely superseded by the.dmg disk image format which is mounted as a volume after it has been double-clicked.
	en.wikipedia.org /wiki/MacBinary (364 words)

	mac.org
		MacBinary II+ is a System 7 drag and drop converter for MacBinary files.
		MacBinary is a binary (non-text) format that encodes Macintosh files so that they can be safely stored or transfered through non-Macintosh systems.
		MacBinary combines the two forks of a Mac file, together with the file information (Name, Creator Application, File Type, etc) into a single binary data stream, suitable for storage on non-Mac systems.
	www.mac.org /utilities/macbinary (143 words)

	What is MacBinary, and how can I decode it? - Knowledge Base
		It is similar to BinHex, but MacBinary produces binary files as opposed to ASCII text.
		MacBinary II remained compatible with subsequent updates of the operating system; however, changes introduced to the Finder in Mac OS 8.5 have necessitated MacBinary III, the third release.
		If you are having trouble decoding a MacBinary file and you know that the file isn't corrupt, upgrade to MacBinary III if there's a newer version of your application that supports it.
	kb.iu.edu /data/aeiw.html (556 words)

	Overview of MacBinary Toolkit 2 for Java
		If you recompile the source with a later JDK, the compiled classes may not be runnable on a JDK earlier than the one you compiled for.
		This layer is partly utilitarian and partly illustrative.
		The actions of the specific data-handler (the builder) are directed by the principal class (the director) at the appropriate times and in the ways that MacBinary requires.
	www.amug.org /~glguerin/sw/macbinary/overview.html (2782 words)

	Mac Binary format (Site not responding. Last check: 2007-11-05)
		MacBinary II is the current standard for the MacBinary format.
		This is a preliminary specification of an extension to the MacBinary II Standard to allow MacBinary to incorporate a directory tree in a similar way to a unix tar file.
		These are the new changes to the MacBinary Standard, as generally agreed upon in the MacBinary II Conference 6/21/87, and as changed in the followup conference 6/28/87.
	local.wasp.uwa.edu.au /~pbourke/dataformats/macbinary/index.html (1711 words)

	BinHex VS MacBinary - MacNN Forums
		The latest version of MacBinary (III) does a more thorough job with catalogue info than the common version of BinHex (4.0), as the former also caters for the extended Finder flags of Mac System 7.x - Mac OS 9.x.
		However, probably the most important difference is that, in MacBinary, the data still remains in binary format -- i.e., a stream with standard 8-bit bytes.
		For details on both the MacBinary (I, II and III) format and the BinHex (4.0) format, see Leonard Rosenthol's Mac Formats web page.
	forums.macnn.com /68/developer/58020/binhex-vs-macbinary (629 words)

	MacBinary Format
		The MacBinary de facto standard (specs of versions I, II and III can be found at Lazerware but should only interest programmers) allows to keep together both forks of Macintosh files on telecommunications lines or on servers which don't know anything about forks.
		It can be useful to create a MacBinary file on the PC, for an example if you have to send a file to a Macintosh user who is not fully aware of all the aspects of the creator and file type signatures (see also our page on signatures to go further on this subject).
		If you think that the file you have to send will be received in a program managing the MacBinary header and that you are the knowledgeable person of the two, it can be useful to "forge" a Macbinary file on your PC and send it in this form.
	www.macdisk.com /macbinen.php3 (745 words)

	Macintosh Font Installation Procedures
		Decode the MacBinary font file: Within the distribution file, the individual font file to be used must be decoded and then copied into the system font folder.
		There are several MAC programs that can open ZIP files and decode MacBinary files such as the Stuffit Expander available from Aladdin Systems.
		MacBinary format encodes both resource and data forks into one file so it can be encoded in a ZIP file.
	www.idautomation.com /kb/mac-fonts-install.html (591 words)

	TidBITS: Macintosh Internet File Format Primer
		That format, MacBinary II, has survived to this day, although it is being replaced by MacBinary III to address the issue raised by the new file flags originally slated for Mac OS 8 and appearing now in Mac OS 8.5.
		MacBinary was the obvious choice, but because MacBinary stores the data fork first in the file, you couldn't do live edits on MacBinary files within A/UX.
		MacBinary III was the course of least resistance.
	db.tidbits.com /getbits.acgi?tbart=05066 (2551 words)

	ITCWeb On-Line Manual Pages
		Conversely, in converting a MacBinary file to BinHex 4.0 format for mailing over long distances, one may be restricted to mail messages of no greater that some fixed length.
		For MacBinary and BinHex 4.0 input files, the base file name is specified within the input file, while for plain files, the file name specified on the command line is used.
		MAC_EXT The MacBinary files created when option -D is selected are named according to the file name field stored in the file header, with the name extended by this suffix.
	www.itc.virginia.edu /cgi-contrib/manpage.cgi?mcvert (2107 words)

	How to transfer an icon on Macintosh® (Site not responding. Last check: 2007-11-05)
		MacBinary - This format permits to easily transfer files between Macintosh® and Windows®.
		To transfer and icon between Windows® and Macintosh®, the easiest method is to use the MacBinary format.
		The MacBinary format permits to merge the 2 forks in one file handy for transfer, mail attachment or Web publishing.
	www.axialis.com /docs/iw/How_to_transfer_an_icon_on_Macintosh_.htm (607 words)

	Fetch Help: MacBinary Format
		MacBinary III (often just referred to as MacBinary) is a format for representing all the information in a Macintosh file (data and resource fork) in one binary file.
		Unlike BinHex, MacBinary is a compact format, but it cannot be passed through most electronic mail systems.
		Fetch automatically recognizes and decodes MacBinary files when downloading, although automatic recognition can be turned on and off by selecting a remote file whose name ends with ".bin", choosing Remote > Get Info to show the info window, and, in the Transfer Options pane, checking or unchecking the Automatically decode files like this checkbox.
	fetchsoftworks.com /FetchWebHelp/Contents/Concepts/MacBinary.html (203 words)

	Rumpus 1.3 - User's Guide: Encoding Options
		Note that MacBinary encoding is always available for clients that support and ask for it (and most Mac FTP clients are smart enough to do just that).
		Files encoded with MacBinary are transfered with their type and creator codes intact, and Rumpus will save the files using the correct, original codes.
		MacBinary is a standard format used by many popular Macintosh clients and servers to send a complete file (data fork, resource fork, and Finder information) over a single data stream.
	www.headgap.com /telefinder/rumpus/R08Encoding.html (1137 words)

	[No title]
		MacBinary also stores other information (such as the filename, creation and modification dates, file type and creator) about the original file.
		MacBinary's purpose is to encapsulate all information contained in a Macintosh file for transport over a non-Macintosh medium.
		MacBinary I is the name given to the old MacBinary standard.
	www.csuhayward.edu /ics/faqs/commfaq.txt (13076 words)

	[No title]
		The primary formats in which Macintosh files are represented on non-Macs are: MacBinary: An eight bit wide representation of the data and resource forks of a Mac file and of relevant Finder information, MacBinary files are recognized as "special" by several Macintosh terminal emulators.
		MAC_EXT The MacBinary files created when option -D is selected are named according to the filename field stored in the file header, with the name extended by this suffix.
		For example, when converting from MacBinary to resource, data, or text, the suffix is only appended if the non suffixed version of the file is readable.
	www.rpi.edu /dept/acm/www/packages/mcvert-1.9.0.html (1486 words)

	unbin (Site not responding. Last check: 2007-11-05)
		BinHex, MacBinary, and AppleSingle are commonly used formats for transferring Macintosh files between machines via email or file transfer protocols.
		MacBinary is the for- mat most often used by terminal emulators "on the fly" when transfer- ring Macintosh files in binary mode.
		MacBinary files often have an extension of ".bin".
	linuxcommand.org /man_pages/unbin1.html (326 words)

	Macintosh Paint: Summary from the Encyclopedia of Graphics File Formats (Site not responding. Last check: 2007-11-05)
		The MacBinary header is a structure which allows a Macintosh file to be copied or otherwise transported between a Macintosh and another system, and which contains the information required to reconstruct the two forks when the file is returned to the Macintosh environment.
		It is not necessary for a non-Macintosh application to modify the MacBinary header unless the image data is changed or the MacPaint file has been created outside of the Macintosh environment with the intent of one day being returned to the Mac.
		The MacBinary header is followed by four bytes of data (00h, 00h, 00h, 02h) signaling the start of the actual MacPaint file.
	www.fileformat.info /format/macpaint (1555 words)

	WGMac Glossary
		MacBinary Header: When Macintosh files are electronically uploaded from a Macintosh, they usually need a MacBinary header attached to them.
		When this file is downloaded back onto a Macintosh, using the MacBinary file transfer protocol, the MacBinary header is stripped from the beginning of the file and the information in the header is used to make the file usable to the Macintosh.
		Files downloaded onto a Macintosh using the MacBinary file transfer protocol have the MacBinary header stripped from the beginning of the file and the information contained within that header is used to make the file usable on the Macintosh.
	www.intbuild.com /WGGlossary.html (1783 words)

	comp.sys.mac.comm FAQ (v 2.4.1) Feb 15 2003
		MacBinary II is the name given to the c1987 update to the standard.
		MacBinary III is an update to the vernerable c1987 format that supports the icon badge custom routing information finder flags that are part of MacOS 8.5 and later.
		While MacBinary internal versions of zip and LZH exist it is better to stick with sit for Mac files.
	www.faqs.org /faqs/macintosh/comm-faq/part1 (6594 words)

	TidBITS: Calling Developers to MacBinary III
		The changes from MacBinary II are minor, I'm told, and several developers are providing sample source code in Pascal and C. More information is available at the page below, and there's a mailing list developers can join to talk about the issues.
		MacBinary III is completely backwards compatible with MacBinary II, so a MacBinary III decoder will handle any files already stored in MacBinary II.
		MacBinary III is the wave of the future, so make sure your programs aren't left behind in a 7-bit BinHex past.
	db.tidbits.com /getbits.acgi?tbart=05050 (796 words)

	How do I preserve the resource fork in a file upload from a Mac?
		If the upload is sent from a browser in MacBinary format, then both the resource and dataforks will be transmitted to the server.
		This property is only relevant when the upload is sent from the browser in MacBinary format.
		Note: FileUp does not provide MacBinary encoding or decoding functionality, it merely preserves the forks if they are sent by the browser.
	support.softartisans.com /kbview_543.aspx (403 words)

	Subsetting the MacBinary Toolkit 2 for Java
		It is not a complete detailed guide, and determining an absolute minimum subset requires you to determine for yourself which components and capabilities can be omitted for your particular needs.
		In the case of the MacBinary Toolkit, "executables" means the compiled Java classes and or JNI-library, in whatever form (JAR, ZIP, separate files, etc.).
		Some classes in the MacBinary Toolkit are useful in isolation.
	www.amug.org /~glguerin/sw/macbinary/subsetting.html (826 words)

	MacBinary III
		This document includes all necessary information needed from the original MacBinary and MacBinary II standard documents to implement MacBinary III.
		The original MacBinary format was ammended (in MacBinary II) to include the sending of the "Get Info comment" after the resource fork was sent, if the length for such comment, given in offset 99, is not zero.
		If they are both zero, either (a) the CRC should match, which means it is a MacBinary II file, or (b) byte 82 is zero, which means it may be a MacBinary I file.
	www.lazerware.com /macbinary/macbinary_iii.html (1055 words)

	Mac-PC Conversions
		However, when the transfer is done via diskette or a typical network (or when a Binary, rather than a MacBinary, modem transfer protocol is used), the conversion from MacBinary to Binary format must be done prior to the transfer in a separate step.
		If a Mac file (MacBinaried as described above) is transferred back from a PC to a Mac, the reverse Binary-MacBinary conversion is needed to strip away the binary “wrapper” and expose the original double-fork Mac structure.
		For binary transfers, a file transfer protocol is needed, and, when transferring a Mac file from a Mac, a MacBinary protocol must be selected or the file must be converted from MacBinary to Binary prior to the transfer.
	www.accurapid.com /journal/mac_pc.htm (2087 words)

	120% MacBinary Compatible
		Many other upload components claim to be able to support MacBinary but their support consists of stripping out what they consider relevant and then throwing away everything else.
		Additionally while we were doing this we discovered that Internet Explorer sometimes incorrectly codes the MacBinary so we had to read the incorrect file.
		However if you do this you loose all sense of what type of file was uploaded (remember it won't have a file name extension) and any other associated information.
	www.websupergoo.com /helpupload/source/2-features/3-macbinary.htm (459 words)

	FTP-Macintosh
		MacBinary II - Mac Binary II (sometimes simply called MacBinary) is a format for representing all the information in a Macintosh file in one binary file.
		Unlike BinHex, MacBinary II is a compact format that cannot be passed through most e-mail systems.
		Automatic conversion of MacBinary I and MacBinary II files can be turned on and off in the Preferences dialog box.
	www.channel1.com /support/Ftp/mac.html (1274 words)

	MacBinary II+ (Site not responding. Last check: 2007-11-05)
		MacBinary is an application "melding" the the data and resource forks together making them savable and servable on such computers.
		Documents encoded with the MacBinary can not be sent through email.
		In any event, you may want the MacBinary utility to decode (or encode) any documents you may receive through the WWW that have the extension.bin.
	www.infomotions.com /musings/tricks/manuscript/0600-0008.html (195 words)

	MacBinary Property
		However Microsoft has given us the ability to handle this kind of file completely correctly and so this is what we do.
		Using ABCUpload you can save a MacBinary file to an NTFS formatted disk maintaining complete integrity of data fork, resource fork, file type and creator.
		Through named stream support available on NTFS the data fork, resource fork and other information is maintained as a package and moves with the file.
	www.websupergoo.com /helpupload/source/4-objectref/2-xfield/2-properties/macbinary.htm (297 words)

Try your search on: Qwika (all wikis)