An LC was the first Mac I owned when I was young. I loved that thing and used it all the time. My father worked at a computer store and could often get good deals on secondhand computers and parts, and somehow that LC ended up getting combined with parts from a few other computers over the years. I still have the result, which is pretty funny to look at - the front says LC on it, the bottom says LC II, and inside is an LC 475 logic board. I just recently I got it back up and running again, with a BlueSCSI replacing the poor dying hard drive inside. No recapping has been done yet and it still seems to work correctly - the internal speaker is a bit iffy at times, but everything else is solid as a rock. I keep it around mostly for old games since emulation just isn't the same. It's still one of my favorite computers ever.
You know, with the advent of people figuring out how the hidden diagnostic mode in Mac ROMs works, it might be easier to find broken traces and troubleshoot bad chips using that than probing around the board.
In my years of experience a keen eye has always beaten automated diagnostic tools. You eventually get a feel for this sort of stuff. While this may not be true in all scenarios, it’s good practice. Also, in order for the ROM to be read the CPU must be executing code, so a lot must be working in order for you to get to that step. I have a TechStep and it has proven handy, but there is often a lot of work required to get to that point.
@@Mac84 I'm thinking more along the lines of figuring out where to even look. Adrian was able to narrow a memory problem down to a problem involving a specific line connected to the GLUE chip. Needing to get the CPU executing code can be a problem, but a CPU that can't execute code well enough to run the ROM narrows things down significantly all by itself. What I'm thinking is that you can run the diagnostic, use whatever information it does (or doesn't) give you to narrow down your search, fix a problem you find, then return to step one and repeat the process. Since the ROM diagnostic starts with the most basic functions and works outwards from there, if you fix things in that order, it should become easier with each problem that you clean up because clearing up the most fundamental problems first results in easier troubleshooting since more of the system will be working and it'll give you more information. If you have a multi-layer failure, this method could potentially clean up the repair process by telling you what specific thing you need to look at to get the system one step closer to functioning.
An LC was the first Mac I owned when I was young. I loved that thing and used it all the time. My father worked at a computer store and could often get good deals on secondhand computers and parts, and somehow that LC ended up getting combined with parts from a few other computers over the years. I still have the result, which is pretty funny to look at - the front says LC on it, the bottom says LC II, and inside is an LC 475 logic board.
I just recently I got it back up and running again, with a BlueSCSI replacing the poor dying hard drive inside. No recapping has been done yet and it still seems to work correctly - the internal speaker is a bit iffy at times, but everything else is solid as a rock. I keep it around mostly for old games since emulation just isn't the same. It's still one of my favorite computers ever.
I wish I had caught this stream live, @Mac84 was on fire!!
Thank you my friend!
Grad school is killing my attention span. (PS: this is Jeremy Bolanos 🦖)
wow and peace be upon you sir from me
How did this thing chime with so many broken traces?
You know, with the advent of people figuring out how the hidden diagnostic mode in Mac ROMs works, it might be easier to find broken traces and troubleshoot bad chips using that than probing around the board.
In my years of experience a keen eye has always beaten automated diagnostic tools. You eventually get a feel for this sort of stuff.
While this may not be true in all scenarios, it’s good practice.
Also, in order for the ROM to be read the CPU must be executing code, so a lot must be working in order for you to get to that step. I have a TechStep and it has proven handy, but there is often a lot of work required to get to that point.
@@Mac84
I'm thinking more along the lines of figuring out where to even look.
Adrian was able to narrow a memory problem down to a problem involving a specific line connected to the GLUE chip.
Needing to get the CPU executing code can be a problem, but a CPU that can't execute code well enough to run the ROM narrows things down significantly all by itself.
What I'm thinking is that you can run the diagnostic, use whatever information it does (or doesn't) give you to narrow down your search, fix a problem you find, then return to step one and repeat the process.
Since the ROM diagnostic starts with the most basic functions and works outwards from there, if you fix things in that order, it should become easier with each problem that you clean up because clearing up the most fundamental problems first results in easier troubleshooting since more of the system will be working and it'll give you more information.
If you have a multi-layer failure, this method could potentially clean up the repair process by telling you what specific thing you need to look at to get the system one step closer to functioning.