There is a bug in the drag and drop rebuilding after a scan. I'm using the 64 bit version with Vista. After the scan, some dropped in files won't rebuild, the CRC's match but it does nothing and says they're still missing. The only way to fix it is to manually put the file into the roms dir and then when it scans, the files are no longer missing. Example files that don't work: c1 and c8 from matrimbl. Doesn't happen on all PC's afaik.

Edit: I just remembered I forgot to check if the zip in my roms dir was write-protected or not and now it's gone. So if that could stop it from working correctly then maybe that's it(?)

I never had this problem with ClrMame until the last couple of releases.

Drag'n drop works flawlessly.

There are circumstance where a drag'n drop skips the file:

- under Vista, you can't use drag'n drop if the folder from where you drop is owned by a different user than cmpro is running at. This UAC thing is normal under VISTA. You shouldn't have any problems if you're admin and doesn't run clrmamepro from any UAC protected folder.

- next thing is of course: The dropped archive is bad or in use by a different application, or the archive where the file will be added is in use/bad. Bad can also be bad structures, not bad data. Unless you don't scan zips with full structure test you won't be informed.

- Your destination doesn't point to your rompath.
- The set isn't enabled.
- There are several rebuilder (advanced) options which influence the way how files are rebuilt (if at all)

- generally, crc32+size has to match the database entries for getting rebuilt (+md5/sha1 optionally)
- of course a slight chance is that you got flawy memory/hd/chipset so a hashcalculation fails randomly.

If you can repeat the behaviour in any way, send me a minimum set of files + cmpro.ini + the belonging .cmp file.

Write protection doesn't play a role since cmpro de-write protects the file. Nothing changed rebuilder-wise for several builds now.
There are some anti-virus tools (AVG, Antivir) which usually interfear a lot...so if you're using them, disable them for a test.

Personally I think it's a bad (structurewise) source files. Pretty common for zipfiles in the internet.



Roman Scherzer