Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
03630 Core Critical (emulation) Always Jan 2, 2010, 07:29 Jan 4, 2010, 01:49
Tester Iaspis View Status Public Platform MAME (Official Binary)
Assigned To aaron Resolution Fixed OS Windows Vista/7 (64-bit)
Status [?] Resolved Driver
Version 0.136 Fixed in Version 0.136u1 Build Normal
Fixed in Git Commit Github Pull Request #
Summary 03630: Any EEPROM with an 8-bit data bus is not being saved correctly
Description Example: thndrx2 - There seems to be a failure in the rom check screen (17F BAD), preventing this game and its clones from running.
Steps To Reproduce
Additional Information In particular, Konami games seem most prone to show this error.
asterix.c, gijoe.c, moo.c, tmnt.c, lethal.c, xmen.c, vendetta.c, mystwarr.c, simpsons.c, xexex.c, rungun.c, hornet.c, overdriv.c, konamigx.c
and others.
Github Commit
Flags
Regression Version 0.136
Affected Sets / Systems
Attached Files
png file icon 0000.png (646 bytes) Jan 2, 2010, 14:39
png file icon 0001.png (1,384 bytes) Jan 2, 2010, 14:39
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.05363
Tafoid
Administrator
Jan 2, 2010, 14:18
edited on: Jan 3, 2010, 23:53
EDIT: Well, it appears to be a bug afterall. Not sure what happened, specifically, my complete test in 0.135u4 showed this as working with the F2+F3 procedure. In 0.136 - even after the procedure, the game shows it as bad. Odd.

EDIT #2: Most of the games which the auto-initialize was taken off are affected. Drivers noted.

EDIT #3: r7821 appears to be the culprit
User avatar
No.05377
Tafoid
Administrator
Jan 3, 2010, 21:20
edited on: Jan 3, 2010, 23:51
Some inability to save eeproms correctly are noted in other drivers too - might be a MAME-wide issue.,

EDIT #2: This is infact an issue with 8-bit EEPROMS not being able to be saved correctly. Corrected bug description.