Support Forum

To add to that: par2 files can be used if somehow the data got corrupted during the uploading/downloading. So it's good to have it. SABnzbd will only get the par2 files if the files need repair, we can detect that. When creating par2, it can check the integrity by analyzing parts of the data. The si...

It might be that it's still decoding articles before it can unpack. Where is the download when it is delayed? In the queue or already in history?

What does it show as state?

Het uitpakken is dus vastgelopen?
Je kan via task manager proberen unrar.exe te killen.

You can run it using the portable.cmd, this will force it to use a locally hosted sabnzbd.ini!

Because it requires us also to re-work the way we handle the files. We need to keep track which "holes" are left in the files, which we don't do.

Should normally work just fine, unless the server isn't very good..

While we could do it, we should do this with the header (like Unrar does). Needs a seperate version for rar3 and rar5.

Depends how you setup your synology host, if it's different from the name we get from the system. We try to automatically detect it when installing.

There is a way to indeed extract this from the header of the rar-files.
Maybe you have some coding skills and can help us out with this? I have some basic documentation!

You should have enabled in Config > Switches > Post-process only verified jobs.

We catch all the output from the script and display it in the GUI or the log, for debugging it can be usefull.

The \\? is correct.
Does it work when you unpack to a "normal" locatie like the C drive? I assume the O drive is some network-share?
Seems it gets stuck because of a permissions error possibly.

Je hoeft alleen je history1.db file te verwijderen, niet al je settings.
Deze staat waarschijnlijk in de map "~/.sabnzbd/admin/"
Wel eerst SABnzbd uitschakelen, anders kan het niet!

Will sabyenc auto-update on Ubuntu?