Blakflag Posted November 3 Share Posted November 3 Hi all, I am having trouble launching any MAME 2.70 roms from a new Launchbox install on my desktop system. I am not a brand new user, I have a second arcade box that works fine, and I just redid my MAME set to 2.70 using the Full Set Importer successfully on that system. But when I tried the same procedure on my desktop, it installs MAME but will not launch any roms. The ROMS try to launch, the screen blinks and it fails. If I launch directly MAME 2.70 and add the rom path inside the MAME that got auto-installed, I can play games from MAME's own picker. The issue is with Launchbox invoking the emulator. The options are exactly as the auto-install set them. I tried removing almost every option and no luck. The logs complain about an image file being in use but I do not know if that is the issue. Adding a debug log of my trying to open 1943u. Thanks for any advice. Debug 2024-11-03 08-09-58 AM.log Quote Link to comment Share on other sites More sharing options...
Blakflag Posted November 3 Author Share Posted November 3 One other thing. I already tried excluding Launchbox folder from Windows Defender, in case that was locking the file mentioned in the logs. It did not help. Quote Link to comment Share on other sites More sharing options...
JoeViking245 Posted November 3 Share Posted November 3 50 minutes ago, Blakflag said: If I launch directly MAME 2.70 and add the rom path inside the MAME that got auto-installed, I can play games from MAME's own picker. I know you said you're not new and you've probably tried/did these rudimentary things, but based on what you shared, this is all I can think of. Also, the "cannot access the file [image_file]" exception occurs after starting the LaunchBox shutdown process (i.e. click the X to close LaunchBox). So is not related. When (in standalone MAME) you went to General Settings < Configure Folders, and set the ROMs folder, did you click Save Settings? aka, Saved to the rompath in mame.ini. If so, try removing -rompath %romlocation% from the Default Command-Line Parameters. If not, leave that in and double-check 1943u's Application Path. (D:\LaunchBox\Games\MAME 2.70 (Merged)\1943u.zip) And just in case, check in the Emulator section that it's pointing to MAME 0.270. Lastly, though I don't think it should affect things, try un-checking Attempt to hide console window.... Quote Link to comment Share on other sites More sharing options...
Solution Blakflag Posted November 4 Author Solution Share Posted November 4 On 11/3/2024 at 10:10 AM, JoeViking245 said: I know you said you're not new and you've probably tried/did these rudimentary things, but based on what you shared, this is all I can think of. Also, the "cannot access the file [image_file]" exception occurs after starting the LaunchBox shutdown process (i.e. click the X to close LaunchBox). So is not related. Thanks JoeViking245, I just figured out what was happening.. basically me being an idiot. I somehow had copied only a subset of roms I thought I had. Nothing to see here... 🙄 Thank you for helping! 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.