> > So the question is, Is this the expected behavior of the listsoftware command? > > yes, because in some cases we add software list per dumper requests even before the > corresponding driver is written, or before the system BIOS is dumped, or before the > code necessary to load the dumped images is created > thus you end up with software lists which contain valid dumps and document them, > without being hooked up to any MAME/MESS driver (and thus without being accessible to > the -listsoftware command) > > eventually, all lists will be hooked up to the emulator, but for the time being the > existence of the xml allows to document all we currently know about those dumps, > which is better than not having anything at all > > also, you can always use the batch scan/rebuild options of cmpro to handle those xml > files separately (fwiw, personally I prefer to handle *all* software lists via such > option ;-) )
OK, thanks for responding.
Yes, I have used the batch mode.
I guess all that work in clrmamepro to handle the [SOFT] systems isn't fully utilized yet, due to the issues you point out.
|