Hi, I have a problem with the scanner. My set is compressed with 7-zip. When the scanner finds a wrong named rom it renames the .7z correctly, but instead of renaming the rom inside it deletes it, so the compressed file becomes empty with no rom in it! I've tried to changed the path of the 7z.exe executable, or copy it in the clrmame dir. I've also changed the parameters in the command line in the compressor options. A complete failure, nothing change.
With .zip files everything is ok. With .rar i don't know because I don't use WinRAR.
With version 3.116a I never had a problem even with a modified packer.ini, but I can't find the old version anywhere.

hmm...ok, I will check that later at home today. Sounds like it uses the delete option for adding 8) which would be critical of course. Or the add operation failed and the old wrongly named file was removed.

Again...don't use it for the next 8 hours so I got a chance to review this.


Roman Scherzer

Ok, thanks Roman.

> Ok, thanks Roman.
>

Maybe in the meantime you can send me your cmpro.ini, the used datfile + belonging .cmp file and the 7z in question so I can test it using your environment


Roman Scherzer

Sorry, I've deleted and reinstalled clrmame several times because I feared that the problem was caused by some options, but the problem is present also with default settings after a clean install (or decompression, I use clrmame zipped version). The dat is the latest nds no-intro set (2008-07-29 15:44:02), not numbered, encrypted, no unlicensed, no bios.
http://datomatic.no-intro.org/?page=download
For the rom, i think it doesn't matter. I renamed on purpose old roms with wrong names and the error appears every time, with other dats and romsets as well (n64 for example).

ok....when I'm back home I will have a look


Roman Scherzer

> ok....when I'm back home I will have a look
>
>
> Roman Scherzer
>



Roman Scherzer

Thank you very much! It work perfectly again. Keep up the good work!

> Thank you very much! It work perfectly again. Keep up the good work!
>

no prob...it was caused by spaces in filenames....


Roman Scherzer