Page 2 of 2
Re: Post processing doesn't seem to work properly - Mac OS 10.5
Posted: January 27th, 2009, 3:39 pm
by shypike
Replace the unrar for OSX?
We've had loads of trouble with unrar 3.80Beta2 on Linux.
RAF, do you know of any unar problems on OSX?
Re: Post processing doesn't seem to work properly - Mac OS 10.5
Posted: January 28th, 2009, 12:49 pm
by syth
shypike wrote:
Replace the unrar for OSX?
Can I simply replace the binary that is embeded in the SABnzbd package, or is there some way to simply point it at the unrar binary I have installed in /opt/local/bin/ ??
Re: Post processing doesn't seem to work properly - Mac OS 10.5
Posted: January 28th, 2009, 2:16 pm
by shypike
The OSX pre-packaged version only looks at the embedded unrar version.
You'd have to replace that one.
Look, I'm not sure about this either. I hope our OSX specialist can help you out.
Re: Post processing doesn't seem to work properly - Mac OS 10.5
Posted: January 28th, 2009, 2:32 pm
by rAf
Hi,
I never had problems with unrar but if you want to replace you can, the unrar binary is in :
/Applications/SABnzbd.app/Contents/Resources/osx/unrar/
Hope it helps.
Re: Post processing doesn't seem to work properly - Mac OS 10.5
Posted: February 6th, 2009, 11:35 am
by interfacelift
Arithmeticae wrote:
EDIT:
After reverting to the old par2 binary, (only the par2 binary was change, all other settings and preferences remained the same) everything works like it should, files that are corrupt/broken are successfully repaired and unrared.
I did the same. 0.4.6 with the included par2 binary failed when repairing/unraring due to the .1 bug apparently. I moved the par2 folder from 0.4.5 in to 0.4.6 and tried the same download again, and it was successful, with no errors.
Something is wrong with the new par2 in 0.4.6 versus 0.4.5 when it comes to repairing files.
Re: Post processing doesn't seem to work properly - Mac OS 10.5
Posted: February 8th, 2009, 2:34 am
by shypike
For OS, this is true when any of the downloaded RAR files contain accented characters (like é).
This will be fixed in 0.4.7.