05695: amerdart, amerdat2, amerdart3: Crash after game completion

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
05695	Crash/Freeze	Critical (emulation)	Always	Sep 8, 2014, 17:30	16 days ago

Tester	evh347	View Status	Public	Platform	MAME (Official Binary)
Assigned To	peterferrie	Resolution	Fixed	OS	Windows Vista/7/8 (64-bit)
Status [?]	Resolved			Driver	misc/coolpool.cpp
Version	0.154	Fixed in Version	0.272GIT	Build	64-bit
		Fixed in Git Commit	a8e009e	Github Pull Request #

Summary	05695: amerdart, amerdat2, amerdart3: Crash after game completion
Description	All amerdart variants crash/freeze after completing a game. The waitress comes out after the entering initials, thanks the player for playing and a voice says, "How about another round?". The game then freezes. Player can enter additional coins, but cannot start another round without hitting F3 to reboot. The game mode doesn't seem to matter.
Steps To Reproduce
Additional Information	This has been an issue, I think, since the game has been added. Since it doesn't actually effect the game play during game, I don't believe it got the attention it should. (Tafoid)
Github Commit

Flags
Regression Version
Affected Sets / Systems	amerdart, amerdat2, amerdart3

Attached Files

No.13395 Fujix Administrator Nov 18, 2016, 15:21	Moved the attached original video by evh347 to YouTube.
No.22404 peterferrie Developer 17 days ago	It stops crashing if I put RAM at 0x2xxxxx (because there's an access in that range that looks like a bug), but the animation is broken. Perhaps the address should be masked & 0xfffff?
No.22405 Robbbert Senior Tester 17 days ago	Removed link to private youtube video.
No.22407 hap Developer 16 days ago	I added VRAM mirroring. There's a glitchy line during the game over animation. I don't know if it could be a BTANB (did not find a pcb video of game over sequence). If the glitchy line is a MAME bug, it's much more preferable than the game locking up.
No.22408 peterferrie Developer 16 days ago	Thanks! The glitchy line is a result of the OOB access at 0x2xxxxx (it's a timer value interpreted as a pointer). That's not a MAME bug.