-
Notifications
You must be signed in to change notification settings - Fork 50
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
mame creates folders cfg and nvram in the home dir #14
Comments
@sergiobenrocha2 is this still the case with mame2010? |
yup |
I've found the reason for this issue: So, I made the following:
I.e., change from this:
to this:
|
It does seem like this should work by default like mame2003, which handles this more gracefully and in a cross-platform manner. |
mame2003 takes, by default, the current rom folder to create the So, if you're using mame under |
Hi there, Thanks for posting this workaround. So just to confirm, until the core is changed so the paths are more graceful, with your workaround, ultimately you end up with a mame.ini in your home folder, and then the other cfg and nvram paths in the more conventional place? And MAME no longer ignores the .ini for games like Operation Thunderbolt? Thanks! |
Hi @movisman! Yes, with the |
Perfect! Thanks a lot for the clarification. I will do this with my MAME 2010 instance to tidy things up a tad, until such a time comes where the paths are properly tidied up. Thanks again! |
@sergiobenrocha2 or others in this discussion, I've submitted a PR that I hope addresses this issue and others caused by the way mame2010 handles paths: #83 I wound up touching several different source files. It all seems to work on my system but if you have the ability to test it out and confirm I'd appreciate it. |
@sergiobenrocha2 the PRs have been merged and I am hoping that this issue is now fully resolved. Please let me know if you notice other problems. |
It's quite annoying, this mame core creates cfg and nvram folders in your ~/ or in the folder you launch RA in the terminal.
The text was updated successfully, but these errors were encountered: