PAR quirk, 6.52B3 Build 3196

[orygun]

6.52B3 Build 3196 on a Win 7 whitebox.

The files in question are given one filename (000001).r00, but when processed by NB or quickpar, reveals another name (abcdefg).r38.

NB would not recognize files for par processing if the file was incomplete on the server, but all available parts were assembled in the folder as a file, - file.R38 100,000,000 Missing (32/33 blocks available).

However, if the damaged file is renamed manually (from 000001.r00 to abcdefg.r38 ), quickpar fixes it and continues but NB doesn't- leaving the comment "[Par Process] UnRAR Failed- No PARS 0% Completed" in the log.

Note: As I was typing this, I believe you don't use qp to fix and reassemble. I still have it, but noted that qp also fails to recognize a damaged file part unless manually renamed, however, it will automatically rename complete files parts in the directory.

File is not PW'd.

[Quade]

PM me an example file. I'll check it out. Incomplete missing the first part of the file with the wrong name, simply won't work with quickpar or with Newsbin.

There are three ways to ID the file.

1 - The first 16K of the file.

2 - The hash of the entire file

3 - The filename, if it's correct.

If none of this is available, which seems to be what you're describing, you're going to have to fix it by hand. As long as the first chunk is available, Newsbin should be able to ID the file. Basically the file is completely missing to Newsbin so, that's probably why it doesn't trigger a repair.