Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[s_bastian]

We often see in forums people speaking about the use of different versions of MAME to play. EG: standard 0.139 for normal use, wolfmame 0.106 for recording inp. I imagine that those persons are now keeping two complete separate sets, and have set different paths to do it. Wouldn’t it be useful to have cmpro handle more than one dat simultaneously, as “separate” or “fully merged”?

A developing idea might be
- Set one set as MAIN (eg 139.dat) and one as ALTERNATE (eg 0.106)
- Set the option to MERGE the two sets or to keep them separated, and set the relative folder/s
- Rebuilder/scanner should check that ALL ROM from the MAIN set are in the main ROM folder
- Regarding the ALTERNATE set, cmpro should IGNORE the COMMON roms (they are already in the MAIN) and put the alternate roms in the alternate folder OR into the main romset by appending a suffix to the rom name, eg, 0000lo.bin.106.  As MAME reads first the CRC32 from the ZIP heading to choose the rom to be loaded the presence of the suffix should not be a problem when loading the roms

This function should allow people to use multiple MAME versions keeping the number of roms to the minimum. It will be enough to set a double rompath (in case of split set), or to point both MAMEs to the same folder (if merged) and MAME will do the rest.
Can this be a good idea?

[Roman]

why not simply using logiqx' supplement dats instead, which were created for multi emu users.

[s_bastian]

I had a check on the "superdat" in logiqx site, but that's not what I meant. This dats cannot combine eg multiple versions of the same emulator, like I told.

[Roman]

supplement dats... not superdats.

[s_bastian]

*me feels stupid, but I cannot find them... O_o

[donnyj]

split-merged

and

fully-merged

the links are right after the supersets on this page

[s_bastian]

foun them, but again, unless I am missing something, they are not what I am looking for. Can you explain how I can use them to rebuild a MAME 0.139 AND mame 0.106 together? They say they are to optimize MAME and other emu sharing the roms, not to optimize mameUI 0.139 and Wolfmame 106, to make an example...

[Roman]

There is no sense in keeping more than one MAME version (which is the most current).

[s_bastian]

As explained at the beginning, there actually IS sense, eg, for people playing on turnaments or submitting inps to sites like MARP and having the need to use wolfMAME 106, but still willing to keep their main mame release up to date

Anyway, nothing to bother about, it was just an Idea

[Roman]

Then you can still use mamediff to create supplement dats for old mame versions.