MAMEWorld Forums - News - Re: Mamesaver 2.0 released

> > Hmm i tried with command line mame but i have this error
>
> Thanks for reporting this! What version of MAME are you running? If you are able, can
> you go to the Advanced tab, enable debug logging, try it again, and send the relevant
> contents of the log file which will have been created in %temp%\Mamesaver?
>
> Older versions of MAME had a different XML file structure returned from -listxml, so
> I suspect this may be it if your path is correct.
>
> There's no reason why we can't add support for old versions if it's something which
> is important to people.

its actually the latest mame, 201. the folder is called "mameold" because i discern between command line (old) and ui( new) folders.

here's the log

2018-09-12 11:31:22.630 +02:00 [INF] Mamesaver started with args /p,132382
2018-09-12 11:31:22.817 +02:00 [DBG] Stopping screen cloning
2018-09-12 11:31:22.821 +02:00 [DBG] Stopping activity hook
2018-09-12 11:31:22.823 +02:00 [DBG] Container disposed
2018-09-12 11:31:24.289 +02:00 [INF] Mamesaver started with args /c:1312984
2018-09-12 11:31:27.076 +02:00 [DBG] Getting MAME rompath
2018-09-12 11:31:27.076 +02:00 [INF] Invoking MAME with arguments: -showconfig
2018-09-12 11:31:27.082 +02:00 [DBG] MAME started; pid: 12524
2018-09-12 11:31:30.211 +02:00 [DBG] Stopping screen cloning
2018-09-12 11:31:30.314 +02:00 [DBG] Stopping activity hook
2018-09-12 11:31:30.315 +02:00 [DBG] Container disposed
2018-09-12 11:31:30.498 +02:00 [INF] Mamesaver started with args /p,132382
2018-09-12 11:31:30.829 +02:00 [DBG] Stopping screen cloning
2018-09-12 11:31:30.833 +02:00 [DBG] Stopping activity hook
2018-09-12 11:31:30.834 +02:00 [DBG] Container disposed