2013-03-06, 13:13
(2013-03-06, 01:51)streets ahead Wrote: OK. after much trial and error I seem to have figured it out. I just changed the arguments to "%rom%" and removed the -initpath.Maybe the command line to use a specific inipath with MAME have changed. Normaly, if you start MAME without specify it, MAME should load the mame.ini file from its installation directory. But, some time it was happening that MAME was trying to load this file directly from the XBMC installation directory. In this last case it is necessary to specify where is located the mame.ini file (so using -inipath argument). But... it seems that it is not acually your case.
I don't know why that worked. It was just dumb luck on my part.
Thanks.