-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cfg and nvram not being created [$10] #13
Comments
Presumably this is also the reason why settings in the MAME "tab" menu are not saved between sessions with this core as mentioned here: #29 (comment) |
@r-type I apologize I keep tagging you, but this issue seems like it could also be a simple path or permissions problem in mame2000 |
no , it's not directly related. let me explain why it's not working... First , //parse_cmdline (argc, argv, game_index); is commented
Secondly, when you exit game in mame2000 , it exit roughly the core thread.
a quick hack (for WANT_LIBCO) will be to use a variable int libco_quit=0;
and in void cpu_run(void) (cpuintrf.c)
this will lead that the core thread will ending and writing file before RA quit the core. thirdly, maybe it will remain the WIN32 slash problem in fileio.c ...
to
|
another problem is that this core does not create the folder , what add to backport something like |
#47 should fix build introduce with errno. |
@r-type you should go ahead and claim this bounty, I think! Thank you for your work. |
@markwkidd if you have an account. |
@r-type that is fine with me. However I may be tempted to add the money to this bounty -- are you any more interested in it? libretro/mame2015-libretro#54 |
@daweze or @twinaphex would you be willing to close this issue so we can roll the bounty forward to another issue? |
In my testing, this does appear to work properly now as openice now will write out nvram and read it in next play session. |
imame4all appears to not write out save games or any data after it is run rendering games that save user statistics broken.
The MAME core is not dumping a cfg file or nvram file for games. Each time the game is launched, you get the legal disclaimer which is only supposed to show when there is no cfg file and you'll see that the nvram is always reset.
There is a $10 open bounty on this issue. Add to the bounty at Bountysource.
The text was updated successfully, but these errors were encountered: