- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
05774 | Crash/Freeze | Major | Always | Nov 1, 2014, 20:57 | Nov 3, 2014, 00:22 |
Tester | Justin Kerk | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | crazyc | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) |
Status [?] | Resolved | Driver | |||
Version | 0.155 | Fixed in Version | Build | Normal | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 05774: calchase: Page fault when booting game | ||||
Description | GAME_NOT_WORKING, but I'd call this a heavy regression. The game used to boot to attract mode, coin up, and enter gameplay, but now it just shows a "Run time Protected Mode termination" and "Page fault" error message. | ||||
Steps To Reproduce |
1. mame calchase 2. When the BIOS screen asks you to press F1 to continue, press "s" (mapped to F1 in the controls) 3. Wait for the Windows logo to go away and the DOS prompt to appear 4. Slowly type "boot" and press Enter |
||||
Additional Information |
In 0.148, the game boots into attract mode and you can coin up and enter the game. (See e.g. Kale's WIP at http://mamedev.emulab.it/kale/?p=1652 ) In 0.149 and 0.150, it still boots and runs but the graphics mode is garbled. In 0.151 and 0.155, it shows a page fault error and dumps you back to the DOS prompt. (386 issue?) |
||||
Github Commit | |||||
Flags | |||||
Regression Version | 0.151 | ||||
Affected Sets / Systems | calchase | ||||
Attached Files
|
calchase_0148.png (146,822 bytes) Nov 1, 2014, 20:57 Uploaded by Justin Kerk
| ||||
calchase_0149.png (44,386 bytes) Nov 1, 2014, 20:57 Uploaded by Justin Kerk
| |||||
calchase_0151.png (3,856 bytes) Nov 1, 2014, 20:58 Uploaded by Justin Kerk
| |||||
Relationships
There are no relationship linked to this issue. |
Notes
2
No.11206
NekoEd Senior Tester
Nov 1, 2014, 23:36
|
I'm going to confirm this, it's a pretty heavy regression indeed. |
---|---|
No.11215
crazyc Developer
Nov 3, 2014, 00:22
|
Fixed in https://github.com/mamedev/mame/commit/414477ee2ca3e85b80509e523721625312e02714 The BIOS stores the ram size in the cmos and it was getting overwritten which was causing the dpmi server to get confused when allocating ram. |