Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All ThreadsShow in Flat Mode*


SubjectRe: ClrMAMEPro Fails to Rename Conflicting ROM Files Reply to this message
Posted byf205v
Posted on08/19/07 10:58 AM



> If two different ROM sets have some common ROM files, but with different names,
> ClrMAMEPro totally fails to rename them if they have the names switched.
> Exemplifying:
>
> * ROM Set 1 has a ROM file named "abc.123" (correct name for that set);
> * ROM Set 2 (either a clone of ROM Set 1 or an entirely different game) uses
> exactly the same file "abc.123", but it should be named "rom-1.bin".
>
> When CMP scans ROM Set 1, everything is fine, ROM names are correct, but when it
> scans ROM Set 2, it finds the file "abc.123", reports it as belonging to ROM Set
> 1 and, after that, reports missing file "rom-1.bin". It's obvious that the
> sequence of checking is completely wrong, it should first check if the ROM
> belongs to the set (by CRC) and, IF IT DOES NOT BELONG TO THE ROM SET, it should
> check if that ROM file belongs to another ROM set. If it belongs, but the file
> name is not correct, it should prompt for renaming. If the other ROM set is also
> missing the file, it should be able to copy the ROM file into it, with its
> correct name.
>

There is something wrong in your settings/files (maybe bad zipstructure), because what you describe is NOT the real behaviour of cmpro.
In the "scan" windows, you have to select ALL "fix" toggles (and make sure that backups are enabled, as described in previous post), and cmpro WILL do exactley as you expect it.

ciao
f205v

-
Entire Thread
Subject  Posted byPosted On
*ClrMAMEPro Fails to Rename Conflicting ROM Files  temporalbolt08/19/07 09:01 AM
.*It's a case of priority  Roman08/19/07 02:12 PM
..Re: ClrMAMEPro Fails to Rename Conflicting ROM Files  f205v08/19/07 10:58 AM