Hi everyone!
I'm a newbie to the amiga world; I just recently got my hands on an amiga 600, and I have a little problem. Or better, sometimes I have a little problem, and I hope you can give me some clue on what to look for.
The fact is that sometimes (let's say more or less 3 out of 4 times) it boots up normally (at least to the kickstart [the purple screen with the floppy, forgive me if I use wrong terms], but I got it to load workbench 2.05 the first times before I opened it), but at seeming random times during the boot phase I get a guru meditation, with varying error codes (e.g. 8100 0008, 8100 0000, 8000 0004, 8000 0000, 8000 0003), but always in the same task (000026D0). If I press the left mouse button, then it boots ok.
This behaviour happens also with nothing but the motherboard connected.
Oh, and another detail (that might or might not help, I really don't know): occasionally (say... it happened like 4-5 times in about 50 tries, and just once after I reseated the rom chip) the kickstart screen has some messed up colors, with a lot of gray in the zone of the amiga logo and the floppy.
Actually, when I opened it up to check for visible damage, I noticed that a ceramic smd capacitor near the RAM chip (C17B) failed short (and in fact, burnt a hole in the plastic shield below it), so I removed it (I think it is not essential), but to no avail. Everything else looks fine on the board: I checked the traces near the burnt capacitor and everything seems ok.
I'm a newbie to the amiga world, so I really don't know what to do now. As a side note, I haven't recapped it yet, since I really have no idea if that may be the cause of the problemr. I just don't like the fact that sometimes my A600 doesn't boot at totally random times for unknown reasons, and I would like to fix it if it is possible (before doing other things with it, like cleaning it really well, retrobrighting, installing an hdd...).
I really hope someone can give me some hints on what to look next, I'd really like to solve this issue.
I posted it in this section becouse I suspect it is a hardware issue, since it happens with literally nothing else connected by the pcb (and no software loaded). I hope it is the correct one