ROM name oddity

Here’s a strange one. Updated my Beagle’s ROM today. Instead of the new copy overwriting the old, two copies appeared in the Loader partition. Seems that due to a typo I’ve been running RICOS for the last week. It’s been running fine. I didn’t think that possible. Had to re-install the boot files as deleting the erroneous copy killed it.

On the Pi, I use the CONFIG.TXT file to switch between RISCOS (my build) and RISCZP (a recentish official nightly).
I just need to ensure that I load the SDCMOSZP (a binary hack) module or else settings will be written into the wrong ROM image. ;-)

On the Beagle, I used the USER button to switch between two different copies of RISC OS.

Instead of the new copy overwriting the old, two copies appeared in the Loader partition.

A well known issue, much discussed. It will happen (for example) if the file name is not upper case.

Might this be an appropriate forum to ask about the RPi firmware?

I have seen that to get the RPi3 working it is advised/necessary to use the most recent firmware. Is this backwards compatible as we RISC OS users might expect?

Will something – the FAT partition Loader contents – prepared for the RPi3 work equally well on the earlier models, or is this hoping too much?

I realise the CONFIG/TXT will probably need to be individually tailored.

Will something – the FAT partition Loader contents – prepared for the RPi3 work equally well on the earlier models, or is this hoping too much?

Yes it will. With some caveats – some RISC OS software will not run on the Pi3.

See this thread

I realise the CONFIG/TXT will probably need to be individually tailored.

No, I don’t think so.