04504: blitz2k: Cannot change settings in test mode (always fails)

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
04504	DIP/Input	Minor	Always	Oct 7, 2011, 05:58	Oct 9, 2024, 13:55

Tester	geforcefly	View Status	Public	Platform	MAMEUI
Assigned To		Resolution	Open	OS	Windows Vista/7 (64-bit)
Status [?]	Confirmed			Driver	midway/seattle.cpp
Version	0.143u6	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	04504: blitz2k: Cannot change settings in test mode (always fails)
Description	Attempting to make any adjustments in the test mode always fails. It also shows in the additional adjustments that all current settings are invalid.
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	blitz2k

Attached Files	0001.png (8,982 bytes) Oct 7, 2011, 12:53 Uploaded by Fujix
Attached Files	0000.png (9,607 bytes) Oct 8, 2011, 05:52 Uploaded by geforcefly POST from the original NFL Blitz... same FBI Memory error.

No.07820 Fujix Administrator Oct 7, 2011, 12:55	Confirmed the issue. When I turn on the boot up diagnostic by the dip option, it fails to pass "FBI Memory Test", maybe this has to do with this???
No.07822 geforcefly Tester Oct 8, 2011, 05:51	Also to note: in the disk tests, the surface scan stops at sector 16,048 of 16,065. The disk data integrity tests also fail. Blitz 99's surface scan stops at sector 992 of 1,008.
No.14026 tedgreen Developer Jul 30, 2017, 14:46	I strongly suspect that the boot rom version / chd version are not compatible. The current MAME boot rom POST message is: Phoenix Seattle R5000 BIOS for Blitz 99 - $Revision: 4 $ There is also a post on KLOV stating that the MAME chd does show/save the proper settings on the real hardware either. https://forums.arcade-museum.com/showpost.php?p=3401519&postcount=2 We need someone with actual hardware to verify if the MAME boot rom and chd are correct.
No.22368 Robbbert Senior Tester Oct 9, 2024, 13:40	A bit more info in https://mametesters.org/view.php?id=8935 , which being a duplicate, has been closed.
No.22370 JimCarlTay Tester Oct 9, 2024, 13:55 edited on: Oct 9, 2024, 13:56	I suspect that the CHD file or one of the ROM set files (maybe an incompatible boot ROM) may be a bad dump given those notes above.