01789: fiveside: Game doesn't initialize / stuck on rom test

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
01789	Gameplay	Major	Always	May 7, 2008, 16:22	May 8, 2008, 11:59

Tester	Osso	View Status	Public	Platform	MAMEUI
Assigned To		Resolution	No change required	OS	Windows XP/Vista 64-bit
Status [?]	Closed			Driver	konami/ultrsprt.cpp
Version	0.125	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	01789: fiveside: Game doesn't initialize / stuck on rom test
Description	The game remains stuck on rom test. F2+F3 doesn't seem to initialize the eeprom correctly.
Steps To Reproduce	1) Delete nvram file 2) Start the emulation
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	fiveside

Attached Files

No.00904 Tafoid Administrator May 7, 2008, 16:57 edited on: May 17, 2009, 19:58	I don't think this is a bug. Bug which require F3 to reproduce are not bugs unless the emulation crashes MAME. bug1439 In this case, after the failed RAM ROM CHECK comes up, simply shut down and restart MAME - the game functions properly. I tested behavior of this since the first main release it was available (0.110) and it acted the same: - Make sure there is no NVRAM - Start game - the RAM ROM CHECK appears. - 26A shows as bad - this is the EEPROM. Use the F2+F3 to create - EEPROM is completed and a reset attempts to happen - resulting in the bad RAM ROM CHECK. - Simply exit MAME completely and restart (in essence, toggling the machine power switch) - the RESET (F3) doesn't do this. The test should come up as all OK and the game should work.
No.00916 etabeta Developer May 8, 2008, 11:59 edited on: May 8, 2008, 12:07	here the last step fails and 26A always shows up BAD EDIT: false alarm... I had a couple of keys mapped in the wrong way, so I was using hard reset in place of soft reset when trying to generate the EEPROM... just for completeness: after EEPROM is generated, you can perform a Hard Reset (Shift+F3) instead of quitting and restarting MAME

No.00904

Tafoid

Administrator

May 7, 2008, 16:57

edited on: May 17, 2009, 19:58

I don't think this is a bug. Bug which require F3 to reproduce are not bugs unless the emulation crashes MAME.

bug1439

In this case, after the failed RAM ROM CHECK comes up, simply shut down and restart MAME - the game functions properly. I tested behavior of this since the first main release it was available (0.110) and it acted the same:

- Make sure there is no NVRAM
- Start game - the RAM ROM CHECK appears.
- 26A shows as bad - this is the EEPROM. Use the F2+F3 to create
- EEPROM is completed and a reset attempts to happen - resulting in the bad RAM ROM CHECK.
- Simply exit MAME completely and restart (in essence, toggling the machine power switch) - the RESET (F3) doesn't do this. The test should come up as all OK and the game should work.

No.00916

etabeta

Developer

May 8, 2008, 11:59

edited on: May 8, 2008, 12:07

here the last step fails and 26A always shows up BAD

EDIT: false alarm... I had a couple of keys mapped in the wrong way, so I was using hard reset in place of soft reset when trying to generate the EEPROM...

just for completeness: after EEPROM is generated, you can perform a Hard Reset (Shift+F3) instead of quitting and restarting MAME