by DThor » Sun Feb 19, 2012 8:09 am
Regarding the slow speed when picking up an old download, I'm guessing you're watching newsbin going through the existing chunks on disk at the same time it's snagging new chunks. In other words, it's doing exactly what it's supposed to - using what's already downloaded.
It might be a good idea to not download the first chunk with autopar off, yeah.
I don't want the 'smart' behaviour of quickpar since what's going on is a lot more dynamic, chunks being grabbed potentially from several sources. I'd rather have the security of a proper test, rather than relying on a saved file that may or may not be out of date. Bottom line is, you can't please everyone. It's always a balance between getting complete downloads without having to intervene, and downloading a few extra chunks to ensure that happens. Most people with highspeed connections don't care about the odd chunk when you're talking about restarting the application. Some, like you, want just what you want and not a byte more, and are willing to micromanage (i.e. not use autopar) to meet that end. Fair enough. Maybe autopar off shouldn't do any extra downloading at all.
As far as the rest of your experiences, I don't know what's going on. I never have incomplete rars when it's in progress and you restart newsbin, that sort of renders the restart feature pointless. I'm wondering if you have a problem with your downloads.db3 file? When your queue is empty, quit Newsbin and delete that file, see if that makes a difference.
DT