Stubborn C64 Repair

[@thebyteattic]

You're on a row, Jan, great and instructive video! :-) That wonky signal is an example of three normal effects we may often confuse with a problem when interpreting the output of an oscilloscope: (1) the rising edge of a signal depends on the parasitic capacitance inherit to the network transmitting that signal; that is, it is design dependent. In the 80s, people had little care for this effect, because slow rise only slightly delays the point when the system recognizes a transition from logic zero to logic one. And since those computers operated at very low clock speeds anyway, this delay was often negligible. This is what you saw, I think. (2) Sometimes a bus line (particularly address lines) switches from zero to one, and back, without any periodicity (that is, without a discernible, repeating pattern), which confuses the trigger mechanism of the oscilloscope. The result is signals that seem to climb a step ladder up or down, displaying ambiguous logic values. This is often an artifact of the oscilloscope and not a problem in the circuit. Many a repair person has gone down a wild goose chase when, in fact, there is no problem at all. (3) Chips have internal switching because of the dynamic activity of their internal logic gates. This activity often leads to relatively small changes in the signal level visible from the outside, which is also synchronous with the system clock. Those can be confused with bus conflicts, and also lead people down a wild goose chase. In general, the oscilloscope is only as good as the operator's ability to interpret what it displays, and shouldn't be believed blindly! What you did (that is, to compare the signal to that of a working machine) is the way to go!

[@alerey4363]

Jan Beta, 8-bit guy, Adrian Black and Noel Retrolab, all quality assurance seal in retro home computers repair and restoration, thumbs up!

[@tharkthax3960]

Best thing to watch on a Sunday afternoon 👌

[@RalonsoF1]

👍

[@davidczepanski1359]

Well done for hanging in there and working it out... a true "diy" and "right to repair" inspiration. I'm sure that others (myself included!) would have given up much sooner, thrown it away and told the owner to just get another one.... oh... wait... mmmm. well done again.

[@danielmantione]

A12..A15 are not connected to the VIC-II. To prevent them from floating during VIC-II half-cycles, resistor pack RP4 acts as pull-up resistor. This is what causes the wonky signals: The bus acts as a capacitor and the resistor pack needs more time to charge it, than the chips do with their MOSFETS.

[@JanBeta]

That makes sense. Thanks for the clarification! Obviously, the strange sloped signals drove me nuts for quite a while. Should have looked at the working C64 earlier... :D

[@rdh2059]

Enjoyed this video! Repairing old computers can be extremely frustrating at times, followed (hopefully) by the delight that you once again brought something back from the dead! Keep up the good work, Jan!

[@Wallygjs]

Wow, that was a long slog to a fix. It's really great to see that you have the same sorts of issues that I do, as sometimes we get the feeling that "Jan Beta or Gadget UK or Noel would have cracked this by now" but in reality you guys sometimes hit stupid snags like this and we are not alone! Great video, I often think that you learn more from making mistakes then you do when things just go right so well worth watching a lot of useful tips.

[@JanBeta]

I find it quite amusing that Noel had a similar C64 repair recently. The small things can sometimes completely ruin your day. Even if you have some experience with the system you're working on. But it's a good way to learn indeed!

[@LUNATIC75]

The PLA always likes to get involved in any C64 repair video.

[@proCaylak]

that darn -chinese army- chip assembly!

[@stephenbruce8320]

Rabbit Holes followed by giving the board the one finger salute spells frustration we have all experienced at one time or another. Last time I went down that road on a Commodore 8 bit was when two pins on one of the control ports on a 128DCR were shorted because one pin was bent. Yea had I done a full inspection of the ports I would of saved myself a lot of frustration and time. I have an old SAMS Computerfacts repair guides which have expected signals on the schematics which are helpful. When you have what you believe to be strange signals you did eventually do a comparison with a working unit which is a good practice which is not really different then swapping out IC's to test between working and non working units. Nice to see you putting the new scope to work. Now you have a behavior that you can document for future reference. if you have space around your bench you might want to put a Desktop or at least a notebook just for pulling up schematics and for documenting everything. Using Microsoft One Note is very helpful for creating your notes which can be synced to your other devices including your cell phone which is always with you so you can call up and review your notes or make new notes on the fly. I use One Note for everything at work and those notes save my behind more than you know. The other benefit for having a computer at your bench is if you ever get a microscope with a good camera you can do inspections and display points of interest on your screen and take pictures and what not but a good microscope takes up quite a bit or real-estate which is why some use those digital USB Scopes which kind of sort of work and I do have them which is better than nothing but only useful if you need a portable inspection tool. We all go down rabbit holes and once your through them they always help improve your troubleshooting skills. Never apologize for what your doing its all a learning experience both for you and those watching your videos. We all learn from the from the success and failures of others and none of us are perfect believe me I have make my fair share of mistakes which often occur when I get distracted, yea distractions for me is an on going 24-7 event so I have to do a lot of back tracking on what I was doing last before being able to move forward again.

[@hansoak3664]

Your bad days are of interest to multitudes of us viewers. Thank you for bringing us along.

[@darrylteichroeb9132]

Loved it Jan! Sorry it was a tough one, but it was so great to see you try everything!

[@JanBeta]

Thanks! I certainly learned a lot from this!

[@darkstatehk]

The BSOL! I love how you used a contemporary based term to describe a retro repair success!

[@bradnelson3595]

Would make a great t-shirt.

[@johnlanigan5532]

Thanks for persevering with this repair video. I am part way through a similar marathon. You covered methods and techniques, showed results, found revisions in the schematic. I could go on and on. Well done. A marvellous tutorial omnibus of investigation, deduction and repair. It's my goto reference work on C64's lol. Brilliant.

[@JanBeta]

Glad to hear that! Thanks for the kind words! I recommend checking out my collection of useful C64 repair resources (linked in the video description), too. :)

[@gertsy2000]

Well done Jan! I would have given up. It's a surprise that some chips seem to work in another machine; that would confuse any repairer. And that reset signal source coming from a different pin on a diff rev was another gotcha. Always good to have a known good machine and chips even with the expensive digital test equipment.

[@spotterinc.engineering5207]

Love your repairs, wrong turns and all!

[@al.d9592]

Shorter legs? Crazy, never heard of that. Great video, as always. As stubborn as Noels patient in the video you linked

[@JanBeta]

Noel's video actually inspired me to do another C64 repair. Never anticipated it would be as messy as his recent one though! :D

[@LongyFromCork]

Well done Jan. Another one resurrected from the dead. Stressful repair for you, but an enjoyable watch for the rest of us. Thanks for uploading 👍

[@soothcoder]

Yeah I wonder if it would have been worth triggering on a bus control line (no idea about the C64 bus architecture - been years since I looked at the schematic). Otherwise when the bus is tristated you will get junk. Could also trigger on a bus control line and watch one of the data lines to see if the data line is stuck. I'd love to get a broken C64 to fix and play with but they are expensive here!

[@jaycee1980]

Oh, another little tip I picked up from watching arcade board repair videos - those Fujitsu logic IC's are known for going bad ! When you see them, suspect them. I've seen it happen myself repairing a few BBC Micro's at the Centre for Computing History in Cambridge, UK where I volunteer

[@JanBeta]

That is good to know indeed. Thanks!

[@jaycee1980]

When you see a slow rise time like that, it's usually a sign that the bus is not being driven at all... the slow rise is often due to a pullup resistor. Sometimes this can be normal.... but typically not on an address bus! However in this case the address bus is split by muxes, because the VICII also generates addresses for the RAM. I know how you feel when you wanna give a stubborn system the middle finger all too well, i've had a few 500+'s with Varta damage just like that :)

[@JanBeta]

Ah, yes, that makes sense! It obviously really confused me to see a sloped signal like that on the address bus! :D And I feel you about the battery damage. Currently working on an A4000 with a lot of bad traces caused by the Varta. :/

[@lotharschwab8376]

"The things that ruin your day are often the most obvious ones" ... so true. When nothing makes sense or when the behavior is just off the charts, then we are likely to overlook the most obvious of things. The censored middle finger was priceless :)

[@JanBeta]

Thanks! Yeah, it happens a lot and can really kick your butt. I certainly learned a lesson. :D

[@transistorbaluba]

i was guessing leaking capacitors... but short ic-legs.. never crossed my mind. Well done! i was watching it to get my time going (3dprint a key for my paper-dispenser) it just bendt it self... so.. i made a hole int the dispenser, and placed a splint.. problem fixed.

[@MC-1173]

Jan, I feel your pain. Been there too. :) Very happy to see another C64 saved. And as always, another great video.

[@esshahn]

Very well done Jan, thanks for showing the failures as well, that's what we learn most from.

[@JanBeta]

Thanks. I certainly always learn the most from mistakes I make. :)

[@zuimelanieforno4654]

You are my Hero. Who was "stubborner" or was it "stubbornier"? It was Mr. Beta, the Savior of C64´s. 👌 It is very Kind, that You mentioned Mr. Peters. 💚💚💚 c.u. Zui 😎

[@bitoxic]

29:30 I think a lot of us have been there giving the middle finger at stubborn c64 repair! 😁 Can you please comment what was beeped out on 33:28?!😄

[@JanBeta]

No comment! ;)

[@tommyovesen]

Now I know what a wonky signal looks like. Great video Jan!

[@RudysRetroIntel]

Nice to see I'm not the only one getting frustrated with a repair. Great work! Flash codes can be a rabbit hole.

[@JanBeta]

Yeah, the flash codes usually work well if it is indeed broken RAM but in all other cases they can be really misleading... :D

[@claytonmoore9530]

Apparently, you didn’t hear me yelling “it’s the PLA” half way through. Lol Another great video. Thanks, Jan!!

[@Wikcentral]

I love the 425. Best picture and sound of all of the revisions imho.

[@JanBeta]

I like the 466 even better. Sturdier RAM chips, otherwise very much the same. :)

[@Wikcentral]

@@JanBeta I have stacks of spare ram chips. lol More 8kB in inventory than 32kB ;)

[@Even-Steven]

I always enjoy these videos, even if the investigation may seem frustrating. You didn't give up, and got the best result: a c64 was saved. The middle finger made me lol :) Thanks for sharing the journey!

[@diddyman1958]

29:00 Whistling "Mission Impossible" made me chuckle :)

[@JamesPotts]

Those two address lines are crazy. I wonder what loads them like that.

[@JanBeta]

It really confused me!

[@kudlok1]

Did I somewhat enjoy? I enjoyed the video a lot! Thanks, Jan!

[@Sephnroth]

Thanks for sharing this and including all the mistakes Jan! It's great to know it happens to everyone and for those of us learning really it's more useful to see things go wrong than to magically go right which is hardly ever a realistic experience!

[@850BRICK]

Great job. Well done for hanging in there.

[@giuseppelavecchia775]

Jan,hai dovuto tribolare su questo C64 ma hai vinto tu.sei il migliore.alla prossima amico,ciao.

[@SidebandSamurai]

You get a thumbs up for giving the C64 the bird! Great repair work. Always love watching you repair C64s

[@TheErador]

I had to laugh when you gave it the middle finger!

[@Starter61]

Great repair, great video. Congratulations one more time. The short chip legs thing was not of this world !

[@JanBeta]

Thanks! I felt stupid for not taking the short legs into account. It worked perfectly fine in my test machine! :D

[@runcmd8851]

Always love a C64 fault find video.. great work Jan..

[@JanBeta]

Thanks! It was quite the adventure this time! :D

[@claudiosalib774]

It is worth trying another power supply to check as to whether the power brick is at fault. 🤔

[@JanBeta]

I usually use one of my self-made, known to work power supplies for these repairs so I can pretty much rule PSU faults out. The original power supplies a notoriously unreliable indeed!

[@frazzleface753]

No need to apologize 😎Your videos are always great to watch 😊

[@JanBeta]

Thanks! Glad you enjoy the videos. This one was particularly messy though. :D

[@willyc7873]

I worked as an arcade game tech for 26 years and I had to laugh when you swore.... I remember the frustration of thinking for sure you found an issue only to have it make you feel like taking an axe to it when it proved you wrong... a familiar feeling lol

[@m4dizzle]

Love seeing that new Keysight DSO on the bench! It's a ton easier to read on video :D

[@JanBeta]

It is great to work with, too. I have yet to set up the network stuff that it has, I might be able to show crisp scope screen shots in the future, too. :)

[@m4dizzle]

@@JanBeta That'd be fantastic! I do have to say too that it's nice to see what you're probing and the scope's readings at the same time

[@admirerofclassicalelectron2858]

That wasn't an easy task but you managed it. Congratulation! Might be a satisfying feeling. The misleading slow rising signal, which seems to be wonky, could be a result of a (normal) tri-state high impedance condition. When no component drives that signal actively it goes slowly to high (or low or something between). And sometimes such a signal form indicates a real fault. Thats digital business.

[@w4twa]

Great video, looks a lot like my efforts, with same frustrations. Maybe it would be helpful if you did a series in which you scope every chip ,one at a time, on your functional computers. This way he people who do not have a working 64 to aid in our troubleshooting , could benefit from seeing what the proper waveforms should look like. I have a scope, but I’m not sure how the waveforms from each component should behave in a machine that is not sick. That old make my scope readings meaningful. Thanks again!!

[@JanBeta]

I remember seeing a guide on some C64 forum that had osilloscope readings but I can't find it now. :/

[@Thomaniac]

That was a really exciting episode :-)

[@skeptic10]

What I've been working on the long board ones, I first check the fuse. It it's ok, it's usually the PLA (like 80% of the time), then CIAs and then RAMs. With short board ones, it's never the PLA, but usually CIA's and then the RAMs.

[@ExFobtAddict]

Always a journey with Jan! Thank you for all the great informative content 👊 Much love London u.k

[@petesapwell]

Hi Jan, really enjoyed it, it’s sooo annoying getting trolled by a fault you accidentally caused yourself. All’s fine in the end :) have subscribed!

[@JanBeta]

Thanks Pete! Yeah, sometimes these faults can drive you to the completely wrong track. Glad I managed to fix this one in the end. :D

[@HuntersMoon78]

Only thing that died in my C64 was the SID, replaced it with a SwinSID Nano, OK replacement but not so good at the sound reproduction

[@KieronWray]

great video, fascinating trace through diagnostic process, and like others i lol'd when you swore and when you showed it the finger :)

[@SledgeFox]

Thank you, great to watch!

[@markgoldspink5109]

36:33 I felt that sigh in my soul. Great job.

[@JanBeta]

Thanks! This one sure took some emotional energy... :D

[@VincentGroenewold]

What would be great is to have the scope graphs of a working one saved, maybe in a program or database.

[@albertdelafuente9977]

muchas gracias Jan por tan ilustrativo vídeo aprendo mucho con ellos buen trabajo. Podías hacer un vídeo de como se construye un FE3 para el vic 20?

[@awilliams1701]

I know a lot of people suggest right off the bat to yank out the roms and the CIAs. Granted you only had one socketed. But a number of times when I realized you were having misleading results, I was suggesting it to the screen over and over again. lol

[@pb7379-j2k]

I agree with this. Jan indicated that the ROM shouldn’t matter because it’s switched out by the dead test. But the chip can still pull down or up any data or address line, right?

[@joopidema]

I was shouting at the screen REMOVE THAT PLA AGAIN! Haha, one can get caught up in these repairs! Well done.

[@dieSpinnt]

Thanks for the exciting thriller. Murphy gets us every time ... :) Nevertheless: the patient is alive!

[@orinokonx01]

Really enjoyed this one, a lot of great tips on troubleshooting a very odd problem!!

[@JanBeta]

Thanks! It was an easy problem to fix in the end. Made me feel stupid but I certainly learned a lot from this repair. :)

[@roheinz5007]

Wie immer: Ein super Video und ein Genuss zu schauen 👊🏼💥😊

[@MechaFenris]

Whew... that made me tired just watching! You have the patience of Job, sir! Well done! :)

[@Gerrysynth]

You have the patience of a saint jan, well done chap. :)

[@jimmy2drinks]

Thanks again Jan! :)

[@Radiocruncher]

What a nightmare Jan. well done for sorting it. Cheers Graham

[@robertturner4913]

I have really enjoyed watching this.

[@apb311]

A great example of the "Hunt and Peck" method of troubleshooting. Once you've replaced every component and it still doesn't work then you have become your own saboteur.

[@MrToast64]

Occam's Razor: "I suspect the PLA..." 48 hours later after exhaustive diagnostics and a few f-bombs..."It turns out the PLA was the problem!"

[@JanBeta]

Haha, yeah. :D

[@holleholl3057]

Misled by readings from the oscilloscope - and by way too short pins. Wow ! Aber jetzt haste ja (fast) alles auf dem Board gesockelt :)

[@jameslewis2635]

Part way through I was wondering 'will he end up socketing and replacing every chip on this machine?' In the end he was nearly there. The only way this would have been more agonising for Jan is if upon reasembling the machine it suddenly stopped working again. At that point C64's might fly (most likely out of a window).

[@JanBeta]

I was really close to giving up on this one. Glad I persisted and found the - admittedly stupid - fault in the end. :D

[@pb7379-j2k]

@@JanBeta my actual 466 64 that I bought used in the 90s is a case like this one. I have socketed almost everything and I still have the flash

[@RalonsoF1]

Grande, legendary Jan Beta! 👍👍👍

[@Berend70]

From mistakes you learn the most.. and in the end a working c64.. bravo again Jan...is it possible to check if the short pins make or don't make contact on the board?

[@JanBeta]

Thanks! You could check continuity with the board of course. I didn't think of that because I just assumed the PLA would work after testing it in the other board and didn't look into it any further. Lesson learned for sure! :D

[@philchurch927]

Jan has the patience of a saint !!

[@EudesRJ]

Since this case already have 2 holes on it, how about putting 2 switches on it? One to switch kernels and other to switch between PAL and NTSC?

[@nefaurora]

Never give up....Never Surrender!.....Sometimes we have to walk away to come back another day! :) Kudos Jan Beta....!

[@KolliRail]

Well... That reminded me of Noel's latest C64 video... And don't forget: If it shows a black screen, it is almost always the PLA! ;-)

[@JanBeta]

Noel's video certainly was an inspiration for making another C64 video. I just didn't think I would end up with an equally messy repair! :D And, yeah, it kind of was the PLA. But it still works fine in the other machine. That one really got me!

[@lenniegodber7805]

Every time there’s a shot in this guy videos that points out his window all I can think is ‘A tall nondescript building with minimal windows. Why does it look like he lives in a prison?’

[@necro_ware]

We call it Germany :D

[@TheMovieCreator]

Tip for quick-testing DRAM: If you suspect one chip is bad, you can piggyback a known good chip right on top of it. Bad DRAM usually don't drive its output, so the known good chip which is tucked on top takes precedence.

[@JanBeta]

Yes, I use that method frequently.

[@Raul_Gajadhar]

Very helpful and informative video for me.

[@rdwoodw]

I enjoyed this video immensely....it was like a hawk chasing a squirrel around and up and down a tree trunk for 40 minutes.

[@JanBeta]

It was a real head scratcher! Glad you enjoyed the journey. :D

[@SimonEllwood]

Testing the logic chips in a TL886 like Noel may be a good plan.

[@JanBeta]

Yes, definitely! I was about to do it in this repair but I figured out that the ICs were okay before I even got the TL866 out... :D

[@Plan-C]

Awesome job as usual Jan.

[@jdryyz]

I enjoyed the Mission: Impossible theme. :)

[@DragoKraner]

Great video, where can i get sockets pack for all main chips CPU, PLA, SID,...

[@necro_ware]

Hi Jan! Thanks for the exciting content. Do you know what the diodes left of 7406 IC are for? I repaired one C64 a year ago and it had such diodes there as well. They looked pretty much self made and I removed them, but I'm still curious why they were there at all. The repaired C64 works at least like charm until today without that diodes.

[@danielmantione]

These diodes protect the lines of the serial bus. Excess voltage on these lines is directed to VCC, where it cannot do much harm. With these diodes you are much less likely to destroy a CIA a static discharge of you touch the signal lines on the bus. They were clearly not part of the original plan, but warranty claims may have made Commodore to add them.

[@necro_ware]

@@danielmantione I see, thank you very much.

[@_mcdope]

"Today in the lab..." I see what you did there, watching Fran too it seems :D

[@JanBeta]

That wasn't even intentional! Although I am indeed a huge Fran fan. Possibly watched too many of her videos... :D

[@ojkolsrud1]

@@JanBeta Hehe, Fran fan. I am one too!=D

[@Ramdileo_sys]

@@JanBeta aahhhh.. at 28:58 ..... due to "the music"..... I thought that "this C64 will self-destruct at 29:10" :-D ... by the way ... do you see the @Techmoan videos about the Mission: Impossible Reel to Reel pocket corder?? >> kzbin.info/www/bejne/bHWxcqB6js6obM0

[@hansoak3664]

@@JanBeta There is no such thing as too many Fran videos. :)

[@winstonsmith478]

Where'd you hear about too much boron in the IC die insulation layer? I've always wondered why MOS Technology manufactured ICs seemed to be a major failure point and suspected it must be something in their manufacturing process or too much power dissipation or power dissipation not properly distributed on the die surface or a combination of those.

[@JanBeta]

Ex-Commodore engineer Bil Herd mentioned it in some of his talks/interviews. He didn’t know about what exactly was wrong with the chips until recently it seems.

[@danielmantione]

According to the PLA dissected document, they bought Frontier semiconductor and tried convert their fab to NMOS. This is where it went wrong with boron and chips produced in this fab have high failure rated. Chips produced in the MOS Technology fab are much more reliable.

[@winstonsmith478]

@@JanBeta Ah, OK. I've watched many of his videos and in the past he was always excusing the failures as, basically, "what do you expect from chips this old" which was never acceptable to me since there are plenty of ICs not made by MOS that still work just fine in even older hardware.

[@winstonsmith478]

@@danielmantione Peoples Liberation Army? 😎 Starting at approximately what date would the ICs be more reliable? It would be interesting for those who save the bad ICs they've replaced, like Adrian at Adrian's Digital Basement, to take a look at their inventory.

[@danielmantione]

@@winstonsmith478 Programmable Logic Array: ftp://ftp.zimmers.net/pub/cbm/c64/firmware/C64_PLA_Dissected.pdf According to what we know, the bad years were 1983 and 1984. In 1982 the Frontier Semiconductor fab wasn't operational yet, in 1985 the problem was solved.

[@guillaumegaudin694]

18:00 at this point, you could have tried to cut the pin on the suspected chip and checked if that solved the issue on the other components

[@RavenWolfRetroTech]

Awesome video, I enjoyed the process and was really surprised that the address signal was normal, that looked terrible (Sawtooth binary anyone).

[@w0lfgm]

Maybe turn your old phone camera into the thermal for testing.

[@ralfr.5974]

You bring Another C64 back to Life!! Great👍👌

[@JanBeta]

Thanks! It was quite a mess but always good to have another C64 back in business. :)

[@ralfr.5974]

@@JanBeta Great Job Jan!! Thumbs Up!!💻👍👍👍

[@nerdygeezer78]

Wow this one was a real slog for you..... glad you got it fixed in the end

[@JanBeta]

It was driving me nuts! :D

[@asdfasdfasdf12]

I love it, that even with your experience you can get to the wrong slope of analysis! Just fixed up a my first dead c64 from ebay, somehow I love fixing things now...damn..bought ebay empty with electric utils and stuff

[@radio655]

Jan, where did you get this nice IC extraction tool? Can you recommend it?

[@Doug_in_NC]

In the text he gives a link to all of the equipment he uses. The IC extraction tool he links to is available on Amazon - in the US it’s a bit under $25.

[@Torbjorn.Lindgren]

The silver one at 9:45? - I'm guessing it's a Jonard EX-2 (24-40 pin chip extraction tool). It's not the cheapest tool and the usual suspects (like AliExpress and eBay) have much cheaper all-plastic variants going by the name GJ-3 (16-22 pin) and GJ-6 (24-40 pin), search for "Chip Extractor GJ-6" (or GJ-3). For casual use the plastic ones are fine and has a variant for smaller chips that Jonard doesn't make (it's *less* useful for smaller chips but it's still nice to have), I expect that Jan use his enough for it to make sense to go with the high-quality option. At 17:56 we see the standard "flat" extractor lying on the desk (it's used shortly afterwards), it's the one with yellow handle (green and blue are also common), this is usually the first one everyone gets because it's usable in so many situations even if you can get by without one. The second extractor people get is usually a PLCC extractor because PLCC's are *hard* to get out without damage if you don't have one.

[@JanBeta]

What Torbjorn says. It's a Jonard EX-2, I can definitely recommend. Makes things a lot easier and doesn't bend any pins etc during extraction.

[@radio655]

@@JanBeta Excellent, thanks! Amazon DE is sold out on it currently so I hope it is back soon.

[@stevenspmd]

@Jan Beta is the your dead test cartridge modified or stock? I have a borked machine with an overworked motherboard .. I'm thinking I want to replace it with a SixtyClone and extra debugging is always a good thing.

[@anno5936]

hahaha... 29:00 "Mischen impossible" ... when all replacements do not work.

[@r.d.machinery3749]

I think the Commodore 64 is going to need a fan if you leave it on for extended periods of time. The reason is that one of my Commodore 64s with heatsinks on the chips gave me a black screen after a week of being left on. I switched it off for a few hours and it came back to life.

[@mattcole6230]

Was great watching this and the Atari ST renovation

[@andreasu.3546]

1:33 It was made in England. Definitely not out of Cadillac muscle though.