Hi Roman. This has been bugging me for a while: I can't figure out how to get cmp to delete wrong named files like the ones below automatically when the correct file is already in there.

MAME Titles - v0.101 Title Pack [folder: titles - size: 102mb]
wrong name: I:\MAME\titles\titles\poker4.png [wrong: poker4.png] [right: lvpoker.png] [not fixed]
wrong name: I:\MAME\titles\titles\jollypkr.png [wrong: jollypkr.png] [right: jollycrd.png] [not fixed]
wrong name: I:\MAME\titles\titles\bonuscrd.png [wrong: bonuscrd.png] [right: royalcrd.png] [not fixed]

I hope that made sense. As it is I have to delete the files manually.

Many thanks as always for any help,

Sean

What I do is use the rebuilder fuction to rebuild the titles, snap, ... sets. What I do is rename the folder to old, then create a new folder (i.e. titles). Then use the rebuilder to move the files from old to the new folder. This has the effect of renaming all the files, and leaving the obsolete file in the old folder. Then all you have to do is delete the old folder.

> wrong name: I:\MAME\titles\titles\poker4.png [wrong: poker4.png] [right:
> lvpoker.png] [not fixed]


1st of all...there is no need keeping artfiles (flyers, snaps, etc.) unzipped

2nd of all...usually rebuilding the art files with recompress disabled is faster than using the scanner

3rd of all...well..you guessed right...the "not fixed" appears because a file with the 'newname' already exists. To prevent overwriting, clrmamepro won't fix it. Since in zipfiles I do replace the file I will think about changing the behaviour of unzipped files as well.



Roman Scherzer

> 1st of all...there is no need keeping artfiles (flyers, snaps, etc.) unzipped

OK, I understand that, but it's a preference thing with me as I've had problems in the past with updating. I'm a bit of a dinosaur, perhaps!!

> 2nd of all...usually rebuilding the art files with recompress disabled is faster
> than using the scanner
Good point- I should have thought of this myself after all this time!

> 3rd of all...well..you guessed right...the "not fixed" appears because a file
> with the 'newname' already exists. To prevent overwriting, clrmamepro won't fix
> it. Since in zipfiles I do replace the file I will think about changing the
> behaviour of unzipped files as well.
OK, thanks. If you do- great, if not- no worries! I shall finally try the 'no recompress' option after all this time.

Typically- thank you so much for your quick and helpful response Roman.

Regards,

Sean

> OK, I understand that, but it's a preference thing with me as I've had problems
> in the past with updating. I'm a bit of a dinosaur, perhaps!!


You should switch to zips 8) There are no problems updating them and it's usually much faster to handle them.

> OK, thanks. If you do- great, if not- no worries! I shall finally try the 'no
> recompress' option after all this time.


'no recompress' is only useful if the rebuilder sourcefiles and destinationfiles are/should get zipped.


Roman Scherzer