- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
04262 | Gameplay | Minor | Always | Feb 27, 2011, 01:21 | Oct 4, 2014, 08:59 |
Tester | AWJ | View Status | Public | Platform | SDLMAME |
Assigned To | Resolution | Fixed | OS | Linux | |
Status [?] | Resolved | Driver | |||
Version | 0.141u2 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 04262: bbakraid and clones: "Initialize EEPROM" doesn't work | ||||
Description | The "Initialize EEPROM" option in the service menu, which should erase the high scores and other contents of the EEPROM and restore it to default contents, doesn't do anything. | ||||
Steps To Reproduce |
1. Play the game and get a high score. 2. Enter Service Mode. 3. Select "Initialize EEPROM". Select "Yes" when it asks "are you sure". 4. Return to game mode. 5. Exit MAME for EEPROM can write. 6. Play the game again and notice that your high score is still there. |
||||
Additional Information | Affected set updated (March 2011): bkraidu -> bbakraid | ||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | bbakraid and clones | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
4
No.07268
Tafoid Administrator
Feb 27, 2011, 02:01
|
Normal MAME function is that if you clear an eeprom while running the game, you need to exit MAME to let it write to disk the (.NV), then it should be clear. Doing it here, though, doesn't seem to clear it - so I can confirm your bug. |
---|---|
No.07269
AWJ Developer
Feb 27, 2011, 02:09
|
The high score initials are visible as plain ASCII in the .nv file, so you can even confirm using hexdump that your high scores are still there after "initializing". |
No.11020
Osso Moderator
Oct 4, 2014, 06:56
|
Can't repro anymore. After getting a high score, initialized the eeprom, quit the game. Reloaded the game, high score table is clean. Someone else can verify, please? |
No.11022
AWJ Developer
Oct 4, 2014, 08:59
|
Yeah, this is fixed now. Aaron's big serial EEPROM rewrite a while back probably took care of it. |