0.5.0 RC3 and previous version not unraring/deleting

[jatilq]

I have been using Sab for a long time (since the first beta of the original). I appriciate all the hard work put into it. I'm not a coder at all, even though I fumbled through the original install of the original on osx/win/nix.

The previous version gave strange errors about » Unpacking failed, an expected file was not unpacked , I read on here about changing a 1 to a 0. The error went away, but its never extracted since even in this version. I have switched  from delete to unpack... then saved then switched back to delete no fix. I noticed that I have padlocks on all the files, but unlike osx I dont have an option to do 777 for permissions. I'm using x86 win7.

Thanks in advance

[shypike]

Where do you see the padlocks?
It could be that the poster packed his files with read-only attributes, resulting in "protected" files.
We fixed that for Linux, not realizing that it could be a problem for Windows too.
However, on Windows you can easily fix that yourself (attrib -r *)

I'll try to fix this before 0.5.0 Final.

[jatilq]

Thank you for the fast reply. The padlock has been on every file in the folders in all categories.  The padlock is not as bad (unless related) as the unrar issue. I been downloading alot of 4.6 items of late and believe me its a pain.

I'm also starting to wonder if there is a problem downloading par files, because I am getting of "Post processing failed because of verification" I go back in to download the pars and they are messed up. I use giganews and never have so many problem for items with ages under 100 days.

[jatilq]

As I was writing my previous post I had quickpar running because of the verfication failed error and it reportd repair not needed. I do wonder if its something with the pars being downloaded for items that need to be repaired.

[shypike]

I'm still not sure what you mean with "padlocks", please post a screen shot.
It's very unlikely that R attributes occur on many downloads.

SABnzbd relies on regularity in the naming of par2 files.
QuickPar is more permissive, because it relies on you to determine which par2 files to use.
From your post I cannot gather what's going on.
If you have an example NZB file that shows this behavior, please email it to bugs at sabnzbd.org
with a reference to this forum thread.

[jatilq]

I reverted back to beta 5.6 and it worked for a little while, but its not unraring anymore. I removed the read only on the folder and set the permissions for users. I hope I havent posted this more than once. I had to resize the image a couple times.

[shypike]

Rather odd. Does the icon of the NFO file change if you remove the read-only attribute?
On my system it shows always the same icon (not the same as your's).
The icon is determined by the program that is associated with NFO files.

Anyway, the next 0.5.0 release will not let unrar create read-only files anymore.

You're unrar problems are still a riddle to me without the NZB.

[jatilq]

Its not checking with Par2 and if it needs more pars it doesnt download them. All the downloads are just moved to the complete folder with those permissons

[shypike]

Unless there's something wrong with your system,
SABnzbd doesn't suddenly stop par checking.
There can be problems with specific NZB files or NZB files that SABnzbd fails
to handle properly.
If so, please email one or more if these NZB files to bugs at sabnzbd.org,
so we can investigate this.

[jatilq]

I discovered the issue. Folder permissions were screwed up. I did a usb upgrade on my Acer Aspire Revo. Once I took ownership and added some users everthing returned to normal. I'm back using RC3 with no problems