01793: bishjan: Hardware reset (shift-F3) doesn't work

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
01793	Interface	Major	Always	May 8, 2008, 12:28	May 9, 2008, 22:14

Tester	nightsoil	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Bugs That Aren't Bugs	OS
Status [?]	Resolved			Driver	subsino/subsino2.cpp
Version	0.125	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	01793: bishjan: Hardware reset (shift-F3) doesn't work
Description	Shift-F3 for hardware reset doesn't work
Steps To Reproduce	Play the game a bit. Then, in the middle of the game, try shift-F3. Wait for the boot-up screen to disappear, and lo and behold, the game reappears just as you left it.
Additional Information	bishjan.c -> subsino2.c in 0.141u2
Github Commit

Flags
Regression Version
Affected Sets / Systems	bishjan

Attached Files

No.00920 Tafoid Administrator May 8, 2008, 16:30	Strange. Even if I exit MAME normally and restart without any save state or autosave enabled - I still get put back into game where I was. Deleting the NVRAM brings shutdown behavior back to normal. I'm curious if this is a function of the hardware being emulated.. some internal save stating that puts information into NVRAM? Any comments?
No.00925 Tafoid Administrator May 8, 2008, 23:32 edited on: May 9, 2008, 00:04	I'm putting this back to acknowledged. The more I consider this 'bug', the more I think it's correct behavior. The resuming only happens while in game - I can see the purpose in that. (power outage) The ability to resume does not happen while not playing and it's all dependant of the NVRAM write. This is likely a FEATURE of the game, in case the power goes down while playing.
No.00927 Tafoid Administrator May 9, 2008, 00:03	It looks like F1 functions as the true RESET button (as mapped in the Input menu.). If you use F1 rather than F3 or even SHIFT-F3 - you will get a truly reset game. So, this is not a bug and no change is required.
No.00928 Haze Senior Tester May 9, 2008, 18:28	does MAME exhibit the same behavior when you press shift+F3 as if you hit escape back to command line and reloaded MAME? if not then the hard reset is broken.
No.00929 etabeta Developer May 9, 2008, 18:42	well, if the game saves on .nvram say any 30secs (or at any move), MAME would correctly save on .nvram at that point when you press Shift+F3, and then restore the state at reboot... Of course, this is assuming that, in the original cabinet, the game would restart at the last move after a blackout or after any shutdown of the machine (except when done with the Reset switch)...
No.00930 Tafoid Administrator May 9, 2008, 19:11	If you are playing a game, short of deleting your NVRAM after exiting MAME or using the mapped F1 key - the game will resume when you restart MAME by any other method (F3, SHIFT-F3, escape, select new game). I don't know how a bug could mistakenly save the game's progress in NVRAM - it only stands to reason this is intended behavior of the PCB.
No.00931 Haze Senior Tester May 9, 2008, 22:14	yes, if the behavior is the same as exiting Mame and reloading then it isn't a hard reset (shift + f3) bug. Only cases where shift+f3 is not the same as quit + reload are bugs.