EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: oddi on 10 February 2015, 19:54

Title: Maybe problem with new merge chd
Post by: oddi on 10 February 2015, 19:54
Hello Roman , have new  chd : mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01.chd
see pics where may have "problems"
when cmp load dat:

(http://store.picbg.net/pubpic/09/FA/23e78062472f09fa.jpg)

sets with duplicate chd:
(http://store.picbg.net/pubpic/B9/6D/0de037f81be4b96d.jpg)

see little fragment from dat:

(http://store.picbg.net/pubpic/75/80/2a5bde31881c7580.jpg)

here upload full MAME dat for your proffesional look.
https://www.sendspace.com/file/c9rl7l (https://www.sendspace.com/file/c9rl7l)
---------
and question is : that is normal because cmp wanna safe mame structure or again mamedev bug ? Tnx :)
Title: Re: Maybe problem with new merge chd
Post by: Roman on 11 February 2015, 08:06
Well...the "wrong mergetag" warning comes up if a rom or chd with a merge tag A and a checksum X points to a rom/chd with name A but checksum B...

so..maybe MAMEdevs should double check this...since it seems to be a wrong entry within MAME....

..but yes...I will also double check it tonight (it's 9 am now...)
Title: Re: Maybe problem with new merge chd
Post by: Roman on 11 February 2015, 08:43
hmm...a quick look at the data shows nothing really bad....
I will look into this more deeply tonight...could be something on the cmpro side...thanks for reporting
Title: Re: Maybe problem with new merge chd
Post by: Roman on 11 February 2015, 18:23
ah ok....disks within a bios set (and the merge check only looked in the parent for disks)...something new ;-)

I will fix it as quick as possible....

Update:
As quick as possible means...NOT TODAY/TONIGHT ;-)
It takes a bit more effort needed as I thought...but most is done already...generally it's the first time where bios sets contain chd(s)...sounds easy...but yes..I actually did forget this possibility....so I need to add some things here and there....
If everything works out well it should be in a testable state tomorrow night....if not you may have to wait till next week since I don't have time over the weekend....

...since the next MAME release comes in two weeks I should have a little bit of time ;-)
Title: Re: Maybe problem with new merge chd
Post by: Roman on 12 February 2015, 22:18
ok here we go...testing "chd support for biossets"...

http://mamedev.emulab.it/clrmamepro/binaries/cmp20150212.rar (http://mamedev.emulab.it/clrmamepro/binaries/cmp20150212.rar)
Title: Re: Maybe problem with new merge chd
Post by: oddi on 13 February 2015, 03:30
Hi Roman, now testing , results is : cmp removed all duplicate chds and create new folder "lindbios" - inside with this chd.
Maybe correct because all lindberg games have
<game name="blablabla" sourcefile="lindbergh.c" romof="lindbios">.
U say "something new" - future chds with bioses :)
Title: Re: Maybe problem with new merge chd
Post by: Roman on 13 February 2015, 07:56
"maybe correct" ..hahaha...of course it's correct... you don't want to copy a large chd which is part of the bios in each and every set which uses the bios.....
Title: Re: Maybe problem with new merge chd
Post by: oddi on 13 February 2015, 09:09
Uncle oddi say: correct !
Tnx Roman :)