mrrockitt Posted September 17, 2015 Author Share Posted September 17, 2015 Hi, I'm new to Launchbox and loving it!! Got all my emulators working on it except one, Mame32. I initially tried Mame64 on my Windows 7 64-bit machine but had a problem at which point I decided to try Mame 32 instead. Got the same issue with Mame32, the roms simply do not launch, I get the briefest glimpse of the 'Initializing' window flashing up and that's as far as I get. Strange thing is, if I run the mame32.exe file directly from the Mame32 folder that I placed under my Launchbox directory, I can launch every rom fine. I have even run all my roms through RomCenter using my Mame32 install first to tidy them up and fix issues and more work now in Mame32 than did before. They just won't launch through Launchbox! I have checked my Mame config in Launchbox, I am definitely pointing at the right directory to launch it and the right directory for my roms, (all of which are zipped as usual). I think it must simply be the command line options that Launchbox does or does not apply to my Mame32 install which are different from the options Mame32 applies when run directly, does that make sense? Any help much appreciated :) Thanks Russ Quote Link to comment Share on other sites More sharing options...
spycat Posted September 17, 2015 Share Posted September 17, 2015 Hi Russ. Are you talking about Mame32, the Windows GUI version of Mame. I used to use this a long time ago. It did the job, but I wasn't too keen on it and switched to using the official Mame, first with EmuLoader and now LaunchBox. I use LaunchBox to play Mame emulated games and EmuLoader just for easy gui based configuring of Mame. Out of curiosity I searched it out. Apparently it's been replaced with MameUI32, so I downloaded this (version 0.146) and copied my Mame roms and sound samples to it. When I ran an audit, it rejected some of my roms mainly due to my neogeo bios being a different version. I set it up in LaunchBox and it's working fine - tested Zaxxon, Osman and several other availables and they all launched ok. Here are images of MameUI32 set up in my LaunchBox. Your paths will be different of course. Quote Link to comment Share on other sites More sharing options...
mrrockitt Posted September 18, 2015 Author Share Posted September 18, 2015 Hi scree, thanks for advice, I will try MameUI32 as you suggest as I think that is probably the answer. Will reply when I find out just in case others have the issue. Russ Quote Link to comment Share on other sites More sharing options...
TheSickness Posted September 18, 2015 Share Posted September 18, 2015 I had this same issue. Maybe the solution won't be the exact same for you but it's worth a shot. I initially had all my Mame roms imported into LaunchBox and copied into the LaunchBox games folder. They were not located anywhere else on my PC. Read: none of my roms were actually sitting in the rom directory inside of the Mame install itself. Same results, I'd launch a game and get a glimpse of the initializing screen. What I did was copy all my roms into the Mame roms folder as well (so now I have a copy in LaunchBox's games folder and in Mame's roms folder). This corrected the issue and they all launch fine now. I believe Mame checks it's own roms directory upon launching a game, and likely still reads the roms from there regardless of where they are launched from. This may be further supported because I have games that require CHD's to launch, and those CHD's are ONLY located in my Mame roms directory, not anywhere in launchbox's game directory. Yet, I launch those from the game's zip stored in the LaunchBox games folder and they work fine, even though the CHD's are not in the same folder with them. I do not know of a way to force Mame to read it's roms from a different directory other than it's own, but I'm sure there is one. Note: I found the exact same situation to be true of the Atomiswave emulator within Demul Quote Link to comment Share on other sites More sharing options...
mrrockitt Posted September 18, 2015 Author Share Posted September 18, 2015 Hi to TheSickness! I tried that myself, had the same thought that it might be something about the roms location but after copying Afterburner and Afterburner II into the Roms folder of my Mame32 install, wiping my whole Arcade library in LaunchBox and then reimporting just the Afterburner games from there, still no luck. However, I can report that doing as scree said worked! Mame32 did not work for me but Mameui32 works fine! Thanks to you both for the help :) Quote Link to comment Share on other sites More sharing options...
DOS76 Posted September 18, 2015 Share Posted September 18, 2015 MAMEui64 works also Quote Link to comment Share on other sites More sharing options...
mrrockitt Posted September 18, 2015 Author Share Posted September 18, 2015 Was wondering about that but taken me a while to get roms working at all so reluctant to try :) Thanks Quote Link to comment Share on other sites More sharing options...
eric Posted September 19, 2015 Share Posted September 19, 2015 go here ...http://mamemania.forumfree.it/?f=10509624 Quote Link to comment Share on other sites More sharing options...
spycat Posted September 19, 2015 Share Posted September 19, 2015 Hi TheSickness. The problem seems to be that you imported your Mame games into the Games folder in LaunchBox instead of the roms folder inside your version of Mame. Mame's roms folder is where the emulator expects the game files to be, unless you reconfigure it to look elsewhere. If all your game, bios and device roms and your chds are in there, then there is no need to keep a duplicate copy of them elsewhere in LaunchBox. These are doing nothing just taking up space and they can be deleted. 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.