Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider donating by either clicking this text or the Patreon link on the right.

Patreon

Mame32 .111u5 - save files not working??


Recommended Posts

Posted

I just upgraded to .111U5.

I have always upgraded Mame32 in this fashion.:

Unzipped/overwrite my current Mame32 dirctory.

Download and overwrite my current CLRMAME directory

Open clrmame which updates it's databse with the new mame32.exe

Run my scan - add new roms

Start Mame32 and do an audit as I have disabled the startup audit.

For what ever reason now I bring up any game and the first thing I see is failed to load save state .... just like it's supposed to do when you open a game for the first time.

The problem is - I'm opening games that I've had running with highscores for about a year now - now their gone? Not cool at all.

I still have a ton of NV files in the NVRAM foder but it seems to just not care about them. The path is still set to NVRAM folder.

I've googled and have not seen anyone reporting this problem. Anyone having the same problem or can tell me what might be wrong?

Thanks for any help.

Posted
I just upgraded to .111U5.

I have always upgraded Mame32 in this fashion.:

Unzipped/overwrite my current Mame32 dirctory.

Download and overwrite my current CLRMAME directory

Open clrmame which updates it's databse with the new mame32.exe

Run my scan - add new roms

Start Mame32 and do an audit as I have disabled the startup audit.

For what ever reason now I bring up any game and the first thing I see is failed to load save state .... just like it's supposed to do when you open a game for the first time.

The problem is - I'm opening games that I've had running with highscores for about a year now - now their gone? Not cool at all.

I still have a ton of NV files in the NVRAM foder but it seems to just not care about them. The path is still set to NVRAM folder.

I've googled and have not seen anyone reporting this problem. Anyone having the same problem or can tell me what might be wrong?

Thanks for any help.

Try adding

-state_directory c:\emulators\mame\state -nvram_directory c:\emulators\mame\nvram

to your command line and see what happens. (Obviously, you need to change these paths to fit yours) :D

Emph

Guest
This topic is now closed to further replies.
×
×
  • Create New...