Topic: fully merged set - problem with clone CHDs (Read 30823 times)

f205v · « **on:** 08 December 2015, 20:34 »

Hi ppl,
I just updated my spare machine with MAME 0.168, started clrmame, pointed it to mame64.exe and set 2 rompath:
D:\mame-roms
D:\mame-chds
I'm not collecting CHDs on this machine, so in the second directory I only have a bunch of empty folder, with the right name to make clrmame happy and avoid complains about "missing chds".

My scanning setup is:

After scanning I get the following:

The error is the same on all sets.

If I move folder "chaosheaj" into folder "chaoshea" or if I altogether remove "chaosheaj", I get the following in both cases:

How do I solve the problem and get back to a perfect "no miss - no errors" report from clrmame?

TIA for your help

Roman · « **Reply #1 on:** 09 December 2015, 08:47 »

Generally, for merged sets, cmpro will moan about clone folders since the clone chds should be placed in the parent folder, too.

If I remember correctly, you can't fool cmpro anymore by having empty folders for chds you don't have. So you end up with the problem that there are chd-only sets in MAME which of course appear as "missing set" if you don't have the chd.

What you can do:

Well, you can of course disable chd-only sets in set-information...but currently that's a lot manual work...maybe I add a new variable in the select sets field....

...or you generate yourself a datfile where chds are removed totally (should be pretty easy via a xslt transformation)

...or you can fool cmpro by placing chd placeholder files in your folder....a 0 byte file won't enough...I guess you need an empty chd file (so with header etc...)......but I'm not sure at the moment if the set check does check if the chd is valid for the set (i.e. checks the stored sha1)...

...or I add an ugly option to not list such missing chd-only games (but I don't like this idea)

f205v · « **Reply #2 on:** 09 December 2015, 09:45 »

OK, thank you for the explanation.
If you could add a new variable in the select sets field like:
1)"disable all CHD sets"
2)"disable CHD only sets"
3)"keep CHD sets"
that would be highly appreciated by all people who are not collecting CHDs

In the mean time I'll disable them one-by-one.

Roman · « **Reply #3 on:** 09 December 2015, 10:17 »

well %h=1 marks all sets WITH chds....Actually I thought that %h=0 marks all without chds but it does not...I will double check and fix that...and yeah...I can imagine something for chd-only and sample-only sets

Roman · « **Reply #4 on:** 19 January 2016, 20:21 »

ok...pretty busy with real life lately...but still thinking about your request...
...and I got some flag which enabled/disables sets with 'real' roms....(%R=0/1)...

a rom is a "real rom" when:
- not a nodump rom
- set is not a biosset and listed rom is a bios rom
- set is a clone and listed rom belongs to parent

...and in case the upper test succeeds and the set is a clone, the parent set roms are also checked for:
- not a nodump rom
- set is not a biosset and listed rom is a bios rom

the results looks pretty ok for me at the moment (you mainly get chd-only or nodump-only sets). Would be interesting to compare them to your list...

so....can you create a list of your disabled sets please? (.169 prefered as a basis)

That can be a basis for a chd-only set....I can simply then double check the result with "got at least one (no nodump) chd.....

Roman · « **Reply #5 on:** 19 January 2016, 20:36 »

The current (169) chd-only lists should look like this...shouldn't it?

2spicy
bbhsc
bhead2k
bhead2k2
bhead2k3
bhead2ka
bmiidxs
bntyhunt
carnking
chaosbrk
chaoshea
chaosheaj
chasehq2
cndypuzl
cr589fw
cr589fwa
flipmaze
ghostsev
gobyrc
goketsuj
gtfore04
gtfore04a
gtfore05
gtfore05a
gtfore05b
gtfore05c
gtfore06
gvrxpsup
gvrxpsys
gwinggen
haremchl
homura
hotgmkmp
hyperv2
initiad4
initiad4c
kof98um
kollon
kollonc
lasstixx
lbvbiosu
lsrquiz
lsrquiz2
mahjngoh
mgnumber
mgprem11
nfsug
nightrai
odeontw2
orbatak
otenamhf
otenamih
otenki
popn9
ppp2nd
primevah
psyvaria
psyvarrv
quake
quizard
quizard2
quizard2_22
quizard3
quizard3_32
quizard4
quizard4_40
quizard4_41
quizard_10
quizard_12
quizard_17
raiden3
raiden4
raycris
rcdego
samspsen
shanghss
shangtou
shikiga3
shikigam
sianniv
soutenry
speeddrv
spicaadv
spuzbobl
spuzboblj
tmosh
tokyocop
trbwtchs
usagi
usagiol
vtennis3
wontmuch
xiistag
zokuoten
zooo

Roman · « **Reply #6 on:** 19 January 2016, 21:03 »

That's all??? hmmm. imteresting....guess I will have a closer look at the sets from my list hich don't appear in yours....guess it's something obvious.....

f205v · « **Reply #7 on:** 19 January 2016, 21:06 »

Sorry, in the haste I made a mess.
Here is my correct list:

You are missing 112 of 35893 known MAME sets (+ BIOS sets)

2spicy
bbhsc
bhead2k
bhead2k2
bhead2k3
bhead2ka
bmiidxs
bntyhunt
carnking
chaosbrk
chaoshea
chaosheaj
chasehq2
cndypuzl
cr589fw
cr589fwa
flipmaze
ftaerobi
genpin
ghostsev
gobyrc
goketsuj
gtfore04
gtfore04a
gtfore05
gtfore05a
gtfore05b
gtfore05c
gtfore06
gvrxpsup
gvrxpsys
gwinggen
haremchl
homura
hotgmkmp
hyperv2
initiad4
initiad4c
kof98um
kollon
kollonc
lasstixx
lbvbiosu
lsrquiz
lsrquiz2
mahjngoh
mgnumber
mgprem11
moepro
moepro88
moepro90
mpsaikyo
mptennis
nes_bandai_pt554
nes_jf13
nes_jf17_pcm
nes_jf19_pcm
nes_jf23
nes_jf24
nes_jf29
nes_jf33
nfsug
nightrai
odeontw2
orbatak
otenamhf
otenamih
otenki
popn9
ppp2nd
primevah
psyvaria
psyvarrv
quake
quizard
quizard2
quizard2_22
quizard3
quizard3_32
quizard4
quizard4_40
quizard4_41
quizard_10
quizard_12
quizard_17
raiden3
raiden4
raycris
rcdego
samspsen
shanghss
shangtou
shikiga3
shikigam
sianniv
smoepro
soutenry
speeddrv
spicaadv
spuzbobl
spuzboblj
terao
tmosh
tokyocop
trbwtchs
usagi
usagiol
vtennis3
wontmuch
xiistag
zokuoten
zooo

f205v · « **Reply #8 on:** 19 January 2016, 21:21 »

So, my list has the same sets as your plus:
ftaerobi
genpin
moepro
moepro88
moepro90
mpsaikyo
mptennis
nes_bandai_pt554
nes_jf13
nes_jf17_pcm
nes_jf19_pcm
nes_jf23
nes_jf24
nes_jf29
nes_jf33
smoepro
terao

Roman · « **Reply #9 on:** 20 January 2016, 06:36 »

These are sample-only sets if I remember correctly....

but you say my list if (chd-wise) complete and matches yours?

f205v · « **Reply #10 on:** 20 January 2016, 07:22 »

yes, your list is fully included into my list.

Roman · « **Reply #11 on:** 20 January 2016, 08:04 »

so I guess for the next version you can use %H=0 (no chd-only-sets) plus %P=0 (no sample-only-sets)....or something ;-)

f205v · « **Reply #12 on:** 20 January 2016, 13:17 »

Thank you so much!
I can't wait for it.

Roman · « **Reply #13 on:** 20 January 2016, 20:25 »

Little thinking mistake when I said %H=0;%P=0...so what happens...
%H=0 enables all non chd-only sets (sample only sets are part of this...)
%P=0 enables all non sample-only sets (chd-only sets are part of this...)
so combining this...will enable all ;-)

correct is %H=1;%P=1 plus INVERT button (plus "initial invert checkbox)

So...we enable all chd-only and all sample-only sets and then invert the selection ;-)

f205v · « **Reply #14 on:** 21 January 2016, 18:06 »

Thank you very much for this.
It's a little convoluted, but if it works it's OK.

What about making it some sort of radio button, just to make it "newbie" proof.

I know of a lot of people that do not collect CHDs, and they would love to have a simple way of discarding them from the internal DB of clrmame.
Also, if it's a setting, it wil get saved into ini and manteined while updating from one version to the next.

Roman · « **Reply #15 on:** 21 January 2016, 19:57 »

The select sets settings in set info will be stored and reassigned even after an update....

coccola · « **Reply #16 on:** 21 January 2016, 20:54 »

I don't get it.

Shouldn't "You want to scan" ==> CHDs = disabled be enough?

Roman · « **Reply #17 on:** 22 January 2016, 05:27 »

no. because the chd switch is for checking the existence, name, checksums, case etc of the chd files themselves. the set check does the same for sets (name,exists, case).
Set checks the container, roms, samples, chds check the files inside the containers.

If you have a set which only consists of chds and you don't have the chd, the set check will
tell you you dont have the set xyz while the chd check will
tell you you dont have the chd blabla.chd.

turning of one check will only thurn of one message.

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

f205v · « **Reply #18 on:** 22 January 2016, 10:31 »

Quote from: Roman on 21 January 2016, 19:57

The select sets settings in set info will be stored and reassigned even after an update....

I didn't know about it! This is very convenient.

Does it store the selected sets (as a list of names), or does it store the setting itself and rebuilds the correct list at each update?

Roman · « **Reply #19 on:** 22 January 2016, 10:50 »

The "Select Sets" (if filled) value is applied automatically....so no, it does not store the enabled/disabled setnames if you use "select sets".
When an update is loaded it re-applies the variables/whatever is listed there....so for you, if new chd-only sets were added, you disable them without having to do anything manual....

News:

Author Topic: fully merged set - problem with clone CHDs (Read 30823 times)