A month ago, my K6-2 system suddenly stopped POSTing. I tried swapping the RAM modules, replacing the CMOS battery, removing expansion cards and adjusting connectors to no avail. I even measured the 5 V-to-3.3 V regulator and found out it was operating within spec.
Without much else to try, I simply assumed the motherboard was dead and left matters there.
Today, I got desperate and thought I'd power the system on one more time. It worked right away!
Once the initial excitement wore off, I got around to testing a silly idea I had cooked up a month ago – to run TempleOS on a processor nowhere near the minimum requirements.
I already knew QEMU could emulate x86-64 on newer processors, allowing Windows 10 to "run" on a Pentium II.
I gave the last Windows XP-compatible build of QEMU a shot, only for it to crash. Running a debugger revealed that the program was trying to execute the now-ubiquitous cmov instruction. I was thinking I could patch it out, but a search in a disassembled listing of the binary came up with over a thousand instances. I wasn't going to spend a quarter of a year on this experiment, so this idea had to go.
I soon switched my focus to Linux. This computer multiboots with Arch Linux 32 – a distribution that happens to provide an i486-compatible build of QEMU. I was golden, or so I thought.
Any attempt to start QEMU with a graphical front-end caused a segmentation fault. The kernel log suggested that the fault took place in the graphics driver, nouveau_vieux_dri.so. The Nouveau website has a section pertaining to this driver, ending with the following message:
Do not file bug reports about this driver.
Sigh. And they say Linux breathes new life into old hardware...
Now that I was back on Windows, I could only hope an older build of QEMU supported the K6-2. I tried one dated November 19, 2011; sure enough, it worked, and I was able to play Varoom at a blistering 12 seconds per frame!
I've had the time of my life
I've never felt this way before
Yes, I swear, it's so true
I'm holding onto used hardware