EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: llagos on 17 October 2019, 22:21
-
Hola Roman,
Just doing a new full scan... all options marked for what, check, and fix. All in.
I've noticed that cmp sometimes fix an "unneeded" rom, to just add it immediately after by fixing "missing"...
Is this correct?
Attached an example.
Salu2,
-
ehehe...never seen this before....guess I have to rebuild this scenario.
-
hmm...very interesting....when you single-load the msx1_cass.xml file in the profile, the set gets imported correctly (i.e. the clone set 4x4offrda only holds one unique rom, while the 2nd rom is part of the parent).
When you import the data via the -listsoftware mame run after receving data, the set is imported incorrectly (i.e. the 2nd rom is not part of the parent for whatever reason)
Have to check what is happening there.....the bad set definition causes the weird problem.
ah....the -listsoftware output kills the offset="0" attribute
second "ah": since MAME .210 you need to use the cmpro nightly build to correctly support software lists where the offset attribute is removed
-
Cierto Roman,
I use the nightly build... 4.035 now..
So, I'll wait for your feedback... hoping you'll have some free time for that :)
Salu2,
-
feedback?
with the nightly build you shouldn't run into this (you need to clean the cache though)
-
did it... I opened cmp, cleared cached data, loaded dat (it ran -list, swlist, etc., again), scanner full... still happening :(
-
Open scanner -> set information and search in the set tree for the 4x4 set (parent and clone). click the clone and look at the list on the right. It should look like the attached scrrenshot, i.e. only one rom should be listed there. If you see 2 there then you are not using the nightly build ;-)
-
where is this "set information" option? I opened scanner, but can't find it...
or should I run scanner, and then look at the messages window? (if so, I'll need to do it later)
Gracias!
-
Scanner -> Scan Results (Tree Window) -> bottom left button