SABnzbd Forums

Please don't flame me, i know this might be a crazy topic to start, but i have to ask.
Is there any idea how this could be done?
I was using 7zip and jzip and they seem to run smoother and faster on my system than
unrar.exe.

I know rar is the standard, but the other guys are free too and they handle rar just fine.
Anyway to bring this feature in?

Thanx for listening.

Yes, do the unpacking yourself in a script.

We will be looking at 7zip in the future, but I have read mixed reports about it.

Alright cool,

After i wrote it i remembered theres scripting available. This should be good.
Should i just check the wiki for help on this?

I guess i finally found a use for a script, i'll share it with the forums when im done.

one question though, when the script is selected to run after a download, is it applied
to each nzb downloaded? Im just worried about where to put the script in the first place,
but im guessing the filenames are passed in through commandline to the script each time
and then the script executes and then the script takes care of the rest of wateva is
in the folder with all the downloaded files etc?

oh and does the script get activated once the files are moved to completed folder or
before?

Thanx for the help.

Consult the Wiki site:
http://sabnzbd.wikidot.com/user-scripts

quick question.

I was wondering , if anyone could explain how the rar implementations works right now.

So it unrars the initial downloads, and then the rar'd files created by unraring the previous files?

What do i have to send back to the system so sabnzbd knows the script is done.

The unpacking is recursive, this has always been the case in SABnzbd.
Personally, I would prefer it to stop after the first level.
Meaning: unrar the downloaded files, but do not unrar/unzip any
resulting rar or zip files.

The script should return 0 if all went fine or another value when things went wrong.
Current releases of SABnzbd ignore this return value, but future release will not.
Also, the console output of the script is saved and is available from the History page.
A later release will show the final line of the output directly in the History page,
so it's useful to put any summary in the last line.