Damn attachment nonsense.
On Sun, 27 Aug 2017 17:52:51 -0600, harryh89@yahoo.comx wrote:
>In my posts elsewhere I have been using multipar rather than quickpar
>for posting. I had observed some posters using the multipar tool and
>wanted to understand how it helped. I discovered it helped a lot
>because it automates a lot of the effort in creating the pars and
>splits and is way faster than using the GUI. I created two batch
>files run in a command window to help automate the process and the
>attached text file presents what I use. I place files to receive pars
>only in a directory, open a CMD window for that directory and run aThose who post often use split files and QuickPar for verification and splitting. Using a command line tool and multipar par2j has helped speed that process quite a lot. You can get multipar from http://hp.vector.co.jp/authors/VA021385/ beware of imitations - or check Google. The vector site is from the tool creator Yutaka Sawada and you can use Paypal if you like the software.
The basic tool simply creates par2 files in the directory selected:
Open a CMD window, navigate to the folder needing pars, run the
following batch file:
********************* CreatePar.bat **************
set par2_path="D:\Tools\MultiPar\par2j.exe"
FOR /F "tokens=*" %%J in ('dir /a-d /b' ) DO (%par2_path% c -sm384000
-rr20 -rd1 "%%J.par2" "%%J")
*******************
Where my path to multipar is selected via the set command, that will
depend on where you placed the folder MultiPar. The dir command just
provides a list of filenames to process. The DO command processes
that list one by one. When finished there will be the created par2
files.
My parameters for posting - "sm" = slice size 384000 to match settings
in Powerpost for segment size, "rr" = 20 the percentage % redundancy
(recovery records), "rd" = 1 selectes a 1:1 recovery record thus
allowing record sizes to vary.
Another usage is to split after creating the par files, navigate the
CMD window to the directory where the files to get pars and splits:
*********************** CreateS.bat *********
set par2_path="D:\Tools\MultiPar\par2j.exe"
FOR /F "tokens=*" %%J in ('dir /a-d /b' ) DO (%par2_path% c -sm384000
-rr21 -rd1 -ls99840000 "%%J.par2" "%%J")
***********************
Because of the larger file sets, the redundancy record ("rr") was
adjusted to 21%. The additional parameter sets "ls" - size of splits,
in this case 100M per file (the size of .001, 002, etc). Years ago we
might have used a lower number but Usenet has been quite reliable now
with much larger files so the past 10M, 25M or 50M split sizes seem
obsolete, in my experience. If you have an unreliable uplink or a lot
of users on dial-up a smaller split size might be appropriate. The
larger splits reduce header pollution, IMHO.
Multipar reference:
Parameters for Multipar via command Par2j /? -----------
Usage
t(rial) [options] <par file> [input files]
c(reate) [options] <par file> [input files]
available: f,fu,fo,fa,fe,ss,sn,sr,sm,rr,rn,rs,rd,rf,ri,
lr,lp,ls,lc,m,vs,vd,c,d,in,up,uo
v(erify) [ m,vl,vs,vd,d,uo ] <par file> [external files]
r(epair) [lc,m,vl,vs,vd,d,uo,b,br,bi] <par file> [external files]
l(ist) [uo,h] <par file>
Option
/f : Use file-list instead of filename
/fu : Use file-list which is encoded with UTF-8
/fo : Search file only for wildcard
/fa"*": Adding file at search with wildcard
/fe"*": Excluding file at search with wildcard
/ss<n>: Slice size
/sn<n>: Number of source blocks
/sr<n>: Rate of source block count and size
/sm<n>: Slice size becomes a multiple of this value
/rn<n>: Number of recovery blocks
/rr<n>: Rate of redundancy (%)
/rs<n>: Starting recovery block number
/rd<n>: How to distribute recovery blocks to recovery files
/rf<n>: Number of recovery files
/ri : Use file index to name recovery files
/lr<n>: Limit number of recovery blocks in a recovery file
/lp<n>: Limit repetition of packets in a recovery file
/ls<n>: Limit size of splited files
/lc<n>: Limit CPU feature
/m<n> : Memory usage
/vl<n>: Verification level
/vs<n>: Skip verification by recent result
/vd"*": Set directory of recent result
/c"*" : Set comment
/d"*" : Set directory of input files
/in : Do not create index file
/up : Write Unicode Filename packet for non-ASCII filename
/uo : Console output is encoded with UTF-8
/b : Backup existing files at repair
/br : Send existing files into recycle bin at repair
/bi : Replace files even when repair was failed
/h : List hash value of input files
The set of parameters is large because different folk have differing
needs. I only used the parameters that relate to Usenet posting.
>batch file using a selected set of parameters. For splitting, I place
>those files in a different folder and run a slightly different batch
>files allowing Multipar to create pars and splits.
>
>We posters know that creating a post requires some effort. Finding
>files to post and preparing for posting by making pars and splits then
>actually posting. The batch files have made some of that easier for
>me. Wish I had discovered the tools sooner, but maybe I can help
>others in their posting effort,
--
Delete xx in address.
Mail to: harryh89@yahoo.comxx
|
|