clrmamepro [English] > clrmame Discussion

Clrmamepro not giving me option to scan mame 133b roms in merged sets mode?

(1/2) > >>

Dariusz:
Hi,

Just updated clrmamepro 3.127 with mame 133b, when I set to scan my roms dir, clrmamepro no longer gives me the option to scan my dir in merged set mode. It only gives me the option to scan in split sets mode. I don't have the problem when scanning mame 132b roms, but only happens with mame 133b???? Have I done some thing wrong?

D

Roman:
Possible reasons:

- you've loaded a datfile which does not have any parent/clone relationships defined
- you've loaded a datfile which uses "force merge mode" settings
- (most likely) during parsing the mame data you see several warnings about sets which can't be merged since they contain equally named files with different hashes. Merging them would kill one file as long as you don't use subfolders. clrmamepro shows a warning and asks you if you want to remove the parent/clone relation from them or force you to split-merged mode.

Go to profiler, click clean cache and reload the datfile to get the prompts again (and be sure to have "show common" enabled in Profiler->options->datfile errors)

Dariusz:
Thanks Roman,

The problem was relater to option 3. The issue has now been resolved.

Thank you.
D

Dariusz:
Roman,

I have another question which I hope you can clear up for me:

I read your doc relating to the scanning dialog options, and I don't understand what the difference and when to use the options: Sets and Roms.

I 've only ever used the option Roms for my scanning, and can see why there is a need to use Sets to be used in the scanning process?

You explanation to clarify is kindly appreciated.

I extracted below the description of Sets and Roms scanning from you doc below, if it helps.

Thanks in advance for you help.

 ---------------------------

Sets
Check this option if you want to check sets. Combine this e.g. with unneeded, name, missing or case check.


ROMs
This option should be enabled if you want to scan the files of a set. Combine this option with e.g. missing, unneeded, length, CRC32/MD5 checksum, case or name check.

Roman:
ok..rule #1: There is no reason on earth to disable the "SETS" option.

A set is a collection of roms and/or samples and/or chds.

Pacman is a set which consists of let's say 10 single roms. Sets have parent/clone relation ships. You can merge sets. You can store sets packed or unpacked.

The general storing method is: rompath\setname\file 1... file n for unpacked sets and rompath\setname.zip (.rar/.7z) for packed sets.

Having "sets" enabled, the cmpro checks check for example if "pacman.zip" is correctly named, while with only "roms" enabled it will look inside "pacman.zip" to see if the single rom files are correctly named. Similar applies to unneeded...."blabla.zip" in a rompath can be an unneeded set....maybe it's a valid set with a wrong name.....
Unneeded check on "roms" will look inside "pacman.zip" and maybe detects a readme.txt as unneeded.

So I think it should be clear now:

SET checks/fixes work *on* sets (the archives if you like to call it this way) and ROMS checks/fixes work *in* the sets.


again, rule #1: There is no reason on earth to disable the "SETS" option. So keep it enabled!!!!!!

Navigation

[0] Message Index

[#] Next page