First, thank you, thank you, thank you for the fix that puts pars into the wish list if you have Autopar disabled. I still don't understand why the switch that says "Disable Autopar Unpausing" doesn't work, but at least putting them in the Wish List saves a lot of manual effort when downloading posts.
This weekend was the first time I had a chance to test it. It seems to work well, but there is something funny going on, too.
The pars go into the Wish List all right, but some of the parts of the main post show up again at the bottom of the Download List after they have already been downloaded. Not all of them, and not every time, and I haven't been able to see any pattern to it. In a post with 50 parts, maybe the first 12 parts show up at the bottom of the list some time after they've already been downloaded. I usually just queue up a bunch of downloads and then go do other things, so I can't tell you whether they appear one at a time after they've been downloaded, or all at once, and I can't tell you how often it happens, but it happens often enough that I noticed it a couple of times in a couple of days.
When I noticed it, I let a few of them get to the top of the list, and they just disappeared after Newsbin attempted to download them. NB didn't download a second copy of them, and it didn't put them in the Failed Download list as duplicates, so maybe it's no big deal, but obviously something is askew, and it makes the stats about remaining bytes and completion time for the Download List unreliable. Still, the feature is a great improvement, so please don't change it back.
One other thing to report --- this has been happening for the last few months, so it's not related, but about half the time when I start Newsbin, I just get a message box with "Newsbin 50" in the caption, and a triangle with an exclamation point in the middle. No text in the box. I close it, and nothing happens. I start Newsbin again, and it comes up normally. I don't think I've ever had the restart fail, and I haven't noticed any pattern about what else I'm running when it happens. I definitely have plenty of memory and disk space, so it's not that.
If nobody else has reported it, it might have something to do with VS runtime libraries, because I have both VS2010 Express and the VS11 Developer Preview installed. Using Win7-64 SP1.