Hi,

I am currently trying to DL the entire Mame v.108 Romset from Pleasuredome.com.uk as a torrent.

Their "How-to" suggests using Clrmamepro to audit and update/fix my old roms from Mame v.72 to prepare them properly for the torrent file DL.

My question is regarding their warning in their "HOW TO" that says DO NOT include NO DUMP roms in the archive. I want to know how to detect and segregate my NO DUMP roms from the rest, without having to go in and remove them one by one. OR, if I do have to remove them manually, how do I find which roms are "NO DUMP"

As you can tell I'm not a emu-expert, lol, so any suggestions would be welcome. Will my v.72 roms even work with v.108 or do I have to re-DL newer ones? Thanks.

> Hi,
>
> I am currently trying to DL the entire Mame v.108 Romset from
> Pleasuredome.com.uk as a torrent.
>
> Their "How-to" suggests using Clrmamepro to audit and update/fix my old roms
> from Mame v.72 to prepare them properly for the torrent file DL.
>
> My question is regarding their warning in their "HOW TO" that says DO NOT
> include NO DUMP roms in the archive. I want to know how to detect and segregate
> my NO DUMP roms from the rest, without having to go in and remove them one by
> one. OR, if I do have to remove them manually, how do I find which roms are "NO
> DUMP"
>
> As you can tell I'm not a emu-expert, lol, so any suggestions would be welcome.
> Will my v.72 roms even work with v.108 or do I have to re-DL newer ones? Thanks.
>


Use the rebuilder to create the cleaned rom set. Make sure that in the rebuilder options you have "Rebuild 'no dump' Roms (0 CRCs)" unchecked (it is standard anyway, just make sure you did not change it), otherwise you will be creating them. The rebuilder will then take care of everything. No need for manual labour at all. Don't forget to torrentzip your collection afterwards as the zips will be touched by the rebuilding process and will not be recognised as valid sets. You can find a more detailled description in the guides at PD. Good luck!

> My question is regarding their warning in their "HOW TO" that says DO NOT
> include NO DUMP roms in the archive.

Well...I don't know their 'how to' and I don't appreciate spreading copyrighted roms via torrents either..but that's a different story, so...to answer your no dump question:

- enable scanner -> no dump handling -> hide missing
- disable scanner -> no dump handling -> create missing
- enable scanner advanced -> mark no dumps as unneeded (the next scan with (fix) uneeded removes them)


Roman Scherzer

No need for a full rebuild. The Scanner easily filters them.


Roman Scherzer

> No need for a full rebuild. The Scanner easily filters them.
>
>
> Roman Scherzer
>
Oops, really shouldn't try to answer questions for the master ;-) Your advice is the far more elegant way of doing it, of course.

I normally use only the scanner myself for cleaning romsets or for updating.

For sharing I would personally prefer creating a clean copy from the scratch using the rebuilder rather than directly sharing my rom directory (keeping a backup in case something goes wrong, issues with access to files currently kept open by clients, excessive hard drive usage, you name it). Of course you can just make a copy of your directory and scan it the way you described. However, if you have to torrentzip the romset afterwards, time spent on CMPing a romset is not really an issue.

Since you have made your tool so versatile, I found that quite often you have choices to do the same thing different ways, and then for me it all comes down to personal preferences.

Just out of curiosity and correct me if I am wrong, isn't the scanner generally using the same internal functions as the rebuilder? What difference does it make then using one or the other? I suppose sets, which already correct, will be ignored rather than rebuilt and it will save you a lot of time if you intend to upgrade from fairly complete romsets.

> Just out of curiosity and correct me if I am wrong, isn't the scanner generally
> using the same internal functions as the rebuilder? What difference does it make
> then using one or the other? I suppose sets, which already correct, will be
> ignored rather than rebuilt and it will save you a lot of time if you intend to
> upgrade from fairly complete romsets.
>


Generally Scanner and Rebuilder have absolutely nothing in common. The scanner is setbased, the rebuilder filebased. The rebuilder only copies files from a given source to a given destination by a hash compare. It rebuilds anything it finds and which is valid (crc32/size match). It doesn't know anything about completeness of sets etc.

The scanner goes through all sets and does countless more tests (unneeded, checksum, size, name, etc...) and fixes them in place.

If you drag&drop files into the scanner, the current rebuilder options are used and in this case the rebuilder can be used as an 'Adder', adding missing files to your collection.

but as mentioned, generally Scanner and Rebuilder are two totally different things.


Roman Scherzer

> Generally Scanner and Rebuilder have absolutely nothing in common. The scanner
> is setbased, the rebuilder filebased. The rebuilder only copies files from a
> given source to a given destination by a hash compare. It rebuilds anything it
> finds and which is valid (crc32/size match). It doesn't know anything about
> completeness of sets etc.
>
> The scanner goes through all sets and does countless more tests (unneeded,
> checksum, size, name, etc...) and fixes them in place.
>
>
> [...] but as mentioned, generally Scanner and Rebuilder are two totally different
> things.
>
>
> Roman Scherzer
>

Now that I read your explanation, I realise that you must have explained the difference between the scanner and the rebuilder at least umpteen times already. And yes, it is both in the documentation and in the FAQ. Maybe you should point out to people like me with such a short memory to read the documentation again and again until it finally sticks. I believe that I was misled somehow by the part in the documentation for the scanner that says it "will use the current Rebuilder options and rebuilds the dropped files" when using drag'n'drop in the scanner window. I probably started to generalise from this statement to the whole way the scanner operates, however your documentation is very clear about how both modules work. Sorry for asking the same stupid question as probably many others before.

I do a complete documentation rewrite at the moment anyway. 8)


Roman Scherzer