Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05223 DIP/Input Minor Always Jun 29, 2013, 23:28 Jun 30, 2013, 07:10
Tester darq View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Invalid report OS Windows Vista/7/8 (64-bit)
Status [?] Closed Driver
Version 0.149 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 05223: input and ram bad fixes
Description I don't know why I continue to help... however here are two small fixes:

1) To pass the input tests the procedure at 0x4304 requires that all inputs must return 1 as initial state.
So the commented rows in spool99_io_r were correct. (Unknown/Unhandled inputs 0xAFD9, 0xAFDB, 0xAFE5, 0xAFE6 must return 1).
This fixes the 'INPUT BAD' message.

2) The eeprom implementation is correct, what is not hooked up is nvram!
The game saves bookkeeping (CONTABILITA), statistics (STATISTICHE) and inserted credits (CREDITI) in ram, not in the EEprom.

Furthermore, the game, to boot up, expects (at least) some initial values in ram (Ram test procedure at 0x196E):
ram [0xDF57] = 0xAB;
ram [0xDF5D] = 0x07;
ram [0xDF63] = 0x05;
ram [0xDF71] = 0x06;
ram [0xDF77] = 0x12;
These (and other) values are written by the init ram procedure when you press Start + Service 1 at boot.

So I implementend nvram by 'splitting' last part of ram:
AM_RANGE (0xB800, 0xDEFF) AM_RAM
AM_RANGE (0xDF00, 0xDFFF) AM_RAM AM_SHARE ("nvram") // Not sure about the size (I haven't found a clear PCB image)

and of course by adding:
MCFG_NVRAM_ADD_0FILL ("nvram") in MACHINE_CONFIG_START.
This fixes the 'RAM BAD' message after the first nvram init.

PS:
To the great admin Fujix: I'd recommend you to ignore or even close this report!
Even though the entire report is related to the same game, it contains two fixes instead of one! (It may be very dangerous!!)
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.09628
NekoEd
Senior Tester
Jun 29, 2013, 23:52
The reason these reports get closed is because code submissions are not valid bug reports. If you want to submit code to the project, you need to send it directly to MAMEDEV. Please see this page ( http://www.mamedev.org/devwiki/index.php?title=Submitting_Source_Code ) and follow the instructions there.

Report closed as invalid (code submission)
User avatar
No.09629
Fujix
Administrator
Jun 30, 2013, 07:10
huh?