02995: liberate, dualaslt: Black screen shows after disclaimer

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
02995	Crash/Freeze	Critical (emulation)	Always	Mar 1, 2009, 11:39	Mar 1, 2009, 21:03

Tester	moa	View Status	Public	Platform	MAME (Unofficial Binary)
Assigned To	Phil Bennett	Resolution	Fixed	OS	Windows XP/Vista 32-bit
Status [?]	Resolved			Driver	dataeast/liberate.cpp
Version	0.129u5	Fixed in Version	0.129u6	Build	I686
		Fixed in Git Commit		Github Pull Request #

Summary	02995: liberate, dualaslt: Black screen shows after disclaimer
Description	After the initial quick flash of the disclaimer - the game sits at a black screen and seemingly idles.
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version	0.129u1
Affected Sets / Systems	liberate, dualaslt

Attached Files

No.03870 Phil Bennett Developer Mar 1, 2009, 19:40 edited on: Mar 1, 2009, 21:03	Following core changes to opcode memory accessing, READ8_HANDLER( deco16_io_r ) has become a problem. It's overlaid over the encrypted ROM region of the CPU space and represents either I/O ports or ROM. Opcode accesses go through this handler when the game jumps to $8009. The opcodes themselves are encrypted but the arguments/data are not. The function is only returning encrypted ROM values. EDIT: I think I have a reasonable solution.

No.03870

Phil Bennett

Developer

Mar 1, 2009, 19:40

edited on: Mar 1, 2009, 21:03

Following core changes to opcode memory accessing, READ8_HANDLER( deco16_io_r ) has become a problem. It's overlaid over the encrypted ROM region of the CPU space and represents either I/O ports or ROM. Opcode accesses go through this handler when the game jumps to $8009. The opcodes themselves are encrypted but the arguments/data are not. The function is only returning encrypted ROM values.

EDIT: I think I have a reasonable solution.