Print

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

[XangXing]

If there are two copies of the same CHD clrmamepro signals one as "wrong name" but he doesn't succeed in resolving the problem. 

example: 

take the file "a51site4.chd" of the set of MAME, we do a copy of it in the same folder with a different name, clrmamepro will report this file as "Wrong name", but he won't succeed in resolving the problem.

[Roman]

Generally a fix-name operation fails if the 'new' name already exist.
Normally you have a scanner-advanced option to "Move not-renamed sets to backup" to get this working. However this won't work for chds. In this case you have to manually remove one instance.

[XangXing]

Ok, thanks for your explanation Roman.

[Roman]

by the way, the use case for this is pretty uncommon. It'd mean that you got identical 2 chdfiles in the same folder where one is not correctly named. So it's safe to remove one. The only thing I could think of is the current chdman -update mania where you updated the existing file to the new format but you put it in the same folder...assuming the new file got a different name, clrmamepro should then list one file as wrongly named and the other one as "upgrade chd..". Again, you'd need to remove the old file manually.

[XangXing]

Yes, this is the problem, but I have resolved with a batch file.