Chief Delphi - pic: Chief Delphi in Black and White!

Wow, I'm really becoming a flipflop now. The Mac Classic shal live! I did a little researching on the problem which didn't prove to be too helpful (said I needed to replace capacitors or the logic board or the power board) and then I opened the case to take a look around. Nothing out of the ordinary, just LOTS of dust. So, I blew it all out and then I tried to start it up again. This time vertical lines. Then I saw the memory expansion board inside. The Mac Classic (and classic II) is the only Mac where it uses an expansion board to put more memory. I had never opened this Mac before, nor had I ever seen a memory expansion board before, so I decided to pull it out and check it out. Anyway, I popped it back in and then started it up once more. Aha! A sad Mac face behind "jail bars" I knew Mac was still in there somewhere. So after some more tinkering (like cleaning the SIMM contacts) which didn't lead much of anywhere, I decided to see what would happen if I just took the expansion board out (since there is already 1mb RAM soldered to the logic board). I powered on and it chimed and started to boot! Hooray! It said there wasn't enough memory to load system 7.5 (which was expected) but it functions just fine. It can boot all the way from the internal ROM, or from a system 6 floppy. So the problem (which all others including Apple diagnose as a faulty logic board or power board) turned out to be a bad memory expansion board. I have a new one on order (yes a couple places still sell them) and it should be back up and running in about a week or so.

So yes, (and I'm reluctant to say this for fear of jinxing it) Old Macs Never Die!

One strange thing on the SE/30 that is serving up those screenshots on page 1 of this thread is that it is not letting go of some connections. I have the timeout set but it holds on to some connections (or at least says it does) I have no idea what it is. Maybe I'll revert back to an older version of the server software. But first I'll put it into verbose logging mode to hopefully see what's up.