roms work in mame32 but not in windows commandline mame ? help !

[david656]

i have quite a few roms that work fine in the 'lastest' mame32 but not in the 'latest' command line mame

any idea's? its really anoying me !

thanks a lot

[TheShanMan]

By "latest" I assume you mean matching version numbers, like .125. And there is no such thing as mame32 .125, but I presume you mean mameui.

Try putting the mame.exe file in your mameui directory and see if it works then. There's probably a difference in configuration between your mameui and command line mame directories.

Personally, I use mameui as my command line mame anyway. No real downside to doing so as far as I've been able to tell (calling it like command line mame just bypasses the front end part).

[david656]

mame 32 .103  and cmd mame .125 are the ones i am using

humm thanks for the quick input i tried it but it appears to still not be working,

they have changed the way the roms work since the old mame i used to use so now its asteroids rev 2 as a parent rather than rev 1 as was in the older mame 32 .91

but what is interesting is asteroids still didn't work in the older cmd mame at that time either and i thought the newer one might.

it comes up with the error missing roms or CHD's

anyone know what its missing in commandline mame ?

i have all the bios files in there too just incase they're needed

[TheShanMan]

You're definitely going to run into problems trying to mix such differing versions of mame and mame32. In addition to the fact that many roms changed between .103 and .125, command line options may have changed to some degree as well (I don't know).

You need to match your versions of mame and mame32/mameui as well as get a set of roms that are compatible with the version of mame you're running.

I'm presuming that your roms are matched to mame32 .103. If you want to update to .125 then make sure you update whatever roms aren't compatible with .125 and then drop your mame32 version altogether.

May I ask why you're converting to command line mame? Is it to get new features? If not, why not just stick with mame32 and call it as though it's the command line mame?

[Space Fractal]

frontends never user mame32 with its GUI, why he might have tested the commandline.

Yes, dont mix the versions, since roms can been changed and then some might not work anymore.

Download version .103 of commandline if you want to use this with a FE, if you have roms for version .103.

[TheShanMan]

Nah, you can use mame32/mameui with front ends (well, I should say that I have been doing so with mameui .122 and onwards so I don't know for sure with mame32 .103). It may not be "recommended" by the FE's but I've never had trouble with it. I simply use mame32 for game option configuration and then let the FE call "mame32.exe <rom>". Works great.

[david656]

frontends never user mame32 with its GUI, why he might have tested the commandline.

Yes, dont mix the versions, since roms can been changed and then some might not work anymore.

Download version .103 of commandline if you want to use this with a FE, if you have roms for version .103.

thanks for the advice i had a go at it and obviously it all went fine :-)  thank you for your help and input as to the rest

just seems a shame i have to use a version of cmd mame thats 2 years old !

why is mame 32 so far behind ?

[Ginsu Victim]

It's not Mame32 anymore, that's why.

[u_rebelscum]

It's not Mame32 anymore, that's why.

Yup.  It has a 64 bit version, and mame3264 is confusing, while MameUI32 vs mameUI64 are clearer.  And more truthful, since official mame has been 32 bit for years, too.

MameUI is up to the same as official mame, and is usually less than a couple hours behind official mame.