Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
01996 Crash/Freeze Critical (emulation) Always Jul 10, 2008, 11:21 Aug 16, 2010, 03:46
Tester JoshuaChang View Status Public Platform MAME (Official Binary)
Assigned To Resolution No change required OS
Status [?] Closed Driver
Version 0.126 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary 01996: rfjets: The game still shows the black screen
Description it just doesn't boot~
this problem can be reproduce in both 0.126 and 0.125
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems rfjets
Attached Files
 
Relationships
duplicate of 00841Resolved  rfjets: The game doesn't boot up (shows blank screen) 
Notes
3
User avatar
No.01571
Tafoid
Administrator
Jul 10, 2008, 12:58
I'm afraid the 0.122u1 is a mis-entered resolution version here. The actual fix came in 0.119u4. It's been determined this is the one SINGLE BOARD version of this hardware that would not function properly until a valid NVRAM is created.

Right now, the easiest method to create one was developed in 0.119u4 then the original bug was 'fixed'. Couriersud in that version coded added a hack to enable Test-Switch (F2) to enter testmode if no nvram exists. Upon entering service mode, you select: RESET SETTING with Button 1. This will create the valid NVRAM the game needs to boot. Choose EXIT (RESET BOARD) with Button 1 again and the game should start with no problems.
If you delete your .NV file at any time, you'll need to recreate it.

This probably should be added to MAMEDEV's lists for particular game setup procedures.
User avatar
No.06556
Smitdogg
Senior Tester
Aug 16, 2010, 03:30
This should probably have the nv file included in the rom zip now and the hack removed?
User avatar
No.06557
Tafoid
Administrator
Aug 16, 2010, 03:46
Might not be for this specific game, but there was a recent seibu dump that got the .nv treatment.