Hello, I think I am messing up with clrmame program in updating my MAME ROM collection as a newbie. I read http://www.mameworld.net/easyemu/clrmameguide.htm and still can't seem to get it right. OK, here's my situation...

I downloaded the whole MAME v0.113 ROMs collection from via BitTorrent with http://www.pleasuredome.org.uk's torrent. I went through the whole collection and only kept the games I wanted (about 2.2 GB). They are located in i:\MAMEroms\.

Today, I see v0.114 was released, so I downloaded MAME32 v0.114, MAME ROMs update (v0.113 to v0.114 from http://www.pleasuredome.org.uk), and Clrmame Pro v3.99c. I extracted all and installed them. The 100 MB ROMs updates are in E:\dl\MAME 0.113 to 0.114 update\ folder/directory.

I ran clrmame and let it make a dat file from mame32.exe. I clicked on my profile and Rebuilder. I set source as E:\dl\MAME 0.113 to 0.114 update\ and destination I:\MAMEroms\. I had scan subfolders, split sets, compress files, recompress files checked/enabled, separate BIOS sets, remove empty sourcefolders, addtionally test SHA1/MD5 for matches, create logfile, beep when done, and backup replaced files. I assume these are correct. When I run the rebuild, I noticed games that I did not want get added to i:\MAMEroms\. I only want to fix problematic/outdated MAME ROM files for v0.114 (latest version).

http://pastebin.ca/425710 has my logging enabled and my MAME ROM collection before I used rebuild (made a backup of it manually).

Am I doing something wrong or missed something? Thank you in advance. :)

already answered on usenet:

The rebuilder is a file based (not set based) operator. It rebuilds anything it finds and which matches against the loaded data. If one source rom is used by 20 sets, this one file is added to 20 sets in the destination.

If you only work with some sets, go to scanner->scanresults->setinformation and limit the enabled sets to the ones you want.


Roman Scherzer

The normal steps when updating to a new mame version are (assuming you got already a profile based on a mame binary):

- load profile, profiler detects new exe and updates its data
- go to scanner, run a scan with all check/fix options to fix all fixable stuff. You should end with only missing (recently added sets to mame) sets and not-fixable problems
- Now you can decide how to add the new stuff. The rebuilder is the prefered method but keep in mind it's file based as described in the other post.

Generally if you only have a few sets, you should either

a) go to scanner->scan results->set information (button in left bottom corner of tree window) and limit the sets.
Only enabled sets will be scanned / rebuilt / merged etc.

or b)
keep all sets enabled and if you don't like millions of missing sets reported, turn off scanner->popupmenu->view->show all missing sets.


Roman Scherzer

> already answered on usenet:

Weird, I didn't get an e-mail notification about the replies. This is what I posted in the newsgroup reply.


> The rebuilder is a file based (not set based) operator. It rebuilds anything it
> finds and which matches against the loaded data. If one source rom is used by 20
> sets, this one file is added to 20 sets in the destination.
>
> If you only work with some sets, go to scanner->scanresults->setinformation and
> limit the enabled sets to the ones you want.

OK, ahh! I missed that part. It wasn't showing enough (not running high resolution).

I went to Scanner, checked/selected: Sets, ROMs, prefer Split Sets, Hide Missing 'NoDump' Handling, Check and Fix All (Missing, Case, Unneeded, Name, Size, Date, and Checksums [everything except Fix File and MD5], both Options, Advanced (Unneeded check looks for dupe sets, Move not renamed sets to backup, Use optimized ROMPath scanning, Deeper check for fixable missing files, and Additionally test SHA1/DM5 for matches), logging (autosave), and all items in Systems.

Results: http://pastebin.ca/426448

Even if you limit the sets, you still have to look at the scan results tree after the scan and it tells you exactly what is wrong with your sets. You're done when no output is shown.


Roman Scherzer

Ah, thanks. I think I understand how this works now. Shoot, I got a bunch of files I didn't copy over from the whole v0.113 collection. :(


> Even if you limit the sets, you still have to look at the scan results tree
> after the scan and it tells you exactly what is wrong with your sets. You're
> done when no output is shown.
>
>
> Roman Scherzer
>

OK, I narrowed down to three games left, but I can't figured out what's wrong. Am I missing more files? My sets are bad? I need to download more files?

Results: http://pastebin.ca/426931 ... :(

The tree output says exactly what you miss. Yes, if it says missing rom, you miss the file. Without it, the set won't run.


Roman Scherzer