So the question is, which, if any, encoding is preferred here? By encoding the file's resource fork in the data fork (basically converting the file into plain text), the resource fork can be preserved on non-Macintosh file systems, and only requires de-encoding by the user upon downloading before opening. Way back in time, this involved UUEncode, or a program called PackIt, but later was superseded by BinHex, specifically BinHex 4 (.hqx) and the later MacBinary format (.bin, aka BinHex 5). Something like a DC42 disk image can have its resource fork and type codes restored using ResEdit (or similar), but this is an extra step that can be avoided by using binary encoding first. Not a problem for a JPEG, but this renders many Macintosh files useless (in particular Application programs). As many will no doubt know, when non-Macintosh file systems get ahold of Classic Mac files, the resource forks are instantly stripped away. DC42 doesn't store any of its imaged data in the resource fork, but the File Type and Creator Codes, used by Classic Mac OS to identify files, are. However, the other element is the resource fork.

DC42 is also the preference on the Garden for such disks, since Disk Copy 6.x doesn't preserve everything correctly, even when saving in DC42 format. This is necessary, since they can't be dd'd on modern floppy drives like 1.44MB diskettes. From older posts on the forum, I have gathered that Disk Copy 4.2-format disk images are preferred, though it is not mentioned in the guidelines. In particular, much of the software I deal with is stored on Macintosh 800k (or 400k) floppies. I have read through the guidelines, but very little is said about formatting prior to OS X.

I just discovered BetaArchive and am interested in applying for FTP access, but I wanted to verify the procedure before submitting my application. My name is Lilliputian and I am a regular contributor to the Macintosh Garden.

Diskcopy mac