Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
04656 Misc. Trivial Always Feb 1, 2012, 20:09 Feb 4, 2012, 15:01
Tester Bubblun_Z View Status Public Platform MAME (Self-compiled)
Assigned To Kale Resolution Fixed OS Windows Vista/7 (64-bit)
Status [?] Resolved Driver
Version 0.144u7 Fixed in Version 0.145 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 04656: Various Sets: "Timer Error" shows before start of game each time, showing odd time during setting
Description A number of games on Super Kaneko Nova System are giving a "Timer Error" and take you to the Time Set screen or just immediately going to it without a prior screen (like Saru-Kani-Hamu-Zou). It also happened in the last version (0.144u6), and with all the galpanis sets working again, they're all doing the same thing. It can also display odd times for the currently set time (over 24 hour time?).

This happens each time you load the game, accepting the time with or without changing it will get you through, but you'll be seeing it again every time.

There are exceptions (Cyvern, Gals Panic S2 & S3, Guts'n, Panic Street, Puzz Loop, Sen-Know...) that just start the game without the error, I haven't checked their time settings yet. It happens mostly for all four Electro Design mahjong games and various Kaneko titles.

Sengeki Striker is an odd case. During the checks, it'll say the clock is NG, and you'll need to push a button to go into the Test Menu, where you'll need to use Clock Adjustments, then Exit afterwards. It didn't seem to be showing 42:##:## as the time, either. The others just immediately take you to the set screen.
Steps To Reproduce 1) Load up any game on the hardware.
2) Wait past the BIOS, you'll see it as soon as it's done. If you don't, that's an exception.
Additional Information
Github Commit
Flags
Regression Version 0.144u6
Affected Sets / Systems Various Sets
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.08129
haynor666
Tester
Feb 1, 2012, 20:27
Looks like NVRAM is not saving as well.
User avatar
No.08143
Kale
Developer
Feb 4, 2012, 15:01
Let's say "resolved" but it's actually pretty weird as an issue (it tries to read uninitialized registers?), probably needs HW tests ...