| - As of 0.139u2, some drivers and options show "16-bit EEPROM set with 8-bit data". Check 4030. - Haze is calling for mixing issues with *SINGLE* VDP games in toaplan2.c. Check 4044. |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Source: jpmimpct.c ] | |||||||||||
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update | |||||||
| 03781 | Misc. | Trivial | Always | 2010-03-13 02:06 | 2010-03-13 15:24 | |||||||
| Tester | BarnacleEd | View Status | Public | |||||||||
| Assigned To | Platform | SDLMAME | ||||||||||
| Priority | normal | Resolution | Open | OS | Linux | |||||||
| Status [?] | Confirmed | Driver | jpmimpct.c | |||||||||
| Projection | None | Version | 0.137 | |||||||||
| ETA | None | Fixed in Version | Build | Normal | ||||||||
| Summary | 03781: trivialp: [possible] In-game EPROM tests take a ridiculous amount of time | |||||||||||
| Description | The EPROM checksum tests in set trivialp take an incredibly long time to complete, well longer than the approximate times listed on the test screens. Compare to scrabble, where the tests complete in reasonable amounts of time rather close to the approximations given. To complete the tests in trivialp in a reasonable, but still rather long amount of time, unthrottling the game is necessary. | |||||||||||
| Steps To Reproduce | Open the back door ( "9" by default ), then wait until the game displays "BACK DOOR OPEN". From there, hit the "TEST/DEMO" key ( "=" by default ) and you'll hear a sound then go to the test menu. The ROM tests are in the second half of the menus, accessed on this set by touching "MORE TESTS" at the bottom of the list. | |||||||||||
| Additional Information | I have not tested any of the other sets in the driver, feel free to do so if I don't get around to it. | |||||||||||
| Flags | Possible | |||||||||||
| Regression Version | ||||||||||||
| Affected Sets | trivialp | |||||||||||
| Old BugID | ||||||||||||
| Attached Files | ||||||||||||
|
|
|
|
Tafoid (Administrator) 2010-03-13 02:26 |
Again, like your other bug, specific steps to reproduce would be helpful. |
|
BarnacleEd (Tester) 2010-03-13 11:56 edited on: 2010-03-13 11:57 |
Done. Added to main report. |
|
Haze (Senior Tester) 2010-03-13 14:36 |
I have my doubts that this is a bug. If anything ROM/RAM tests are usually *faster* under emulation due to missing watistates / ram access time emulation. I imagine they just have a very inefficient routine to do the tests, and have inaccurate values displayed on the screen. Test Screens are often an unreliable source of information. It *could* be a bug, but given other games on the hardware work as expected I'd be surprised. |
|
Tafoid (Administrator) 2010-03-13 15:24 |
Got a chance to try this - starting fresh and doing the test directly it does it in almost exactly 2 minutes (compared to realtime clock). There might be something out of whack or not being processed correctly - doubling the time? The DUART emulation (according to the source), is still in progress. I'll confirm, but set as possible pending some investigation and some input from driver author would be helpful too. |