1
clrmame Discussion / Built a non-merged romset, but get missing BIOS errors?
« on: 15 June 2022, 09:18 »
Hi all,
Apologies in advance if this is a silly question.
I recently used clrmamepro to build a MAME 0.235 non-merged romset.
I used the following sets to build this romset:
0.235 romset merged
0.232 romset non-merged
Updated roms between 0.234-0.235
Updated roms between 0.232-0.233
I thought the more sources it had to pull from the better chance at building the set, but could of course be wrong.
I also unselected the option to "Separate BIOS sets", as I was under the impression this would include the BIOS file in each rom created so it could run standalone?
After creating the romset, I then did a scan and got the following results, in the attachment, which seems to indicate everything appears ok (minus a few missing sets).
I then ran the romset through LaunchBox to create a smaller set and remove games that don't work, etc.
But when I attempt to run some of the games in MAME 0.235, it advises of missing BIOS files (the example shown in the attachment is "19xx.zip")?
Apologies in advance if this is a silly question.
I recently used clrmamepro to build a MAME 0.235 non-merged romset.
I used the following sets to build this romset:
0.235 romset merged
0.232 romset non-merged
Updated roms between 0.234-0.235
Updated roms between 0.232-0.233
I thought the more sources it had to pull from the better chance at building the set, but could of course be wrong.
I also unselected the option to "Separate BIOS sets", as I was under the impression this would include the BIOS file in each rom created so it could run standalone?
After creating the romset, I then did a scan and got the following results, in the attachment, which seems to indicate everything appears ok (minus a few missing sets).
I then ran the romset through LaunchBox to create a smaller set and remove games that don't work, etc.
But when I attempt to run some of the games in MAME 0.235, it advises of missing BIOS files (the example shown in the attachment is "19xx.zip")?