Viewing Issue Advanced Details
[ Jump to Notes ]
midway/vegas.cpp
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08652 Gameplay Major Always May 31, 2023, 12:51 Jun 2, 2023, 03:20
Tester Robbbert View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Invalid report OS Windows 10/11 (64-bit)
Status [?] Closed Driver
midway/vegas.cpp
Version 0.255 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 08652: gauntleg, gauntdl24: Listed as working, but don't work
Description These 2 games have no warning screens, but at start they display a message

Error mounting filesystem
MOUNT error, file header read error

and cannot proceed.
Steps To Reproduce Start game.
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems gauntleg, gauntdl24
Attached Files
png file icon 0000.png (1,661 bytes) Jun 1, 2023, 01:20 Uploaded by Hydreigon
Hydreigon
png file icon gauntleg.png (1,404 bytes) Jun 1, 2023, 07:12 Uploaded by Robbbert
Robbbert
Relationships
There are no relationship linked to this issue.
Notes
8
User avatar
No.21478
Hydreigon
Tester
Jun 1, 2023, 01:19
 This is a general issue with the Vegas system as I'm having a similar error in sf2049 sometimes when you start a game or enter/exit test mode. See the above screenshot I posted.
User avatar
No.21481
Balthier
Tester
Jun 1, 2023, 05:18
 Works just fine here with official build:
https://i.imgur.com/jZhrWWk.png
User avatar
No.21482
Robbbert
Senior Tester
Jun 1, 2023, 07:12
edited on: Jun 1, 2023, 07:13
 This is all I ever get with gauntleg - never seen it work. (see attached)

sf2049 works fine.
User avatar
No.21483
Haze
Senior Tester
Jun 1, 2023, 07:45
 also can't confirm, works here.
User avatar
No.21484
PepsiBoy428
Tester
Jun 1, 2023, 13:10
 Have you tried deleting or renaming your nvram folder contents?
User avatar
No.21485
Robbbert
Senior Tester
Jun 1, 2023, 14:01
 Of course, a number of times.
User avatar
No.21486
Balthier
Tester
Jun 1, 2023, 15:07
 I was able to run these even with diff and nvram files copied over from a previous mame version. Did you try deleting your cfg files and running the games again? Mine look like this:
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
    <system name="gauntleg">
        <image_directories>
            <device instance="harddisk1" directory="" />
            <device instance="cdrom1" directory="" />
            <device instance="harddisk2" directory="" />
            <device instance="cdrom2" directory="" />
        </image_directories>
        <network>
            <device tag=":ethernet" interface="-1" mac="00:00:00:00:00:00" />
        </network>
    </system>
</mameconfig>

Check your cfgs and see that they don't have some directory being pointed at on the "device instance" lines.

Your report also says "Platform MAME (Self-compiled)", so maybe you didn't compile it correctly. If all else fails just use the official build from mamedev.org as that definitely works.
User avatar
No.21496
Robbbert
Senior Tester
Jun 2, 2023, 03:20
edited on: Jun 2, 2023, 13:16
 Even though the CHDs came from a supposedly impeccable source, I decided to run chdman verify on them, and they turned out to be corrupt.

Unfortunately, MAME only checks the inbuilt SHA1, but if the CHD was changed later, the corruption won't be detected when loading.

I'll have to find a better place to get replacements.

Closed.