- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
02528 | Core | Critical (emulation) | Always | Oct 11, 2008, 15:35 | Oct 12, 2008, 04:04 |
Tester | Terryn | View Status | Public | Platform | MAME (Self-compiled) |
Assigned To | Resolution | Fixed | OS | ||
Status [?] | Resolved | Driver | |||
Version | 0.127u7 | Fixed in Version | 0.127u8 | Build | Normal |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 02528: xexex and clones: Game checks halt with "VERSION ERROR" | ||||
Description | The initial "CHECKING EEPROM" screen gets skipped; just past the initial RAM/ROM checks, the game declares "VERSION ERROR" and will not proceed. | ||||
Steps To Reproduce | |||||
Additional Information | Regression either is in .127u2 or .127u3 (u1 works, u3 doesn't, I didn't test u2 since the u2 upload of MAMEUI on the whiper Mame mirror is broken). Tested in self-compile .127u7 and MAMEUI32. | ||||
Github Commit | |||||
Flags | |||||
Regression Version | 0.127u3 | ||||
Affected Sets / Systems | xexex and clones | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
3
No.02769
Haze Senior Tester
Oct 11, 2008, 15:38
|
it still boots if you initialize the eeprom. |
---|---|
No.02770
Terryn Tester
Oct 11, 2008, 15:40
edited on: Oct 11, 2008, 15:42 |
Ah, was this changed to be done manually? My mistake, apologies (yet again). I should have made a more general examination rather than just checking xexex.c. Sorry for wasting your time =( |
No.02771
Tafoid Administrator
Oct 11, 2008, 15:47
edited on: Oct 11, 2008, 15:51 |
Hold down F2 then reset the game with F3 and wait for the "Checking EEPROM" message to disappear. It would appear in 0.127u3 onwards - the auto create EEPROM behavior was changed in source and must now be done manually like most of the other same-era Konami games. I'll leave open for more testing/comments. EDIT: Gaah.. I sit at the create note screen for too long and it resolves itself :) Anyway - it would be nice to know if this was expected - since prior to the regression that the EEPROM initialized itself. Is this change to keep it consistent with actual behavior? |