Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

ok....in case of exisiting separated bios files, the missing rom count will be adjusted....in the next nightly build

I found it, syspath is setted well but I found that rompath for that softwarelist was disabled and I really don't know why: I enabled it and scan works flawlessy now.
Thank you.

The count is not wrong...it's just how the stats counts work. The rom count does not care about bios/merge but works on the plain defintions. If you miss a set, every file in its definition is counted as missing (as well as each file is counted for the total). There is a slight exception if no dump chds or no dump roms are included. But such files do not exist at all, while the chd belonging to the set is 'real'.

loveber3cn is a set which consists of a chd (mda-c0071) and bios rom (mb_eeprom_exp.ic54s).
Since you don't have the chd, you don't have the set and so the bios rom is counted as missing (and the set is counted as missing, too).

You don't see a message about a missing chd, since the scan tree output hides it when you disabled chds.
You don't see a message about a missing bios rom, since the scan tree output will only list it inside the bios sets themselved.
You migh not see a missing set message if you're using merged sets since then the existance of the parent + biosrom is enough...

You see....Statistic total/missing counts are based on set definitions, not parent/clone/bios relationsships....forget about the numbers...they don't bring you anything....Look at the scan tree output...if it's empty, you're good...but only related to your chosen check options.


Update: However, I will have a 2nd look at it since if biossets are separated and are available it should be counted as available.....but anyway...don't care too much about these numbers...

hmm.....I can't repeat this problem here.

Please double check your setup paths. Ensure that your rompath for orionpro_flop sets really contains the sets (e.g. bascom.7z) and it's correctly assigned to the sysdefault path belonging to the software list orionpro_flop (and not e.g. orion_flop).

I checked with a MAME + single software list import of orionpro_flop but no other lists....do you include more (if not all)?

However, if it does not see a single one of orionpro_flop sets it seems to be more a setup path problem rather than a problem in cmpro....

I use the complex setup with sysdefpaths, lists are imported straight from MAME binary.
Thanks.

to get the bios dat of 139u1 .
use a dat of 139u1 or just mame.exe .

in ClrMamePro.
in Scan Rescults ,at the bottom ,click Set Information ,
in Set Selection , %B=1 ,Apply ,Exports current database.

mame 0.208 64bit.
ClrMamePro 4.035.
in scanner , choose Sets , choose Roms , not choose Samples ,not choose Chds.

the number of missing roms is not right. I got all the roms , but it still show that I miss one roms.
already find the problem game , loveber3cn . If creat an empty folder , named loveber3cn ,it will show 0 miss.

the related problem , in
https://www.emulab.it/forum/index.php?topic=4173.0

( Sorry for my bad English , if i made any mistake )

Ah sorry...I thought you were talking about a nightly MAME version ;-)

I will have a look...you're using standalone profiles for software lists of the all-in-one mode where you imported the information from the MAME binary, so you got MAME sets plus software lists plus the complex setup with sysdefpaths?

I rebuilded the set from scratch with clrmame rebuild (merged). It's very strange.
When I spoke about nightly build I'm referring to clrmame pro nightly, dated 02/02/2019, MAME build is the official .208 x64 version.

Apologies.

Just noticed this board was only regarding arcade games.