newsbin.com

Version 6.70 Beta 5 has a number of bug fixes and seems pretty stable. There are a number of small clean-up fixes as well as some esoteric issues that have been addressed.

Here is a summary of changes:

• Fixed issue processing files that start with "con.". They will fail to be created during download.
• Fixed issue where the speed guage reading was about 10% high
• Fixed issue where not all downloaded headers were showing up in the post list.
• Fixed issue where header downloads weren't using the server colors.
• Fixed issue where large search based downloads don't always show "part01.rar" as the primary file.
• Sped up startup time when you have a large files list. Like > 10,000 items.
• Fixed the files list search function. Works on filename, path and subject
• Fixed issue where the Find in files list wasn't scrolling to the top most item.
• Fixed issue with filter file sizes not applying consistently.
• Fixed issue with NZB Filename cleaner cleaning a bit too much.
• Fixed issue with Ctrl-Y not forcing a re-download
• Fixed issue where Ctrl-R was feeding binary to the output file resulting in much larger files than they should be.
• Fixed issue where Watch re-scan won't work in local mode if you don't specify a topic.
• Watch List re-scan now obeys any set age limit.

The complete list of changes and the download link is on the Newsbin Beta Page. Any questions, comments, or bug reports can be made by replying to this thread or by using the Technical Support Contact Form.

Has handling Gzipped NZB's changed? Have loaded a Gzipped NZB from a site I use regular and NB is not recognising it? Worked in previous releases and previous Beta4! Extracting the NZB and loading/downloading in NB is working as expected so the NZB is valid, just NB not recognising it when gzipped!

Send it to us and we'll check it out. ts at newsbin dot com

64 bits or 32?

Restart Newsbin and look in the logging tab.

[22:23:56] DEBUG High Speed File Creation Mode: Disabled - "Run as Administrator" to Activate this mode
[22:23:56] HIGH PAR Pausing: Enabled
[22:23:57] HIGH Par2Repair - Single-core 1.5
[22:23:57] HIGH MessageId Filter: Enabled
[22:23:57] HIGH FileType Version: 2.01

You should see this. If you're missing "FileType" then I'd suggest a re-install.

LibFiletype32.dll
LibFiletype64.dll

You should see one or both of these in the install folder.

From the 6.70b2 thread:

BZee wrote:I'm seeing bright blue progress bars for individual pictures with single or multiple [2 or 3] parts (not a color I have set for a server). also the 'Current Progress:' area is not divided by lines for multi-part pictures (but the blue shading does fill in the correct part areas).

Still the same in 6.70b5. I would like to see the server colors used so I could get an idea of how each server is being utilized (I access 5 servers).

Edit: For incomplete multi-part pictures the missing segment(s) are shown in red at the end of the file even if it is a middle segment that is missing.

Quade,

I run Win10 x64 LTSB so only have the LibFiletype64.dll.

I have now totally uninstalled/deleted NB and re-installed/re-registered from scratch but get the same issue with gzipped NZB's, Logging TAB shows the info about HIGH FileType Version 2.01! I then copied over my NBI and SPOOL_V6 folder from my backup and now Logging info does not show on restart but same issue with gzipped NZB files!

I've always upgraded over the top of my NB install so wonder if it's time for fresh start regards the NBI/Logging issue, old/stale settings no longer used?

I've also emailed one of the NZB's to the address Dexter gave!

I've also emailed one of the NZB's to the address Dexter gave!

I reproduced it. Thanks. Works if I un-gz it first. Doesn't work as a GZ.

Yes, works when extracted so that's what i'm doing until it's fixed, thanks for confirming!

In NewsBin 6.70B 5, Safe Configuration as... a click, and later on save click, there comes a popup window
"Newsbin50" and the Message is "Encountered an improper argument". I click on ok, the window closes.
NewsBin hangs and can exit only via the Task Manager.
sorry my bad englisch

Teddy wrote:In NewsBin 6.70B 5, Safe Configuration as... a click, and later on save click, there comes a popup window
"Newsbin50" and the Message is "Encountered an improper argument". I click on ok, the window closes.
NewsBin hangs and can exit only via the Task Manager.
sorry my bad englisch

I had this same error on B4 and it doesnt seem to have saved any configs since the update. I now tried to install B5 and it was as if my previous install didnt exist. I managed to get it running by double clicking and older nbi file from B3. But I still cannot exit without task manager and cannot save a new config file. Always "Encountered an improper argument".

I've been trying to reproduce this but haven't managed to. I wonder if the folder you're trying to save to is read only or something like that?

How about trying to save to your "My Documents" folder or something like that?

Quade wrote:How about trying to save to your "My Documents" folder or something like that?

In documents or other folders, same error. Must end with Task Manager.

Most recently, NewsBin automatically makes backup, Einstellung.nbi.bak, and Einstellung.nbi.old. Can hang it so together.

Most recently, NewsBin automatically makes backup, Einstellung.nbi.bak, and Einstellung.nbi.old. Can hang it so together.

Yeah when it saves, it first write the new NBI file to the "nbi.old" then when it finishes the write, it copies the old one to ".bak" then copy's the new one to the real name.

I doubt that has anything to do with this issue. The change means that in a crash, if Newsbin is in the middle of saving the NBI you still have it original NBI in place when you restart.

Ok I figured out what's going on. "Save As" wasn't actually saving the NBI, it was just setting the new path so, parts of the program were unhappy that I was setting a path for a file that didn't exist yet.

Thanks for the report. Kinda surprised people are actually using "Save As". I've fixed it. It'll be in the next beta. You can manually copy the NBI file for now using explorer.

Quade wrote:

Thanks for the report. Kinda surprised people are actually using "Save As". I've fixed it. It'll be in the next beta. You can manually copy the NBI file for now using explorer.

Thanks, I've done that.

Thanks for fixing the save as. I use it each month or release to save a new config with date version in the name. I was also getting the error just trying to save as well.

With the change to show dates in tabs such as "Last Updated", will there be an option to keep the old format of time lapsed in days/hours etc?

Ctrl-T toggles the date format. There's an option in the advanced options too.

Activate speed limiter is not working now.

My network works at about 120 Mb. I've set the limit to 100mb and all I get is 60mb with NB. I even set the limit to 200 and only got 70 mb. If I turn off speed limiting, it uses all the bandwidth, but with it on I only get about 50%. I noted something changed in this area, maybe it needs a little more attention.

Thanks.

I just updated from 6.70B2 to 6.7B5. With both versions I'm having a problem with Newsbin freezing constantly as the download finishes/starts to par repair/starts to unrar. It'll freeze from anywhere to 5secs to 45 seconds before it starts to work again. I don't know if has something to do with the re-written download engine, but it was never a problem before 6.70B2.

Just a few stats for reference:
i7 3730K
32 GB DDR3
Windows 7 x64
Samsung PRO SSD


edit: After writing this, Newsbin was trying to par repair a download and has been frozen for 2+ minutes. I'm sure it'll come back at some point, but it's still a pain.

Also, I've recently noticed that several of my downloads (that are par repairable) have "finished up and been removed from the download list" without assembling the 20-30 files that are yellow with red lines (missing parts), which means that there aren't enough files in the Newsbin folder to repair it with quickpar. I then have to go back and find the NZB and "redownload" the file (which happens essentially instantly) and manually "Assemble Incompletes" for all the unfinished rars.

just updated from 6.70B2 to 6.7B5. With both versions I'm having a problem with Newsbin freezing constantly as the download finishes/starts to par repair/starts to unrar. It'll freeze from anywhere to 5secs to 45 seconds before it starts to work again. I don't know if has something to do with the re-written download engine, but it was never a problem before 6.70B2.

Yeah. Thanks for the report.

The problem is assembling partial PAR files. They cause the GUI to stall till the par processing completes. I've actually fixed it already and the fix will be in the next beta. If you can just ignore the stall it'll fix itself. The larger the PAR the longer the stall is.

Also, I've recently noticed that several of my downloads (that are par repairable) have "finished up and been removed from the download list" without assembling the 20-30 files that are yellow with red lines (missing parts), which means that there aren't enough files in the Newsbin folder to repair it with quickpar. I then have to go back and find the NZB and "redownload" the file (which happens essentially instantly) and manually "Assemble Incompletes" for all the unfinished rars.

How many retries do you have set? Do they end up on the failed list?

Activate speed limiter is not working now.

I'll have to check it out. Reducing connections will reduce the speed too as a work around.

Re: Activate Speed Limits:

I'm not reporting that it is running too slow, but not fast enough under limited speed. I set it to about 90% of my network speed and it seems to run at 50%. BTW: Sometimes it does a little better getting to about 75%.

I'm not reporting that it is running too slow, but not fast enough under limited speed. I set it to about 90% of my network speed and it seems to run at 50%. BTW: Sometimes it does a little better getting to about 75%.

Yeah, I understand but if you don't want to use it at all, you could tweak the speed by reducing connections also.

Quade wrote:

Also, I've recently noticed that several of my downloads (that are par repairable) have "finished up and been removed from the download list" without assembling the 20-30 files that are yellow with red lines (missing parts), which means that there aren't enough files in the Newsbin folder to repair it with quickpar. I then have to go back and find the NZB and "redownload" the file (which happens essentially instantly) and manually "Assemble Incompletes" for all the unfinished rars.

How many retries do you have set? Do they end up on the failed list?

I've got the default max 2 retries it looks like. They don't end up in the failed file list, but it's also a hard thing to watch. When it's an 8+ GB download, with 20-30 rars with missing parts, I see the files continuously retry and at some point I get bored and look at something else and the next time I check the file is gone from the download list. I'm actually not sure if this is a new problem or has been around for a while (pre-6.70B2 versions).

Have an NZB with some PARS and a RAR that has a part missing but shows as complete when loading in NB, blue dot with P status?

Thought it was strange that the download list showed the RAR as incomplete and clicking Retry Download wasn't doing anything as the post list shows it complete, but the properties show 1 part missing. Normally I get the yellow exclamation triangle if an NZB has incomplete files but not this one? Assemble Incompletes works and can repair the file with the included PARS, but wondering why NB isn't detecting the NZB as incomplete?

You could email it to ts@newsbin.com and we could check it out.

Keep in mind, turning red is error and not incomplete. Incomplete shows as a black bar. You can have complete files with bad chunks of the file (turned red).

Not red or black, my download bar is blue and there is a white space at the end, presumably indicating the missing block! I'll email the NZB to you!

You need to hit the + icon to see what's actually there. It's probably got 20 or more RARS and pars hidden away under the +.

Not sure how long ago this was implemented, but I have a question about the "Cache: n1/n2 (n3)" that is displayed in the status bar at the bottom of the program. What is the number in the parentheses? I know it corresponds to how many .gz files are stored in the Import folder, which I am guessing are compressed lists of downloaded headers, but what exactly does that mean?

I know that after I download headers from a group with 10s of millions or more headers, it takes the program quite a long time to import all these headers into the corresponding spools, resulting in a lot of CPU and disk activity. Is it supposed to take a long time to do this? I don't recall it taking nearly this long (approximately an hour to import about 44 million headers in one group) to import header in the past, but then again, I don't think I was dealing with groups with quite this many headers. Just trying to see if it's my system or if this is typical for the program. I am running Win 7 x64 with 8 GB of RAM and a Quad Core AMD, although it's at least a 5 year old system, with a main HD of 1 GB about half full, plus a 2nd 1 GB HD, again about half full, where I am keeping the Newsbin data which would usually be in the C:\User\...\Newsbin\ folder on the main drive.

Look at the size of the import folder, multiply it by 10 and that's how much data was downloaded from the news server. Depending on the groups, it's a bunch of data. I have about 200 groups and even though my machine is pretty powerful it takes 10-15 minutes to import them all.

I could import them faster by say doing 2 GZ's at a time but I think many PC's would groan under the load. One thing you can do it set Newsbin to download headers every 30 minutes to an hour. Then there's never a huge lump of headers to process in one go.

Quade wrote:You need to hit the + icon to see what's actually there. It's probably got 20 or more RARS and pars hidden away under the +.

Already have, 9 PAR files and 1 RAR and all files show complete status, but properties of the RAR show it has part 49 missing yet NB isn't identifying it's incomplete visually! Only when checking the properties of every file does it show the RAR having part 49 missing and looking at the NZB, part 49 is missing from it! Obviously the NZB was generated with part 49 missing, should NB be identifying it as incomplete when parsing the NZB?

Edited:

I had a chance to look at the NZB. It's not showing incompletes so I can repro your results.

It shows a black bar in the download list.

Strange, I don't get a black bar showing though? I've downloaded it again using Download - Bypass Filters and the download list shows a blue bar progressing then stops just short of complete with a white space at the end, no black bar for the missing part?

You'll only see a black bar if you hit the + icon. Like I mentioned above. There's a single RAR in the group and it's showing a black bar. It's possible you have the progress bar set too small to see it.

Quade wrote:You'll only see a black bar if you hit the + icon. Like I mentioned above. There's a single RAR in the group and it's showing a black bar. It's possible you have the progress bar set too small to see it.

I've stretched the Current Progress bar as wide as my 24" monitor and it still shows the same, no black bar only a white space at the end? I have to click the + icon so I can see the RAR as I only download the RAR first, then repair if needed! So I totally uninstalled NB and got rid of everything and started again, still no black bar shows in the download lists current progress bar? One other thing, my servers are set as yellow in the server options but the bar is blue?

You'll only see a black bar if you hit the + icon.

I've said this 2 or 3 times already. It sure doesn't look like you've hit the + icon from your screen shot.

While you're making changes, would it be possible to change the background color of "incomplete" posts to something other than white? This is the same color as posts I've already downloaded, and it's a little confusing.

Look in the options for "colors/fonts". I think "Partial Download" (which probably needs to be renamed) is the color you want.

Excellent - thanks!

Quade wrote:

You'll only see a black bar if you hit the + icon.

I've said this 2 or 3 times already. It sure doesn't look like you've hit the + icon from your screen shot.

You mean the + icon in the post list after loading the NZB:



If so, that's how I've always downloaded RARs in NZB files!

If you look at the progress on that RAR, you should see a black bar about 1/2 in. That's the one missing block you noted.

Quade wrote:If you look at the progress on that RAR, you should see a black bar about 1/2 in. That's the one missing block you noted.

I know this will piss you off but I don't see a black bar, the pic I posted of the current progress bar is all I see with the + icon expanded, blue with a white space at then end Whatever the issue, it doesn't stop me assembling the incomplete file and repairing it!

Think we'll leave it at that as I either have a setting not configured or old registry entries, you can see it so it's obviously something my end I can't figure!

It's really not that important. I confirmed that it wasn't tagged incomplete even though one block was missing.

It's on my todo list and I have the NZB so, it's all good.

Yep, thanks Quade!

I guess I'm spoiled because it seems gone are the days of backward compatibility. I guess Microsoft, seeing the abysmal compatibility of the various Android versions, decided they no longer need to spend the extra money they had spent in the past to migrate customers AND their old programs.

That said, could you enlighten me as to the special differences (besides sociability) that leaps Win 7, 8.1, and 10 apart from Windows XP? Full disclosure, I have my old XP desktop, but I do possess a Win 8.1 tablet. I have tried three times to upgrade my 8.1 tablet to Win 10, unsuccessfully. I finally figured out an Intel Web Cam upgrade was incompatible. Speaking to MS I found there are many unresolved third party issues.

I'm staying w/8.1 anyway after I saw the even fewer number of apps for Win 10 than for 8.1 (if you could believe it). I am completely baffled that Microsoft with it's dearth of apps wouldn't want to entice new users by allowing them access to their old programs. Even Turbo Tax warned me 2015 is the last year for XP support.

Again, what are the unique features that operating systems beyond XP have?

Not sure what you're asking.

MS is the king of backwards compatibility. Nobody in the industry can match them.

Quade wrote:Not sure what you're asking.

MS is the king of backwards compatibility. Nobody in the industry can match them.

OK then, why is the new Newsbin not able to run on XP. What makes the New operating systems so different?

OK then, why is the new Newsbin not able to run on XP. What makes the New operating systems so different?

You know I initially assumed this had something to do with Newsbin and XP but you didn't actually say it so I didn't go down that path.

The tools I use to make programs don't by default make programs compatible with XP. I could make it happen by jumping through some hoops but I decided that supporting XP for 15 years was enough. it's time to make a break with the past. You can keep using 6.62 on XP if you want to. 6.70 just won't work under XP most likely.

I am looking for a more general answer. Sure, I can live w/6.62 and I am doing so. I have no complaints about your decision. I would just like to know what distinguishes the new tools that causes the exclusion of XP?

My experience w/Win 10 has me uncertain about change. I clung to Win 2000 longer than I should have until I realized XP was more beneficial for multimedia (I bought a digital video/camera). Give me reasons to upgrade - what are the benefits?

It seems to me that there was a leap beginning with Windows 7. I'm just curious what that could be? Is it simply more modular programming tools to ease production of Apps/Programs as you may be suggesting?

I think I've answered my own question - it's mostly about gaming and networking. I knew there was a leap beginning w/Win 7, so I found the answers - I think (you can further clarify):

Windows XP will not support DirectX versions beyond 9.0c.

HomeGroup is a major shift in home networking simplicity that makes older paradigms seem archaic.

Windows 7 is the first operating system from the software giant to natively support touch as a computer interface.

Found that if i deleted all posts from one poster and then clicked on 'clear the search entry' the deleted posts would pop back up,when i shut down newsbin pro and started it up gain those posts were gone.