EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: Roman on 23 December 2014, 23:36
-
So what will change if you scan your MAME set with the new cmpro version:
- unmerged sets:
(you don't use this for MAME, do you...), nothing changes...
- split merged sets:
you will see some wrong placed roms now since clrmame did not kill parent/clone relationships
- full merged sets:
you will see several wrong named roms (due to hash collisions)
So what's new:
misc: Changed the way how hash collisions are handled. A hash collision happens when you got
identically named files with different hashes within a parent/clone relationship.
In the past cmpro either removed the parent/clone relationship completely or you were
forced to split merged mode.
Now, in case of a hash collision *and* only if switch to full merged sets (scanner,
rebuilder or merger), the rom names of the clones will be switched to a naming convention
which you can select. Default is setname\romname. You can select the naming in profiler
options 'Naming pattern'. A flyover tells you which variables you can use
there. %1 (plus something else) is mandatory here.
Again, only if full merged mode and hash collisions are active.
You also got an option there to say how many files get renamed. Either only the single hash
collision clone file, or all files in this clone set or all clone files in all clones of this
parent clone relationship.
added: added option (Settings screen) to allow a full merge mode which ALWAYS stores parent/clones
the way described above, no matter if a hash collision is there or not. This is the
"hash collision name" mode. If you're using this, the upper mentioned selection of files which
get renamed is obsolete. In this mode all clone files in the parent clone relationship are
renamed.
added: batcher rebuilder option "never compress files" which allows you to create unpacked sets
removed: "Possible wrong nodump definition found" cleanup step prompt. It's actually a special
case of hash collision and so it's handled the same way as other collisions.
misc: some intern changes so that you got theoretically 32k path length support (Hello Tosec..)
If you need such long paths, you need to add "\\?\" in front of your rom/sample/add/rebuilder
source/destination/etc paths..
So for example:
\\?\E:\temp\this is a long folder name right or wrong blabalbalblablablablabalabl\
misc: updated to latest unrar dlls
misc: merger works with subfolders
misc: "double roms detector" during parsing handles weird merge tag combinations better
misc: "double setname" is also performed when you're using "release" elements and switch modes
fixed: belongs_to_parent check fails on 0-byte files
fixed: weird messages when you enable the clone but disable its parent in full merged mode
fixed: remove obsolete wrong merging or missing set messages (which normally get removed in 2nd scan)
fixed: adding sampleonly sets may cause issues when you got softwarelist which share the setname
-
misc: some intern changes so that you got theoretically 32k path length support (Hello Tosec..)
If you need such long paths, you need to add "\\?\" in front of your rom/sample/add/rebuilder
source/destination/etc paths..
So for example:
\\?\E:\temp\this is a long folder name right or wrong blabalbalblablablablabalabl\
Hello Roman... ;)
Thanks again for this, most appreciated.
-
Thank you for the new version.
This new version seems to be having a problem. I get the following error:
---------------------------
Settings Problem
---------------------------
An error occured while reading information from:
D:\Mame\mame.exe
You either stopped the loading process or the file is corrupt.
---------------------------
I didn't get that message before this version of ClrMamePro.
I'm using Win7 Ultimate (32bit) and the latest binary of mame 0.156
It happens right at the end of loading the newly generated profile.
-
Thank you for the new version.
This new version seems to be having a problem. I get the following error:
---------------------------
Settings Problem
---------------------------
An error occured while reading information from:
D:\Mame\mame.exe
You either stopped the loading process or the file is corrupt.
---------------------------
I didn't get that message before this version of ClrMamePro.
I'm using Win7 Ultimate (32bit) and the latest binary of mame 0.156
It happens right at the end of loading the newly generated profile.
I had the same problem at first but i had to generate a BRAND NEW profile (means new name for the description, using "Create", not just "load/update" the old profile).
Now it works fine
NB : If you want to import back certain settings, just edit the old settings file and copy paste the corresponding lines into the new one.
I guess there are some incompatibilities between the settings files.
-
If you used a recent MAME from git.....there was a known error which created a bad xml list....
I don't think official 156 was affected (maybe a selfcompiled one which was not a clean build...)
If the error happens then something simply went wrong during data extraction...either MAME created a bad xml or there was not enough free diskspace..etc...etc...
-
Deleting the old profile was the ticket here.
All is working great now.
Thanks for the help! :)
-
If you used a recent MAME from git.....there was a known error which created a bad xml list....
I don't think official 156 was affected (maybe a selfcompiled one which was not a clean build...)
If the error happens then something simply went wrong during data extraction...either MAME created a bad xml or there was not enough free diskspace..etc...etc...
Well, when the same compiled MAME version worked with the previous CMP and not with the newer...
... and creating a new CMP setting file fixed the problem. ;D
-
hmm...weird..nothing really has changed when it comes to importing data from MAME and my profile is like 10 years old ;-)
-
Hi Roman , 4.016 is best but :
between options "Single file" and "All clones in Relationship"
When "All clones in Relationship" is active cmp create many double roms
I back to "Single file" - cmp rename only collision and remove double roms, think that is good
also i upload first 2 affected roms for test, tnx :)
[PS] after change "All clones in Relationship" to "Single file", cmp removed about 288MB double roms
-
hmm...weird..nothing really has changed when it comes to importing data from MAME and my profile is like 10 years old ;-)
That may come down to one particular option perhaps... I had to do it for both MAME and MESS...
Well it doesn't really matter to find the culprit if it doesn't come back i guess
-
oddi Im pretty sure it works correct. there are plenty of files which are shared within clones but not with their parent set and if you use that naming mode you will of course create dupes since then the identical files get different names. I will look at some examples in 2015. so it might look weird but could be correct.
-
oddi Im pretty sure it works correct. there are plenty of files which are shared within clones but not with their parent set and if you use that naming mode you will of course create dupes since then the identical files get different names. I will look at some examples in 2015. so it might look weird but could be correct.
Indeed it's working correct :) Thank You so much for this release Roman ;D
If you set your settings\Full Merge Mode to Hash Collision Name and your Hash collision option to All Clones in Relationship, You retain the benefits of the 7-zip merged compression while the sub folders and file organization is absolutely beautiful. The sub folders seem to match MAME's -listclones output 100% ;D
I'm permanently switching to the above settings to keep 100% consistency among my entire set with clones.
Thank You again Roman for all your work :) ;) ;D
-
Roman, thanks for great release!!
B2K24, thanks for the explanations.
as B2K24 suggested, i use these settings for MAME and HBMAME merged sets:
-
Hello Roman, have little request :
Please add this two options from Settings "Normal Mode" and "Hash colission names" in batch mode, many tnx :)
-
As far as I remember this option is a general "global" option, not per-profile...so you simply change or not change the option before the batch and after...
I will double check my assumption though....
edit.... ok ..I was wrong..the general settings are the format and which files to rename...but not the normal mode/hash collision mode one...that's really per-profile...
ok...I will put it on the request list to have that as batch option