Version 6.82 Release Candidate 3 Available...

[dexter]

Two more fixes for 6.82. Here is the third Release Candidate:

Changes:

• Fixed issue where the disk free popup would pop spuriously.
• Fixed issue where MP3 files after repair would sometimes be deleted after moving to MP3 mode folders.

Download link is on the Beta Page.

[Voyager62]

You mean it focuses on a particular line?

Yes, it actually selects the line as if you clicked on it. Here is a video of the behavior in RC2, but I've confirmed the same behavior in RC3.

https://youtu.be/T97dJ-9jniA

[depredador]

You mean it focuses on a particular line?

Yes, it actually selects the line as if you clicked on it. Here is a video of the behavior in RC2, but I've confirmed the same behavior in RC3.

https://youtu.be/T97dJ-9jniA

I always assumed this was just some new feature but could not figure out what it did.

[Quade]

Yeah, 750 Mbps, things move pretty fast. I'll have to think about it.

[Voyager62]

Yeah, 750 Mbps, things move pretty fast. I'll have to think about it.

Okay, thanks Quade.

[TheGlade]

With the latest 2 RCs I often get a few of these errors. But downloading goes fine:

Code: Select all

[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>
[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>
[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>
[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>
[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>
[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>
[12/07 22:20:28]  ERROR BR: Read Failure: 16384 to read 0 Actual Read Code: 18446744071562145803
[12/07 22:20:28]  ERROR BR: Read Failure - Would Block
[12/07 22:20:28]  ERROR Downloader: SocketException NEWS SERVER ERROR: <newsserver> NNTPServer: zero bytes read from socket <newsserver>


Is this harmful? Or can it be ignored?

[Quade]

I probably need to suppress that error. Zero bytes read means the server end is disconnecting. Some of them do that after some number of bytes is sent over the connection. it's not really an error.

[depredador]

When I go to kill all connections it now stops downloading and the only way to get it to resume is to exit Newsbin and then open it again.

[Frodoger]

The Sort for Error Messages in the "Failed Files" Tab doesnt Work in the actual Build 5133.

[Frodoger]

I probably need to suppress that error. Zero bytes read means the server end is disconnecting. Some of them do that after some number of bytes is sent over the connection. it's not really an error.

no. Not supress. Comment the error. I always want to know what newsbin do at this moment, when the download speed is not as aspected

[Voyager62]

It looks like the problem with the downloading post being selected when others are being selected has been fixed, but the problem with Newsbin unpausing after unRARing a post still hasn't. This happens even if "Pause Download during UnRAR/Repair" isn't checked. Is it possible you are automatically unpausing and not checking the status of that option first?

Thanks.

Update: build 5142

[Quade]

Newsbin notes the pause status before the unrar starts. Then when the unrar completes, it tries to restore the pause state. If you pause after the unrar starts, the pause state becomes stale. So it restores the state to the state from before the unrar started.

What I'm going to do, is if "autopause" is disabled, it'll not change the pause state. That will solve the immediate issue but IF you have pause during unrar enabled, you'll still run into this timing issue.

[Voyager62]

What I'm going to do, is if "autopause" is disabled, it'll not change the pause state. That will solve the immediate issue but IF you have pause during unrar enabled, you'll still run into this timing issue.

Thank you. That is what I thought was happening and, with a gigabit connection, it is almost impossible to time it exactly between UnRAR events.

[Ronbyram]

Is Newsbin Beta still holding at release 6.82 rc 3? has updates scheule been changed? Just wondering?

[fidodkk]

Ronbyram check this thread:

viewtopic.php?f=44&t=47514

[Quade]

6.82 is the current release.

http://www.newsbin.com/freetrial.php