As the subject heading says, when I try to scan my Control Panel Packs (from the .dat file downloaded in WWW mode), ClrMame 3.87a hangs.

If I open SysInternals Filemon, I see that when CMP scans the last file in the (cpanel) directory, it starts back at the beginning again, resulting in a never ending scan loop.

Steve

> As the subject heading says, when I try to scan my Control Panel Packs (from the
> .dat file downloaded in WWW mode), ClrMame 3.87a hangs.
>
> If I open SysInternals Filemon, I see that when CMP scans the last file in the
> (cpanel) directory, it starts back at the beginning again, resulting in a never
> ending scan loop.
>
> Steve
>



It's not a never ending loop.
Well...most likely you got fixmissing enabled in combination with scanner's advanced option "fix missing scans all sets". This is of course overkill. It will scan each and any file in addpaths and backup and maybe even the cpanels.zip itself for any missing file.

Working and especially fix operations on huge zipfiles (huge in terms of archived files) take long. Very long under some circumstance. Enabled virusscanners will easily double the time, too.

For the "art" sets it's always much more clever to do a full rebuild instead of using the scanner to fix names etc. It's much faster (esp. when you don't use 'recompress').


Roman Scherzer

> > As the subject heading says, when I try to scan my Control Panel Packs (from
> the
> > .dat file downloaded in WWW mode), ClrMame 3.87a hangs.
> >
> > If I open SysInternals Filemon, I see that when CMP scans the last file in the
> > (cpanel) directory, it starts back at the beginning again, resulting in a
> never
> > ending scan loop.
> >
> > Steve
> >
>
>
>
> It's not a never ending loop.
> Well...most likely you got fixmissing enabled in combination with scanner's
> advanced option "fix missing scans all sets". This is of course overkill. It
> will scan each and any file in addpaths and backup and maybe even the
> cpanels.zip itself for any missing file.
>
> Working and especially fix operations on huge zipfiles (huge in terms of
> archived files) take long. Very long under some circumstance. Enabled
> virusscanners will easily double the time, too.
>
> For the "art" sets it's always much more clever to do a full rebuild instead of
> using the scanner to fix names etc. It's much faster (esp. when you don't use
> 'recompress').
>
>
> Roman Scherzer
>

The images in Cpanel were unzipped and CMP was re-reading the same directory of file over and over again. Fix missing was enabled, but I thought that would just search the file list and compare CRC's for a match (and look in the backups folder). The title bar of the program said it was "not responding" and my CPU load went to 100% (all to the CMP process according to task manager).

I eventually managed to force it through by enabling only one option at a time and deleting some files by hand - one strange quirk I've noticed is that if a file, say "abc.png" is renamed in a newer set to "def.png" ... and if newer file "def.png" is already present along with the older set name "abc.png" still intact, then CMP keeps warning me that it could not rename "abc.png" to "def.png", instead of just deleting the old uneeded file.

Other than that, thanks for a very useful tool to help keep MAME up to date. It took some getting used to, but the newer versions are much more user friendly (especially with the WWW mode for downloading .dat files).

Steve

Well...if you work with unzipped files and fixmissing is enabled, it has to calculate all crc32 of all files over and over again...so this can take long 8)
Fixmissing normally looks in addpaths and the backupfolder, but there's also another fixmissing advanced option which checks if the file is in another rompath, too. So I guess it looked in the same set.

For the "can't rename" message...well...clrmamepro doesn't rename the file if a file with the new name already exists. For sets (folder and zipfiles), there's a scanner advanced option to automatically move the file to the backupfolder. For unzipped files in sets, it won't rename it as long as there is a possibility to overwrite a file with the same name.



Roman Scherzer

btw...after looking at your reported issue again, I now know what's happening.

No endless loop 8)

It is indeed one of the fixmissing advanced options. But I think it's the 'deeper check for fixable missing files'. That check also looks in each rompath (in your case the unzipped set) for each missing file. And even worse, it calculates hashvalues for each file....and that happens over and over again.
I guess I can speed it up by remembering the already calculated hashes.


Roman Scherzer