Re-downloading of incompletes

[bruce73]

I was downloading a large file which had many incompletes (they were mostly ID'd as "downloading", a couple were "incomplete"). I manually assembled them. I needed to stop the download temporarily, so I moved the file to the Wish List and closed the program. When I resumed later, all of the incompletes I had combined were re-downloaded, which amounted to several gigs.

When you manually combine an incomplete, isn't the part written to disk? Is there any way to avoid this in the future. Thanks.

6.40B7 Build 1997

[bruce73]

No one sees this? Maybe I'm not understanding what should be done, then. What exactly is the difference between "downloading" (where it doesn't seem to be any longer) and "incomplete?"

[Quade]

You may be the first person to ever test this. I've never done it before. Once you assemble them, you might as well remove them from the download list anyway. No more data will be added to them.

What were you trying to accomplish?

[bruce73]

I was downloading a large rip (40GB+). Normally, with files >25GB+ or so, I disable AutoPAR so that I can unRAR manually. Also, since this was a old post (~18 mos.), I expected to get some incompletes, and, sure enough, about 15% of the parts were.

As I monitored the download, I would manually combine the incomplete parts (a few showed a status of "Incomplete," but most still said "Downloading," even though it was clear they had finished -- that's why I asked the difference between those two descriptions). Anyway, I needed to pause the download, so I moved the file to the Wish List and closed the program. When I re-opened NB and moved the file back to the Download list, NB seemed to be scanning all of the downloaded parts -- I guess to get caught back up (?) -- but all of the parts that I had manually combined (and thought were ready for repair) were re-downloaded all over again, which amounted to several gigs (most had been only incomplete by a block or two).

I'm not sure if moving the file to the Wish List caused this behavior, or closing/re-opening the program did. I hope this makes sense.

[Quade]

"Downloading" means it's still trying to acquire chunks of the file. It won't "Assemble Incompletes" if it's still in the "downloading" state.

15% is pretty aggressive. In a situation like that, you might want to first see how many PAR blocks you can get because that determines whether it's fixable or not. If you can only get 10% of the files par blocks, then it'll never be able to repair with 15% damage.

[bruce73]

True, I understand. But I mis-spoke. What I meant was that 15% of the parts had blocks missing (with most only missing 1 or 2 blocks). There were plenty of PARs to fix which took a couple of hours on my dual core 6600 machine.

But most of the parts listed as "downloading" had been sitting like that for several hours. I understand (hopefully correctly) that with a new file, NB is perhaps waiting for missing parts to populate on the servers. But at what point does NB throw in the towel with old posts and label the part "Incomplete?"

[lordkinbote]

"Downloading" means it's still trying to acquire chunks of the file. It won't "Assemble Incompletes" if it's still in the "downloading" state.

How does one stop the "Downloading" state of certain files in order for you to be able to Assemble Incompletes? I've tried Pausing them and doing it and it doesn't seem to work.