07756: UI: ROM sets incorrectly reported as not found.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07756	Interface	Major	Always	Sep 19, 2020, 07:10	Sep 27, 2020, 07:31

Tester	VasiliyFamiliya	View Status	Public	Platform	MAME (Official Binary)
Assigned To	cuavas	Resolution	Fixed	OS	Windows 10 (64-bit)
Status [?]	Resolved			Driver
Version	0.224	Fixed in Version	0.225	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07756: UI: ROM sets incorrectly reported as not found.
Description	Certain machines are incorrectly reported as not found when auditing. This prevents them from being launched from the internal UI. Examples of affected system include "snes" and "fds".
Steps To Reproduce	Just open the emulator and select SNES (NTSC) from roms menu.
Additional Information	MESSUI v0.224 hasn't this bug.
Github Commit

Flags
Regression Version
Affected Sets / Systems	UI

Attached Files

No.17989 Robbbert Senior Tester Sep 19, 2020, 13:42 edited on: Sep 19, 2020, 13:50	Amazingly, I can confirm this. Type snes in the search field, this brings "Super Nintendo Entertainment System / Super..." to the top. Hit enter, you get the red message that roms are missing. Just to be helpful, it doesn't say WHAT is missing. When run from the command-line, it doesn't complain at all, but it needs a mandatory cart. MESSUI ignores the mandatory requirement, and so running without a cart produces the expected black screen.
No.17991 Robbbert Senior Tester Sep 20, 2020, 00:59 edited on: Sep 20, 2020, 01:03	"fds" also has this issue - see https://forum.mamedev.org/viewtopic.php?f=14&t=543 which I can confirm. Type fds in the search field, this brings Famicom (w/ Disk System add-on) to the top. Press enter and get the red screen. Running fds from the command-line gets an in-game message, but it is running as expected.
No.17992 Robbbert Senior Tester Sep 20, 2020, 01:06 edited on: Sep 25, 2020, 11:22	~~It looks like this issue occurs for any set that doesn't have roms, the message "romset not found" being misinterpreted as an error.~~ above was wrong conclusion
No.17999 cuavas Administrator Sep 25, 2020, 10:20	But SNES does need ROMs, as does the FDS: `mame64d.exe -listroms snes ROMs required for driver "snes". Name Size Checksum spc700.rom 64 CRC(44bb3a40) SHA1(97e352553e94242ae823547cd853eecda55c20f0)`
No.18000 cuavas Administrator Sep 25, 2020, 10:24	`mame64d.exe -listroms fds ROMs required for driver "fds". Name Size Checksum rp2c33a-01a.bin 8192 CRC(5e607dcf) SHA1(57fe1bdee955bb48d357e463ccbf129496930b62) rp2c33-01.bin 8192 CRC(1c7ae5d5) SHA1(af5af53f66982e749643fdf8b2acbb7d4d3ed229)` You’re going to have to come up with a better explanation of this bug, because the description right now doesn’t make sense.
No.18001 cuavas Administrator Sep 25, 2020, 10:55	At any rate, 44416bee2d3b14dabc32df064f93af5b6bb740c0 caused MAME to incorrectly report sets as not found, preventing them from being launched from the built-in UI. It doesn’t affect machines that don’t have ROMs, though.