Support Forum

The Plush and Smpl authors will fix their own license issues. For the main program. Your comment on JSON.PY is a bit odd, since this is the one module that does not have a license problem. The source file itself is quite informative about its license and origins AND the LGPL-file is present, since S...

It took a long time, but I got some test results. On Windows XP with Microsoft IPV6 and AICCU installed, I can access newszilla6.xs4all.nl fine. No problems. Testing on Vista is officially not possible this way. The SiXXS website says there is no support for AICCU on Vista. How do you guys test IPV6...

I find see something in the logs: Par verify failed on \\XXXXLaptop\sabdown\Incomplete\wwo2-dvd 1²2\wwo2-dvd 1+2.vol000+01.PAR2! Is this the job that failed? Looks like PAR2.EXE indeed concludes that the set is not correct, if that is justified I don't know. SAB tries no further download of PAR2 fil...

Vinny, Studying the logs gives no conclusions. Ok, it's easy to blame memory. It looks like the PAR2 processing passed OK, otherwise you would have had an error message before. The error message comes from Unrar. Maybe the PAR2 program makes mistakes? I don't know for sure. I've never seem it on my ...

binsearch should be usable with the current RSS. First find the right RSS feed where you expect your downloads. Enter the URL in the Config->RSS page of SABnzbd. Specify a text fragment that will identify the type of download you're interested in. This is the hard part, since you have to be able to ...

Your logfile is incomplete, it does not contain the post-processing part, where things went wrong. Could you send all of the logfiles (like sabnzbd.log.1 .2 etc.). Somehow the repair by PAR2 failed, the CRC error comes from unrar (which received an incorrect file). One extra check: assuming the job ...

We're overhauling the RSS module currently. We'll have a look at the specifics of BinSearch.

Could you specify the exact Operating system version and possibly email your sabnzbd.log file (preferably zipped) to [email protected] ?

Looks like newzbin changed their RSS format again and SABnzbd does rather clumsy handling of these files.

I found the problem and have improved the code.
Will be part of the soon-to-be-released 0.3.1 bugfix release.

Do you have "Enable periodic Save" active in Config-->Switches on? This saves the queue state after each file completes. Ungraceful stops are by definition a problem. SABnzbd can only resume for the state it reads from the last saved state (stored in the cache directory). If those files ha...

Got your logfile. Something goes wrong in the user profile detection, I think. Lines like: C:\Users\\Documents\SABnzbd\interfaces\Default are suspect. It should read (assuming your Windows name is turkarican): C:\Users\turkarican\Documents\SABnzbd\interfaces\Default Assuming you have installed SABnz...

What firewall software do you use?
Any other "special" stuff regarding networking?
Can you email the sabnzbd.log file to [email protected] ?

Unfortunately the test team does not have access to a Vista-64 system,
but we did not receive such complaints before.

I would not be suprised, newzbin keep changing things.
Since I'm working on the RSS module anyway, I'll make sure I test newzbin properly.

Thanks for the info.

Found a solution, remapping the characters that come from unrar seems to work.
Only I don't know if this will have side effects.
It's touch and go with these 8-Bit ASCII chars, Unicode was invented for a reason. Sadly yEnc does not support it.

Just posting complaints in this way is not very useful.
Please explain more about your situation.
Operating System? Do you run Python sources, if so what do Python and what modules did you install?
Can you send logfiles (zipped!) to [email protected].