Mame trouble after newest update.

[Kagan]

Hi all, 

After the newest update I started having trouble with launching Mame-games. Some still launch fine but a lot of the simple refused to launch, and after looking at the error promt the problem seems a bit strange: 

With 1942 as an example I get this "srb-03.m3 NOT FOUND (Tried in 1942 1942)"

It seems to be searching for the files in a 1942 folder within a 1942 folder and I have no idea why! The files are all there within the original 1942 folder, but of course not in a folder named 1942 within the 1942 folder.

It might just be a simple thing, but as said some games work whereas most others dont.

Can anyone help? - thanks!

[Lordmonkus]

This message is telling you that the rom is missing files that it needs.

If the game was working before then something in the Mame update broke the rom version you had before and you either need to update your roms or roll back to the version of Mame you were using before.

[Kagan]

I appreciate the answer, but that does not make any sense.

1. Everything was working fine before Launchbox was updated. The romset was running with a version of Mame for that specific romset and had worked fine.

2. I updated to a new romset, got the matching version of Mame and have everything working without any problems on another PC. It also works fine if I run the rom directly through Mame  on the arcade-machine, but not when it is set up through Launchbox.

3. The error specifically says that Mame is looking for roms within another version of the rom-folder.

Using 1941 as an example, normally Mame would look for files inside the 1941.zip folder. The error message I get here, says that it is looking for the files inside a folder called 1941, within the 1941.zip folder beforee looking for the files.

Can the Launchbox-standard command prompt for Mame-emulators be at fault?

[neil9000]

14 minutes ago, Kagan said:

I appreciate the answer, but that does not make any sense.

1. Everything was working fine before Launchbox was updated. The romset was running with a version of Mame for that specific romset and had worked fine.

2. I updated to a new romset, got the matching version of Mame and have everything working without any problems on another PC. It also works fine if I run the rom directly through Mame  on the arcade-machine, but not when it is set up through Launchbox.

3. The error specifically says that Mame is looking for roms within another version of the rom-folder.

Using 1941 as an example, normally Mame would look for files inside the 1941.zip folder. The error message I get here, says that it is looking for the files inside a folder called 1941, within the 1941.zip folder beforee looking for the files.

Can the Launchbox-standard command prompt for Mame-emulators be at fault?

Have you told your new version of the emulator the path to your MAME roms? MAME has to know that path as well as Launchbox.

[Retro808]

16 minutes ago, Kagan said:

I appreciate the answer, but that does not make any sense.

1. Everything was working fine before Launchbox was updated. The romset was running with a version of Mame for that specific romset and had worked fine.

2. I updated to a new romset, got the matching version of Mame and have everything working without any problems on another PC. It also works fine if I run the rom directly through Mame  on the arcade-machine, but not when it is set up through Launchbox.

3. The error specifically says that Mame is looking for roms within another version of the rom-folder.

Using 1941 as an example, normally Mame would look for files inside the 1941.zip folder. The error message I get here, says that it is looking for the files inside a folder called 1941, within the 1941.zip folder beforee looking for the files.

Can the Launchbox-standard command prompt for Mame-emulators be at fault?

Are you using MameUI orArcade64 by any chance? Also what version # is your Mame? I have seen that error with older versions of those two emulators. 

[Kagan]

@neil9000: Good tip, I will try that!

@Retro808: I tried standard Mame and MameUI, and just gave Arcade64 a go. Version number for all of them are 201 to match the Romset. All work fine directly through Mame, but not through Launchbox.

 

[JoeViking245]

If they all work fine running directly through the emulator(s), and not through LaunchBox, 1st thought is double check the rom's location in Edit game(s).  (stranger thins have happened...)

Next verify the emulator settings in the Emulation tab.  Edit the emulator selected.  Verify the emulator path is pointing to the correct (updated) location/executable.  You mentioned looking for a file in a folder in a zip.... Could it be somehow "Extract ROM..." inadvertently got checked?   

[Retro808]

2 hours ago, Kagan said:

@neil9000: Good tip, I will try that!

@Retro808: I tried standard Mame and MameUI, and just gave Arcade64 a go. Version number for all of them are 201 to match the Romset. All work fine directly through Mame, but not through Launchbox.

 

But which version were you originally using?

Make sure in the folder where your Mame.exe is you see the Mame.ini file. If not look in the ini folder for it and try copying it and pasting into the main folder where the exe is. I can replicate this exact error if the ini file is in the sub folder called ini. This is with MAmeUI and Arcade64. command line Mame not an issue as it stores the ini once generated in the main folder. 

The pic below is just now from removing that ini from the main folder. 

 

[Kagan]

Hi all, 

It is almost embarrassing to write, but @neil9000 simple advice turned out to do the trick - I simply had to correct the ROM-path in Mame to the new ROM-folder for it all to work - that I was able to forget that kindda shows how long it has been since I updated Mame!...

I still do not know why my previous version of Mame suddenly stopped working after updating Launchbox though.

I greatly appreciate all the answer in here - thank you all for the help.

 

Edited July 1, 2019 by Kagan