Make ParPar the default par client instead of par2cmdline

[didamsko]

Been experimenting with nntpPoster on Windows OS for a while now and came to the conclusion that its not useful to use par2cmdline (https://github.com/Parchive/par2cmdline/) as parring client as suggested in the "Prerequisites" (https://github.com/boranblok/nntpPoster) and in the Windows installation instructions (https://github.com/boranblok/nntpPoster/wiki/Installation-on-Windows).

I like to strongly suggest making ParPar (https://github.com/animetosho/ParPar) the default par client, instead of only mentioning it as alternative.

If one uses nntpPoster for small, a couple 100 MB, files then par2cmdline is probably workable but when using it on bigger files the problems start, it took me hours to par a 25 GB release and I soon realized that I had to throttle my CPU (via Windows Power Options) to prevent it from getting damaged by overheating, all my system resources were claimed by the parring process and when I then started monitoring my CPU I saw it was running at temperatures over 90 degrees Celsius. Surely not advisable for hours on end.

I then tried ParPar (still on a throttled CPU) and saw it worked a lot quicker. Where a 27 GB parring job with par2cmdline took my system 4 hours a similar size job took 40 minutes with ParPar. Reason enough to make ParPar default I say.

I noticed your conf\99_nodejsParPar.ini that mentions:

#
# Copy this file to the userconf folder if you want to use nodejs parpar
# Alter the path to the .js file if required.
#
...
ParLocation=nodejs
...
ParCommandFormat="/opt/ParPar-master/bin/parpar.js -n -s{0}B -r{1}% -d pow2 {4} -o {2}{3}"
...

The new ParPar pre-packaged Windows builds (currently v0.3.1: https://github.com/animetosho/ParPar/releases v0.3.1 > Assets > parpar.v0.3.1.win32-sse2.7z (32bit) or parpar.v0.3.1.win64.7z (64bit)) come as standalone application, a "parpar.exe" plus a "vcomp140.dll" and can be run by placing the "parpar.exe" and "vcomp140.dll" in a location and linking to the parpar.exe in the nntpPoster userconfig.

I got ParPar v0.3.1 working by editing/adding following lines to the userconf\10-MyConfiguration.ini:

ParLocation="path-to-parpar.exe"\parpar.exe (editing this line)

ParCommandFormat="-n -s{0}B -r{1}% -d pow2 {4} -o {2}{3}" (adding this line)

So I recommend switching to ParPar, it uses less system resources (good for computer lifespan) and is a lot faster. I can not think of anything why to stick with par2cmdline.

[didamsko]

PS. after further experiments I found that instead of:

ParCommandFormat="-n -s{0}B -r{1}% -d pow2 {4} -o {2}{3}"

It is better to not use the standard ParPar naming scheme for recovery files and to remove the "-n" from the ParCommandFormat and use this instead:

ParCommandFormat="-s{0}B -r{1}% -d pow2 {4} -o {2}{3}"

Then ParPar will use the par2cmdline naming scheme. Benefit of doing this is that some indexers (at the time of writing this) do not seem to recognize and include par sets generated with the standard ParPar naming scheme:

filename.vol00-01.par2
filename.vol01-02.par2
etc...

But they do recognize and include par sets generated with the par2cmdline naming scheme:

filename.vol00+01.par2
filename.vol01+02.par2
etc...