mrrockitt

Was wondering about that but taken me a while to get roms working at all so reluctant to try :) Thanks

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 :)

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

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