> I will do some further investigations next week.
>
> Roman Scherzer
> ClrMamePro
>
Aha! I think I have found the problem (where have I heard THAT before?!?!)

I just started getting the message again, and I thought I would look at the settings files in each step.

When I load the 'official mame32 icons' datfile (after loading the 'test drivers' file & going back to the Profiler), the following line is written to the .cmp file (as soon as the datfile is loaded) :

Misc_BIOSSets = decocass|*|1|pgm|*|1|playch10|*|1|stvbios|*|1|konamigx|*|1|tps|*|1|taitofx1|*|1|cpzn1|*|1|cpzn2|*|1

If I go back to the Profiler & load the Modeler datfile, then go back & load the icon datfile again, the line in the .cmp file read as :

Misc_BIOSSets =

If I then load the Nebula v2.23c datfile, then load the icon datfile, the line is changed to :

Misc_BIOSSets = neogeo|*|1|pgmbios|*|1

Load the Modeler file, then the icon file again, and the line is clear again.

(the .cmp file in question is 'j4_rc_icon.cmp' in the 'settings' folder)

All of these changes are made WITHOUT ever touching any settings. All I was doing while testing this was to open ClrMamePro, load a datfile, go back to the Profiler, load another one, etc. & checking the .cmp file at each step (I use UltraEdit, so it would tell me if the file had changed & if I wanted to reload it)

Interestingly, this does not occur when I use the internally created Mame datfile, only seems to be the additional files that contain BIOS's.

Here's hoping that this info leads you in the right direction!