All,
I ran into the problem today:
On boot: Exception #3 (0xc)
After spending way too much time diagnosing the issue I figured out that I had reversed the memory module positions. Bank 0 is towards the edge of the board (which seems counter intuitive since you have to remove the existing modules to add more with this configuration). If the memory is populated starting at bank 0 this error goes away. I'm posting this here because what little information I could find in the newsgroups was misleading.
--
Brian
Yeah, sometimes it'll also make a weird sound when starting up and the wrong bank is populated.
I happened to notice last week that this info is in the official NeXT service guide.
Quote from: "barcher174"On boot: Exception #3 (0xc)
After spending way too much time diagnosing the issue I figured out that I had reversed the memory module positions. Bank 0 is towards the edge of the board (which seems counter intuitive since you have to remove the existing modules to add more with this configuration). If the memory is populated starting at bank 0 this error goes away.
The boot ROM needs a little bit of memory at a known location to get started. It it can't even find that there's some hacky code to *BLAT* at the sound out hardware. We probably should have tweaked it to look for the other bank by default, in retrospect.
Hi M Paquette,
I very much enjoy your perspective on these things. It's very cool to get insider confirmation. Thanks for sharing your stories!
--
Brian