Cannot read mame configuration with latest 262 mame release

[Solstar]

here's the error, when i try to run the screen saver after updating the emulator

[mika76]

Please turn on logging and see what errors might be there: See https://github.com/mika76/mamesaver#logging

[nullpainter]

Have you had any success, @Solstar ?

[McHale72]

Just tried using 3.0 today using various versions of MAME and it found no ROMS after a scan (rebuild list). Versions from .139 to current.

[nullpainter]

@mika76 would you like me to take a look at this?

[mika76]

Hey @nullpainter sure go for it - maybe see if pull request #54 has anything useful as I never pulled that in at the time...

[nullpainter]

here's the error, when i try to run the screen saver after updating the emulator

Can you attach the output of the latest file in %TEMP%\MameSaver\Logs please (so, C:\Users<username>\AppData\Local\Temp\MameSaver\Logs...`) - I don't have this issue locally, but am having issues with Windows 11 not focusing MAME. Mamesaver hasn't been updated for years, so I will look at this first.

You can also try to run MAME from the command-line using the same arguments as Mamesaver. e.g.:

.\mame.exe lresort -skip_gameinfo -nowindow -noswitchres -sleep -triplebuffer -sound none

If this fails, there may be an issue in your MAME config (as the error indicates)

[nullpainter]

Just tried using 3.0 today using various versions of MAME and it found no ROMS after a scan (rebuild list). Versions from .139 to current.

Sorry, what do you mean by 3.0? This feels like a separate issue.