newsbin.com

I have some watch folders set up for special processing of downloads. When I'm doing manual searches through the Search Tab, many times I like to right click a result, use the Create NZB from Posts... option and then save the .nzb in a specific watch folder. As far as I can remember, 6.50B12 was the last version that saved .nzbs from the Search Tab correctly. When I do this with B14, the posts that are loaded from the watch folder are not the correct post. If, however, I use the Download option in the Search Tab and then use the Create NZB from Files... option from the Download List, the .nzb appears to be created correctly. To replicate the problem, use the Search Tab and search for 'ubuntu 13.04 amd64 iso'. I get only one significant search result that is approx. 816.9 MB. (1) Try to create a .nzb from the search tab. (2) Select the same post to download and create an .nzb from the download list. The resulting .nzb files are drastically different--3KB vs. 208KB. I'll past the first couple of lines from each so you can see the difference. If you need, I can upload the complete .nzb files for further inspection.

NZB from Search Tab (corrupt):

Code: Select all

<file subject="z.565 (264 of 346)(1/19)" poster="Yenc-PP-A&amp;A (Yenc-PP-A&amp;A)" date="1294844968" >
<groups>
<group>alt.binaries.amos</group>
</groups>
<segments>
<segment number="1" bytes="258350">4d2dc365$0$3359$c3e8da3$f017e9df@news.astraweb.com</segment>
<segment number="2" bytes="258350">4d2dc370$0$3359$c3e8da3$f017e9df@news.astraweb.com</segment>

NZB from Download List (good):

Code: Select all

<file subject="testupload [12 of 38] &#34;ubuntu-13.04-desktop-amd64.iso.001&#34; yEnc(1/143)" poster="BinUpPro &lt;youwish@this.is.where.invalid&gt;" date="1372351697" >
<groups>
<group>alt.binaries.jbinup.test</group>
</groups>
<segments>
<segment number="1" bytes="363439">kqhob3$enq$21@nnrp.blueworldhosting.com</segment>
<segment number="2" bytes="363439">kqhobi$enq$22@nnrp.blueworldhosting.com</segment>

Totally bizarre.

I'll check it out. Thanks.

Forgot to mention this is 64-bit version running on Win 7 Pro, if that makes any difference.

Problem fixed in 6.50B15. Thanks!