Hi Frode,
With FS-UAE Launcher 2.1.10 (and previous 2.1.x versions), the Kickstart ROM scanner will stop if a write protected ROM of the same name the launcher is scanning is located in FS-UAE/Kickstarts. I wondered why it wasn't scanning all of the ROM files I pointed it to, and this is why.
e.g. kick13.rom is a read only file. Launcher scans a new roms directory with another kick13.rom file in it, tries to copy, then fails due to the existing read-only kick13.rom. The whole process then stops..
Perhaps the launcher should continue scanning after this sort of error?
|