03873: All sets in megaplay.c and megatech.c: Individual games incorrectly writing an NVRAM file.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03873	Misc.	Minor	Always	Jun 2, 2010, 16:47	Mar 23, 2013, 11:08

Tester	Tafoid	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver
Version	0.138u1	Fixed in Version	0.148u3	Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	03873: All sets in megaplay.c and megatech.c: Individual games incorrectly writing an NVRAM file.
Description	All games in megaplay.c and megatech.c produce a sized 0 .NV file. There is no function on the original board in my discovery to allow per-game battery backup saving on any games for these systems. The boards, however, allow for saving of the BIOS settings via battery, so when a game is run - it should instead create a proper NVRAM for the system you are using. However, at the current time, even the BIOS sets save sized 0 .NV files.
Steps To Reproduce
Additional Information	If this is already a source listed issue, we can change it. Otherwise, it's something that should eventually be addressed. This also affects all megadrive-based bootleg drivers: ~~aladbl.c~~ hshavoc.c ~~mk3ghw.c~~ puckpkmn.c ~~ssf2md.c~~ ~~ssgbl.c~~ ~~topshoot.c~~ aladbl, ssf2md now merged to genesisb.c in 0.139u1 genesisb.c renamed to megadrvb.c in 0.139u2 topshoot.c, mk4ghw.c now merged with megadrvb.c in 0.139u2 ssgbl.c merged with megadrvb in 0.139u3
Github Commit

Flags
Regression Version
Affected Sets / Systems	All sets in megaplay.c and megatech.c

Attached Files

No.06223 Haze Senior Tester Jun 2, 2010, 17:18	it comes down to a core issue (i'm sure there was already a report for this?) whereby if you have an nvram handler you'll always end up with a blank file.. in this case, some megadrive games have nvram, so you need an nvram handler, the code is shared. I'd say it was harmless...
No.06224 Tafoid Administrator Jun 2, 2010, 17:48	It might have been discussed before, but I didn't see an official report about it nor a source code mention. Just making sure something solid gets logged.
No.09434 etabeta Developer Mar 23, 2013, 11:08	megadrive and other drivers in MESS were not using the NVRAM handler from MAME anymore, so I removed it fixing this bug too. if any bootleg board actually needs the NVRAM to be saved please let us know.