Using 3.111, and when I have "sets" selected it hangs within seconds. The scan dialog where a filename usually is goes blank, so i'm unable to see what its hanging on.

Am i doing something wrong?

If you toggle the sets (or other) checkbox(es), the scan results tree view gets updated (you can hide/show specific issues by toggling the checkboxes). If a lot items are shown there, it takes a while (depending on your system specs) to redraw the tree. This is a pretty normal Windows behaviour.


Roman Scherzer

I know it can take awhile, but I mean it locks up completely. It sits for 10+ minutes. I can hit cancel, and it works, but the status list doesnt get updated, and it's hung.

Works fine here. Even a full error list for all mame sets takes maybe 5 seconds to get redisplayed. What are your system specs?
Try to minimize the issue (e.g. an empty rompath), zip up your cmpro folder (or at least: cmpro.ini, .cmp and .dat file for the used profile) and send it to me.


Roman Scherzer

I think I might have left out info, the scan window says "Checking unknown sets..."

I also added screen shots of with and without the sets option selected, and you can see the the scan works without, and fails with.

http://rapidshare.com/files/93494845/clrmameprob.zip.html

wait a second...what exactly did you do?

You started a scan and it hangs while "Checking unknown sets"?
That's something completely different to "I clicked on Sets" and it hangs.

Please tell me exactly what you're doing.


Roman Scherzer

When "Sets" is selected, the scan will start. It goes through maybe 20 files, and hangs. "Looking for unknown sets" is when the scan is working, then the title of the window changes to "Checking unknown sets", and freezes there without a rom title in the dialog.

If I have the "sets" checkbox unselected, it goes through all my roms fine.

FIXED MY PROBLEM!

I went through each rom, one by one, trying to find out what was wrong.

Turns out I had a old set of roms in a temp folder, inside my roms folder, and CLRMamePro thought it was a CHD, and was scanning inside of the folder. That was making it hang.

Thanks for the trouble!

ah ;) ok...so it analyzed a lot of files I guess....and it calculated the crc of each...ok..this can take some time ;)

*edit* ok, I changed the prompt output slightly, so it will definetly show the worked on file before it actually goes into long crc calculation...


Roman Scherzer

Thanks a bunch, and as always, it was an end user created problem :)