Error when used with MAME 0.227 about mamesaver

[mika76]

Which version of mame are you using?

[VonSupponnatime]

I apologize, I incorrectly indicated 0.227 in the header of this email. I'm actually using 0.232. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

…

On Wed, Jun 16, 2021 at 3:42 PM Mladen Mihajlović ***@***.***> wrote: Which version of mame are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APJSSWXK5E2CGEX3BJK6LPDTTD5D5ANCNFSM46YDA32A> .

[mika76]

Heh I finally checked this out - and tried it with the currently latest MAME 0.259 and it seems to be working fine. Maybe it was something in the actual MAME config which was broken?

You can always turn on the Debug Logging checkbox in the settings and it should log any errors to %LocalAppData%\Temp\Mamesaver\Logs see here.