newsbin.com

Hi!

I'd like to understand:

Why, when downloading, sometimes there are 'missing parts' (in red). I understand that often they are not "really missing" because when I right-click 'Retry Download', not always, but most of the time, missing parts are actually downloaded successfully and 'Downloading' becomes 'Downloaded'. When they are "really missing", I then "Assemble Incompletes".

So:

Is there a way to make Newsbin "Retry Download" automatically? 'Max Retries' option is set to 15, but it doesn't seem to be retrying as I have to do it manually every time.

Also, is there a way to force "Assemble Incompletes" if after x retries, parts are still missing?

Thank you!

What version are you using?

In the latest beta (which I recommend over 6.42) the number of retries determines how long Newsbin will wait before assembling the files. I use 2 which means it'll retry 3 times and then assemble the files IF there's a PAR file and IF it looks like it has 90% of the set of files downloaded. The 90% number is because most files seem to have 10% recovery files which can be used to repair the files.

The latest beta will fail incomplete files that don't have PAR files. You can add them back from failed an manually assemble them from the right click menu.

Thanks.

Yes, i'm already using the latest beta...

I'll try to put Max Retries at 2 and see how it goes...

You might want to figure out why you have errors that later work. Suggests to me that you might be running too many connections to the server.

Error should be listed in the logging tab.

You can watch it count down and then retry. You should see the red blocks change color and switch back to red or succeed. It's the right most element of the status columns. "N:XX".

The errors in the Logging tab are all the same (with of course different articles):

[12:48:31] HIGH Failed to retrieve Article from Server:PowerUsenet ARTICLE <IoWQDxrpJV199wHpb8U5@JBinUp.local>
| 430 no such article

But when I hit "Retry Download", it is actually downloading...

Tried to reduce to 3 my number of connections, and it's doing the same thing...

Yeah, that's not a connectivity problem. It's a server problem. How many does powerusenet permit? I'd use 1/2 that number or 10, whichever is smaller.

Quade wrote:Yeah, that's not a connectivity problem. It's a server problem. How many does powerusenet permit? I'd use 1/2 that number or 10, whichever is smaller.

PowerUsenet is allowing 15 connections... I even tried with 2 connections, and I still have some (not really) missing parts...