Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05974 Interface Minor Always Jul 3, 2015, 21:30 Aug 28, 2017, 17:10
Tester ZoeB View Status Public Platform MAME (Unofficial Binary)
Assigned To Resolution No change required OS MacOS X
Status [?] Closed Driver neodriv.hxx
Version 0.153 Fixed in Version Build 64-bit
Summary 05974: Neo Geo games work from command line but not menu
Description For instance, the following work just fine:

./mame64 mslug
./mame64 kof98

But if I try the following:


Then select any Neo Geo game I can think of from the menu, it says it's missing one or more required ROM or CHD images.

So it looks like there's some disagreement between directly loading a specific game vs. going through the menu when it comes to finding the Neo Geo BIOS files.
Steps To Reproduce As above.
Additional Information I'm not sure how up to date my Neo Geo BIOS files are, so I'd better tell you they're these:

$ md5 roms/neogeo/*
MD5 (roms/neogeo/000-lo.lo) = fc7599f3f871578fe9a0453662d1c966
MD5 (roms/neogeo/asia-s3.rom) = ff453315c5ddacc0f3bf4ca994c13adc
MD5 (roms/neogeo/japan-j3.bin) = 5b2d6f653ba4cf36e7fe237e4acb2f50
MD5 (roms/neogeo/sfix.sfix) = aa2b5d0eae4158ffc0d7d63481c7830b
MD5 (roms/neogeo/sm1.sm1) = 8c26241f9f5beb3a55c8d6ab638d250e
MD5 (roms/neogeo/sp-1v1_3db8c.bin) = 629e6beaa277e039eae2f96ff237f8e6
MD5 (roms/neogeo/sp-45.sp1) = 0396470c1ed8b1a7d5cce754924246bb
MD5 (roms/neogeo/sp-e.sp1) = a7b798c9cafb1aba49090bca34e1d4ec
MD5 (roms/neogeo/sp-j2.sp1) = a51ad226535ff862c1f54120e4298f79
MD5 (roms/neogeo/sp-s.sp1) = 908b5a0026b2b10f2a7c01ccd98a1236
MD5 (roms/neogeo/sp-s2.sp1) = 2968f59f44bf328639aa79391aeeeab4
MD5 (roms/neogeo/sp-u2.sp1) = b60fb8ea07e8a64772ab717afba3706d
MD5 (roms/neogeo/sp1.jipan.1024) = a80fffe27bf8e615171ce728e43d2f6c
MD5 (roms/neogeo/uni-bios_1_0.rom) = 6293999bbc32e594aa0ae1da2113dc4d
MD5 (roms/neogeo/uni-bios_1_1.rom) = cafa6c274b271c769b8246c8f87473a1
MD5 (roms/neogeo/uni-bios_1_2.rom) = 206fb0d9b5d01a0375d2d3ecab2401b1
MD5 (roms/neogeo/uni-bios_1_2o.rom) = 6b2f2d8507be4d1feb14fdfbab0bf22e
MD5 (roms/neogeo/uni-bios_1_3.rom) = 856d122ee5fc473d7d1dd99dbf42c25b
MD5 (roms/neogeo/uni-bios_2_0.rom) = 1b9724d1b9d41a1a9b733007b2033fb5
MD5 (roms/neogeo/uni-bios_2_1.rom) = 0377c32f69a28f23d9281c448aafb391
MD5 (roms/neogeo/uni-bios_2_2.rom) = 5b9079a81d84137d8b6f221659d777c5
MD5 (roms/neogeo/uni-bios_2_3.rom) = 74c4bb6a945f7284350036b40f0a0d9d
MD5 (roms/neogeo/uni-bios_2_3o.rom) = d9f0ed2e0eeab813c9692d7e8d037fd8
MD5 (roms/neogeo/uni-bios_3_0.rom) = 727b731c1f4bd643094574ebaa3814b4
MD5 (roms/neogeo/vs-bios.rom) = 530fb9761957e59aeb47f2e8782df288

Sorry I'm not using the latest version of MAME, I never did have much luck compiling other people's programs!

First I thought it might be to do with how I don't zip my ROM files, so I made a roms/ with the relevant files, but it still didn't work, so I don't think that's part of the issue.

This is the only version of MAME I have to test with, but I'm happy to try out anything to see what works and what doesn't.
Regression Version
Affected Sets / Systems
Attached Files
There are no relationsihp linked to this issue.
User avatar
Jul 3, 2015, 22:58
edited on: Jul 3, 2015, 23:06
Current baseline MAME works fine.
 I'm going to guess it is because your isn't updated.. every once in a while a new bios version or universal bios added
What happens if you just try to run "mame neogeo" from command line? Do you get any incorrect crc matches or anything else showing?

EDIT: I checked back and the changed between 0.152 and 0.153 which pretty much confirms you are missing a rom or a rom is crc mismatched.

User avatar
Jul 4, 2015, 13:21
Huh, I've never tried that before...

./mame64 neogeo

I get a calibration grid, by the looks of things, so that seems to work just fine. No errors.

Regarding the linked patch, I didn't have neodebug.rom. I've now got it:

$ openssl sha1 roms/neogeo/neodebug.rom
SHA1(roms/neogeo/neodebug.rom)= 081c49aa8cc7dad5939833dc1b18338321ea0a07

I just tried selecting mslug from the menu and it still doesn't work.
User avatar
Jul 4, 2015, 13:33
edited on: Jul 4, 2015, 13:34
Latest official x64 version works fine on 7 x64. Maybe it's problem with only MacOS version?

User avatar
Jul 4, 2015, 15:49
I managed to get MAME v0.163 64-bit from and it has the same problem as before. It might be OS X specific, but it's even in the latest version.
User avatar
Senior Tester
Jul 7, 2015, 01:56
Confirmed on SDLMAME64 0.163 running on Linux/x64.

It looks like it may be SDL-specific.
User avatar
Mar 5, 2016, 21:29
FYI, this is kind of by design.

When I added the 'bios' functionality, I made it possible to load a game so long as you had the minimum roms to launch it in a given configuration (i.e. the bios you specified was available + the game roms). This was to address a concern from Nicola that users might feel they had to track down all roms even if their hardware didn't have said revision.

However, when the internal menu was added by Aaron, it didn't take this into account, and only showed games as available if all roms were present. It never bothered me enough to change, and I consider that it's a cool secret feature that you can launch incomplete sets from the command-line...
User avatar
Jul 3, 2016, 00:31
If this differential in functionality is known and intended behavior, then an issue doesn't exist to keep this status in Confirmed state.