Okay, I'm getting back to this part of my question. However, I'm still having issues.
the "version" prompt....guess this appears if the auto-update check does not find the needed version information on the clrmame homepage....which is a bit weird unless you don't have an internet connection ready. I can check this when I'm back. If you don't want to see it anymore, change the update check (cmpro's about window) to don't check daily/weekly/etc...
I just go rid of it by not checking it at all. It's not a biggie, but I would be interested to hear what you find out when you get back.
Again, the "download folder" is for cmpro's own download functionality which you can use from the scanner popupmenu. It lets you download missing listed items from a given URL...and these downloaded files will be stored in the download folder. Nothing more, nothing less.
So, it sounds like it's pretty useless for my purposes, then. I download roms via usenet (the horror!), not from a specific site.
The common way to update sets is if the new data is loaded in in the profiler, go to the scanner, enable all check/fix options and do a full scan. this should fix all fixable stuff and you most likely end with some missing sets (the ones which are new or were replaced in the new version). Now use the rebuilder to add the missing stuff. Do a scan again...and repeat the described way until nothing is listed anymore.
Well, no matter how many times I use the rebuilder, there are still a LOT of flagged files which are reported by the scanner. However, see my previous message about some scanner weirdness. Could the two be related?
Assuming you've downloaded new sets to a folder c:\temp, let c:\temp be your rebuilder source folder and the rebuilder destintion should point to your cleaned up collection. The rebuilder adds all valid files. Even easier if once configures, you can simply drag'n drop files into the scan results window...this will internally use the rebuilder to add the files.
Okay, this added a critical part to my configuration. I had no idea that I was suppose to define my rom download path here.
Now, regarding drag 'n' dropping - it doesn't work (for me). I can highlight my download directory or all the contents in that directory and I can see where the pointer changes to that little plus sign underneath the pointer, but nothing seems to happen. The same with the scan results window. I don't know if this is particularly critical, but it is worrisome.
I did run the rebuilder and it picked up on my rom download directory and "did its thing". However, as I wrote, I'm still getting a LOT of flagged items in the scanner. I really don't understand what I'm doing wrong and am beginning to feel like the program is starting to defeat me.
If you want to split sets by bios sets as you wrote, you need to use "system default paths". You can set them up in "Systems". Also set them up as rompaths. Since cmpro's rebuilder and scanner's fixmissing option needs to know if it should use system default paths, you need to enable the belonging options in the rebuilder or scanner-advanced.
I'm pretty sure I've done this. The only options NOT checked in the Advanced Scanner Options are "Allow not separated BIOS ROMs", "Allow CHDs in ROMPath root", and "Show 'baddump' ROM & inverted CRCs". All the other options are checked.
Yes, you don't need external datfiles for MAME, MESS, RAINE, PINMAME. clrmamepro gets the data directly from the executable...and if you replace the exe file, it regets the data.
That takes a load off. I keep seeing these websites with all these DAT files available for download and my heart sinks. That clrmamepro handles DAT processing via the executable itself is a Godsend.
Just in case you're using Windows7 or Vista, please store cmpro in a NON UAC protected folder (e.g. NOT in c:\programs). I use for example d:\cmpro.
Well, I am using Win7 x64 and clrmamepro is installed in C:\Program Files\clrmamepro, but I have Properties -> Compatibility set to run the program as an admin. And it does ask me that UAC question every time I invoke the program. Do you think this could still cause problems?