Wiki editing discussion

Ah.... I see the problem. I will fix that.

Yes, but not by selecting a language when using a firmware.

Does this have any influence on the aera bit of the RTC?

In fact, it's Sony that makes specific use of this bit so you were correct in this case. Must say that the standard is not clear about the use of the bit. And to make matters worse, Sony got the code wrong. Anyway it would be interesting to know who is right. Sony or the datapack?

Wiki writes:

That reason is totally unclear. Who checks that byte in which way and how does it conclude what exactly is normally working?

Another blueMSX extra setting also exists, but only for Russian Yamaha computers with network. It probably checks if the MSX-Network is correctly working (value 0Dh when all is OK).

These extra blueMSX settings don't correspond to a register in the RTC chip.

The blueMSX code just writes 4*13 bytes from the RTC registers the the file, as far as I can see:

    UInt8 registers[4][13]; 
...
    if (rtc->cmosName[0]) {
        FILE* file = fopen(rtc->cmosName, "w");

        if(file != NULL) {
            fwrite(rtc->registers, 1, sizeof(rtc->registers), file);
            fclose(file);
        }
    }

So, I can't even explain why it would write more than 52 bytes... and it also only reads the same number:

        file = fopen(cmosName, "r");

        if (file != NULL) {
            fread(rtc->registers, 1, sizeof(rtc->registers), file);
            fclose(file);
        }

I don't think. It's more confusing, as you transform the normal registers from blocks 1 to 3 in 'extra' registers when they are converted into a file by both emulators. Actually, it's the same registers but with a different number, because the emulators don't generate 4 files, one for each block, but only 1 file.

@Manuel: one thing is the code, another thing is the file effectively stored by blueMSX. The differences are probably generated by another part of the code, still for reaons I ignore.