07983: Warp-1 (Japan): Warp-1 (Japan) fails in UI, but works from CLI

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07983	Interface	Minor	Always	May 22, 2021, 17:44	May 22, 2021, 20:18

Tester	gspat	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Invalid report	OS	Windows 10 (64-bit)
Status [?]	Closed			Driver	sunelectronics/dai3wksi.cpp
Version	0.231	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07983: Warp-1 (Japan): Warp-1 (Japan) fails in UI, but works from CLI
Description	starting MAME and selecting "Warp-1 (Japan)" using built-in UI, it shows wrong checksums popup and fails back to UI with the following in Windows CLI: System media audit failed: tvg_23.6 (2048 bytes) - INCORRECT CHECKSUM: EXPECTED: CRC(c956b3a8) SHA1(1e90d3480ac8ebb26eed5800a453b2b9484a8b05) FOUND: CRC(2025a316) tvg_26.9 (1024 bytes) - INCORRECT CHECKSUM: EXPECTED: CRC(840c1a75) SHA1(63853e560c0fba5600a8ad0408cc9e7a55db6d93) FOUND: CRC(6bf25327) However, run straight from Windows CLI, the machine starts up and plays fine (albeit flipped as cocktail) with the following info on the CLI: tvg_23.6 WRONG CHECKSUMS: EXPECTED: CRC(c956b3a8) SHA1(1e90d3480ac8ebb26eed5800a453b2b9484a8b05) FOUND: CRC(2025a316) SHA1(704798ec1d0039cb977396330801a625c8b02cff) tvg_26.9 WRONG CHECKSUMS: EXPECTED: CRC(840c1a75) SHA1(63853e560c0fba5600a8ad0408cc9e7a55db6d93) FOUND: CRC(6bf25327) SHA1(ee9f635d70a97628ab82efa12efdb39349b52e2b) WARNING: the machine might not run correctly. Average speed: 100.05% (100 seconds) SHA1 for found ROM checksums is missing when using UI
Steps To Reproduce	Start MAME from CLI > Select "Warp-1 (Japan)" (Fails back to UI) Start MAME without UI from CLI using "mame warp1" (Works! But flipped)
Additional Information	Using 0.231 (mame0231-374-g6df539817dd) - (Compiled using official toolchain on 05/21/2021)
Github Commit

Flags
Regression Version
Affected Sets / Systems	Warp-1 (Japan)

Attached Files

No.18878 Tafoid Administrator May 22, 2021, 18:51	The roms have changed. Current Git with correct roms also display correctly. Delete all warp*.cfg files, update roms and try again.
No.18880 Tafoid Administrator May 22, 2021, 19:40	Just to clarify - MAME's built-in UI does not allow usage of romsets with any differences from what is 100% expected. It will tell you it is wrong and not launch the emulation. Command line launching has certain 'cheats' built-in to assist development as a hash/label change to test other sets to be added is common and therefore, while it still let's you know there are mismatches, the machine will start in those cases.
No.18881 gspat Tester May 22, 2021, 19:50	[SOLVED] New ROM Updated