> 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.