Hi! I've installed batocera for my Odroid C2. It's already very neat that there's an image for this platform!

I have a couple of starter questions:

1. It took a moment to figure out how to name TOS images so that they launch. If I ask the UI to check for missing bios files, the system can see the /userdata/bios/tos*.img files I've put in place, listing the ones that are missing. So that's good. But the launcher will always tell me there's no ROM for the system, asking if I wish to proceed.
   If I enter the per-system advanced settings and select Hatari as my emulator, Hatari will launch even with that warning, using one of the TOS ROMs in the directory. But if I stick to "Libretro: Hatari" (the default), it doesn't launch and I have no way that I can see to specify the TOS ROM to use.
   Question(s): should 'Libretro: Hatari' work? Why does the launcher complain if the system sees some appropriate files in the bios directory? (Do I need a copy for all potential ROM versions listed?) The logs look like this. Finally, is it somehow detrimental to just run "plain" Hatari?

2. I see files like /overlay/base/usr/lib/python3.10/site-packages/configgen/generators/hatari/hatariGenerator.py and /usr/lib/python3.10/site-packages/configgen/generators/hatari/hatariGenerator.py, which are identical. For my understanding of the system beneath, is one of these the "authority", and one just a copy? One isn't a symlink to the other, so curious about the duplication. I can see it might be beneficial for me to skip the magic in the future and just hardwire, say, an emutos image.

3. Hatari version 2.3.1 is installed in this image. This is probably going to be fine for what I want, but is it possible to build and install more recent binaries for my platform? Understand the Odroid C2 is a niche/old platform and it's already a blessing that batocera has an installable build for this! Thinking about future maintenance.