v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
Forum rules
IMPORTANT : Be sure to read the NewsLeecher forums policy before posting.
IMPORTANT : Be sure to read the NewsLeecher forums policy before posting.
v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
Group:audiobook OR Group:book
\\TM5\T5.Audiobooks\<Date>\
No
Is saving other group files to this Folder.
After deleting the Audiobook entry, files were unpacked to the next entry in the Advanced "Unpack" Folder
Groups entry does not appear to be evaluating Groups properly or Unpack is defaulting to one of the Fileset Name listings instead of the default folder.
Update: once I deleted all entries except the first 2, Unpack began to unpack to the default folder. It appears that unpacking is defaulting to third Fileset entry.
The first Fileset entry with the "OR" was not working.
\\TM5\T5.Audiobooks\<Date>\
No
Is saving other group files to this Folder.
After deleting the Audiobook entry, files were unpacked to the next entry in the Advanced "Unpack" Folder
Groups entry does not appear to be evaluating Groups properly or Unpack is defaulting to one of the Fileset Name listings instead of the default folder.
Update: once I deleted all entries except the first 2, Unpack began to unpack to the default folder. It appears that unpacking is defaulting to third Fileset entry.
The first Fileset entry with the "OR" was not working.
Last edited by noblemd on Mon Dec 09, 2019 5:13 pm, edited 3 times in total.
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack
Further update: As soon as I entered a listing with a single Group specifier in ANY position - Unpacker defaulted to that folder.
Last edited by noblemd on Sat Dec 07, 2019 10:09 pm, edited 2 times in total.
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack
Update2: "OR" does not appear to work with the Group specifier
The Group specifier cannot be used in Folder Fileset Matching.
It screws-up the default Folder choice.
The Group specifier cannot be used in Folder Fileset Matching.
It screws-up the default Folder choice.
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack
noblemd,
Try this unofficial forum test release when you got the time:
https://www.newsleecher.com/nl80004.ufr2.exe
I haven't tested much yet, but the group:groupname tag should be working now. Multiple group-tags cannot be used in the same query though, so no group:groupname1 OR group:groupname2 syntax.
Try this unofficial forum test release when you got the time:
https://www.newsleecher.com/nl80004.ufr2.exe
I haven't tested much yet, but the group:groupname tag should be working now. Multiple group-tags cannot be used in the same query though, so no group:groupname1 OR group:groupname2 syntax.
bug fixed. no idea how. hate it when that happens. trying to break it again now. will. not. be. defeated.
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed
v8v4 UFR2 - Win 10 1909
Thanks for the Group specifier quick fix.
Not thoroughly tested, but seems to work.
Thanks for the Group specifier quick fix.
Not thoroughly tested, but seems to work.
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
Using nl80004.ufr2 Ive selected Leech to Specific Folder but it still unpacks a rar to the default download folder instead of the specific folder I've set that leech to. Ive left unpack folder blank and don't wish to unpack to a sub folder.
sorry Found nl80004.ufr4 and tested with that and it still same
sorry Found nl80004.ufr4 and tested with that and it still same
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
If I am not understanding your problem (see below) - could you give a specific example of what you are referring to.XManJx wrote: ↑Tue Dec 10, 2019 11:26 pmUsing nl80004.ufr2 Ive selected Leech to Specific Folder but it still unpacks a rar to the default download folder instead of the specific folder I've set that leech to. Ive left unpack folder blank and don't wish to unpack to a sub folder.
sorry Found nl80004.ufr4 and tested with that and it still same
If I am understanding your post properly...
Leeching and Unpacking are totally different Functions - each would have its own set folder unless both are set to the same folder.
The Leeching folder is where the files from the NewsGroup (RAR/Pars) are downloaded and reside until unpacked.
The Unpacking Folder is where those files (RAR/Pars) are unpacked recreating the posted file(s).
Specifying to Put in Folder would put the leeched RAR/Par files in the subfolder NOT unpack to the subfolder. As I mentioned above Leech is about Leeching and Unpack is about Unpacking - two different functions.
I tested what I think you were talking about - Selecting a file to download and Leeching to a specific folder - it worked as expected - the Par/RAR files downloaded to the specified Leeching Folder: W:\_Temp and were then unpacked to my default Unpacking Folder: \\TM5\T5.Current exactly as it should.
Image below:

Last edited by noblemd on Wed Dec 11, 2019 10:24 pm, edited 5 times in total.
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
Further Info:XManJx wrote: ↑Tue Dec 10, 2019 11:26 pmUsing nl80004.ufr2 Ive selected Leech to Specific Folder but it still unpacks a rar to the default download folder instead of the specific folder I've set that leech to. Ive left unpack folder blank and don't wish to unpack to a sub folder.
sorry Found nl80004.ufr4 and tested with that and it still same
Later, perhaps, an UNPACK Specify will be added to the Search Tab.
For now, what is available to you is in the FOLDERS settings. See my post below for an example of how to use the FOLDERS settings - ADVANCED UNPACKING. These settings do not allow you to change the unpacking folder "on the fly" but will allow you to automatically set unpacking folders based on several criteria.
http://www.newsleecher.com/forum/viewto ... =9&t=35687
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
With the Unpack folder left Blank it should unpack to the the folder you selected to download to. I had it set to C:\Downloads and then removed it but it still unpacks to C:\Downloads when i specified to leech to D:\AnotherFolder
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
The command you purported to use is LEECH (specify)
NOT Leech AND UNPACK (specify).
As stated previously – Leeching and Unpacking are not the same - the only thing you are telling NL to do is LEECH to the selected folder - You are not telling it to UNPACK to that folder - LEECH only (specify). NL unpacks to the default UNPACK folder when no User unpack folder is specified - That is absolutely the correct thing for NL to do.
LEECHING and UNPACKING are two different and exclusive functions.
Also as I stated, maybe later (up to the programmers at NewsLeecher) the Leech menu will include a Leech & Unpack (specify) option (NOTE: Both functions included - NOT LEECH ONLY).
For now NL DOES NOT INCLUDE a Leech AND Unpack menu item.
NL is absolutely operating properly in this instance - Doing exactly what it is supposed to do.
Since this is NOT A BUG but PROPER OPERATION you should request the Leech & UNPACK (specify) function be included in NewsLeecher in the Wishlist Board Forum:
Wishlist for Santa
If you got suggestions for new features or feature changes in NewsLeecher, go ahead and let santa know.
http://www.newsleecher.com/forum/postin ... e=post&f=4
Windows 10 v.20H2
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Ryzen 3950 (16 Cores 32 Threads - OC 4.0 GHz)
DeepCool Captain 240 RGB V2, AIO Liquid CPU Cooler (Max Temp 75°C 100% load)
NL download drive: M2 2280 500 GB NVME SSD (2.5 GB/s r/w)
Synology DS1621+ NAS #1: 32 TB RAID 5 (5 x 8 TB Drives) 10GbE
Synology DS1520+ NAS #2: 18 TB RAID 5 (4 x 6 TB Drives) 5GbE
500 Mb/s Internet Connection (NL Avg D/L speed 55 MB/s)
Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
It doesn't matter how much red and bold text you use, it doesn't make you correct.
In the previous version, without an entry in the RAR extract folder setting, it would indeed extract to the specified download folder (see screenshot from v7 final). This is the correct behaviour IMO, the most logical, and as far as i can remember, how it's always worked. Why would I want to specify a different download location, only to have the files moved back to the default extract location? ..and even if I did, i should have to specify that location.
I'm all for new features, but there needs to be a way to select the old behaviour.

In the previous version, without an entry in the RAR extract folder setting, it would indeed extract to the specified download folder (see screenshot from v7 final). This is the correct behaviour IMO, the most logical, and as far as i can remember, how it's always worked. Why would I want to specify a different download location, only to have the files moved back to the default extract location? ..and even if I did, i should have to specify that location.
I'm all for new features, but there needs to be a way to select the old behaviour.

Re: v8b4 UFR1 - Incorrect Folder Unpack - Fixed in UFR 2
I too have the problem TheSiege describes here. When I use Leech Specify (CTRL+Y) and specify a sub folder it will create the sub folder and place the archives within the specified sub folder. However, when it extracts it moves the extracted files to the default Download Folder. Whereas in previous versions it would both download and extract to the folder you specified in the Leech Specify dialog.
Are you saying that this was never the intended functionality and we now have to make a feature request to get it back?
Are you saying that this was never the intended functionality and we now have to make a feature request to get it back?