• 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.

Macintosh SE with constant Address errors.

Hello! I recently restored a Macintosh SE to "working" condition (Can read disks and get into the OS from a Boot-disk) but I am having constant bomb errors with Address error. As soon as you try any action you get either a Bomb with Address error if in the OS or the 0000000F 00000002 if in the startup. From other posts I initially thought it was dirty RAM so I cleaned and reseated it (and cleaned the slots). It got me further into the OS (Launched Disk Service but crashed right before I got into it, tried getting there to see if the non-responsive hard drive still worked). Probably only luck. After that it crashed with a blinky menu and a buzzing from the speaker, and I kept getting address errors. Two other errors I have had (both only once) was Stack collision with heap and 00000003. Do not know if these will help as they have only occurred once. 

What I have currently done with the machine is: Disassemble, clean and lube the disk drive. Tried it with the inactive HDD disconnected. Cleaned off surface dust from most parts. Reseat and clean ram and slots.

Does anyone know what might cause these address errors, and how I may go about fixing it? Thank you a bunch!

 
Could be a multitude of things. 

One, could be the power supply itself not supplying clean power, or high enough voltages. 

It can equally be the NMI pullup connection open, or button bad, it could be any of the chips on the logic board, many things unfortunately. Could even be a bad copy of the System Software. 

 
Could be a multitude of things. 

One, could be the power supply itself not supplying clean power, or high enough voltages. 

It can equally be the NMI pullup connection open, or button bad, it could be any of the chips on the logic board, many things unfortunately. Could even be a bad copy of the System Software. 
Damn, I suppose that was what I was expecting though... Probably not a software problem though as it sometimes gets the same errors even before beginning to read the disk. 

 
Back
Top