Mame issue launching and general issues

[Jacobjacobs3]

Trying to launch new mame .288 and this is the error i'm getting. Anyone have the same issue?

 

Running windows 10 x64 enterprise edition. Thank you

[JoeViking245]

6 hours ago, Jacobjacobs3 said:

Trying to launch new mame .288 and this is the error i'm getting. Anyone have the same issue?

Never seen such a thing.  What exactly are you doing when you see that?  Are you seeing that by just double-clicking mame.exe from windows explorer?  If so, your MAME setup is corrupt. Redownload it and install it over your existing build.  If not, what happens when you do double-click mame.exe from windows explorer?

[Jacobjacobs3]

It happens when i launch from both launchbox and windows explorer exe.

[JoeViking245]

17 minutes ago, Jacobjacobs3 said:

It happens when i launch from both launchbox and windows explorer exe.

Delete the files in your existing MAME folder and manually redownload it from MAMEDev's site and install into that folder.  (or delete the folder and install)  Be sure to download the x64 binary and not the Arm64 build.  Then try starting it from Windows Explorer.

[Jacobjacobs3]

Same result unfortunately.

[JoeViking245]

41 minutes ago, Jacobjacobs3 said:

Same result unfortunately.

Make sure your video drivers are up to date.

Open the windows Command Prompt (from your MAME folder) and run "mame.exe -v".  This should give you a verbose output showing you what it's doing and better details about where it's hanging up at.

 

[Jacobjacobs3]

Same result with the running from cmd "mame.exe -v"

[JoeViking245]

37 minutes ago, Jacobjacobs3 said:

Same result with the running from cmd "mame.exe -v"

Try downloading an older release of MAME (don't worry about the ROMs, yet).  See if you can at least get it to launch from Windows Explorer or the Windows Command Prompt.  If you can't get it to launch there, it won't launch from LaunchBox.

If you still get that same error, you're going to have to ask the MAME folks about the issue.

[Jacobjacobs3]

So .273 and before works but now some roms dont. Is that the trade off i have to deal with? Lol

[JoeViking245]

19 minutes ago, Jacobjacobs3 said:

So .273 and before works but now some roms dont. Is that the trade off i have to deal with? Lol

Maybe not go back that far. Try 0.287.  Or did you start there and nothing worked until 0.273?

And yes, some ROMs won't work. But may be ones you won't notice or care about. (can deal with that later)

[Jacobjacobs3]

i tried every release back till that one and nothing. Yeah... lol

 

[JoeViking245]

34 minutes ago, Jacobjacobs3 said:

i tried every release back till that one and nothing. Yeah... lol

So, releases 0.274, 0.275, 0.276, ..up thru.., 0.288 all give that same error?

Dang. K.  So I guess we're back to "you're going to have to ask the MAME folks about the issue."  And in the meantime, don't play the games that don't work. But do play the ones that do.  

[Jacobjacobs3]

i may have discovered the issue. but cannot check for another day or two. My install of windows is special. Its and win 10 enterprise LTSC which means its stripped down and my not have the dependencies the program requires.

[JoeViking245]

11 minutes ago, Jacobjacobs3 said:

i may have discovered the issue. but cannot check for another day or two. My install of windows is special. Its and win 10 enterprise LTSC which means its stripped down and my not have the dependencies the program requires.

👍 That would make sense.  Hopefully you can find out exactly which dependencies need insalled.