1
clrmame Discussion / Re: clrmamepro generates duplicated files
« on: 17 September 2018, 19:54 »
Ok. I will try to explain myself a bit better.
I have a MAME 0.106 dat file that I use to prepare games for advmame/raspberrypi.
I did a rebuild using as Add Paths some folders that I have with roms. I chosed split roms.
The problem is that clrmamepro did not create a jdreddb.zip file because the 3 roms that should be inside that zip file were already in jdredd.zip file.
If I run the scanner over the just rebuilded collection, clrmamepro says that jdreddb is a missing romset. To get a "no missing rom" result from clrmamepro scanner i can either:
- create a empty folder named jdreddb in rom path or....
- ... make a copy of jdredd.zip named jdreddb.zip (In this case the scanner shows a warning telling that the 3 roms inside jdreddb should be move to parent)
It's not a big problem for me. I just described it trying to find some differences between this case and natodef one. With natodef this problem does not happen.
Thank you and regards.
I have a MAME 0.106 dat file that I use to prepare games for advmame/raspberrypi.
I did a rebuild using as Add Paths some folders that I have with roms. I chosed split roms.
The problem is that clrmamepro did not create a jdreddb.zip file because the 3 roms that should be inside that zip file were already in jdredd.zip file.
If I run the scanner over the just rebuilded collection, clrmamepro says that jdreddb is a missing romset. To get a "no missing rom" result from clrmamepro scanner i can either:
- create a empty folder named jdreddb in rom path or....
- ... make a copy of jdredd.zip named jdreddb.zip (In this case the scanner shows a warning telling that the 3 roms inside jdreddb should be move to parent)
It's not a big problem for me. I just described it trying to find some differences between this case and natodef one. With natodef this problem does not happen.
Thank you and regards.