The only thing I can't get to work is the 256 colours mode.

Click to expand...

Oops. I missed seeing this reply before. Better very late than never?

The trick to get color to work in System 6 in the current state of Mini vMac Macintosh II emulation is to install 32-Bit QuickDraw (which is available from the System 6.0.8 installer).

I understand that the starting point of dissasembly has to be known, that's what the bin_map file is for, and it's likely to help with locating the original execution address -- don't know if it will support the aforementioned mirroring, though.

Click to expand...

Macintosh 68k ROMs seem to contain mostly position independent code. My disassembler doesn't know where the ROM is in memory, and it mostly doesn't matter, with some exceptions that can be dealt with manually.

The bin_map file doesn't just say where the starting offset of the code is. Blocks of code and data are mixed throughout a ROM. The bin_map file says where these blocks are, and what areas aren't known yet.

You supply some of this files (thanks again!) for disassembling specific > ROMs, but I understand that the bin_map file for the Mac II ROM won't do > for the IIx ROM, right?

Click to expand...

The Mac IIx ROM seems to be very similar to the Mac II. It differs only by a few patches until it gets to the floppy disk driver, in the resources in ROM section, three fourths of the way to the end. So format files I supply for the Mac II would be a good starting point.

I tried using it but it seems the disassembly doesn't go too far

Click to expand...

This should have worked. Did you copy the Mac IIx ROM image into the FDMacII disk image, and rename it to "bin"?

Any clues about the bin_map file format?

Click to expand...

Each line of the bin_map file contains a starting address and a type (both in hexadecimal). The type in the final line must be 0. The meaning of other types are:

1 - Unexplored

2 - Code

3 - Data

4 - Unknown opcode