• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Another IIci ROM hack

WOOHOO! NINE pages and counting for your first post, dougg3! 8-)

How does the Macintosh Family Hardware Reference differ from the earlier Inside Macintosh volumes?
MFHR and GttMFH2E are Hardware Reference Materials printed on wood pulp based storage media which would the Paleolithic era distribution model for the Neolithic Developer CDs, both predecessors of the more current PDF based DeveloperNote model.

All of which refer to the Macintosh Hardware: I/O subsystems, memory management and physical layout of the case and design guidelines for those systems & subsystems.

Inside Macintosh is for software only developers right alongside hardware/software developers.

For the most part, the Hardware References give a vague description of the way a Mac is supposed to work and spend a LOT of ink/bits making it VERY CLEAR that the Mac Hardware should ONLY be addressed via the ToolBox routines found in: Inside Macintosh

 
Here's the RoadMap:

xxixfigurep1.jpg.dcb8adf3a7eee6284a998b19e2398a7f.jpg


. . . with a couple of other Titles I'd like to nab!

Here's the .TXT info:

xxviitablep1.jpg.b507fca882f7032e5f7a2e12c5f87fc6.jpg


There wasn't much need for Macintosh Hardware Reference Material until the release of the SE and the Macintosh II.

Before then, the Classic Macintosh was SJ's dream of the perfect "monolithic" AIO computing appliance . . .

. . . just add the "optional" :lol: second FDD, Double the RAM and add a SCSI port to the Box . . .

. . . then a killer app like PageMaker can save the poor little critter from oblivion!

;)

 
I just ordered TIttMF in collectable condition from amazon.com for $35, shipped 2-Day, so I should have it Saturday.

tmfcover.jpg.526c31a044e22de6714e100fe01e53e2.jpg


Technical Introduction to the Macintosh Family the root level of the Macintosh Family TechInfo Tree! :approve:

 
I just ordered TIttMF in collectable condition from amazon.com for $35
I bought my copy from AbeBooks, where if you want something that is in good condition, the price is very "affordable" (cheap as) and some copies for more, that are described as "as new".

http://www.abebooks.co.uk/servlet/SearchResults?bt.x=0&bt.y=0&sts=t&tn=Technical+Introduction+to+the+Macintosh+Family

I always check for availability of old books/manuals at AbeBooks as shipping to the land down under is quite reasonable.

 
I got my copy of MFHR from abebooks and was very satisfied. I saw several copies of TIttMF for less . . .

. . . but the price was right for a "collectable" Reader that I don't expect to be scanning from cover to cover! }:)

Designing Cards and Drivers for the Macintosh II and Macintosh SE is next on my list and abebooks has some great prices!

DCaDftMIIaMSE is beginning to get just a tad cryptic! :lol:

 
LOL...I thought GttMFH2E was cryptic enough, but DCaDftMIIaSE is just insane!

Between all of the posters here, we could open a freakin' library with how many books we have!

 
De nada, compadre! [;)] ]'>

My "Collectable, Like New" copy of TIttMF arrived today and I could swear it's in better shape than my brand new, special ordered, GTttMFH2E was when it arrived at B&N back in the day! It's certainly in much better shape than the "in stock/on the shelf" copies had been at Barnes & Noble . . .

. . . before they'd discontinued stocking them. :approve:

More info after I take a gander at this new research toy! [:D] ]'>

 
ya i have the designing cards and devices book as well. I also have inside macintosh vol2 i think? but thats all i have.

Vol 1 through III is downloadable on the web. I have vol 2 in book form.

 
:O BUMP!!!!!!!!!!!!! }:)

I can't believe this thread dropped all the way down to page 2 of "Active" Topics! :-/

Meanwhile, back at the banana ranch . . . yo!!! dougg3!!!!!!

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?

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! ::)

 
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!

Top.JPG

Bottom.JPG

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.

 
Well, I've started feeling a lot better today, so naturally this afternoon I sat down and put one of them together. I ended up destroying the center plastic plate on the sockets so I could reach the pins. I also ended up having to cut off the alignment pegs from the bottom of the sockets because I accidentally ordered sockets that had alignment pegs!

Haven't tested it yet because I rinsed it off with water to clean off the flux and I'm going to let it dry for a while. I have done some continuity checking and everything seems to be connected right. Here's what it looks like (don't laugh too much at my surface mount soldering ;) , especially on the back side...even those "big" 1206 capacitors are TINY!):

AssembledTop.JPG

AssembledBottom.JPG

 
I see solder bridges along the top row of pins on both IC2 and IC3. Should be easy to fix with some solder wick.

I'm looking forward to seeing this in action!

 
Hey, thanks for pointing those out--I noticed those when I soldered, but those pins are connected together on the board anyway in order to pull the write enable pin high (the other pin is VCC), so I just left the bridges there. I forgot to mention that :) I think the solder bridged because there is a via between the pins.

 
Ah, that makes sense. Then you're almost ready to go!

Drumroll:

TATATATATATATATATATATATATATATATATATATATATATATATATA

TATATATATATATATATATATATATATATATATATATATATATATATATA

(waits expectantly)

 
Back
Top