I am scanning and rebuilding back and forth between rebuilding and scanning and this is my latest log:

Missing Sets: 5 of 7186
Wrong SetName Case: 0 [0 fixed]
Wrong Named Sets: 1 [0 fixed]

Missing Roms: 723 of 100819
Missing Bytes: 708mb of 59gb
Missing BIOS Roms: 0 of 125
Wrong Named Roms: 0 [0 fixed]
Wrong RomName Case: 0 [0 fixed]
Wrong Sized Roms: 0 [0 fixed]
Wrong Date/Time Roms: 0 [0 fixed]
Wrong CRC32s: 0
Wrong MD5s:
Wrong SHA1s:


Getting there now!

I am going to start the art today.


> The rebuilder is an engine which is usually used to
> a) convert a mess/unknown collection into something useful
> b) add files to an existing collection
>
> The rebuilder simply takes any sourcefile, tries to match the hashvalues against
> the database, and in case of a match, it creates the file in the destination but
> with the correct name. It creates all found instances there. So if a file is
> shared by 10 sets, all 10 sets are created with that one rom. You see it's a
> file based not set based operation. It doesn't care about completeness of sets.
>
> So for the usual operations a), you can "convert" your e.g. MAME roms to another
> emulator where you loaded a datfile for. In case of b), you can let the
> rebuilder destination point to your clean collection and your source files are
> being added to that collection.
>
>
>
>
> Roman Scherzer
>