newsbin.com

been a user since close to the beginning, thanks for all you have done.

say, i have a d/l folder selected, and an unrar folder. I have used this config since it was first available many many years ago. for some reason 6.90 5524 and possibly before doesn't follow the unrar folder
any thoughts or ideas ?? I selected it again, but still it unrar in the d/l folder

dl folder is C:\ZZZ Newsbin\Newsbin dl location\
dl folder for nzb is C:\ZZZ Newsbin\Newsbin dl location\$(NZBFILE)\
unrar folder is D:\newsbin unrar\$(NZBFILE)\

my unrar files end up in the C:\ZZZ Newsbin\Newsbin dl location\$(NZBFILE)\ folder
dl folder works as intended

thanks for your time

What version are you using?

How are you feeding the NZB's?

For 6.90, I recommend feeding the NZB's directly to the download list for manual downloading.

If you use NZB Autoload, set an unrar path in the autoload options. There does seem to be a bug where autoload uses the download path unless you set an unrar path in the autoload options.

version was 690 final (5524?), sorry, not sure exact numbers, since I rolled back a few

I always feed the nzb from a auto load folder , not sure where the autoload options to set the unrar path,
rolled back to b12 5396 and that seems to work as before.

I have the unrar path set in the options / setup as I always have
could be option changes were made/tweaked and I haven't kept up.

I did change the unrar folder for the nzb in the d/l list, that worked before i rolled back. is that what you were referring to ??
thanks much for your time.

On the options, under the "NZB options" there's a list. Select the item in the list and then "Properties".

You can set an unrar path there. You can have more than one NZB Autoload, that's why there's a list. Each NZB autoload can have unique download and unrar folders.

got ya, found it. thank you.
not sure why it changed in the last release or 2. all good though

I did have 2 autoload folders listed, I only use one of them so deleted the other. both are still valid folders though.

As I said, it seems to be a bug in autoload.