Autopar and split files

[dane]

Hi - I'm using 64 bit Newsbin - 6.80RC3 - Build 5035 on a windows 10 machine. The command 'automatically unrar complete files' on the autopar options menu works fine for rar files - if I uncheck this option, it downloads all the rar files but does not unrar them. If I download the parts of a file which has been split - e.g. file.01
file.02
file.03
etc.
the files are combined and decoded and the original file is created whether this option is checked or not checked. Is there any way to keep these files from decoding the split file. If I can enter them into winrar manually, I can be sure there are no dangerous files in the set.

Thanks,
DaDane

[Quade]

the files are combined and decoded and the original file is created whether this option is checked or not checked. Is there any way to keep these files from decoding the split file. If I can enter them into winrar manually, I can be sure there are no dangerous files in the set.

They're not being unrared, they're being repaired into a single file. You'd have to disable autopar if you don't want Newsbin to combine them back into a single file. Typically these aren't rar files but naked files like MKV's so there's no danger in letting them get repaired into a single file.

As for your manual unraring, you know it doesn't matter if you unrar a virus or trojan as long as you don't run it.

[jakew]

Related to autopar and split files: Newsbin 6.82 keeps "jumping the gun" on me by processing only the first .001 split file. Essentially it just strips off the .001 extension from the first file, and downloads the remaining split files but does nothing with them. For example, if I download the example files below, the result will be an example_movie_hd.mp4 that's just the first chunk, then the .002, .003, .004, etc. files. In order to combine the rest, I have to manually rename the mp4 back to .001, then select Quick UnRAR from the context menu.

Note that the open bracket in my example below is intentionally missing from each post, because that's how the real post looked. Could that have anything to do with it? The files appear this way in the posts list--they aren't being combined. Also, there is no .000 file for these posts (and no pars obviously).

Example Movie 01of12] - "example_movie_hd.mp4.001" yEnc 52428800 bytes
Example Movie 02of12] - "example_movie_hd.mp4.002" yEnc 52428800 bytes
Example Movie 03of12] - "example_movie_hd.mp4.003" yEnc 52428800 bytes
Example Movie 04of12] - "example_movie_hd.mp4.004" yEnc 52428800 bytes
Example Movie 05of12] - "example_movie_hd.mp4.005" yEnc 52428800 bytes
Example Movie 06of12] - "example_movie_hd.mp4.006" yEnc 52428800 bytes
Example Movie 07of12] - "example_movie_hd.mp4.007" yEnc 52428800 bytes
Example Movie 08of12] - "example_movie_hd.mp4.008" yEnc 52428800 bytes
Example Movie 09of12] - "example_movie_hd.mp4.009" yEnc 52428800 bytes
Example Movie 10of12] - "example_movie_hd.mp4.010" yEnc 52428800 bytes
Example Movie 11of12] - "example_movie_hd.mp4.011" yEnc 52428800 bytes
Example Movie 12of12] - "example_movie_hd.mp4.012" yEnc 40755814 bytes

[Quade]

How are you feeding them to the download list? If it's an NZB you need to drag and drop the NZB directly into the download list so, all the files appear in a single line. If they appear one file per line and there are no pars, there's no way for Newsbin to really know when they're done.

Pretty much all NZB's need to be sent directly to the download list and not to the post list first. I'm guessing you don't have PAR files so, there's no way for Newsbin to really verify these files.

You might find for these ungrouping oddballs that making an NZB from them first then feeding the download list directly with the NZB is the best way to handle them. They won't group normally because as you can see the file counters are messed up.

[jakew]

Thanks. So if I understand you correctly, under normal circumstances (where the poster included the correct amount of brackets), NB will combine the split files into one line and then the autopar will work.

So for malformed files like these, the next best thing would be for NB not to try to process them at all. Hence maybe a good improvement is that NB doesn't attempt to combine split files if it sees only one .001 chunk (or have an option to exclude them).