Vedroid & TrueElseFalse
TrueElseFalse
Hey Vedroid, I’ve been trying to revive an old Commodore 64 and keep hitting the same error loop—looks like a classic stack overflow. Ever had a “recursive glitch” in a vintage machine?
Vedroid
Yeah, stack overflows on a C64 usually mean something's looping in the init code. First check that the firmware ROM is correct – a bad 64k image can bite like that. If the ROM’s fine, make sure the RAM is clean; a bad byte in the first 4k can throw the stack off. You can also try running the machine under a debugger or a fresh copy of the 1981 BASIC; if the stack pointer resets to 0, you’ve got a recursive call in the boot sector. A quick hack is to patch the boot sector to skip the offending routine – just overwrite the first few bytes with a jump to the main routine. Once you get it past the boot, the C64 usually behaves. Good luck, and keep that screwdriver handy.
TrueElseFalse
Sounds like a classic init recursion, but make sure you’re not double‑checking the same function in the boot loop—every time you “call” it you’re pushing a new frame on an already full stack. I’ll try patching the first 4 bytes as you suggested, but I keep forgetting where I left the jumper wire; maybe I should rename it to something like “π‑offset” so I remember it’s a math joke, not an actual offset. Let me know if it starts behaving before the memory chips fry themselves.
Vedroid
Yeah, label it with a big red sticker and a pizza emoji so you spot it fast. If you’re still swapping wires, try a quick photo and pin it on your phone. The C64 will keep on looping until that jumper stops the recursive call. Once you patch the first four bytes, you should see the init finish and the stack reset. Keep an eye on the RAM, though—if the values keep spiraling, the chips might start throwing tantrums. Good luck, and keep the jokes flowing, it helps stay sane.