fdisasm-1.1.3.zip (80K) a zipped hfs disk image and checksum file. The disk image can be mounted with Mini vMac. Includes source code.
The following disk images contain all the formatting information needed to disassemble specific Macintosh ROM images:
fdplus-0.4.0.zip (72K) Macintosh Plus ROM
fdmac128-0.4.0.zip (49K) Macintosh 128/512 ROM
fdmacse-0.5.0.zip (85K) Macintosh SE ROM
fdmacii-0.2.0.zip (95K) Macintosh II ROM
fdpb100-0.2.0.zip (101K) Macintosh PowerBook 100 ROM
FDisasm is a formatting disassembler for Motorola 680x0 code. It makes it possible to distribute the means to create an annotated disassembly of copyrighted code (such as Macintosh ROM images), without distributing that code or files derived from it.
To use FDisasm to disassemble the Macintosh Plus ROM, launch Mini vMac and boot from a disk image containing a system folder. Mount the fdplus-0.4.0 disk image, and import a copy of the Macintosh Plus ROM onto it. (Such as by using ImportFl.) Mount the fdisasm-1.1.3 disk image, copy the FDisasm application to the fdplus disk image, and then eject the fdisasm image. Rename the ROM image to "bin", and then launch the FDisasm application. The program displays a progress indicator, and quits when it is finished. (It could take five minutes at 1x speed, so set speed to "all out". At "all out" speed it takes under 10 seconds to finish on my Mac Mini.) When the program finishes, the output is in a file named "listing".
This listing file is over 2 megabytes. The program MPW Shell 3.2.3 works in Mini vMac and can work with such large text files. But probably almost nobody else has an old copy of MPW. (The final version of MPW still available for free download requires a Mac II or later.) Instead you can export the listing file to the host computer (such as by using ExportFl), and find some program there that can view it. (For OS X, TextWrangler would work, for example.)
Warning : Not enough people are paying enough attention to FDisasm (especially me) for it to be relied upon. If you notice something odd in the output, double check it, and if it is wrong, please report it to me.
This listing file is derived (in terms of copyright law) from the Macintosh Plus ROM, and so may not be redistributed.
To disassemble the Macintosh 128/512 ROM, follow the above instructions, except use the fdmac128-0.3.0 disk image, and of course use a ROM image from a Macintosh 128 or 512. And similarly for the Macintosh SE, Macintosh II, and PowerBook 100 ROMs.
Here are some details about the formatting information files used by FDisasm:
The only file required by FDisasm is "bin". But if this is all it finds, it will just create a hexadecimal dump of the file. To disassemble code, it needs to know where the code is. It looks for a file named "bin_map" for this information. It also looks for a file named "bin_names" for names of locations within "bin", and for a file named "abs_names" for names of absolute memory locations, and for a file named "trap_names" for names of A-line instructions. A file named "format" can give additional formatting information, and comments to include in the listing.
The FindCode tool can help to create the files "bin_map" and "bin_names".
The FindRes tool will create an initial "format" file for Macintosh resources, and also "bin_map" and a set of entry points to feed to FindCode.
Besides ROM images, FDisasm can also disassemble Macintosh 680x0 applications. But the code and other resources are located in the "resource fork" of such appplications, while FDisasm only operates on the "data fork" of the file "bin". The GetRsFrk tool gets the resource fork of a file you select, and saves it into the data fork of "bin".
The software that has become FDisasm, FindCode, and FindRes was my first serious programming project, started in 1985 in Basic, and later converted to Pascal, and now converted to C when I got back to it recently. I wonder if 23 years to first public release is any kind of record.
If you find FDisasm useful, please consider helping the Gryphel Project, of which it is a part.
Here is the md5 checksum for the download:
-----BEGIN PGP SIGNED MESSAGE----- 4f1a24c87c6c170bf6ce7ba76866432b fdisasm-1.1.3.zip 7de0fb6f4fe0305ebb168fad6188b470 fdplus-0.4.0.zip 3e91fa766f6ddfa4d4dfc03aa6d326f1 fdmac128-0.4.0.zip 7ef5aaa0099c7266b37904e646649b0c fdmacse-0.5.0.zip 755aa3346a0d9fbd5a35ecad049781a6 fdmacii-0.2.0.zip 4765e0074c5b63c4668ad95c9866f814 fdpb100-0.2.0.zip -----BEGIN PGP SIGNATURE----- Version: 2.6 iQCVAwUBUFDRjtiugru7WJg5AQG5GgP+OrBthoUB33xMjmyzwMMV+g18oZFxX7O0 YG15DCk7CHk0QflXxBMFeSlZYgnB5RBKTRu4LeLqsutQnnwTpp5Y6jBQ5aXlXT+w FkplQif+DeZbgsszk/froWGhRylBWBkr0OTQDETk7GA7c2ji+37NQ73muErnTgeG BoUSD+7f4Mw= =2bwQ -----END PGP SIGNATURE-----
See the Compiling page for instructions on compiling FDisasm from the source code.
You can redistribute FDisasm and/or modify it under the terms of version 2 of the GNU General Public License as published by the Free Software Foundation. See the included file COPYING.
FDisasm is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the license for more details.
September 12, 2012 version 1.1.3 includes code from Rob Braun for the "pmove, pload, and pflush family of instructions for the 68851 and 68030".
September 7, 2012 version 1.1.2 includes a bug fix from Rob Braun. A 32 bit offset for the Bsr or Bra instruction was not decoded correctly.
October 6, 2011 fdplus-0.4.0 merges in changes from Steve Chamberlin, that "added many more comments of my own, and many new meaningful names for previously-unamed routine entry points, especially in areas related to the boot sequence and Sony disk driver".
September 25, 2011 new versions of all the formatting information disk images, removing the FDisasm application. The version of the application on them was out of date.
June 5, 2011 version 1.1.1 fixes a bug reported by "Ben". The size field was not correct for AddQ and SubQ.