Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All Threads*Show in Threaded Mode


Subjectclrmame bug? new Reply to this message
Posted byczokie
Posted on01/08/06 11:55 PM



I have a question about the current version of cmpro. My source romset is the current online version at Retroroms for 0.103u1. I have had a number of reports that files are missing from the retroroms sets, yet these files are available in parent zip files.

As an example, lets look at dbldyn.zip. In the set at retroroms, dd.* are not included in the zip, since they are available in the parent "dynduke.zip"... yet cmpro says these files are missing. I have had a number cmpro users reporting this problem.

Then, there is a harder example: diggerc.zip is missing dig.bin. This file is available in a parent rom with the same CRC and SHA1 values, but a different filename in the parent rom.... and cmpro also lists these files as missing.

Personally, I am not a cmpro user, so I cannot respond to them in person. Could anyone comment please?

Thanks

Czokie




SubjectRe: clrmame bug? Reply to this message
Posted bydjspeedy
Posted on01/09/06 01:44 AM



Sounds to me like the "split sets" option is checked on the scan instead of "merged sets".

I could be wrong, but this is what it sounds like.


SubjectRe: clrmame bug? new Reply to this message
Posted byRoman
Posted on01/09/06 02:12 AM



> I have a question about the current version of cmpro. My source romset is the
> current online version at Retroroms for 0.103u1. I have had a number of reports
> that files are missing from the retroroms sets, yet these files are available in
> parent zip files.
>
> As an example, lets look at dbldyn.zip. In the set at retroroms, dd.* are not
> included in the zip, since they are available in the parent "dynduke.zip"... yet
> cmpro says these files are missing. I have had a number cmpro users reporting
> this problem.
>
> Then, there is a harder example: diggerc.zip is missing dig.bin. This file is
> available in a parent rom with the same CRC and SHA1 values, but a different
> filename in the parent rom.... and cmpro also lists these files as missing.
>
> Personally, I am not a cmpro user, so I cannot respond to them in person. Could
> anyone comment please?
>
> Thanks
>
> Czokie
>


If cmpro says something is wrong with your set, something is wrong with your set ;) Of course this is based on the currently used options. First, recheck your settings. This includes the rompaths and the prefered merge mode. Be sure to enable all check options and 'sets' and 'roms'. The scanner is able to fix nearly all problems (ok it doesn't magically create missing files in all cases ;)), so read the scanresults tree output carefully and you should know what's wrong with the sets.
Another way to build up a clean set is using the rebuilder.


Roman Scherzer



SubjectRe: clrmame bug? new Reply to this message
Posted bySalmonKing
Posted on01/09/06 11:30 PM



> I have a question about the current version of cmpro. My source romset is the
> current online version at Retroroms for 0.103u1. I have had a number of reports
> that files are missing from the retroroms sets, yet these files are available in
> parent zip files.
>
> As an example, lets look at dbldyn.zip. In the set at retroroms, dd.* are not
> included in the zip, since they are available in the parent "dynduke.zip"... yet
> cmpro says these files are missing. I have had a number cmpro users reporting
> this problem.
>
> Then, there is a harder example: diggerc.zip is missing dig.bin. This file is
> available in a parent rom with the same CRC and SHA1 values, but a different
> filename in the parent rom.... and cmpro also lists these files as missing.
>
> Personally, I am not a cmpro user, so I cannot respond to them in person. Could
> anyone comment please?
>
> Thanks
>
> Czokie
>

I would have thought ticking Fix Missing would sort that out. As Roman suggested, rebuilding files rather than copying them into the collection would pick them up in the first place.




SubjectRe: clrmame bug? new Reply to this message
Posted byRoman
Posted on01/10/06 03:05 AM



> I would have thought ticking Fix Missing would sort that out. As Roman
> suggested, rebuilding files rather than copying them into the collection would
> pick them up in the first place.


1st rule: Never ever add sets manually. Always use the rebuilder or fixmissing.


Roman Scherzer



SubjectRe: clrmame bug? new Reply to this message
Posted bySalmonKing
Posted on01/10/06 04:58 AM



> 1st rule: Never ever add sets manually. Always use the rebuilder or fixmissing.

2nd rule of CMP Club : Never EVER add sets manually. Always use the rebuilder or fixmissing.




SubjectRe: clrmame bug? new Reply to this message
Posted bySalmonKing
Posted on01/10/06 05:08 AM



> Personally, I am not a cmpro user

Get a proper OS....BWAHAHAHA! ;)




SubjectRe: clrmame bug? new Reply to this message
Posted byRoman
Posted on01/10/06 07:03 AM



> > 1st rule: Never ever add sets manually. Always use the rebuilder or
> fixmissing.
>
> 2nd rule of CMP Club : Never EVER add sets manually. Always use the rebuilder or
> fixmissing.
>


3rd rule: never say you found a bug. It's always your fault and cmpro is always correct 8)


Roman Scherzer



View All Threads*Show in Threaded Mode