Peter KreftingIf a #Commodore64 starts up with an Out Of Memory error, that's probably not a good sign.
root42@root42 Long board, this is an early model, they stopped selling Swedish C64s when Handic went out of business, IIRC.
@root42 I need to read up on chips to see which one is which.
I don't know the history of this unit, I think my father received it as broken from someone.
@nafmo they are not μT RAMs. That’s good. Could also be the PLA, Muktiplexers or something else. Needs more analysis, maybe test with DesTestMax and DeadTest /DiagROM.
@root42 Can any of the diagnostics cartridges be flashed onto a Retro Replay?
It can boot into the Retro Replay cart. With that I can get it to boot into BASIC with "38911 bytes free", but FRE(.) now reports -26627.
@root42 It was a wild chance, I got a Retro Replay when those were new and hot (this stuff has been sitting in storage since 2006…), so that's what I have to work with.
Maybe I should just keep it as a donor for a SID to a future 64 Ultimate?
@nafmo No! It can be fixed and MUST be fixed. :)
SID replacements are cheap and plentiful. These quirky machines are not.
SID replacements are cheap and plentiful. These quirky machines are not.
@root42 *If* I can find a diagnostics cartridge that I can flash to the RR, I'll have a go at that.
I'm a software engineer, not a hardware one. I'm horrible at fixing hardware. 🙂
@root42 For reference: I used FMGPUCCRBRR from https://csdb.dk/release/?id=39383 to create a cartridge image that I flashed on the RR.
The boot menu doesn't display on the broken C64, but the programs do start.
@root42 I don't think so.
https://gitlab.icomp.de/c64-dev/replay/-/tree/main/flashutility?ref_type=heads is the closest I have to documentation.
Looking at the old files I have, I bought this in 2000 or 2001 :-)
(EDIT: It was released late 2001)
@root42 It can run anything that runs on Action Replay hardware, since that is what it was set out to emulate.
(I grew up with a TFC3, so I never quite did get along with it)
@root42 Looks like one of the eight RAM chips is uT, according to my colleague, who does hardware, it looks like the other 7 have been swapped at some point.
@root42 There was also some stuff that had come loose, but soldering that back up didn't help.
We'll try switching the bad chip (at some later point in time) and see if that helps.
I'd really love to have a proper localized C64. They had stopped selling them by the time I bought mine.
@root42 I've ordered a set of 4164 chips now. Maybe I'll get lucky.
The board shows signs of having been tampered with before, perhaps a previous attempted repair that didn't work?
@root42 This seems to indicate a single bit failure, which, according to the schematics, matches the one chip that was not the same as the others...
@root42 Success! Now the test runs through without issues!
@root42 Yes, it's not that easy to see on the small screen I have available at the office.
The old Commodore diagnostic tool didn't like them, though, being the Swedish localisations..
So, it looks like that Swedish KERNAL EPROM is socketed... Does anyone know if there is a Swedish localized #Commodore64 #JiffyDOS around that one can get from somewhere?
14 iterations without reporting any errors!
The old PSU started smelling a bit funny, so I think it is best avoided. I bought one from https://www.c64psu.com/ that works like a charm, though.
Finally got around to open my 2017 birthday gift from Mermaid! #PondSoftware #TheBearEssentials #Commmodore64
That's exactly the same chip that the diagnostic I ran a month ago blamed, BTW.
https://social.vivaldi.net/@nafmo/115288762186806724
But now I have a KFF2 cartridge to play with (I wanted an S-Video cable, and since I had to pay import duties anyway I'd added some more stuff to the order...)
Peter Krefting (@[email protected])
Attached: 1 image @[email protected] This is as far as the diagnostics I found on CSDb got before crashing.