MAMEDEV Forum

Hi

What is the preferred method of updating Mame on each release? I would like to preserve current configurations (i.e remapped buttons, hiscores, etc). Is it just a case of copying over the new executable?

Graham wrote:Hi

What is the preferred method of updating Mame on each release? I would like to preserve current configurations (i.e remapped buttons, hiscores, etc). Is it just a case of copying over the new executable?

Most of the time, it is a simple issue of downloading the latest binary and overwriting and duplicate files with the ones in the package. Rarely, there will be work done which will cause older .cfg files will need to be redone or certain commands stored in your mame.ini may have changed which will be announced with the released if widespread breakage of old files is expected. Beyond that, there isn't much to worry about. The hiscore script (which is an LUA plugin in official distribution) is very unlikely to regress and, depending on if work is submitted to the hiscore.dat file, there may even be increased compatibility (new clones/machines covered).

Hi Tafoid

Thanks for your reply. So you reckon just unzipping the latest build over the existing should do the trick? i just wanted to make sure that no "template" (basic structure) type ini or cfg files would overwrite any modifications that I may have made.

I just create a new directory to run the drivers that have been improved in that version. It's not like MAME's that big.

Hi cps1fe

I'm not sure what you mean by "new drivers"? Would unzipping the contents of each new release over the exisiting keep my current setup?

Redhat / Debian (Ubuntu) does a pretty good job in updating the software and not the configurations.
"apt-get update" "apt-get upgrade" and your software is update to date.

Would it be an option?

Hi gabriel.klein

I'm already using Ubuntu and as you mentioned, Mame works a treat with repositories . I'm currently running Mame on 2 platforms (Ubuntu 16.04 and Windows 7) using a shared "Mame" folder (for roms, snaps, etc). Was having a few issues with joypads in Ubuntu but that seems to be sorted now, so I was using the Windows version during that time. Sorry, I should have mentioned in the original post that I was using Windows.

Does the issue with joypad is related to joypad called joy1 joy2 then joy3 joy4
How did you fixed it?

I may have the same issue

Probably related to
https://www.reddit.com/r/MAME/comments/ ... _on_a_mac/

gabriel.klein wrote:Does the issue with joypad is related to joypad called joy1 joy2 then joy3 joy4
How did you fixed it?

I may have the same issue

Probably related to
https://www.reddit.com/r/MAME/comments/ ... _on_a_mac/

In my case, the up and down directions didn't work (within Mame GUI). At first I thought maybe the joystick wasn't supported under this version of Ubuntu (as it had worked in previous versions). Once into the game, left and right (inc. buttons) would work but still no up and down . Even though all directions were assigned to Joy1 Up, Joy1 Down, Joy1 Left and Joy1 Right. I ended up re-assigning these buttons which then appeared as "Joy1 A3 DragonRiseInc.GenericUSB Joystick -" and "Joy1 A3 DragonRiseInc.GenericUSB Joystick +".

Does your board looks like this one


I have two.

Sometime they appear as
Joy1 A3 DragonRiseInc.GenericUSB Joystick

Sometime
joy1 joy2 that become joy3 joy1 then joy4 joy1.

When I plug them in a different port / hub ... the behavior seams to change. (But I haven't been able to fix the issue.).

One of my issue
I configured the first one, the second one and in a game the second one is assigned to "player 2" and "player 1" (and seams to be linked to "joy1 joy2 joy3..." the other one if then linked to joy4).


What is strange is that Ubuntu seams to recognize them perfectly (I don't see that they are renamed.)

How did you fixed your issue?

I think it's a naming issues (they may have the same *name* = UUID on macos) somewhere... but I haven't found a way to "hardcode" this uuid or change the firmware of the joystick to have a different id.