6.30 b4 file renaming issues

[nzwhat]

It appears build 1747 still has occasions where a file is being overwritten by another file of the same name, instead of adding the 0001 at the end, or Copy (1) of .. in the front. Perhaps because it's being downloaded AFTER the large file was, or because the unrarring process is overwriting the larger file.

Is there a possibility we can perhaps get an option to say 'only overwrite if file is more than 50% larger than the previous file of the same name' .. or something to this effect?

This is mostly to overwrite sample files that have the same file name.

[Quade]

There should be no overwriting at all. Even the unrar process renames.

PM me an example and I'll try it.

[nzwhat]

Still seeing this problem, although very rare now. Just had a 5.5 gb mov file overwritten by a sample with the same filename, that extracted after the larger filename.

[DThor]

If you don't PM what the post was, it won't get fixed.

DT

[nzwhat]

I actually did PM a while back. I'm currently on 6.31 build 1877 and found two other instances.

Here's what appears to be happening:

nzb file leads to:

abc.wmv
abc.par(set)
abc.rar
abc.sfv

where:
abc.wmv is 10mb sample
abc.rar unrars to 100mb full file, also named abc.wmv

one of the two is happening:

1)when the sample abc.wmv (sample )has been downloaded first, abc.wmv (full file) is getting skipped as abc.wmv already exists. ( a greater than logic here would resolve this issue )
2)when the abc.wmv (full file ) has been downloaded first, abc.wmv (sample ) is overwriting the exists abc.wmv without adding a 0001 or different renaming, as it does when the same filename is already within the par set being extracted.

is there a heavier debug log setting aside from what's in the Log window that can explain the logic?
I can send nzb file as well if required.