• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

SE Superdrive - system locks up when repairing/init'ing disks

raydeen

Member
Ok, not sure what the trouble is here. Everything seemed pretty good at first when I got the SE except that it only had 2 megs of RAM. So among some other addons I got for it, I got it up to 4 megs so that I could run Anubis and some other memory demanding things. Well, it started getting a bit flaky with disks, both removable and internal. I had some Syquest 44MB carts that worked and a couple that went bad during use (considering the age, I'm not surprised). I've got two Syquest drives, and just recently got a SCSI Zip drive for easier file transfer between the SE and a newer PPC Mac. But just about every time I attempt to check a disk, verify it, init it, format it, be it the internal HD or an external cart, the SE will get most if not all the way through and then very quickly and repeatedly flash what looks like a an empty Finder message, or I'll get an actual error and the system will lock, or the screen will suddenly get all sorts of data corruption and either lock solid or reboot. I'm currently running with no PRAM battery as the batt had exploded before I got it and had pretty much destroyed the terminal on the left side (looking down on the board with the mem chips at the top and the main ports at the bottom). I'm not seeing any obvious capacitor related problems. The only thing I've noticed is that one end of one of the long thin yellow-ish chips near the memory slots is raised up quite a bit from the surface of the board. It doesn't appear to be breaking any contact with the board, but as I don't know what those are for, It might be one of my problems. It looks like the legs are still down through the solder holes so it might have been a manufacturing defect. I tried pushing it back down into place but it doesn't seem to want to go. 

Thoughts? I've spent way too much money on this thing to give up now. It's become a challenge!

TIA.

 

Themk

Well-known member
You said your battery exploded? It's near by the 5380 SCSI host controller. You even mentioned the terminal nearest to the SCSI host adaptor was bad. Likely, you have a damaged trace or two around in that area. That would cause your SCSI to have problems.

You will need to spend some quality time with the schematics, and your multimeter, to see which traces went bad.

 
Last edited by a moderator:

raydeen

Member
You said your battery exploded? It's near by the 5380 SCSI host controller. You even mentioned the terminal nearest to the SCSI host adaptor was bad. Likely, you have a damaged trace or two around in that area. That would cause your SCSI to have problems.

You will need to spend some quality time with the schematics, and your multimeter, to see which traces went bad.
Well, it was like that when I got it. :) It didn't look like the explosion did much except rust out the frame a bit. I'll have to check into this then. I believe we have a multi-meter, but I admit I have no idea how to use it. Might have to take the lobo to my father-in-law's house for some training. How would I fix the traces if/when I find them? I'm a bit new to the hardware end of things, especially when it's this low level. I know how to replace things, not how to repair them. This would certainly explain what's going on though. Thanks for steering me in hopefully the right direction!

 

Themk

Well-known member
To fix the traces you will need to run a 'patch wire'. What that is, is a small wire that completes the electrical connection that the trace would have made. You solder one end of the wire onto the leg if the IC (chip), and the other end to where ever the connection should complete (normally another IC pin).

Also, clean up what ever is left of the battery 'acid'. If it continues to sit on the board, it will continue to eat away at what is there, and you will have more issues in the future.

Using a multimeter to test for continuity shouldn't be too hard. Either use the continuity test mode, or you can use the resistence measuring mode. When using resistance measuring mode, you want to be at 0 ohms, or really close to see if something is connected. When in continuity mode, most multimeters have a little buzzer that makes a noise to let you know it is connected

 
Last edited by a moderator:

raydeen

Member
Very cool! This little guy is turning into quite the learning experience! Thank you very much for your time and info. 

 
Top