Print

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

[manliodp]

Hi Roman,
thank you for your great work on clrmame.
I've just upgraded to 3.135 but everytime i make a new scan with the FBA v0.2.97.08 dat, it asks me to fix the neogeo bios.
If i let it fix it it shows no errors/missing set; if i make a scan (cached) no errors/missing set.
If i make a new scan it asks again to fix the bios and so on..if i don't fix it clrmame reports an error on the set.
I would like to add that the 3.134b version didn't have this issue.

Thank you

[Roman]

Can you send me the set and the used datfile?

[manliodp]

Hi Roman,
i sent a mail to the address in your profile with the files attached (i 7zipped them for space but i keep them zipped).

Thank you


Manlio

[Roman]

Thanks.

However I don't get any error.
The datfile holds the neogeo set twice...which is a bit dumb but cmpro imports it then as neogeo and neogeo_0.

I've zipped up your neogeo folder and the first scan only complains about missing files in neogeo_0. So fix-missing fixes them fine and that's all. New 'new scans' don't popup any message.

So....maybe you should

a) send me your original zipfile (maybe it's corrupt).
b) send me cmpro.ini plus the belonging .cmp file (settings folder) to that datfile
c) what does cmpro ask you in detail? What does it want to fix?

[manliodp]

Thank you for your prompt reply,
i've notified the double neogeo set issue to the FBA devs, removing the duplicate no error occurs.

Thank you again

[Roman]

hmm..interesting....

[Roman]

ah ok...you didn't let cmpro import the 2nd instance of neogeo with a changed name....will change this for the next version so that double entries are forced to get renamed during parsing the dat.