Oh hi! I'm still here ;-) I just haven't had any reason to update while waiting for the PCBs to arrive. xx(
Have you considered a side by side comparison of ROM Dumps of the SE/30 <-> IIci <-> IIfx <-> IIsi in order to simplify your search methodology by eliminating repetitive/identical instruction sets and repetitive data sets?
It really depends on what I'm looking for. If all I'm looking for is the startup chime, I already have ROM maps from Apple of several of the various II series (but not all! -- II, IIfx, IIci, IIsi, and IIvi) which will directly show me where the code is. But if we're looking to see just how similar two ROMs are, it would probably be awesome to have some kind of app that figured out the differences.
With a comparative parser (?), you could identify blocks of instructions that are identical, even when stored at different address spaces on the four ROM samples.
Using a more complicated parser, you could identify blocks of instructions with a variable scale of change differential in similar blocks of instructions.
Kinda like running a PhotoShop Filter on sets/subsets of ROM instructions? :?:
If this is a standard feature of de-compiling (?) software a/o S.O.P. for such processes, forgive my ignorance, but I just
HAD to ask! :
I actually have no idea if this is a standard thing that reverse engineering types do. I would imagine it would be a very useful tool to have. To be completely useful, I'm thinking it would need to be integrated into a disassembler to help determine what's code and what's data -- this would probably help some kind of algorithm to know what chunks to compare between the two files. Also it would need to know to ignore jump/branch targets when comparing two chunks of code because as code is rearranged in the ROM the offsets to jump to would change. This is true even though the ROM is position-independent because the relative jump offset would still be different as code was moved around/inserted/deleted in ROM. Who knows--maybe IDA Pro already has something like that?
The most basic example would be a binary diff tool, but that would be very, very simple and probably wouldn't give much useful information -- for instance it doesn't know how to ignore jump targets. It would take quite a bit of effort, I'm guessing, to make a "ROM diff" utility as described above. It would probably be quicker just to manually inspect the ROMs

but I do have to say it would still be useful, especially if you could just use it to play around and see how different the LC 520 ROM is from the LC III ROM for example. It's probably not something I have any time to work on though.
Anyway, it's great that you posted this "bump" today because...
The boards have arrived!
Unfortunately I have been battling a stomach bug of some kind all week (I won't go into any detail! haha) and it's still attacking me, so I'm not sure when I'll get around to assembling one to make sure they work. But at first glance, they look very nice! They also fit into the IIci's ROM SIMM slot great as far as I can tell.
Excellent turnaround time. Order was placed the night of 9/5/2011, I got the shipping notice 9/13/2011, and the package arrived 9/23/2011. Like most others whose reviews I read, I got 12 boards instead of 10 and they added a few numbers of their own to the silkscreen (I added my order number to the silkscreen too, because their instructions said to do that). They are actually about 50 mils thick instead of 47, but that's still perfect. I have to say I'm pretty darn impressed with Seeed Studio! Thanks again for letting me know about them, bigmessowires. Definitely awesome!
Anyway, once I'm feeling better I will start doing the fun stuff with these PCBs!
And then once it's all good, I'll get some skull versions of the board made! Haven't had any time to look at the LED stuff yet, but that can wait until I know that this board works.