Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08625 Interface Minor Always May 3, 2023, 01:59 May 9, 2023, 08:20
Tester Robbbert View Status Public Platform MAME (Self-compiled)
Assigned To cuavas Resolution Fixed OS Windows 10/11 (64-bit)
Status [?] Resolved Driver
Version 0.254 Fixed in Version 0.255 Build 64-bit
Fixed in Git Commit abd47e6 Github Pull Request #
Summary 08625: UI: Not possible to start sarpc from the UI
Description See steps to reproduce, below.
Steps To Reproduce Start MAME.
Make sure "Unfiltered" is selected.
Type in sarpc
You should have "StrongARM Risc PC" (sarpc) at the top - not to be confused with sarcpc.
Hit enter to run.
You get the message "Required ROM/disk images for the selected system are missing or incorrect. Please acquire the correct files..."

This message is incorrect - you can get all the files it's possible to get, and you can never start this system from the UI.
Additional Information
Github Commit
Flags
Regression Version 0.226
Affected Sets / Systems UI
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
3
User avatar
No.21394
Haze
Senior Tester
May 3, 2023, 13:13
I'm not even sure why the set exists, everything in it is NO_DUMP

the only ROMs it expects are device ROMs, which don't appear to be unique to this set.

it does not appear to exist to hold a Software List either

so why is it even there
User avatar
No.21395
Tafoid
Administrator
May 3, 2023, 19:35
edited on: May 3, 2023, 19:36
Prior to 0.226, MAME loaded (or attempted to load) this entry correctly.
I traced the commit which appears to have opened this up to failing internal audit so it will no longer run.
October 3, 2020: https://github.com/mamedev/mame/commit/aca0aaaa3d6870f0372316912031794329a5ca41
I have not checked the full day's commits, so I can't confirm 100%.
07410 is listed as fixed this commit, but as mentioned also a previously resolved one in 07756 might have regressed.
User avatar
No.21409
cuavas
Administrator
May 9, 2023, 05:33
Oh this is stupid. It thinks it’s not found when no ROMs for the system or its parent are found, even though it doesn’t share any ROMs with its parent at all. Attempts to hide “missing” ROM sets all end up being a cure worse than the disease.