I remember one particular one a few decades ago, where I was feverishly (pun intended) trying to achieve something with XML, only it being a fever dream, nothing of it made sense, so I was wracking my brain for nonsense those entire hours.

The first color was obvious to me, as it was designed to be (it even tells you if you intentionally misclick). But at the very next color, the first "test color", I literally face palmed and said "oh my god" out loudly.

It was so, so hard for me to decide. I really just wanted to pick a non-existent "teal" option. Both "blue" or "green" felt wrong and equally right at the same time.

It just got harder from there. At the end, it told me that my threshold is "bluer than 80% of the population", but honestly, I don't think that's really true in my case. I was so ambivalent, my choices really felt random to me very quickly.

But yeah, it may not make a real impact yet anyway.

(Or maybe not, if it doesn't perform better than random, I haven't actually tried it out yet. Some more examples would have been nice!)

I wonder how far you could push this while still staying period correct, e.g. by adding a REU (RAM Expansion Unit), or even a GeoRAM (basically a REU on steroids).

SuperCPU would also be an option, but for me it's always blurring the line of "what is a C64" a bit too much, and it likely just makes it faster anyway.

I also lost the game not too long ago, but before that, I think I didn't actually lose it for a decade of more? And losing it wasn't even because it was mentioned anywhere, I genuinely just thought of it by myself, after forgetting about it for so long.

So my sincerest apologies if my comment just made any readers lose their long streak in the game.

What I'm saying is: I still feel (perhaps wrongly, quite possibly so) that in 1997, changing the global volume was more common, and that even being able to change app-specific volumes required some non-trivial features from the app who can do so.

If you turned off the preamp (could be directly done in the EQ window I think), what did the volume control actually do?

And I’m not sure if that was still the case in 1997, but most likely changing the volume of digital sound meant the CPU having to process the samples in realtime. Now on one hand, that’s probably dwarfed by what the CPU had to do for decompressing the video. On the other hand, if you’re already starved for CPU time…

Side note: virtual 8086 mode was protected mode, or rather, implied protected mode. A task could run in virtual 8086 mode where to the task it was (mostly) looking like it was running in real mode, when in actuality the kernel was running in full protected mode.

Note that the "kernel" was never DOS. It could often actually be a so called "memory manager", like EMM386, and the actual DOS OS (the entire thing, including apps, not just the DOS "kernel") would run as a sole vm86 task, without any other tasks. The memory manager was then serving DOS with a lot of the 386 32 bit goodness through a straw, effectively.

It's very bizarre from today's (or even back then's) OS standards, and evolved that way because compatibility.

(It's fun to note that I try to type out "virtual memory" in this thread, because I don't want people to think I talk about virtual machines.)

Sure, you're still better off with 24 GB overall compared to 8GB+swap whether you add swap to your 24 GB or not, but swap can still make things more better.

(That says nothing about whether the 2x rule is still useful though, I have no idea.)