Ingo Korb

I'll assume that you mean GAME=1, EXROM=0 (i.e. not Ultimax mode) since you mention RAM at $8000 and there is no RAM in Ultimax mode at that address. Why do you think that this configuration should enable the cartridge ROM when LORAM=0, HIRAM=0? To my knowledge that is not what a correctly-working C64 would do and also contradicts multiple sources about the memory map, e.g.: https://archive.org/details/transactor-magazines-v6-i05/page/n55/mode/2up (oldest known public PLA reverse engineering) https://www.zimmers.net/anonftp/pub/cbm/firmware/computers/c64/pla.txt...

improve checkstyle.sh compatibility with non-GNU systems

The current behaviour is correct. Since the C64 can read back the oscillator state of voice 3, pitching it down to compensate for increased emulation speed would allow a program to detect that it is running on an emulator - but since an emulator's goal is to work exactly as the original machine, that would be a bug. Furthermore, pitching down the SID would lead to inconsistent pitch if the program is playing samples - like Impossible Mission does. Sample playback on the C64 is fully CPU driven, the...

On a real C64 it's actually a real locking switch that is connected in parallel with the left shift key.

Remapping the caps-lock key to something more useful is not that uncommon. Depending on the method the software may see an actual control keycode instead of capslock.

You're not limited to the high byte of the (in-incremented or current) address, if the dummy read hits a non-open memory address its content will stay on the bus.

You're not limited to the high byte of the (in-incremented or current) address, if the dummy read hits a valid memory address that value will also stay on the bus.

That's an unfortunate quirk of autoconf: It only checks if it can use a certain library, but it cannot tell why using that library fails. If it has some further dependency that is broken, the only thing it will print is that the library is looking for is not usable.