Hi Roman,
situation is as following:
1- datfile is straight from 0106u1 exe
2- rompath are: c:\mame\roms -> roms in zipformat splitted
c:\mame\chds -> chds, each one in it's own subdir
3- I make a scan with "set" and "roms" activated and I get an -susume.chd unneeded- error
4- I make a scan with "set" and "chd" activated and I get no errors.

Shouldn't it be the other way round?

TIA

ciao
f205v

> Hi Roman,
> situation is as following:
> 1- datfile is straight from 0106u1 exe
> 2- rompath are: c:\mame\roms -> roms in zipformat splitted
> c:\mame\chds -> chds, each one in it's own subdir
> 3- I make a scan with "set" and "roms" activated and I get an -susume.chd
> unneeded- error
> 4- I make a scan with "set" and "chd" activated and I get no errors.
>
> Shouldn't it be the other way round?
>
> TIA
>
> ciao
> f205v
>


not weird ;)

First of all...susume.chd (known from pre 106u1) is in fact unneeded in u1 (since it was replaced with a raw-cd read and the new chd is named differently too. So the unneeded message is absolutely correct. If you rename it to gv027j1.chd you'd get a wrong chd-md5/sha1 error by the way ;)

when you disable 'roms' you won't get the unneeded susume chd entry since it's the roms unneeded check which discovers it...but you still should get a missing diskimage: gv027j1.chd entry (as long as you miss it and 'missing' is enabled).


Roman Scherzer

> First of all...susume.chd (known from pre 106u1) is in fact unneeded in u1
> (since it was replaced with a raw-cd read and the new chd is named differently
> too. So the unneeded message is absolutely correct. If you rename it to
> gv027j1.chd you'd get a wrong chd-md5/sha1 error by the way ;)

Yes, I already knew it.

>
> when you disable 'roms' you won't get the unneeded susume chd entry since it's
> the roms unneeded check which discovers it...

How comes that unneeded CHDs are discovered by ROM checks? I would have thought it was the CHD check to discover unneeded CHDs....

> but you still should get a missing
> diskimage: gv027j1.chd entry (as long as you miss it and 'missing' is enabled).
>

Yes, I get a missing gv027j1.chd

ciao
f205v

> How comes that unneeded CHDs are discovered by ROM checks?

Because they are stored like roms, unpacked romsets use rompath\setname\file 1..file n storing method and so cmpro's rom-unneeded check finds the susume.chd (since cmpro supports zipped and unzipped sets). So for cmpro, it's basically an unneeded rom (of course additional checks see that it's not a valid chd anymore) because it's stored in a romfolder-subfolder for the unpacked susume set and doesn't match (checksum check) any belongin romfile.

Not all check options work with all 'you want to scan' options by the way...iirc diskimages only support missing, name, case and checksum chds...guess there is no unneeded test for diskimages (since they would likely pickup unzipped roms as unneeded) ;)


Roman Scherzer

> Because they are stored like roms

Thank you, now I understand it, it's logical.



ciao
f205v

> > Because they are stored like roms
>
> Thank you, now I understand it, it's logical.
>



well...of course I can add an additional check which lists the chd as an unneeded chd too....I will think about it...


Roman Scherzer