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

Mac SE 800k 20SC bad startup screen no boot

Dear all,

I’m the happy owner of a Macintosh SE M5011 first version with the 800k floppy and internal 20SC which luckily badged as well at its back.

Unfortunately I’m not able to have it booting despite of trying different ram simms combinations that were tested well on my other SE Fdhd.

Here is video of that startup screen which is anyway changing when I push the reset button on the side of the motherboard.




R35 was cut, R36 is empty.
I did resolder R35 in order to try the pictured 4*256ko configuration but anyway.. same startup screen.

Any idea what could be the issue ?
Many thanks beforehand for your time spent in reading and helping me.
F360FB41-E6C9-4C6F-8385-B7486B4E634C.jpegB28DF135-1796-4630-8E76-DCCFD1DF6649.jpeg55660270-BB75-4F62-9F8B-A6BD542FEC28.jpeg2A42BDEF-0768-44C5-96D4-75473EED87DC.jpeg
 
Thanks a lot for your help.
No chime at startup unfortunately.

Here are some closer pictures. The screen isn’t frozen compared to chessboard issues, there are kind of speedy activities.

Here is also a new video with reset button effect. it also makes a slight tic sound in the speaker when pushed (see also last 2nd picture which is with button pushed ).

Could / Should I test the Rom chips on the working FDHD motherboard ?

thanks again

EF9CBCE8-D194-4E24-8428-DC2003317232.jpeg8C653672-E1CB-4B56-B961-E9DD3BE9827D.jpeg8469A95B-1BF3-4F26-9417-4FF06F1C56A3.jpeg
 

LaPorta

Well-known member
Has that original axial battery leaked at all? They usually don't, just checking. Some good shots of the entire board would be very helpful, as well.
 
Hi,

here are the requested additionnal pics I took in best quality with my wife's phone lol.

Also, I found this link which is interesting relatively to HALT and RESET mistakes/short on the cPU caused by a wrong sound chip ?


What I found is that both RESET and HALT lines are driven LOW (active) and for some reason they are both short. On working computer I applied 5V to them... and got sad mac face!
So I desoldered audio chip again, and tried resetting CPU by hand (this time on correct connector). And I got usual background!
After soldering ADB chip, got mouse and no system disk indicator, with disk connected it was hanging somewhere during MacOS boot - I added SCC back and it booted.

Sound UC is broken, at least RESET line part. It's LOW all the time. I isolated this single pin and after resetting CPU everything boots, and works, including sound.
I checked whole reset and power circuit, everything seems to be right. Schematics of this part is 1:1 from Mac Plus, just elements IDs are different.

Thanks again for your possible help,

Regards

20231011_215735.jpg20231011_215751.jpg20231011_215819.jpg20231011_215830.jpg20231011_215850.jpg20231011_215922.jpg20231011_215939.jpg20231011_215948.jpg20231011_220010.jpg20231011_220033.jpg20231011_220048.jpg
 

LaPorta

Well-known member
Sometimes those two-chip RAM chips don’t play nice. Do you have any regular sticks around?
 
thank you so much for reading my post and answering ♥️

I do have some 8 pins that I guess being 1Mb Simms, see first pictures on top of this topic. A

ll of them were tested successfully on the FDHD board
 

bigmessowires

Well-known member
OP has no chime, and a changing pattern of garbage on the screen. I'm not 100% sure about the SE, but on the Mac Plus I think you'll get a boot chime even if there's no RAM at all.

The video circuitry displays a fixed region of RAM as an image. It's interesting that the video image is continuously changing. Either the CPU is continuously writing data here (unlikely) or the video circuitry is reading from the wrong address, because of problems with the address lines or another reason.

When you hold the reset button, the video image stops changing. This suggests to me that the changing garbage may actually be written by the CPU. Maybe it read the wrong instruction from ROM, putting it into an infinite loop that continuously writes data across the whole address space? That seems a bit far-fetched though.

Problems with the address lines could prevent reading ROM during startup (no chime) and could also result in reading video data from a non-RAM address (changing garbage image). There might also be a problem with the address decoding, but that seems less likely.

I would use a schematic and check for continuity on all of the address lines to all of the chips where they should be connected, and also check that there is not continuity between any address line and an adjacent address line or other signal or supply voltage.
 

LaPorta

Well-known member
OP has no chime, and a changing pattern of garbage on the screen. I'm not 100% sure about the SE, but on the Mac Plus I think you'll get a boot chime even if there's no RAM at all.

Is that so? I guess if I thought it through that would make sense, playing before any sort of conceivable RAM check could happen. Thanks for that, and I missed the no chime.
 
OP has no chime, and a changing pattern of garbage on the screen. I'm not 100% sure about the SE, but on the Mac Plus I think you'll get a boot chime even if there's no RAM at all.

The video circuitry displays a fixed region of RAM as an image. It's interesting that the video image is continuously changing. Either the CPU is continuously writing data here (unlikely) or the video circuitry is reading from the wrong address, because of problems with the address lines or another reason.

When you hold the reset button, the video image stops changing. This suggests to me that the changing garbage may actually be written by the CPU. Maybe it read the wrong instruction from ROM, putting it into an infinite loop that continuously writes data across the whole address space? That seems a bit far-fetched though.

Problems with the address lines could prevent reading ROM during startup (no chime) and could also result in reading video data from a non-RAM address (changing garbage image). There might also be a problem with the address decoding, but that seems less likely.

I would use a schematic and check for continuity on all of the address lines to all of the chips where they should be connected, and also check that there is not continuity between any address line and an adjacent address line or other signal or supply voltage.
Thanks a lot @bigmessowires , that's for sure a very helping post <3

Do you think I could try to switch the 2 Rom chips with the ones of the working FDHD motherboard ? Or at least try the Rom chips of the non-working 800k motherboards on the working FDHD motherboard ? same for IWM ?
I checked all markings on the chips but they are quite different...

thanks a lot again for your input
 

bigmessowires

Well-known member
It couldn't hurt to try swapping chips between two logic boards. But I'm guessing the problem is something more than a bad chip. If you don't have a multimeter, get one that has a continuity check mode where it beeps when there's a low-ohm connection. Then use it to beep out all the address and data lines on the board and make sure they're correct.
 
Top