Questions and comments regarding Newsbin 6.40B2
Posted: Tue May 29, 2012 7:15 pm
I was using Newsbin 6.20B1 and just installed 6.40B2 yesterday (on XP64). I like it. All the options are nice and in general it works very well for me.
But I have some questions about Newsbin 6.40B2:
1. I never saw these error messages with version 6.20B1; is it just coincidence that I started seeing them with version 6.40B2? They may be totally unrelated to the version. Even if it's just a coincidence that I just started seeing them after I installed 6.40B2, what's the point in making these specific critical error messages trigger a popup? Couldn't these just be in the logging tab without appearing in a critical error popup? I have no idea what I'm supposed to do about these, and everything works fine in spite of these errors. I need a few PAR repair blocks but I often need those when I don't get the critical errors too. Or is there something I should be doing about these instead of ignoring them? They are infrequent so it's not a big deal, but if there's a point to making these messages appear in popups, I'm missing the point and need help to see it.
[20:05:30] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[20:50:34] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[21:50:30] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[12:40:31] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
2. The signature detection works well on 6.40B2. I was having problems with that on 6.20B1 for some reason. However, there are some instances where I want to override the signature detection and I right click the rejected file, and choose "Add to download list - bypass filters". That works fine too, except the status column (and colored icon at the left) never updates to show it was downloaded. Why is this? In an older version of Newsbin the status column and icon changed to reflect when the signature rejection was over-ridden and that the file was downloaded anyway...shouldn't it still do this or is there some reason why it doesn't? And if there's a reason other than a bug, can this be made an option to show it's been downloaded when it's been downloaded after it was rejected by the signature filter?
3. As another thread posted by someone else noted, after long download sessions, somehow I end up with stray nb2 files. In some but not all cases, they have remained because I cancelled the download of a huge file that was in progress when I realized it wasn't something I wanted and was taking a lot of time and bandwidth. (I right clicked the file and chose "remove from download list", in the download list section, but I've also ended up with stray nb2 files when I didn't do this, for unknown reasons). The stray nb2 files aren't a huge problem except for one thing: I can't delete them unless I shut down Newsbin. When I try to delete them without shutting down, an error message tells me the file is in use, even when all downloads finished 30 minutes ago and there's no activity at all.
3a. Is there any way to have Newsbin clean up and remove these orphan nb2 files automatically? When I remove a file from the download list, shouldn't that nb2 file be cleaned up automatically?
3b. Alternatively, can the nb2 files be made to appear in an alternate directory rather than the final destination directory (make this an option)? This way, if the stray nb2 files appear and don't clean up (and can't be deleted), they won't clutter the destination directory and won't require a shutdown and restart of Newsbin to clean up the directory, which is kind of annoying, especially when you have a large header list, have to reload it, and find your place again. It can be done but it's a pretty large annoyance. I realize this takes extra resources like CPU/HDD to move the file from the temp directory to the final destination directory, which is why it would need to be an option only, but I really don't have performance issues so I think I could take the performance hit to avoid the cluttered download directory and avoid the need to restart Newsbin which is an even bigger performance hit.
Having a cluttered temporary directory where the nb2 files temporarily reside wouldn't be a problem like having a cluttered destination directory is, where I'm trying to select files to move to other directories and the nb2 file clutter makes this a mess. (Or if I could make the destination directory the first X characters of the post subject line, then in some cases, I wouldn't have to move the files from the destination directory and the clutter wouldn't be so much of a problem).
Overall though I'm pretty happy with 6.40B2, which works very well aside from these issues. Good job!
But I have some questions about Newsbin 6.40B2:
1. I never saw these error messages with version 6.20B1; is it just coincidence that I started seeing them with version 6.40B2? They may be totally unrelated to the version. Even if it's just a coincidence that I just started seeing them after I installed 6.40B2, what's the point in making these specific critical error messages trigger a popup? Couldn't these just be in the logging tab without appearing in a critical error popup? I have no idea what I'm supposed to do about these, and everything works fine in spite of these errors. I need a few PAR repair blocks but I often need those when I don't get the critical errors too. Or is there something I should be doing about these instead of ignoring them? They are infrequent so it's not a big deal, but if there's a point to making these messages appear in popups, I'm missing the point and need help to see it.
[20:05:30] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[20:50:34] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[21:50:30] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
[12:40:31] ERROR NNTPSocket - SendCommand Worker - Server:news.giganews.comSendCommand - failed to Read Response From server: Socket - Read From Server Failed
2. The signature detection works well on 6.40B2. I was having problems with that on 6.20B1 for some reason. However, there are some instances where I want to override the signature detection and I right click the rejected file, and choose "Add to download list - bypass filters". That works fine too, except the status column (and colored icon at the left) never updates to show it was downloaded. Why is this? In an older version of Newsbin the status column and icon changed to reflect when the signature rejection was over-ridden and that the file was downloaded anyway...shouldn't it still do this or is there some reason why it doesn't? And if there's a reason other than a bug, can this be made an option to show it's been downloaded when it's been downloaded after it was rejected by the signature filter?
3. As another thread posted by someone else noted, after long download sessions, somehow I end up with stray nb2 files. In some but not all cases, they have remained because I cancelled the download of a huge file that was in progress when I realized it wasn't something I wanted and was taking a lot of time and bandwidth. (I right clicked the file and chose "remove from download list", in the download list section, but I've also ended up with stray nb2 files when I didn't do this, for unknown reasons). The stray nb2 files aren't a huge problem except for one thing: I can't delete them unless I shut down Newsbin. When I try to delete them without shutting down, an error message tells me the file is in use, even when all downloads finished 30 minutes ago and there's no activity at all.
3a. Is there any way to have Newsbin clean up and remove these orphan nb2 files automatically? When I remove a file from the download list, shouldn't that nb2 file be cleaned up automatically?
3b. Alternatively, can the nb2 files be made to appear in an alternate directory rather than the final destination directory (make this an option)? This way, if the stray nb2 files appear and don't clean up (and can't be deleted), they won't clutter the destination directory and won't require a shutdown and restart of Newsbin to clean up the directory, which is kind of annoying, especially when you have a large header list, have to reload it, and find your place again. It can be done but it's a pretty large annoyance. I realize this takes extra resources like CPU/HDD to move the file from the temp directory to the final destination directory, which is why it would need to be an option only, but I really don't have performance issues so I think I could take the performance hit to avoid the cluttered download directory and avoid the need to restart Newsbin which is an even bigger performance hit.
Having a cluttered temporary directory where the nb2 files temporarily reside wouldn't be a problem like having a cluttered destination directory is, where I'm trying to select files to move to other directories and the nb2 file clutter makes this a mess. (Or if I could make the destination directory the first X characters of the post subject line, then in some cases, I wouldn't have to move the files from the destination directory and the clutter wouldn't be so much of a problem).
Overall though I'm pretty happy with 6.40B2, which works very well aside from these issues. Good job!