08804: p9112, wcombat: Outdated comments in the Konami Viper driver file.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
08804	Documentation	Trivial	Always	Dec 20, 2023, 03:04	Jan 31, 2024, 23:20

Tester	VasiliyFamiliya	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Open	OS	Windows 10/11 (64-bit)
Status [?]	Confirmed			Driver	konami/viper.cpp
Version	0.261	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	08804: p9112, wcombat: Outdated comments in the Konami Viper driver file.
Description	"Game status: <...> p9112 RTC self check bad. The game checks the checksum of 0x157d4d0-0x157d4ee against the checksum that should be at 0x157d4ee-0x157d4ef, but this part of memory is never written to after its initial clearing on boot. If 0xffff is placed at 0x157d4ee then the game will pass the RTC check. The game will later complain about "Hardware Error: Security Key Error" if you try starting the game. <...> wcombat Can boot into a test menu by using a combination of dipswitches, but it says "serial check bad". Can't boot normally. wcombatu Bootable when dipsw 4 is set to on. Controls not implemented so it's not possible to pass nickname selection screen. Freezes when test button is pressed. <...>" Althought I didn't test all wcombat sets yet, as 8801 report shows, wcombatk calmly launches without any troubles.
Steps To Reproduce
Additional Information
Github Commit

Flags	Noted in Source
Regression Version
Affected Sets / Systems	p9112, wcombat

Attached Files

No.21887 Robbbert Senior Tester Dec 20, 2023, 08:01	The games are marked as not working, but they do at least start up - I didn't try playing a game.
No.21927 Kale Developer Jan 31, 2024, 23:20 edited on: Jan 31, 2024, 23:21	https://github.com/mamedev/mame/blob/90d840b6356c67fd735813e8848bfda67fb28aa6/src/mame/konami/viper.cpp#L114 Game status (potentially outdated, to be moved on top): Not even sure I want this bug report to stay open tbh.