PAR2 Creation using ExQueues

[S. Jamison Wilde]

If you need to create a bunch of Par2 volumes, you can add the following to your config.xml file (found in c:\Documents and Settings\%username%\Application Data\ExQueues\).

Insert right before the </Tasks> .

        <Task number="6">
                <Name value="Create PAR2 volumes"/>
                <Extensions value="*"/>
                <MenuText value="Create PAR2"/>
                <MenuShow value="true"/>
                <SeparateFiles value="false"/>
                <DeleteSources value="false"/>
                <CommandLine value="par2.exe c -m128 %1"/>
                <DisplayInfo>
                    <DisplayText value="Create PAR2"/>
                    <ShowDelete value="false"/>
                    <ShowFiles value="true"/>
                    <ShowDestination value="false"/>
                </Displayinfo>
                <ShowAttributes>   
Name, false,
Extensions, true,
MenuText, true,
MenuShow, true,
CommandLine, true,
SuccessCode, true,
DeleteSources, false,
UseRecycleBin, true,
ThreadPriority, true
                </ShowAttributes>
                <SuccessCode>0</SuccessCode>
                <ErrorMessages>
                    <ErrorMessage code="0">
Successfully Completed.
                    </ErrorMessage>
                    <ErrorMessage code="1">
Data files are damaged and there is enough recovery data available to repair them.
                    </ErrorMessage>
                    <ErrorMessage code="2">
Data files are damaged and there is insufficient recovery data available to be able to repair them.
                    </ErrorMessage>
                    <ErrorMessage code="3">
There was something wrong with the command line arguments
                    </ErrorMessage>
                    <ErrorMessage code="4">
The PAR2 files did not contain sufficient information about the data files to be able to verify them.
                    </ErrorMessage>
                    <ErrorMessage code="5">
Repair completed but the data files still appear to be damaged.
                    </ErrorMessage>
                    <ErrorMessage code="6">
An error occured when accessing files
                    </ErrorMessage>
                    <ErrorMessage code="7">
In internal error occurred in the commandline application.
                    </ErrorMessage>
                    <ErrorMessage code="8">
Out of memory
                    </ErrorMessage>
                 </ErrorMessages>
        </Task>

[S. Jamison Wilde]

You can change the par2.exe commandline settings as needed to choose the number of volumes, block size, etc. you wish to use as default.

[S. Jamison Wilde]

PLEASE NOTE: I found a bug while testing this.... use the following instead, requiring a new version.  I also had to deal with how par2 expects par2 c "output" "file1" "file2" by changing the commandline:

<Task number="6">
<Name value="Create PAR2 volumes"/>
<Extensions value="*"/>
<MenuText value="Create PAR2"/>
<MenuShow value="true"/>
<SeparateFiles value="false"/>
<DeleteSources value="false"/>
<CommandLine value="par2.exe c -m128 %1 %*"/>
<DisplayInfo>
<DisplayText value="Create PAR2"/>
<ShowDelete value="false"/>
<ShowFiles value="true"/>
<ShowDestination value="false"/>
</Displayinfo>
<ShowAttributes> 
Name, false,
Extensions, true,
MenuText, true,
MenuShow, true,
CommandLine, true,
SuccessCode, true,
DeleteSources, false,
UseRecycleBin, true,
ThreadPriority, true
</ShowAttributes>
<SuccessCode>0</SuccessCode>
<ErrorMessages>
<ErrorMessage code="0">
Successfully Completed.
</ErrorMessage>
<ErrorMessage code="1">
Data files are damaged and there is enough recovery data available to repair them.
</ErrorMessage>
<ErrorMessage code="2">
Data files are damaged and there is insufficient recovery data available to be able to repair them.
</ErrorMessage>
<ErrorMessage code="3">
There was something wrong with the command line arguments
</ErrorMessage>
<ErrorMessage code="4">
The PAR2 files did not contain sufficient information about the data files to be able to verify them.
</ErrorMessage>
<ErrorMessage code="5">
Repair completed but the data files still appear to be damaged.
</ErrorMessage>
<ErrorMessage code="6">
An error occured when accessing files
</ErrorMessage>
<ErrorMessage code="7">
In internal error occurred in the commandline application.
</ErrorMessage>
<ErrorMessage code="8">
Out of memory
</ErrorMessage>
</ErrorMessages>
</Task>