Add files via upload

This commit is contained in:
Yutaka Sawada
2023-03-20 14:01:38 +09:00
committed by GitHub
parent 443a69f76a
commit 344479f0b1
26 changed files with 3582 additions and 0 deletions

865
alpha/help/0409/batch.htm Normal file
View File

@@ -0,0 +1,865 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css">
<!--
textarea{width:100%;}
-->
</style>
<title>Batch script</title>
</head>
<body>
<font size=5>Sample of batch script</font>
<hr>
<p>&nbsp
Because MultiPar consists of PAR clients and GUI,
it is possible to use a PAR client on Command prompt.
Read a manual of command line for the details of command and option.
It's available by batch file (or command script).
</p>
<p>&nbsp
Below are some samples of batch file for Windows 7.
Copy & paste the whole lines into a text file.
Modify the options for PAR2 files, and set the path of <tt>par2j.exe</tt>.
Write absolute path like;<br>
<code>SET par2_path="C:\something directory\MultiPar\par2j.exe"</code><br>
Read manuals (<tt>Command_***.txt</tt>) to know the detail of options.
Read Windows OS 's help for Command prompt's usage.
</p>
<p>&nbsp
Save a sample script to a file like <tt>batch.bat</tt> or <tt>batch.cmd</tt>.
To specify path of files or folders, Drag & Drop them on the batch file.
When you put a shortcut icon of the batch file in "SendTo" menu,
you can call the batch file by selecting files then Righ-Click & SendTo.
</p>
<p>&nbsp
If you want to confirm the result of scripting,
add "<code>PAUSE</code>" at the end of batch file.
If you want to see how each command line is parsed,
remove "<code>@ECHO OFF</code>" at the top of batch file,
or add "<code>ECHO</code>" in front of the questionable line.
These may help you understanding how batch script works.
</p>
<p>&nbsp
If you want to switch flow by the result, you may use a special environment variable "<code>ERRORLEVEL</code>".
"<code>if ERRORLEVEL number task~</code>" means that the task will start when ERRORLEVEL is greater than or equal to the number.
"<code>if not ERRORLEVEL number task~</code>" means that the task will start when ERRORLEVEL is less than the number.
It's possible to refer the value by using "<code>%ERRORLEVEL%</code>".
The code is such like "<code>set err = %ERRORLEVEL%</code>".
When you want to refer ERRORLEVEL in "for ~ do ~" loop,
you must set a local variable as "<code>setlocal enabledelayedexpansion</code>" and use "<code>!ERRORLEVEL!</code>".
</p>
<hr>
<h3>Index</h3>
<table width="100%">
<tr><td><a href="#C1">Create individual PAR2 set in each selected folder (with GUI)</a><td>
<tr><td><a href="#C2">Create individual PAR2 set in each subfolder under a selected folder (with GUI)</a><td>
<tr><td><a href="#C3">Create one PAR2 file per each file in a selected folder</a><td>
<tr><td><a href="#C4">Create individual PAR2 set per each set of 4 files from many selected files</a><td>
<tr><td><a href="#C5">Create PAR2 recovery data and append it to each original ZIP / 7-Zip archive file</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#V1">Verify and/or Repair individual PAR2 set in each selected folder with GUI</a><td>
<tr><td><a href="#V2">Create, Verify or Repair individual PAR2 set in each subfolder under a selected folder with GUI</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#A1">Add MD5 checksum to each file independently in a selected folder (NTFS only)</a><td>
<tr><td><a href="#A2">Verify each file independently by MD5 checksum in a selected folder (NTFS only)</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#N1">Play sound for notification</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#B1">Batch processing after MultiPar GUI 's Creation</a><td>
<tr><td><a href="#B2">Batch processing after MultiPar GUI 's Verification / Repair</a><td>
</table>
<hr>
<a name="C1"></a>
<h3>Create individual PAR2 set in each selected folder (with GUI)</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of folder1" "path of folder2" "path of folder3"...
<tr><td>Input<td>specify some folders
<tr><td>Action<td>This sample creates individual PAR2 set in each selected folder.
For example, when you supply 7 folders, total 7 PAR2 set are made.
It is possible to show GUI for setting, too.
</table>
</p>
<textarea cols=64 rows=23 readonly wrap=off>
@ECHO OFF
SETLOCAL
SET par2_path="path of par2j.exe"
:GetFilePath
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" GOTO NextFile
REM run PAR2 client
ECHO create for %1
%par2_path% c /sm2048 /rr20 /rd1 /rf3 "%~1\%~n1.par2" *
IF ERRORLEVEL 1 GOTO End
:NextFile
SHIFT
GOTO GetFilePath
:End
ENDLOCAL</textarea>
<p>&nbsp
If you want to use MultiPar GUI for setting, you may call <tt>MultiPar.exe</tt> instead of <tt>par2j.exe</tt>.
When a GUI is closed, next GUI is opened with next folder.
You may set an option in "Automated tasks" to close GUI automatically after creation.
</p>
<textarea cols=64 rows=21 readonly wrap=off>
@ECHO OFF
SETLOCAL
SET multipar_path="path of MultiPar.exe"
:GetFilePath
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" GOTO NextFile
REM open MultiPar GUI
ECHO create for %1
%multipar_path% /create %1
:NextFile
SHIFT
GOTO GetFilePath
:End
ENDLOCAL</textarea>
<p>&nbsp
If you don't want to wait the finish of each creation,
you may use "<code>START</code>" command in the script.
Because all MultiPar GUIs will open at once for each folder,
you can start each creation anytime.
</p>
<textarea cols=64 rows=21 readonly wrap=off>
@ECHO OFF
SETLOCAL
SET multipar_path="path of MultiPar.exe"
:GetFilePath
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" GOTO NextFile
REM open MultiPar GUI
ECHO create for %1
START "" %multipar_path% /create %1
:NextFile
SHIFT
GOTO GetFilePath
:End
ENDLOCAL</textarea>
<hr>
<a name="C2"></a>
<h3>Create individual PAR2 set in each subfolder under a selected folder (with GUI)</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of a folder"
<tr><td>Input<td>specify a folder
<tr><td>Action<td>This sample creates individual PAR2 set in each subfolder under the selected folder.
For example, when there are 7 subfolders, total 7 PAR2 set are made.
</table>
</p>
<textarea cols=64 rows=33 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" (
ECHO The path does not exist.
GOTO End
)
REM set options for PAR2 client
SET par2_path="path of par2j.exe"
REM recursive search of subfolders
PUSHD %1
FOR /D /R %%G IN (*.*) DO CALL :ProcEach "%%G"
POPD
GOTO End
REM run PAR2 client
:ProcEach
ECHO create for %1
%par2_path% c /fo /sm2048 /rr20 /rd1 /rf3 "%~1\%~n1.par2" *
GOTO :EOF
:End
ENDLOCAL</textarea>
<p>&nbsp
Don't remove an option <code>/fo</code> in the command-line.
By this option, PAR2 file contains files only in each subfolder.
</p>
<p>&nbsp
If you want to use MultiPar GUI for setting, you may call <tt>MultiPar.exe</tt> instead of <tt>par2j.exe</tt>.
When a GUI is closed, next GUI is opened with next folder.
You may set an option in "Automated tasks" to close GUI automatically after creation.
You may check "Always use folder name for base filename" option in "Client behavior",
then each PAR2 set is named by the folder.
</p>
<textarea cols=64 rows=33 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" (
ECHO The path does not exist.
GOTO End
)
SET multipar_path="path of MultiPar.exe"
REM recursive search of subfolders
PUSHD %1
ECHO "%1"
FOR /D /R %%G IN (*.*) DO CALL :ProcEach "%%G"
POPD
GOTO End
REM open MultiPar GUI
:ProcEach
ECHO create for %1
%multipar_path% /create %1
GOTO :EOF
:End
ENDLOCAL</textarea>
<hr>
<a name="C3"></a>
<h3>Create one PAR2 file per each file in a selected folder</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of a folder"
<tr><td>Input<td>specify a folder
<tr><td>Action<td>This sample creates one PAR2 file per each file in the selected folder.
If there is a subfolder in a folder, files in the subfolder are searched, too.
Instead of creating PAR2 files for all files in a subfolder like previous sample,
this creates one PAR2 file per each file in a subfolder.
For example, when there are 7 files in the folder, total 7 PAR2 files are made.
</table>
</p>
<textarea cols=64 rows=33 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" (
ECHO The path does not exist.
GOTO End
)
REM set options for PAR2 client
SET par2_path="path of par2j.exe"
REM recursive search of files
PUSHD %1
FOR /R %%G IN (*.*) DO CALL :ProcEach "%%G"
POPD
GOTO End
REM run PAR2 client
:ProcEach
ECHO create for %1
%par2_path% c /fo /sm2048 /rr10 /ri /in /lr32767 "%~1.par2" %1
GOTO :EOF
:End
ENDLOCAL</textarea>
<p>&nbsp
Don't remove an option <code>/in</code> in the command-line.
By this option, index file isn't created.
</p>
<hr>
<a name="C4"></a>
<h3>Create individual PAR2 set per each set of 4 files from many selected files</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of file1" "path of file2" "path of file3" "path of file4" "path of file5"...
<tr><td>Input<td>specify many files
<tr><td>Action<td>This sample creates individual PAR2 set per each set of 4 files from many selected files.
For example, when you supply 11 files, total 3 PAR2 set are made. (11 = 4 + 4 + 3)
</table>
</p>
<textarea cols=64 rows=27 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM set options for PAR2 client
SET par2_path="path of par2j.exe"
SET /a N=1
:GetFilePath
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" GOTO End
REM run PAR2 client
ECHO create for "%~d1%~p1par_set%N%"
%par2_path% c /sm2048 /rr20 /rd1 /rf3 "%~d1%~p1par_set%N%.par2" %1 %2 %3 %4
SET /a N=N+1
SHIFT
SHIFT
SHIFT
SHIFT
GOTO GetFilePath
:End
ENDLOCAL</textarea>
<p>&nbsp
You may modify this sample to accept more files up 9.
Be careful about the number of source files and "<code>SHIFT</code>" per each step.
</p>
<hr>
<a name="C5"></a>
<h3>Create PAR2 recovery data and append it to each original ZIP / 7-Zip archive file</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of archive file1" "path of archive file2" "path of archive file3"...
<tr><td>Input<td>specify some ZIP / 7-Zip archive files
<tr><td>Action<td>This sample creates PAR2 recovery data and append it to each original ZIP / 7-Zip archive file.
Though ZIP / 7-Zip archive don't have a feature of recovery record,
parchive can add the extra feature.
For example, when you supply 7 archive files, total 7 archive files with recovery record are made.
</table>
</p>
<textarea cols=64 rows=36 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM set options for PAR2 client
SET par2_path="path of par2j.exe"
:GetFilePath
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" GOTO End
REM check format
IF /i "%~x1" NEQ ".zip" (
IF /i "%~x1" NEQ ".7z" (
GOTO NextFile
)
)
REM ignore already appended file
%par2_path% l %1
IF NOT ERRORLEVEL 1 GOTO NextFile
REM run PAR2 client
ECHO append to %1
%par2_path% c /fo /sm2048 /rr10 /ri /in /lr32767 /lp4 "%~1.par2" %1
REM join 2 files
COPY /b "%~1"+"%~1.vol_1.par2" /v "%~1"
DEL "%~1.vol_1.par2"
:NextFile
SHIFT
GOTO GetFilePath
:End
ENDLOCAL</textarea>
<p>&nbsp
Don't remove options <code>/ri</code> and <code>/in</code> in the command-line.
By this option, index file isn't created and filename has fixed volume number.
When joinning original archive and recovery data,
it is important to put original archive at first, then append recovery data at the last.
From the nature of ZIP / 7-Zip archive,
appended PAR2 recovery data has no effect to extract or decompress.
If you want to keep PAR2 file separately, comment out the line of "<code>DEL</code>" command.
</p>
<p>&nbsp
To verify the archive, just Drag&Drop it onto MultiPar short-cut icon.
(or right-click SendTo or ShellExtension works, too.)
On the MultiPar GUI,
the archive with PAR2 recovery data is shown as "Appended" status,
when the original part of archive is complete.
If you repair the archive, the archive returns to the original form.
(appended PAR2 recovery data is removed.)
When you want to keep the PAR2 recovery data,
you need to un-check an option "Delete damaged files after Repair".
Then the recovery data is renamed by adding "<tt>.1</tt>" after filename.
</p>
<hr>
<a name="V1"></a>
<h3>Verify and/or Repair individual PAR2 set in each selected folder with GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of folder1" "path of folder2" "path of folder3"...
<tr><td>Input<td>specify some folders
<tr><td>Action<td>This sample calls MultiPar GUI for individual PAR2 set in each selected folder.
For example, when you supply 7 folders, GUI are opened 7 times one by one.
It is possible to repair by the GUI.
When a GUI is closed, next GUI is opened with next PAR2 set.
</table>
</p>
<textarea cols=64 rows=21 readonly wrap=off>
@ECHO OFF
SETLOCAL
SET multipar_path="path of MultiPar.exe"
:GetFilePath
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" GOTO NextFile
REM open MultiPar GUI
ECHO verify for %1
%multipar_path% /verify "%~1\%~n1.par2"
:NextFile
SHIFT
GOTO GetFilePath
:End
ENDLOCAL</textarea>
<p>&nbsp
The key is setting the PAR filename to be based on the folder name.
If you set prefix/suffix to filename at creating time, you need to set same one at verifying time.
</p>
<hr>
<a name="V2"></a>
<h3>Create, Verify or Repair individual PAR2 set in each subfolder under a selected folder with GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of a folder"
<tr><td>Input<td>specify a folder
<tr><td>Action<td>This sample calls MultiPar GUI for individual PAR2 set in each subfolder under the selected folder.
When PAR2 files don't exist, it creates PAR2 set for the subfolder.
When PAR2 files exist, it verifys files in the subfolder.
For example, when there are 7 subfolders, total 7 PAR2 set are made.
Next time you specify the folder, MultiPar verifies the 7 subfolders one by one.
</table>
</p>
<textarea cols=64 rows=38 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" (
ECHO The path does not exist.
GOTO End
)
SET multipar_path="path of MultiPar.exe"
REM recursive search of subfolders
PUSHD %1
ECHO "%1"
FOR /D /R %%G IN (*.*) DO CALL :ProcEach "%%G"
POPD
GOTO End
REM open MultiPar GUI
:ProcEach
IF EXIST "%~1\%~n1.par2" (
ECHO verify for %1
%multipar_path% /verify "%~1\%~n1.par2"
) else (
ECHO create for %1
%multipar_path% /create %1
)
GOTO :EOF
:End
ENDLOCAL</textarea>
<p>&nbsp
The key is setting the PAR filename to be based on the folder name.
You must check "Always use folder name for base filename" option in "Client behavior", then each PAR2 set is named by the folder.
</p>
<p>&nbsp
When a GUI is closed, next GUI is opened with next folder.
You may set an option in "Automated tasks" to close GUI automatically after creation.
If you want to skip complete files at verification, you may set option to close GUI automatically after verification, too.
</p>
<hr>
<a name="A1"></a>
<h3>Add MD5 checksum to each file independently in a selected folder (NTFS only)</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of a folder"
<tr><td>Input<td>specify a folder
<tr><td>Action<td>This sample adds MD5 checksum to each file independently in a selected folder.
If there is a subfolder in a folder, files in the subfolder are searched, too.
This uses "Alternate Data Stream" and works over NTFS only.
Checksum data is saved in an alternate stream "<tt>original filename:digest.md5</tt>",
but it's invisible by Windows Explorer.
</table>
</p>
<textarea cols=64 rows=38 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" (
ECHO The path does not exist.
GOTO End
)
REM set options for SFV/MD5 client
SET client_path="path of sfv_md5.exe"
REM recursive search of files
PUSHD %1
FOR /R %%G IN (*.*) DO CALL :ProcEach "%%G"
POPD
ECHO Finished to add checksums into alternate stream.
PAUSE
GOTO End
REM run SFV/MD5 client
:ProcEach
ECHO create for %1
%client_path% c "%~1:digest.md5" %1
IF ERRORLEVEL 1 (
ECHO Stop at this point.
PAUSE
EXIT
)
GOTO :EOF
:End
ENDLOCAL</textarea>
<p>&nbsp
There are some cautions.
Some binary/text editor seems to remove alternate data stream automatically at over-writing.
If you modify a file, you will need to re-add checksum to the new file again.
Adding checksum will update files' modification time, even though original file data isn't changed.
A user needs to use a special tool to see/delete/copy the stream, because those streams are untouchable by Windows Explorer.
While an alternate stream is kept at copy/move between NTFS drives, it will be removed on other file system.
For example, you cannot backup data in alternate stream on CD/DVD.
</p>
<hr>
<a name="A2"></a>
<h3>Verify each file independently by MD5 checksum in a selected folder (NTFS only)</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of batch file" "path of a folder"
<tr><td>Input<td>specify a folder
<tr><td>Action<td>This sample verify each file independently by MD5 checksum in a selected folder.
If there is a subfolder in a folder, files in the subfolder are searched, too.
This uses "Alternate Data Stream" and works over NTFS only.
Checksum data must have been saved in an alternate stream "<tt>original filename:digest.md5</tt>".
</table>
</p>
<textarea cols=64 rows=43 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM check input path
IF "%~1"=="" GOTO End
IF NOT EXIST "%~1" (
ECHO The path does not exist.
GOTO End
)
REM set options for SFV/MD5 client
SET client_path="path of sfv_md5.exe"
REM recursive search of files
PUSHD %1
FOR /R %%G IN (*.*) DO CALL :ProcEach "%%G"
POPD
ECHO Finished to verify files by checksums in alternate stream.
PAUSE
GOTO End
REM run SFV/MD5 client
:ProcEach
ECHO verify for %1
%client_path% v "%~1:digest.md5"
IF ERRORLEVEL 4 (
ECHO This file is broken.
PAUSE
GOTO :EOF
)
IF ERRORLEVEL 1 (
ECHO Stop at this point.
PAUSE
EXIT
)
GOTO :EOF
:End
ENDLOCAL</textarea>
<hr>
<a name="N1"></a>
<h3>Play sound for notification</h3>
<p>&nbsp
This sample plays sound by Media Player.
This is good to notify the end of process to user, while running script.
This can play any file format which is supported by Media Player.
</p>
<textarea cols=64 rows=13 readonly wrap=off>
@ECHO OFF
SETLOCAL
REM set path of sound file
SET SNDPATH=%systemroot%\Media\ringout.wav
REM set playing time by mil seconds
SET HTA_MAX_TIME=5000
REM call HTA application (JavaScript and Media Player plag-in)
mshta.exe "about:playing... &lt;OBJECT CLASSID='CLSID:22D6F312-B0F6-11D0-94AB-0080C74C7E95' WIDTH=100 HEIGHT=100&gt;&lt;param name='src' value='%SNDPATH%'&gt;&lt;param name='PlayCount' value='1'&gt;&lt;param name='autostart' value='true'&gt;&lt;/OBJECT>&lt;script&gt;window.resizeTo(10,10);setTimeout(function(){window.close()},%HTA_MAX_TIME%);&lt;/script&gt;"
ENDLOCAL</textarea>
<hr>
<a name="B1"></a>
<h3>Batch processing after MultiPar GUI 's Creation</h3>
<p>&nbsp
MultiPar GUI can start script after creation.
The script file must be <tt>auto_c.cmd</tt> in the user's <tt>save</tt> folder.
A user may write any script in this file.
The script gets two parameters from GUI as below;<br>
<code>
%1 = Path of a recovery file<br>
%2 = Path of base directory of source files
</code>
</p>
<p>&nbsp
This sample script moves created PAR2 recovery files into another folder.
</p>
<textarea cols=64 rows=35 readonly wrap=off>
@ECHO OFF
TITLE After creation
SETLOCAL
REM List up parameters
ECHO Path of this batch file =
ECHO %0
ECHO.
ECHO Path of a recovery file =
ECHO %1
ECHO.
ECHO Path of base directory of source files =
ECHO %2
ECHO.
REM check the extension for .par2
IF /i "%~x1" NEQ ".par2" (
ECHO The recovery file format isn't PAR2.
GOTO End
)
REM insert * between filename and extension
SET search_path="%~d1%~p1%~n1*%~x1"
REM move all created recovery files into another folder
SET destination_folder="C:/Sample/"
ECHO Moving %search_path%
move %search_path% %destination_folder%
ECHO Above files were gone to %destination_folder%
:End
ENDLOCAL</textarea>
<hr>
<a name="B2"></a>
<h3>Batch processing after MultiPar GUI 's Verification / Repair</h3>
<p>&nbsp
MultiPar GUI can start script after verification or repair.
The script file must be <tt>auto_v.cmd</tt> in the user's <tt>save</tt> folder.
A user may write any script in this file.
The script gets three parameters from GUI as below;<br>
<code>
%1 = Path of a recovery file<br>
%2 = Path of base directory of source files<br>
%3 = Exit code of the used client (refer the command-line manual)
</code>
</p>
<p>&nbsp
This sample script opens ZIP or 7-Zip archive only when it is complete.
To use this script, you need to create some recovery files for an archive at first.
At that time, the key is setting the base filename to be same as the source file like;<br>
source file's name = <tt>something.zip</tt><br>
recovery files' name = <tt>something.zip.par2, something.zip.vol0+4.par2, something.zip.vol4+8.par2</tt><br>
Thus, when you open the index file "<tt>something.zip.par2</tt>",
the filename without last extension becomes the name of source file.
</p>
<textarea cols=64 rows=55 readonly wrap=off>
@ECHO OFF
TITLE After verification
SETLOCAL
REM List up parameters
ECHO Path of this batch file =
ECHO %0
ECHO.
ECHO Path of a recovery file =
ECHO %1
ECHO.
ECHO Path of base directory of source files =
ECHO %2
ECHO.
ECHO Status of source files = %3
ECHO.
REM check the source file is complete
IF NOT %3==0 (
IF NOT %3==16 (
ECHO The file is broken.
GOTO End
)
)
REM remove last extension from path
SET new_path="%~d1%~p1%~n1"
ECHO Target file = %new_path%
IF EXIST %new_path% (CALL :OpenFile %new_path%) ELSE ECHO The file does not exist.
GOTO End
:OpenFile
REM check the format and open the supported file
IF /i "%~x1" EQU ".zip" (
ECHO Open the ZIP archive
%1
GOTO :EOF
)
IF /i "%~x1" EQU ".7z" (
ECHO Open the 7-Zip archive
%1
GOTO :EOF
)
ECHO The file format isn't supported.
GOTO :EOF
:End
ENDLOCAL</textarea>
<p>&nbsp
This sample script moves log file (<tt>MultiPar.ini</tt>) to PAR2 file's directory.
If there is an old log file already, it appends new log after existing one.
To use this script, you need to enable log.
MultiPar Options -> [Client behavior] -> Check "Log output of clients".
</p>
<textarea cols=64 rows=26 readonly wrap=off>
@ECHO OFF
TITLE Move log file
SETLOCAL
SET old_path="%~d0%~p0MultiPar.log"
SET new_path="%~1.log"
ECHO Path of original log file =
ECHO %old_path%
ECHO Path of moved log file =
ECHO %new_path%
ECHO.
ECHO Copying %old_path% to %new_path%.
COPY /B %new_path% + %old_path% %new_path%
IF %ERRORLEVEL% == 0 (
REM If copy ok, delete original log file.
DEL %old_path%
) ELSE (
REM If copy fail, move log file.
ECHO Moving %old_path% to %new_path%.
MOVE %old_path% %new_path%
)
ENDLOCAL</textarea>
</body>
</html>

238
alpha/help/0409/create.htm Normal file
View File

@@ -0,0 +1,238 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Create window</title>
</head>
<body>
<font size=5>Create window</font><br><font size=1><br></font>&nbsp
When you start MultiPar without selecting a recovery file, this window opens.
On the window, you select source files and specify how to create new recovery files.
<hr>
<h3>Source files</h3>
<dl><dt><b>
Base directory</b> and <b>Browse</b> button
</dt><dd>&nbsp
This directory is the folder where source files exist.
You may change this by clicking "Browse" button, Drag & Drop a folder, or double-click the path box.
When you select a new folder, all files in the folder will be selected.
</dd></dl>
<dl><dt><b>
Add Files</b>, <b>Remove Files</b>, or <b>Reset List</b> buttons
</dt><dd>&nbsp
You may add or remove source files by clicking those buttons.
By right-clicking the file-list, popup menu will appear.
To add files, "Drag & Drop" or "Copy & Paste" works, too.
Every files must exist under the base directory.
Though you can select files only in the parent folder for PAR 1.0,
you can select files in the parent folder and sub-folders for PAR 2.0.
</dd></dl>
<p>&nbsp
Selected files are listed on the file-list, and the total data size and blocks are calculated.
PAR 1.0 supports upto 256 files, and PAR 2.0 supports upto 32768 files.
It is recomended to use archiver (ZIP, RAR, TAR or something) for many files.
In PAR 2.0, parent folders are treated as sub-directory in filenames.
Only empty folders (without files in them) are shown as folder in the file-list.
</p>
<dl><dt><b>
Split Files</b> and <b>Limit Size to
</b></dt><dd>&nbsp
In PAR 2.0, you can split source files by checking this option.
The split size will be a multiple of block size, which is the highest size under than this limit.
Splited files are saved in the recovery files' path.
Including folder disables this feature.
</dd></dl>
<dl><dt><b>
Append Recovery record
</b></dt><dd>&nbsp
In PAR 2.0, you can append recovery record to an archive file (ZIP or 7z format).
This feature will join created PAR2 files at the end of a single source file.
While recovery record is attached, general archivers can treat the archive ordinary.
When you open the archive with recovery record by MultiPar, complete archive file is shown as "Appended".
Caution, if you repair it, attached recovery record will be removed.
</dd></dl>
<hr>
<h3>Block allocation</h3>
<p>&nbsp
For PAR 1.0, number of source blocks is same as number of source files (except empty file).
If their size are different each other, it will become inefficient.
When you treat such files of varied size, you should pack them into an archive,
and split it into pieces of same size, then create PAR1 files for the pieces.
</p>
<p>&nbsp
For PAR 2.0, many blocks are aligned in each source file.
After source files are selected,
ideal blocks are allocated automatically by your <a href="option2.htm#block_allocation">selected allocating method</a>.
You may change block size or number of blocks manually.
As you set more blocks, the speed will be slow down.
As you set fewer blocks, it will be inefficient to recover small damage.
For practical use, number of blocks would better be thousand or several thousands.
When you input block size directly,
you may type the size with unit like "KB" or "MB".
For compatibility, it's good to set less than 100,000,000 bytes (95 MB).
</p>
<hr>
<h3>Recovery files</h3>
<dl><dt><b>
Base Filename
</b></dt><dd>&nbsp
"Base Filename" is a base of naming recovery files.
Though this will be set automatically, you may change it to favorite name.
After the base, volume number and extension are appended.
</dd></dl>
<dl><dt><b>
Path</b> and <b>Browse</b> button
</dt><dd>&nbsp
This is path of the directory where recovery files will be saved.
When you change "Base directory", this is set to the location.
You may change this by clicking "Browse" button, Drag & Drop a folder, or double-click the path box.
</dd></dl>
<dl><dt><b>
Comment</b> button
</dt><dd>&nbsp
If you want to write personal note, you may enter comment.
But, other PAR clients ignore this comment.
</dd></dl>
<dl><dt><b>
Redundancy
</b></dt><dd>&nbsp
"Redundancy" is a rate of how much damage can be recovered.
For example, if you set 10% for source files of 500MB,
you will be able to recover damage or lost upto 50MB.
<b>Caution</b>, actual possibility of recovery depends on the distribution of damage.
In general, while dense damage in narrow area may be recovered with small redundancy,
sparse damage over wide area requires larger redundancy.
When you set 0%, only an index file to verify will be created.
</dd></dl>
<dl><dt><b>
Number of Recovery blocks
</b></dt><dd>&nbsp
You may input the number of recovery blocks directly.
You can set more blocks than the range of redundancy slider.
</dd></dl>
<dl><dt><b>
Fit to free space</b> button and <b>Media size
</b></dt><dd>&nbsp
When you want to fill CD or DVD with both source files and recovery files, this feature is useful.
You may select the media or input the writable size directly.
It is safe to set a bit smaller redundancy,
because the calculation considers total data size only.
</dd></dl>
<dl><dt><b>
Sizing scheme</b> and <b>Number of recovery files
</b></dt><dd>&nbsp
"Sizing scheme" is how are the size of recovery files.
When "<b>All the same size</b>" or "<b>Variable size</b>" is selected,
you can set the number of recovery files.
Then, the specified number of recovery files of same size or different size will be created.
When "<b>Powers of 2 sizing scheme</b>" or "<b>Decimal weights sizing scheme</b>" is selected,
the number of recovery blocks in each recovery file will be
"1, 2, 4, 8, 16, 32, 64, 128..." or "1, 1, 2, 5, 10, 10, 20, 50...".
Each recovery file will be smaller than the largest source file (or splited source files).
</dd></dl>
<p>&nbsp
Sample distribution of 500 blocks for each sizing scheme:<br>
<center><table border=1 cellspacing=0 cellpadding=2 width="98%">
<tr bgcolor="E0F0E0"><th>Sizing scheme<th colspan=2>How many blocks in each recovery file
<tr><td>All the same size<td>167, 167, 166 (when 3 files)<td>84, 84, 83, 83, 83, 83 (when 6 files)
<tr><td>Variable size<td>72, 144, 284 (when 3 files)<td>8, 16, 32, 64, 128, 252 (when 6 files)
<tr><td>Powers of 2 sizing scheme<td colspan=2>1, 2, 4, 8, 16, 32, 64, 128, 245 (total 9 files)
<tr><td>Decimal weights sizing scheme<td colspan=2>1, 1, 2, 5, 10, 10, 20, 50, 100, 100, 200, 1 (total 12 files)
</table></center>
</p>
<dl><dt><b>
Efficiency
</b></dt><dd>&nbsp
This is a rate of how much data the recovery files can recover.
For example, when the efficiency is 95% for recovery files of 200MB,
you will be able to recover upto 190MB.
</dd></dl>
<dl><dt><b>
Number of files that can be fully reconstructed if missing (Min - Max)
</b></dt><dd>&nbsp
You may refer these values to know the recoverying capability of recovery files.
When sizes of source files are largely different, recovering a file may require more redundancy than you thought.
</dd></dl>
<hr>
<dl><dt><b>
Open</b> button
</dt><dd>&nbsp
If you want to open an existing recovery file, push this to select which.
The current setting over Create window is not saved.
</dd></dl>
<dl><dt><b>
Exit</b> button
</dt><dd>&nbsp
You can close MultiPar by pushing this.
Be careful, because there is no warning before exit.
The current setting over Create window is not saved.
</dd></dl>
<dl><dt><b>
Options</b> button
</dt><dd>&nbsp
If you want to change settings, push this, then <a href="option.htm">Option window</a> will appear.
</dd></dl>
<dl><dt><b>
About</b> button
</dt><dd>&nbsp
By pushing this, you can see version number on About window.
You may launch this Help from there.
</dd></dl>
<dl><dt><b>
Preview</b> button
</dt><dd>&nbsp
If you want to know the size of each recovery file,
you can see <a href="preview.htm">Preview window</a> by pushing this.
</dd></dl>
<dl><dt><b>
Create</b> button
</dt><dd>&nbsp
After you selected source files and done every setting,
you push this to create recovery files.
<a href="creating.htm">Creating window</a> will open to show the progress.
When multiple instances of MultiPar are running,
it waits finish of another instance's task, and will start next.
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

View File

@@ -0,0 +1,105 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Creating window</title>
</head>
<body>
<font size=5>Creating window</font><br><font size=1><br></font>&nbsp
When you push "Create" button on <a href="create.htm">Create window</a>, this window opens.
<hr>
<p>&nbsp
While you are creating recovery files, some information and the progress are shown.
Only "About", "Pause", and "Cancel" buttons are enabled while creating.
When the creation requires too long time,
you can return to <a href="create.htm">Create window</a> to change setting by "Cancel" feature.
When you want to stop the creation temporary,
you may use "Pause" feature to resume later.
Though CPU usage becomes minimum while pausing, memory have been consumed still.
</p>
<dl><dt><b>
Area of status text
</b></dt><dd>&nbsp
When you see an error message, the error is saved in log file.
Double-click here, then "<tt>save</tt>" folder will be opened.
</dd></dl>
<dl><dt><b>
Time left
</b></dt><dd>&nbsp
This is a required time to finish.
You may need to wait longer than this time, because the calculation is rough.
</dd></dl>
<hr>
<dl><dt><b>
New</b> button
</dt><dd>&nbsp
If you want to create new recovery files, push this to open <a href="create.htm">Create window</a>.
</dd></dl>
<dl><dt><b>
Open</b> button
</dt><dd>&nbsp
If you want to open an existing recovery file, push this to select which.
</dd></dl>
<dl><dt><b>
About</b> button
</dt><dd>&nbsp
By pushing this, you can see version number on About window.
You may launch this Help from there.
</dd></dl>
<dl><dt><b>
Pause</b> or <b>Resume</b> button
</dt><dd>&nbsp
You may pause the process temporary by pushing "Pause" button.
While pausing, you can resume the process at the point by pushing "Resume" button.
You may push "<b>Pause-key</b>" to pause or resume, too.
</dd></dl>
<dl><dt><b>
Cancel</b> button
</dt><dd>&nbsp
If you want to cancel the creation and return to <a href="create.htm">Create window</a>,
push "Cancel" button.
You may push "<b>Escape-key</b>" to cancel, too.
</dd></dl>
<dl><dt><b>
Return</b> button
</dt><dd>&nbsp
When creation was failed, you may return to <a href="create.htm">Create window</a> by pushing this.
</dd></dl>
<dl><dt><b>
Exit</b> button
</dt><dd>&nbsp
You can close MultiPar by pushing this.
</dd></dl>
<dl><dt><b>
Verify</b> button
</dt><dd>&nbsp
After you created successfully,
you may verify source files with the just-created recovery files.
By pushing this, <a href="verify.htm">Verify window</a> will open.
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

View File

@@ -0,0 +1,30 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Donation</title>
</head>
<body>
<font size=5>How to donate</font>
<hr>
<h3>Donations by PayPal</h3>
<p>&nbsp
While MultiPar is available as freeware, I spent a lot of time and effort to develop.
Your donation will encourage me to continue my efforts to improve and support MultiPar.
I made PayPal account and quick link for donation.<br>
<ol>
<li>Click <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=NPNAKA32N4GD6" target="_blank" title="PayPal - The safer, easier way to pay online!">this link</a> to go PayPal's web-page.
<li>On left panel, you can change Quantity, and click Update to multiply the Amount.
<li>On right panel, you select your PayPal account or Credit card.
<li>You may write Message to developer at the bottom of right panel.
</ol>
</p>
<p>
Other contributions like testing new feature, bug report, advice of refine, etc... would be appreciated also.
</p>
</body>
</html>

123
alpha/help/0409/howto1.htm Normal file
View File

@@ -0,0 +1,123 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Basic use</title>
</head>
<body>
<font size=5>Basic use of MultiPar</font>
<hr>
<h3>Compatibility with QuickPar</h3>
<p>&nbsp
How to use is almost same as <a href="http://www.quickpar.org.uk/" target="_blank" title="http://www.quickpar.org.uk/">QuickPar</a>.
But there are some different behavior,
because the development environment and how to implement are different.
Moreover I added some useful features which QuickPar lacks;
such like supporting directory tree or preview before creation.
If you have a new idea, you may request by mail.
</p>
<p>&nbsp
While QuickPar's default settings are optimized for UseNet, they are different from those of MultiPar.
If you want to set similar setting as QuickPar, you need to change the following items from default setting;<br>
On [GUI options] page, in [<a href="option2.htm#unit_size">Restrict block size to multiples of the unit</a>] section,<br>&nbsp
select "<b>For yEnc: 3,000 lines</b>".<br>
On [GUI options] page, in [<a href="option2.htm#block_allocation">Block allocating method</a>] section,<br>&nbsp
check "<b>Limit Block count up to: 3,000</b>" and set "<b>Block size: 384,000</b>".<br>
On [Client behavior] page, in [Creation options] section,<br>&nbsp
check "<b>Don't search subfolders</b>".<br>
On [Client behavior] page, in [Verification and Repair options] section,<br>&nbsp
select "<b>For 15 days</b>" at "<a href="option3.htm#reuse_result">Re-use verification result</a>".
</p>
<p>&nbsp
There are some different behavior between MultiPar and QuickPar.
Because MultiPar tries to select efficient block size to create PAR2 files,
initial block count may differ, even when the setting is same.
If you want "Recovery File Size: Variable (power of 2 sizing scheme)" in QuickPar,
select "Sizing scheme: Variable size" in MultiPar.
When you create additional recovery files against existing recovery set by "Extra",
QuickPar creates extra files without modifying original files,
but MultiPar re-creates all files by over-writing original files.
</p>
<p>&nbsp
The biggest difference between MultiPar and QuickPar is the support of multi-languages.
While QuickPar saves non-ASCII filename by a system specific character encoding,
MultiPar saves by UTF-8.
Then, QuickPar cannot read non-ASCII filename correctly which was saved by MultiPar.
In PAR2 clients, MultiPar and <a href="https://github.com/Parchive/par2cmdline" target="_blank" title="https://github.com/Parchive/par2cmdline">par2cmdline</a> can support Unicode filename.
</p>
<p>&nbsp
Because Peter Clements allowed me to use similer GUI with QuickPar,
I made MultiPar to treat Japanese filename.
I made English GUI for foreign users, who got failure in QuickPar.
When you have trouble using other PAR clients, MultiPar will help.
If you want to translate MultiPar's text or message, send mail to me.
MultiPar is used in many countries like;<br>
America, Belgium, China, Denmark, England, France, Germany, India, Italy, Japan, Netherlands, Poland, Portugal, Russia, Spain, Ukraina, and so on.
</p>
<hr>
<h3>Short-cut keys</h3>
<dl><dt><b>
ALT-key
</b></dt><dd>&nbsp
Some buttons have a character with under-line, like "<b><u>O</u></b>pen".
For those buttons, pushing "ALT-key" and [the under-lined character]-key at one time is same as clicking the button.
For example, "ALT+O" is same as clicking the "<u>O</u>pen" button.
</dd></dl>
<dl><dt><b>
F1-key
</b></dt><dd>&nbsp
You may push "F1-key" to launch this Help.
There is "<b>Help</b>" button on About window, too.
</dd></dl>
<dl><dt><b>
F5-key
</b></dt><dd>&nbsp
On Verify window, you may push "F5-key" to verify again newly.
</dd></dl>
<dl><dt><b>
Delete-key
</b></dt><dd>&nbsp
While you are selecting some source files in file-list on Create window,
you may push "Delete-key" to remove the files from list.
This is same as pushing "Remove Files" button.
</dd></dl>
<dl><dt><b>
Page Up</b>, <b>Page Down</b>, <b>Home</b>, and <b>End -keys
</b></dt><dd>&nbsp
While you are selecting a slider-bar of "Block Count" or "Redundancy" on Create window or Recreate window,
you may push these keys.
If you push "Page Up-key" or "Page Down-key", the slider moves largely.
It becomes minimum by pushing "Home-key", and becomes maximum by pushing "End-key".
</dd></dl>
<dl><dt><b>
Escape-key
</b></dt><dd>&nbsp
While it is Creating, Verifying, Repairing, or Monitoring,
you may push "Escape-key" to cancel the process.
This is same as pushing "Cancel" button.
Because it requires some interval to interrupt a client actually,
you need to wait for a while until the result is shown.
</dd></dl>
<dl><dt><b>
Pause-key
</b></dt><dd>&nbsp
While it is Creating, Verifying, or Repairing,
you may push "Pause-key" to pause or resume the process.
Pushing first time will pause the progress, and second time will resume it again.
Because it requires some interval to interrupt a client actually,
pushing the key multiple times quickly may fail to pause.
</dd></dl>
</body>
</html>

View File

@@ -0,0 +1,89 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Select source files</title>
</head>
<body>
<font size=5>How to select files to protect</font><br><font size=1><br></font>&nbsp
Before creating recovery files, you select files to protect.
<hr>
<h3>Way to start MultiPar after selecting files</h3>
<p>&nbsp
If you have set options in <a href="option1.htm#shortcut">"System settings" page</a>,
you can start MultiPar with source files, which were selected already.
When you know which files should be protected, this way is convenient.
<dl><dt>
When you have checked "Integrate MultiPar into Shell";
</dt><dd>&nbsp
If you right-click after selecting multiple files over Windows Explorer, right-click menu appears.
When you select "<b>MultiPar</b>" on the menu, sub-menu appears.
Then, you click "<b>Create Recovery Volumes</b>" on the sub-menu.
</dd></dl>
<dl><dt>
When you have checked "Create MultiPar icon on desktop";
</dt><dd>&nbsp
You select multiple files and Drag & Drop them onto the MultiPar icon.
</dd></dl>
<dl><dt>
When you have checked "Add MultiPar icon to [SendTo] menu";
</dt><dd>&nbsp
If you right-click after selecting multiple files over Windows Explorer, right-click menu appears.
When you select "<b>SendTo</b>" on the menu, sub-menu appears.
Then, you click "<b>MultiPar</b>" on the sub-menu.
</dd></dl>
</p>
<h3>Way to start MultiPar and select files</h3>
<p>&nbsp
By double-clicking MultiPar icon on desktop,
or clicking MultiPar icon in a Program group in Start menu,
you can start MultiPar, and Create window opens.
<dl><dt>
If there are only source files in a folder;
</dt><dd>&nbsp
By double-clicking path box at the right of "Base directory",
or pushing "<b>Browse</b>" button, folder selection dialog appears,
and you select the folder.
Or, you Drag & Drop the folder directly onto the path box.
When you select a folder, all files in the folder are selected.
</dd></dl>
<dl><dt>
If you select source files over Windows Explorer;
</dt><dd>&nbsp
You Drag & Drop the selected files onto the file-list on Create window.
Or, after you click "<b>Copy</b>" on right-click menu of Windows Explorer,
you click "<b>Paste</b>" on right-click menu of the file-list on Create window.
If you select a folder, the folder and all files in it will be added.
Though it is possible to add multiple files at once,
you should limit the selected files upto several hundred.
</dd></dl>
<dl><dt>
If you select each file and add to source files;
</dt><dd>&nbsp
By pushing "<b>Add Files</b>" button,
or clicking "<b>Add Files</b>" on right-click menu of the file-list on Create window,
file selection dialog appears, and you select files.
Though it is possible to add multiple files at once,
you should limit the selected files upto several tens.
</dd></dl>
Selected files are shown on the file-list as source files.
You may refer the number of source files or total size of file data.
</p>
<hr>
<h3>Whether to change block allocation</h3>
<p>&nbsp
If you have set options in <a href="option2.htm#unit_size">"GUI options" page</a> properly,
no need to change, because efficient blocks are allocated automatically.
Only when you feel the number of blocks are too many or too few, you may adjust manually.
When you are using a slow PC or want to create quickly, it may be good to decrease the number of blocks.
If you know how many blocks are acceptable for speed,
you would better limit up to the block count at <a href="option2.htm#block_allocation">"Block allocating method"</a>.
</p>
</body>
</html>

View File

@@ -0,0 +1,60 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Design recovery files</title>
</head>
<body>
<font size=5>How to design the recovery files</font><br><font size=1><br></font>&nbsp
After selecting source files, you design how the recovery files will become.
<hr>
<h3>How much redundancy you need</h3>
<p>&nbsp
The most important setting in creating recovery files is "<b>Redundancy</b>".
As you set more redundancy, it will be possible to repair,
but more time and space are required.
The required quantity depends on your circumstance;
like error rate of the saving drive or reliability of the network.
If you create as an insurance against rare incident, 5% or 10% may be enough.
If you get error often, you may require more, such as 30% or 50%.
If you want to protect seriously, backup source files and create recovery files.
</p>
<p>&nbsp
A whole file is lost by a human mistake like careless deletion or forgotten transport.
In this case, the problem is whether you have enough redundancy to reconstruct the whole file.
The measure is "<b>Number of files that can be fully reconstructed if missing</b>" on the bottom of Create window.
The "<b>Min - Max</b>" means that, how many files you can repair at least min and under than max.
The min should be 1 or more for safety.
</p>
<h3>How is the efficiency</h3>
<p>&nbsp
There is a measure of recovering capability,
that is "<b>Efficiency</b>" on the bottom of Create window.
Unless you have a trouble to keep saving space,
you don't need to take care usually.
When there is a big difference between settings,
you would better to select a efficient way,
but you can ignore small difference like several percent.
Because the possibility of repair is largely varied by distribution of damage,
it is worthless to aim for the best efficiency.
</p>
<hr>
<h3>If you post the recovery files on UseNet</h3>
<p>&nbsp
On Option window,
it is important to set <a href="option2.htm#unit_size">the unit of blocks</a> for UseNet.
Though it depends on the server, mostly it is "For yEnc: 3,000 lines" or "For yEnc: 5,000 lines".
No need to change other settings.
If you want smaller recovery files,
you may limit <a href="option3.htm#packet_repetition">repetition of packets</a> by selecting "<b>Upto 4 times</b>".
On Create window, you should select "<b>Powers of 2 sizing scheme</b>" at "Sizing scheme".
</p>
</body>
</html>

106
alpha/help/0409/howto4.htm Normal file
View File

@@ -0,0 +1,106 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Verify and repair</title>
</head>
<body>
<font size=5>How to verify and repair files</font><br><font size=1><br></font>&nbsp
If there are lost or damaged files after verification, you can try to repair them.
There are something to do, before repair and after failed repair.
<hr>
<h3>Way to start MultiPar after selecting a recovery file</h3>
<p>&nbsp
If you have set options in <a href="option1.htm">"System settings" page</a>,
you can start MultiPar by selecting a recovery file.
This way is easier than opening a recovery file by pushing "Open" button after you start MultiPar.
Even when there are multiple recovery files of same set, you must select one of them.
If you happen to select multiple recovery files,
Create window may open, or multiple Verify windows will open.
<dl><dt>
When you have checked "Associate with ... files";
</dt><dd>&nbsp
If you right-click after selecting a recovery file over Windows Explorer, right-click menu appears.
Then, you click "<b>Open with MultiPar</b>" on the menu.
Or, you simply double-click the recovery file, which you want to open.
</dd></dl>
<dl><dt>
When you have checked "Integrate MultiPar into Shell";
</dt><dd>&nbsp
If you right-click after selecting a recovery file over Windows Explorer, right-click menu appears.
When you select "<b>MultiPar</b>" on the menu, sub-menu appears.
Then, you click "<b>Verify Recovery Volume</b>" on the sub-menu.
</dd></dl>
<dl><dt>
When you have checked "Create MultiPar icon on desktop";
</dt><dd>&nbsp
You select a recovery file and Drag & Drop it onto the MultiPar icon.
</dd></dl>
<dl><dt>
When you have checked "Add MultiPar icon to [SendTo] menu";
</dt><dd>&nbsp
If you right-click after selecting a recovery file over Windows Explorer, right-click menu appears.
When you select "<b>SendTo</b>" on the menu, sub-menu appears.
Then, you click "<b>MultiPar</b>" on the sub-menu.
</dd></dl>
</p>
<h3>Prepare to repair damaged files</h3>
<p>&nbsp
While you may verify written files on read-only media like CD-R or DVD-R,
you cannot repair damaged files immediately.
When you repair files, you need to copy those files on HDD.
Even if they are damaged files or fragments of unknown filename,
you should bring all source files and recovery files to a folder on HDD.
To retrieve as many data as you can from the damaged media, you would better use "<b>File Salvager software</b>".
There are many shareware and freeware for the purpose.
Because "Data Recovery service" by a specialist company requires more money,
it's the last way to restore important data.
</p>
<hr>
<h3>If you cannot verify by incomplete PAR2 files</h3>
<p>&nbsp
When some vital packets are missing in a PAR2 file, it will be hard to verify or repair.
But all kinds of packets may exist in multiple PAR2 files.
Because MultiPar will search other PAR2 files of same base filename in the folder automatically,
you should set same base filename for all PAR2 files of the same recovery set.
(Base filename is a filename except extension and volume number.)
When other PAR2 files are put in another folder, or are renamed to different base filename,
you must add them manually by "Add" button.
</p>
<h3>If you cannot repair by a lack of available blocks</h3>
<p>&nbsp
Get more blocks as possible as you can.
If there is a same source file on different location, you should copy it or add it by "Add" button.
You need to find more blocks from the damaged media.
If you cannot recognize fragments are pieces of which source file,
you select "Additional verification" at "<a href="option3.htm#verification_level">Verification level</a>".
If there are old files of modified version in a previous backup, it is worth to add them.
</p>
<p>&nbsp
When a transported file had been damaged already, you cannot salvage lost data on your side.
If there are other recovery files, you get them, too.
If there is same file on another site, you may get it again.
Or, you may ask someone to give another set of recovery files.
</p>
<h3>If you failed to repair, even when you have enough blocks</h3>
<p>&nbsp
Mostly this is caused by "exclusive file access" or "limited privilege".
While a damaged file or recovered file is being accessed exclusively, it's impossible to replace them.
An example is Anti-Virus scanner, and you may need to exclude working folder from real-time scan.
When status of a damaged file became "<b>Locked</b>" after failed repair,
the file is being used by another application.
Of course, you cannot repair (modify) a system file, which is protected by OS.
When repair was failed by a fault of PAR1/2 specifications,
you may solve the problem by getting one more available block.
</p>
</body>
</html>

54
alpha/help/0409/intro.htm Normal file
View File

@@ -0,0 +1,54 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Introducing Parchive</title>
</head>
<body>
<font size=5>Introduction to Parchive</font>
<hr>
<p>&nbsp
PAR is a clipped from Parchive or Parity Archive, which means container of parity.
Even if original files are damaged or lost,
it is possible to repair them by extracting the parity.
Two types of PAR files are made in same time.
While an index file contains data for verification only,
recovery files contain data for both verification and repair.
Normally they don't distinguish, and they are just called as PAR files.
</p>
<p>
<table>
<tr><td>Example of PAR1 files:</td></tr>
<tr><td><tt>Data.PAR</tt></td><td>Index file</td></tr>
<tr><td><tt>Data.P01</tt></td><td>First recovery file</td></tr>
<tr><td><tt>Data.P02</tt></td><td>Second recovery file</td></tr>
<tr><td><tt>Data.P03</tt></td><td>Third recovery file</td></tr>
<tr><td><font size=1>&nbsp</font></td></tr>
<tr><td>Example of PAR2 files:</td></tr>
<tr><td><tt>Data.PAR2</tt></td><td>Index file</td></tr>
<tr><td><tt>Data.vol0+1.PAR2</tt></td><td>First recovery file, which contains 1 recovery block</td></tr>
<tr><td><tt>Data.vol1+2.PAR2</tt></td><td>Second recovery file, which contains 2 recovery blocks</td></tr>
<tr><td><tt>Data.vol3+4.PAR2</tt></td><td>Third recovery file, which contains 4 recovery blocks</td></tr>
</table>
</p>
<p>&nbsp
Though the index file is usable for verification only,
it is very smaller than recovery files.
The construction of recovery file is different between PAR1 and PAR2.
In PAR1, recovery data is calculated for a group of arrayed source files.
The requirement is simple like;
it requires 1 recovery file to restore 1 file, or it requires 3 recovery files to restore 3 files.
</p>
<p>&nbsp
In PAR2, recovery data is calculated for a group of allocated blocks in all source files.
While saving the recovery data,
it is possible to change the number of recovery blocks in each recovery file.
Thus, the required number of recovery files can be minimum by their required recovery blocks.
In above example, you need second recovery file to recover 2 blocks,
or you need first and third recovery files to recover 5 blocks.
</p>
</body>
</html>

View File

@@ -0,0 +1,57 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Option window</title>
</head>
<body>
<font size=5>Option window</font>
<hr>
<p>&nbsp
Usually options are saved on setting file "<tt>MultiPar.ini</tt>" under MultiPar's install folder.
When MultiPar is installed under "<tt>Program Files</tt>" directory,
your setting is saved in "<tt>MultiPar</tt>" folder under each user's "<tt>Application Data</tt>" directory.
You may locate the folder at <a href="option1.htm#folder_location">"System settings" page</a>.
</p>
<p>&nbsp
If you want to reset all options at once, delete the "<tt>MultiPar.ini</tt>".
If you want to reset every options on a page, push "Reset" button at the page.
If you want to reset a specific option only, just erase the line on the setting file.
</p>
<p>&nbsp
When multiple instances of MultiPar are open,
change of setting over an instance won't reflect to other instances.
If you want to enable the changed setting on another instance,
you need to re-open newly.
When you change different setting over some instances,
the result will be the sum of all changes.
</p>
<hr>
<p>&nbsp
Option window consists in the following 4 pages.
<ul>
<li><a href="option1.htm">System settings</a>
<li><a href="option2.htm">GUI options</a>
<li><a href="option3.htm">Client behavior</a>
<li><a href="option4.htm">Automated tasks</a>
</ul>
</p>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

127
alpha/help/0409/option1.htm Normal file
View File

@@ -0,0 +1,127 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Option - System settings</title>
</head>
<body>
<font size=5>System settings</font>
<hr>
<h3>Integration</h3>
<dl><dt><b>
Associate with ... files
</b></dt><dd>&nbsp
You can associate MultiPar with these file types.
Their extensions are PAR1 (<tt>.PAR</tt>, <tt>.P01</tt>, <tt>.P02</tt>, <tt>.P03</tt>, <tt>.P04</tt>, <tt>.P05</tt>, <tt>.P06</tt>, <tt>.P07</tt>, <tt>.P08</tt>, <tt>.P09</tt>),
PAR2 (<tt>.PAR2</tt>), PAR3 (<tt>.PA3</tt>), and SFV/MD5 (<tt>.SFV</tt> and <tt>.MD5</tt>).
Before you check one of them, you should de-associate it from another application (like QuickPar).
</dd></dl>
<a name="shortcut"></a>
<dl><dt><b>
Integrate MultiPar into Shell
</b></dt><dd>&nbsp
This option adds <b>MultiPar</b> on right-click menu over <b>Windows Explorer</b>.
On the sub-menu, you click "<b>Create Recovery Files</b>" to create PAR files,
or click "<b>Verify Recovery File</b>" to verify files by the PAR file.
However this feature is similar to shortcut icon in [SendTo],
you can supply more files, because there is no limit of length as command line.
When only one folder is selected to create, the folder becomes base directory,
and all files in the folder will be selected.
When <a href="http://www.7-zip.org">7-Zip</a> is installed, it's possible to pack files, and create PAR files for the archive.
</dd></dl>
<hr>
<h3>Program Shortcut</h3>
<p>&nbsp
Shortcut icon on desktop or [<b>SendTo</b>] menu is usable to start MultiPar for invoking Open or Create.
If you drop down a recovery file on the shortcut icon,
MultiPar will open the recovery file.
If you drop down some source files on the shortcut icon,
MultiPar will create recovery files for them.
</p>
<hr>
<a name="folder_location"></a>
<h3>Folder location</h3>
<p>&nbsp
By pushing these buttons, you can open MultiPar related folders directly.
Though this feature is useful to refer documents, be careful not to delete important files.
The current user's temporary files and log files are saved in the user specific "<tt>save</tt>" folder,
and it is possible to erase those files in this folder anytime.
</p>
<hr>
<h3>Hardware environment</h3>
<dl><dt><b>
Memory usage upto around
</b></dt><dd>&nbsp
This option is not strict, but a rough rate against available memory size.
"<b>Auto</b>" is good normally.
Only when you want to keep memory for other applications or system cache,
you may try lower rate.
</dd></dl>
<dl><dt><b>
File access mode
</b></dt><dd>&nbsp
Only when MultiPar fails to recognize a drive type, you may change this option.
To enforce random access mode on the drive (SSD or RAM drive), select "<b>SSD</b>".
To enforce sequential scan mode on the drive (HDD or Optical drive), select "<b>HDD</b>".
Because random access mode is very slow (and maybe harmful) on HDD,
you should select "<b>Auto</b>" normally.
</dd></dl>
<dl><dt><b>
CPU usage
</b></dt><dd>&nbsp
If you have recent PC with Multi-Core CPU, you may change the usage rate.
When you want to keep some CPU power for another task or cool down PC, this is useful.
</dd></dl>
<p>
<center><table border=1 cellspacing=0 cellpadding=2 width="90%">
<tr bgcolor="E0F0E0"><th>Position of slider<th>Number of using threads (max 16)
<tr><td>Left most<td>Quarter number of physical Cores
<tr><td>Second from left<td>Half of physical Cores
<tr><td>Medium<td>3/4 number of physical Cores
<tr><td>Second from right<td>For CPU with 5 or less Cores, number of physical Cores (exclude Hyper Threading)<br>
For CPU with 6 or more Cores, number of physical Cores -1
<tr><td>Right most<td>For CPU with Hyper Threading is enabled on 5 or less Cores, number of physical Cores +1<br>
For CPU with 6 or more Cores, number of physical Cores
</table></center>
</p>
<dl><dt><b>
Extra feature
</b></dt><dd>&nbsp
The proper features are selected from checked items.
Only when a feature doesn't work correctly, remove the check.
</dd></dl>
<dl><dt><b>
Enable GPU acceleration
</b></dt><dd>&nbsp
When your PC includes a GPU device, you may check this option for speed-up.
If OS's response is too slow or PC is over heat, you should disable it.
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

182
alpha/help/0409/option2.htm Normal file
View File

@@ -0,0 +1,182 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Option - GUI options</title>
</head>
<body>
<font size=5>GUI options</font>
<hr>
<h3>GUI options</h3>
<dl><dt><b>
Language
</b></dt><dd>&nbsp
You can change language of user interface.
"<b>Auto</b>" is default setting of PC.
Only when you want to use different language, select another.
This change will become enabled, when you start MultiPar next time.
</dd></dl>
<dl><dt><b>
Font
</b></dt><dd>&nbsp
You can change looks and size of characters.
Normally "<b>MS Shell Dlg 2</b>" is the standard font for dialog.
When you set another font at OS's graphic setting, the font may be shown in this list.
If you want to set your favorite font like "Arial",
write this line "<tt>FontName=Arial</tt>" under "<tt>[Option]</tt>" section on "<tt>MultiPar.ini</tt>" file directly.
</dd></dl>
<dl><dt><b>
Format of file size
</b></dt><dd>&nbsp
You may select your favorite format.
When you don't care small difference, "<b>With unit</b>" looks simple.
If you use Windows Explorer, "<b>With kilo-bytes</b>" looks samely.
</dd></dl>
<dl><dt><b>
Style of text on progress-bar
</b></dt><dd>&nbsp
You may change background of text over progress-bar.
</dd></dl>
<hr>
<h3>Supported media and sizes</h3>
<p>&nbsp
These contents are used for a list of "<b>Media</b>" on Create window.
In the edit box, you must put "<b>:</b>" between the media's name and size.
The name is left side, "<b>:</b>" is middle, and the size is right side.
The size must be value only, don't use comma or unit simbol like MB.
The max length of name is 18, and max size is 999999999999 (931 GB).
</p>
<hr>
<a name="unit_size"></a>
<h3>Restrict block size to multiples of the unit</h3>
<p>&nbsp
When you create PAR2 files, you may change the block allocation.
By setting an unit size of blocks,
the block size will become a multiple of the unit.
</p>
<dl><dt><b>
No restriction on the size
</b></dt><dd>&nbsp
When you don't set unit, you will be able to change the block size freely.
</dd></dl>
<dl><dt><b>
Exact
</b></dt><dd>&nbsp
You can set the unit as bytes directly.
By setting <b>Cluster size</b> of your saving drive,
you can verify and repair efficienctly.
For example, you would better set 2 KB for CD-R or DVD-R.
It may be from 4 KB to 64 KB for HDD,
or from 512-bytes to 4KB for USB memory.
</dd></dl>
<dl><dt><b>
For yEnc</b> or <b>For UUEncode
</b></dt><dd>&nbsp
Only when you post the files on <b>UseNet</b>, you should set the unit as lines of the encoding.
Because the setting depends on your UseNet server,
you must follow the directions of the server.
</dd></dl>
<hr>
<a name="block_allocation"></a>
<h3>Block allocating method</h3>
<p>&nbsp
When you select source files to create PAR2 files,
source blocks are allocated for the files.
By this option, you can change the method of how to allocate blocks.
Everytime you add or remove files, blocks will be allocated by the selected method automatically.
</p>
<dl><dt><b>
Limit Block count up to
</b></dt><dd>&nbsp
As there are many blocks, creation will require more time.
If you want to limit the number of blocks, set the max block count and check this.
Be careful not to set too few blocks,
because large block size will be inefficient to recover small damages.
In the era of CD or DVD, par2cmdline sets 2,000 blocks and QuickPar sets 3,000 blocks.
</dd></dl>
<dl><dt><b>
Rate (count / size)
</b></dt><dd>&nbsp
This rate is block count divided by block size.
For example, setting "1%" for 10,000-bytes block size gives 100 blocks,
as "<tt>100 blocks / 10000-bytes = 0.01 = 1%</tt>".
This calculation method is ideal for widely varied data size.
As total data size becomes large, more blocks will be allocated, but the change is mild.
</dd></dl>
<dl><dt><b>
Block size
</b></dt><dd>&nbsp
You may set preferred block size.
When you set unit size, resulting block size will be adjusted.
If you treat similar data size usually, this calculation method may be good.
Be careful about the result of too few or too many blocks.
</dd></dl>
<p>&nbsp
Because MultiPar tries to find efficient allocation by adjusting block size,
the result may be different from your specified value.
If you want to get a specific block size always,
set "Block size" here, and select "No restriction on the size" on <a href="option2.htm#unit_size">above section</a>.
If you want to allocate blocks like QuickPar,
you need to check "Limit Block count up to" and set "Block size".
</p>
<p>&nbsp
Example of how are the blocks in different level of total data size:<br>
<center><table border=1 cellspacing=0 cellpadding=2 width="98%">
<tr bgcolor="E0F0E0"><th>Method
<th width="23%">CD level (600MB)
<th width="25%">DVD level (4GB)
<th width="25%">BD level (20GB)
<tr><td>Rate (count / size): 1%
<td bgcolor="D0F0F0" rowspan=2>Block count: 2,508<br>Block size: 245 KB
<td bgcolor="FFFFD0">Block count: 6,553<br>Block size: 640 KB
<td bgcolor="FFFFD0">Block count: 14,655<br>Block size: 1,431 KB
<tr><td>Limit Block count up to: 3,000<br>Rate (count / size): 1%
<td bgcolor="E0E0FF">Block count: 3,000<br>Block size: 1,398 KB
<td bgcolor="E0E0FF">Block count: 3,000<br>Block size: 6,990 KB
<tr><td nowrap>Block size: 262,144 bytes
<td bgcolor="D0F0F0" rowspan=2>Block count: 2,400<br>Block size: 256 KB
<td bgcolor="FFFFD0">Block count: 16,384<br>Block size: 256 KB
<td bgcolor="FFE0E0">Block count: 32,768<br>Block size: 640 KB
<tr><td nowrap>Limit Block count up to: 3,000<br>Block size: 262,144 bytes
<td bgcolor="E0E0FF">Block count: 3,000<br>Block size: 1,398 KB
<td bgcolor="E0E0FF">Block count: 3,000<br>Block size: 6,990 KB
</table></center>
</p>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

267
alpha/help/0409/option3.htm Normal file
View File

@@ -0,0 +1,267 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Option - Client behavior</title>
</head>
<body>
<font size=5>Client behavior</font>
<hr>
<h3>Common options</h3>
<dl><dt><b>
Log output of clients
</b></dt><dd>&nbsp
You can save command-line by GUI and output from the client.
This log is useful, when you get an error,
or if you want to use the PAR client on Command Prompt.
The log file is "<tt>MultiPar.log</tt>" in "<tt>save</tt>" folder.
The folder can be opened by double-clicking status text on Creating or Verify window.
If the log file becomes too large, next output is saved in another file "<tt>MultiPar.#.log</tt>".
When you don't need those log files anymore, delete them by yourself.
</dd></dl>
<dl><dt><b>
Clear log
</b></dt><dd>&nbsp
When you want to delete all log files at once, push this button.
</dd></dl>
<dl><dt><b>
Run clients with lower priority
</b></dt><dd>&nbsp
When the response of PC to your control becomes too slow, while MultiPar is running,
you may check this option.
This is useful to run MultiPar in background, while you do another task on the same PC.
</dd></dl>
<dl><dt><b>
Don't wait finish of other tasks
</b></dt><dd>&nbsp
Only when you want to run multiple instances' tasks at the same time,
check this option.
Because each creating or repairing task consumes PC resource exclusively,
total speed may happen to be slower than queued tasks.
</dd></dl>
<hr>
<h3>Creation options</h3>
<dl><dt><b>
Format of recovery files
</b></dt><dd>&nbsp
You can change the version of newly creating PAR files.
You should use "<b>PAR 2.0</b>" normally.
You may use "<b>PAR 1.0</b>", only when source files are almost same size.
<!--You may use PAR 3.0 only when you are not satisfied with PAR 2.0 format.-->
<!--Currently "<b>PAR 3.0</b>" is available only for testing purpose of new technology.
If you want to test old sample PAR3 files,
you move "<tt>par3j_old.exe</tt>" from "<tt>tool</tt>" folder to the parent folder,
and rename it to "<tt>par3j.exe</tt>".-->
</dd></dl>
<dl><dt><b>
Range of redundancy
</b></dt><dd>&nbsp
You can change the range of redundancy slider-bar on Create window.
This may be useful, if you want to set small or large redundancy mostly.
Even when the range is limited, you can set more redundancy by typing number of recovery blocks directly.
</dd></dl>
<dl><dt><b>
Always use folder name for base filename
</b></dt><dd>&nbsp
Unless you type the filename by yourself,
"Base Filename" is set automatically after you select source files at first.
The method of naming is same as QuickPar like;
(1) When there is only one source file, the filename is used.
(2) When there are multiple source files, the preceding common part of filenames is used.
(3) Else, the folder name of parent directory is used.
If you want to use the last naming method always,
check this option.
</dd></dl>
<dl><dt><b>
Don't search subfolders
</b></dt><dd>&nbsp
When a folder includes subfolders,
all files in each folder are searched recursively by default.
If you want to ignore subfolders, check this option.
Even when it's checked, you can add inner files manually.
</dd></dl>
<dl><dt><b>
Don't create index file
</b></dt><dd>&nbsp
Index file is the smallest PAR file, which does not contain any recovery blocks.
It is available to verify source files, but is useless to recover a damage.
If you don't need the file, check this option.
</dd></dl>
<hr>
<h3>Verification and Repair options</h3>
<dl><dt><b>
Monitor files to verify
</b></dt><dd>&nbsp
If you check this option,
MultiPar will monitor recovery files and source files after the first verification.
When new files are added or some files are modified, they are verified automatically.
After when a previous verification was ended by error, all files were complete,
or all files were repaired successfully, monitoring will finish.
If you want to cancel monitoring at any time, push "<b>Escape-key</b>".
After that, you may click "Verify" button or push "F5-key" to start monitoring again.
</dd></dl>
<dl><dt><b>
Repair automatically
</b></dt><dd>&nbsp
If you check this option, MultiPar will start repair after verification if possible.
When this isn't checked, it does verification only.
If you are lazy to click "Repair" button everytime, this may be useful.
The setting is enabled for all verification by "F5-key", "Add", or "Monitor".
Even when some files might be restored, if it is impossible to repair all files,
it won't repair at all.
</dd></dl>
<a name="verification_level"></a>
<dl><dt><b>
Verification level
</b></dt><dd>&nbsp
Normally "<b>Detailed verification</b>" is good.
"<b>Simple verification</b>" is faster, when damage didn't delete or insert bytes.
"<b>Additional verification</b>" will check all files in the base directory.
When filenames of damaged files are different,
or when source files are contained in a non-compressed archive like ISO-image,
select "Additional verification" to add them automatically.
"<b>Aligned verification</b>" is the fastest, but it doesn't backup damaged files.
Because it will over-write damaged file directly, there is a risk of more data loss at failed recovery.
</dd></dl>
<a name="reuse_result"></a>
<dl><dt><b>
Re-use verification result
</b></dt><dd>&nbsp
If you want to skip some part of verification at next time, set some period in this option.
When you open a recovery file at first, files are verified automatically and the result is saved.
When you push "Repair" buttom afterwards,
the result is re-used and most part of actual verification will be skipped,
then the speed becomes faster.
By default setting (<b>For a time</b>), GUI keeps the result until it is closed.
When you set a longer period (<b>For some days</b>), GUI keeps the result for the period.
<b>Caution !</b> with this setting you may see the <b>past status</b> of files.
If you want to see the <b>current status</b> of files, push "<b>F5-key</b>",
then all files will be re-verified newly.
The data files are "<tt>***.bin</tt>" or "<tt>***.ini</tt>" in "<tt>save</tt>" folder.
Though old results beyond the period are erased,
sometimes those files may become many and large,
then be careful about setting long period.
</dd></dl>
<p>&nbsp
The difference by setting of re-use feature:<br>
<center><table border=1 cellspacing=0 cellpadding=2 width="98%">
<tr bgcolor="E0F0E0"><th rowspan=2>application and setting<th colspan=3>MultiPar<th rowspan=2>QuickPar<br>(as reference)
<tr bgcolor="E0F0E0"><th>Not used<th>For a time (default)<th>For some days
<tr><td>When you open a recovery file<td colspan=2 bgcolor="E0E0FF">verify newly<td colspan=2 bgcolor="FFE0E0">re-use previous verification result
<tr><td>When you click Repair button<br>
or When you add some new files
<td bgcolor="E0E0FF">verify again newly<td colspan=3 bgcolor="FFE0E0">re-use previous verification result
<tr><td>When you push F5-key to re-verify<td colspan=4 bgcolor="E0E0FF">verify again newly
</table></center>
</p>
<dl><dt><b>
Don't search subfolders
</b></dt><dd>&nbsp
When a file is missing, it will search the misnamed or moved file in folders recursively by default.
If you want to ignore subfolders by the reason of taking time, check this option.
</dd></dl>
<hr>
<h3>PAR2 options</h3>
<dl><dt><b>
Save UTF-16 filename additionally
</b></dt><dd>&nbsp
MultiPar supports "Unicode Filename packet" (UTF-16 filename) in PAR 2.0 specifications.
Only when you use non-ASCII characters in filename,
and you send PAR2 files to someone who has another PAR2 client which supports the packet,
you should check this option.
Usually it is worthless, because most PAR2 clients ignore the packet.
No need to check this for MultiPar and par2_tbb, which use UTF-8 filename.
</dd></dl>
<dl><dt><b>
Use file index for volume number
</b></dt><dd>&nbsp
Standard PAR2 filenames contain how many recovery blocks as their volume number.
If you want to use index of files instead of number of blocks, check this option.
When you transport PAR2 files over UseNet, you must not check this,
because the number of blocks is important for downloaders.
</dd></dl>
<a name="packet_repetition"></a>
<dl><dt><b>
Packet repetition
</b></dt><dd>&nbsp
When you create many recovery blocks, the PAR2 files may have many repeating packets.
You can disable or decrease the repetition of packets.
If you want smaller PAR2 files,
you may select "<b>Not used</b>" (no repetition) or "<b>Upto # times</b>" (packets will be repeated upto # times.).
If you create only one recovery file, you should select "<b>No restriction</b>".
</dd></dl>
<!--
<hr>
<h3>PAR3 options</h3>
<p>&nbsp
My sample PAR3 is implemented only for personal testing purpose.
Because I modify its algorithm and format sometimes while writing the proposal,
current samples won't be compatible with future PAR 3.0 specifications.
This section would be obsolete in future versions.
</p>
<dl><dt><b>
Create PAR 2.0 compatible PAR3 file
</b></dt><dd>&nbsp
If you want to create PAR3 files which enables verification by PAR2 client, check this option.
PAR2 client like QuickPar can use those PAR3 files for verification.
Because PAR3 recovery data is not compatible for PAR2,
PAR2 client cannot recover lost files with PAR3 files.
</dd></dl>
<dl><dt><b>
Use incomplete recovery
</b></dt><dd>&nbsp
Only when you cannot repair files by the lack of recovery blocks,
you may try this option.
This method retrieves damaged blocks from corrupt files,
and tries to repair them as possible as it can.
For setting, low value will read more damaged blocks and slow,
and high value will read less damaged blocks and fast.
When "Delete damaged files after Reapir" option isn't checked,
if the repair is failed, "<tt>.incomplete</tt>" is inserted into filename and lost area is filled by zero.
</dd></dl>
-->
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

103
alpha/help/0409/option4.htm Normal file
View File

@@ -0,0 +1,103 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Option - Automated tasks</title>
</head>
<body>
<font size=5>Automated tasks</font>
<hr>
<h3>File Deletion</h3>
<dl><dt><b>
Delete damaged files after Repair
</b></dt><dd>&nbsp
If you want to delete damaged source files and splited files after you repaired all files completely, check this option.
When source files have been complete at first, splited files are not deleted.
When this isn't checked, numbering extension will appended into filename of each damaged file.
This setting won't delete external files.
</dd></dl>
<dl><dt><b>
Delete recovery files after Repair
</b></dt><dd>&nbsp
If you want to delete recovery files after you repaired all files completely, check this option.
When source files have been complete at first,
or you failed to repair, recovery files are not deleted.
If a recovery file is useless like wrong set, it will not be deleted.
When a specified recovery file don't have a standard extension, this setting is ignored.
You may delete a file manually from right-click menu on file-list after verification or repair.
</dd></dl>
<dl><dt><b>
Send files to Recycle Bin
</b></dt><dd>&nbsp
This option is important, unless you are careful.
When this is checked, all auto-deleted files will goto recycle bin.
<b>Caution</b>, if there is no recycle bin for the drive like USB memory, files will be deleted simply.
</dd></dl>
<hr>
<h3>Batch Processing after Creation, Verification, or Repair</h3>
<p>&nbsp
This batch processing will be started after when the Creation, Verification, or Repair was completed successfully.
If the process was stopped by error or was canceled manually, this isn't started.
For Verification or Repair, this is started, only when all source files are complete or repaired.
</p>
<dl><dt><b>
Start batch script
</b></dt><dd>&nbsp
If you want to start something other tasks, check this option.
You need to write the task on a batch file; "<tt>auto_c.cmd</tt>" or "<tt>auto_v.cmd</tt>",
and put it in "<tt>save</tt>" folder.
You may open the folder at <a href="option1.htm#folder_location">"System settings" page</a>.
"<tt>auto_c.cmd</tt>" is started after Creation,
and "<tt>auto_v.cmd</tt>" is started after Verification or Repair.
These script get some parameters from MultiPar.
For the details, refer the <a href="batch.htm">page about Batch script</a>.
</dd></dl>
<dl><dt><b>
Notify with flash window and sound
</b></dt><dd>&nbsp
If you want to notice the finish, check this option.
This will blink the window and play OS's "notification" sound.
</dd></dl>
<dl><dt><b>
Close automatically
</b></dt><dd>&nbsp
If you want to close MultiPar automatically, check this option.
This won't wait the end of batch script.
</dd></dl>
<dl><dt><b>
Open a source file
</b></dt><dd>&nbsp
If you want to open a verified source file, check this option.
This is ignored for multiple source files.
</dd></dl>
<dl><dt><b>
Expand an archive file (by 7-Zip)
</b></dt><dd>&nbsp
When <a href="http://www.7-zip.org">7-Zip</a> is installed, this option is available.
This will show "Extract" dialog of 7-Zip, if source file is an archive file (ZIP, 7z, RAR, bz2, gz format).
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

View File

@@ -0,0 +1,65 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Preview window</title>
</head>
<body>
<font size=5>Preview window</font><br><font size=1><br></font>&nbsp
When you push "Preview" button on <a href="create.htm">Create window</a>, this window appears.
<hr>
<p>&nbsp
Because the size of recovery files are hard to predict for most users,
MultiPar has "Preview" feature.
You can see the list of recovery files which you will create by the current setting.
You may consider the efficiency of those files.
If you are satisfied with them, you may create recovery files directly by pushing "<b>Create</b>" button.
Or you may return to Create window by pushing "<b>Cancel</b>" button.
</p>
<dl><dt><b>
Source block usage
</b></dt><dd>&nbsp
This rate is a measure of block allocation.
When a file size is different from a multiple of block size,
the reminder in the last block of the file becomes a waste.
If all source blocks are filled by file data fully, the rate becomes 100%.
When it is lower than 90%, you may decrese the block size.
</dd></dl>
<dl><dt><b>
Recovery block consumption
</b></dt><dd>&nbsp
This rate is a measure of recovery file's construction.
While recovery files consist of many packets,
there are some packets which don't contain recovery data.
If packets for recovery blocks consume most of the recovery files, the rate becomes high.
When it is too low, you may decrease the number of source blocks,
or limit <a href="option3.htm#packet_repetition">repetition of packets</a>.
</dd></dl>
<dl><dt><b>
Efficiency of recovery files
</b></dt><dd>&nbsp
This rate is a measure of recovering capability.
For example, when the rate is 95% for recovery files of 300MB,
you will be able to recover upto 285MB.
Because this value is just an avarage assumption,
actual possibility depends on the distribution of damage.
The efficiency is important, when you save recovery files in a limited size.
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

102
alpha/help/0409/problem.htm Normal file
View File

@@ -0,0 +1,102 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Known problem</title>
</head>
<body>
<font size=5>Known problem</font>
<hr>
<h3>Error of PAR clients</h3>
<p>&nbsp
If an error is occured in a PAR client while create/verify/repair,
that is shown as "Error : something..." on GUI.
When PAR client is stopped by an error,
the output of PAR client is save in log file without option setting.
A user may refer the log to see what is the problem.
When a user want to report the problem by sending mail to a developer,
he should attach the log file with the mail.
</p>
<p>&nbsp
When "malloc" error happened, decrease the number of source blocks.
If source files exist on un-writable media like CD/DVD,
copy those files on HDD at first, then repair the copied files.
If the source files are very large, be careful about available space of HDD.
If you cannot open or repair files, other applications or system may prevent your file access.
You should close others and confirm your privilege.
</p>
<h3>Error: checksum mismatch</h3>
<p>&nbsp
When "checksum mismatch" error happened, it was caused by a hardware problem (such like failure in CPU, RAM, HDD).
Because MultiPar consumes most machine power, PC may become un-stable by high stress or over-heat.
If MultiPar detects calculation error, it stops to avoid invalid creation or failed repair.
Your PC should be enough stable for heavy task.
</p>
<p>&nbsp
There are some solutions to try;<br>
(1) Change BIOS setting for safe running.<br>&nbsp
If you set over-clocking, return to the original value.
If you set faster memory access mode, change to slower speed.<br>
(2) Check memory error.<br>&nbsp
Recent Windows OS has memory test feature.
If it finds error, you must replace the bad module.
Even when you never see a problem at daily small memory usage,
MultiPar may use larger memory space and can reveal failure.<br>
(3) Change MultiPar setting to disable GPU acceleration.<br>&nbsp
There is "Hardware environment" section on "System settings" tab of MultiPar Options.
Un-check "Enable GPU acceleration".<br>
(4) Change MultiPar setting to disable extra feature of CPU.<br>&nbsp
There are some check-boxes in "Extra feature".
Un-check them one by one and test until no error.
The order of un-checking is from "AVX2", "JIT(SSE2)", "CLMUL", to "SSSE3".<br>
(5) Change MultiPar setting to use less number of threads.<br>&nbsp
Move "CPU usage" slider from right to left.<br>
(6) Change MultiPar setting to use less memory.<br>&nbsp
Select smaller number at "Memory usage upto around".
</p>
<h3>Collision of Hash values</h3>
<p>&nbsp
If hash value of a damaged file happens to be same as hash value of its original file,
PAR clients cannot detect the damage.
This is very rare case, but serious problem if happen.
Because data in complete files are used to recover damaged files,
miss-detection of damage causes failure of recovery.
If you get this problem, you may check files with another hash like SHA-1.
</p>
<p>&nbsp
Because PAR uses MD5 hash, accidental collision problem will not happen normally.
In addition to MD5, PAR 2.0 uses CRC-32 to check completeness,
then the chance of miss-detection is very low.
Caution, MD5 was broken already as cryptgraphic hash.
When a malicious cracker modified files by forging same hash values,
PAR clients cannot detect the intended modification.
</p>
<h3>Problem of PAR 1.0 specifications</h3>
<p>&nbsp
PAR 1.0 uses MD5 hash to distinguish source files.
When there are files of same contents, their MD5 becomes same also.
In this case, those files are distinguished by filename only.
If one of them are lost and another is misnamed,
it is difficult to determine which file is lost or misnamed.
When a file is thought as lost, it requires parity volume to recover.
If you know those files have same contents,
it is much faster to copy from another file.
</p>
<h3>Fault of PAR 1.0 & 2.0 specifications</h3>
<p>&nbsp
There is a fault in the method of creating generator matrix in PAR 1.0 and 2.0.
Rarely the matrix is not invertible, and repair will be failed.
If you cannot repair files with enough recovery blocks,
you would better try with different recovery blocks.
When there are extra blocks in the set of PAR2 files,
MultiPar tries to solve this problem automatically.
</p>
</body>
</html>

321
alpha/help/0409/python.htm Normal file
View File

@@ -0,0 +1,321 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css">
<!--
textarea{width:100%;}
-->
</style>
<title>Python script</title>
</head>
<body>
<font size=5>Sample of Python script</font>
<hr>
<p>&nbsp
To use Python script, you need to install <a href="https://en.wikipedia.org/wiki/Python_(programming_language)">Python</a> in your PC.
The official <a href="https://www.python.org/downloads/">download site is here</a>.
There are some useful documents and articles on the Internet.
You may edit a sample script for your usage.
</p>
<p>&nbsp
Python script is saved on some text files in <tt>tool</tt> folder under MultiPar's installed directory.
If you put a script file on another folder or under <tt>Program Files</tt> directory, you must set the path of <tt>par2j64.exe</tt> or <tt>MultiPar.exe</tt> on your PC.
By default, I write relative path from the <tt>tool</tt> folder.
You can refer the directory on MultiPar's Option window:
"System settings" tab, "Folder location" section, "Open MultiPar's install folder" button.
</p>
<hr>
<h3>Index</h3>
<table width="100%">
<tr><td><a href="#C1">Create individual PAR2 set in each selected folder</a><td>
<tr><td><a href="#C2">Create individual PAR2 set in each selected folder with GUI</a><td>
<tr><td><a href="#C3">Create multiple PAR2 sets for many files in a folder</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#Q1">Create multiple PAR2 sets for files or folders with Queuing GUI</a><td>
<tr><td><a href="#Q2">Verify multiple PAR2 sets in a selected folder with Queuing GUI</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#D">Check difference of PAR and directory with GUI</a><td>
<tr><td><a href="#R1">Rename included source files in PAR2 sets with GUI</a><td>
<tr><td><a href="#R2">Read a selected JSON file and show contents</a><td>
<tr><td><hr width="95%"></td>
<tr><td><a href="#A1">Automate tasks after MultiPar GUI 's Creation</a><td>
<tr><td><a href="#A2">Automate tasks after MultiPar GUI 's Verification / Repair</a><td>
</table>
<hr>
<a name="C1"></a>
<h3>Create individual PAR2 set in each selected folder</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of folder1" "path of folder2" "path of folder3"...
<tr><td>Input<td>specify some folders
<tr><td>Action<td>This sample creates individual PAR2 set in each selected folder.
For example, when you supply 7 folders, total 7 PAR2 set are made.
<tr><td>Script file<td><tt>each_folder.py</tt>
</table>
</p>
<p>&nbsp
This sample tries to create efficient PAR2 files.
</p>
<hr>
<a name="C2"></a>
<h3>Create individual PAR2 set in each selected folder with GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of folder1" "path of folder2" "path of folder3"...
<tr><td>Input<td>specify some folders
<tr><td>Action<td>This sample creates individual PAR2 set in each selected folder.
For example, when you supply 7 folders, total 7 PAR2 set are made.
It shows GUI for setting.
It's possible to filter source files by their size.
<tr><td>Script file<td><tt>large_files.py</tt>
<tr><td>Caution<td>You must check MultiPar Option: "Always use folder name for base filename" in "Creation options" section on "Client behavior" tab.
</table>
</p>
<p>&nbsp
Instead of searching all files in each specified folder,
it will filter files by their size.
In the sample, it selects files of 1 MB over.
You may change the limit size.
To send name of source files, it uses file-list.
</p>
<hr>
<a name="C3"></a>
<h3>Create multiple PAR2 sets for many files in a folder</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of folder1" "path of folder2" "path of folder3"...
<tr><td>Input<td>specify some folders
<tr><td>Action<td>This sample creates multiple PAR2 sets for many files in each selected folder.
For example, when you supply 3 folders, it creates independent multiple PAR2 sets in every folder.
In the sample, it will create a PAR2 set for 1000 source files.
It's possible to change the limit value.
When there are 3500 files in a folder, it will create 4 PAR2 sets in the folder.
<tr><td>Script file<td><tt>group_files.py</tt>
</table>
</p>
<p>&nbsp
To distinguish PAR2 files, it uses stable filename with serial numbering.
They are like; <tt>#1.par2</tt>, <tt>#2.par2</tt>, <tt>#3.par2</tt>...
When there are sub directories in a folder, it will search inner files.
To send name of source files, it uses file-list.
The process may be very slow for many files.
</p>
<hr>
<a name="Q1"></a>
<h3>Create multiple PAR2 sets for files or folders with Queuing GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of file1 or folder1" "path of file2 or folder2" "path of file3 or folder3"...
<tr><td>Input<td>specify some files and/or folders (You may select them manually on GUI.)
<tr><td>Action<td>This sample creates multiple PAR2 sets for every selected files or folders.
It creates one PAR2 set for each selected file or folder independently.
PAR2 set for a file will be made in the same directory with the source file's name.
PAR2 set for a folder will be made in the folder with the source folder's name.
For example, when 3 files and 2 folders are selected, 5 items are shown on a list.
Then, it will create 5 PAR2 sets continuously.
It's possible to stop queue on GUI.
<tr><td>Script file<td><tt>queue_create.py</tt>
<tr><td>Caution<td>While creation, existing PAR2 files are ignored.
When there are old PAR2 files already, it doesn't erase them. (However it may over-write same name files.)
If you want to re-create all PAR2 files newly, you must delete them at first manually.
</table>
</p>
<p>&nbsp
You must set command-line options of par2j for creation.
You should refer <tt>Command_par2j.txt</tt> in <tt>help</tt> folder.
Because all creating PAR2 sets will use the same options, test with a few files to see result at first.
When you want to confirm result by MultiPar, select a PAR2 set and push "Open with MultiPar" button.
</p>
<p>&nbsp
While creation, it shows details on Command Prompt window.
You can control the progress by pushing a key on the Command Prompt.
You may pause the process by pushing P-key.
You may resume the process by pushing R-key.
You may cancel the process by pushing C-key.
</p>
<p>&nbsp
You may create short-cut file of this script file.
Put the short-cut on <tt>desktop</tt> or <tt>SendTo</tt> folder of Windows OS.
Then, you can drag & drop files and/or folders on the short-cut.
Or, select files on right-click "SendTo" menu.
If you select one folder, it search inner items of the folder.
If you select multiple items or one file, they are selected directly.
</p>
<hr>
<a name="Q2"></a>
<h3>Verify multiple PAR2 sets in a selected folder with Queuing GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of folder"
<tr><td>Input<td>specify a folder (You may select it manually on GUI.)
<tr><td>Action<td>This sample verifies multiple PAR2 sets in a selected folder.
For example, when there are 7 PAR2 sets in a folder, they are shown on a list.
It will verify each PAR2 set continuously.
It's possible to stop queue on GUI.
<tr><td>Script file<td><tt>queue_verify.py</tt>
<tr><td>Caution<td>You must select MultiPar Option: "Re-use verification result" to be "For 3 days" or longer,
and you should check "Don't search subfolders" in "Verification and Repair options" section on "Client behavior" tab.
</table>
</p>
<p>&nbsp
In this sample, it tries verification only.
If you want to repair a damaged set automatically, use <tt>repair</tt> command instead of <tt>verify</tt> of par2j.
When you want to confirm result by MultiPar, select a PAR2 set and push "Open with MultiPar" button.
You may repair on the MultiPar GUI.
</p>
<p>&nbsp
While verification, it shows details on Command Prompt window.
You can control the progress by pushing a key on the Command Prompt.
You may pause the process by pushing P-key.
You may resume the process by pushing R-key.
You may cancel the process by pushing C-key.
Even when you stop the verification task, it may save result partially.
</p>
<p>&nbsp
When you push "Folder" button, it searches PAR2 sets in the selected folder.
By default, It doesn't search files recursively, because it may be slow.
If you want to search all sub-directories, you need to edit the script.
You may change behavior of starting verification automatically or not by editing the script.
</p>
<hr>
<a name="D"></a>
<h3>Check difference of PAR and directory with GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of folder1" "path of folder2" "path of folder3"...
<tr><td>Input<td>specify some folders
<tr><td>Action<td>This is a simple tool to show difference of PAR and directory contents.
<tr><td>Script file<td><tt>diff_folder.py</tt>
<tr><td>Caution<td>Because it checks difference of files' existence and size only,
it cannot detect broken files.
Use MultiPar to see precise status of source files.
</table>
</p>
<p>&nbsp
This sample uses <tt>list</tt> command of par2j.
While it lists source files in the PAR2 set, it doesn't verify them.
After comparison with current directory-tree,
it paints blue color for additional files,
red color for missing files,
and yellow color for files of different size.
</p>
<hr>
<a name="R1"></a>
<h3>Rename included source files in PAR2 sets with GUI</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of file"
<tr><td>Input<td>specify a PAR2 file
<tr><td>Action<td>This is a simple tool to edit names of source files in PAR2 files.
Because it works in a single file, you don't need to set path of another application.
<tr><td>Script file<td><tt>par2_rename.py</tt>
<tr><td>Caution<td>The modified PAR2 files by this tool are different from formal PAR2 files for renamed filenames.
When someone generates new PAR2 files for renamed filenames by QuickPar/MultiPar,
the PAR2 files are incompatible with these modified PAR2 files.
</table>
</p>
<p>&nbsp
If you don't see debug output, you may rename the script file's extension to <tt>.pyw</tt>.
Then, Command Prompt won't open.
</p>
<p>&nbsp
How to use<br>
<ol>
<li>Select a PAR2 file by pushing [ File ] button. PAR2 files of same base name will be listed.</li>
<li>Select a PAR2 file on the left list and push [ Read ] button.
It's good to select the smallest PAR2 file for fast search.
Only when PAR2 files are damaged, select a complete PAR2 file.</li>
<li>Type a new filename on a edit box.
Select editing name on right list and push [ Rename ] button.
You may edit multiple filenames contiuously.</li>
<li>After you finish to edit filenames, push [ Save ] button.
PAR2 files will be saved with prefix "<tt>new_</tt>" in the same folder.</li>
</ol>
</p>
<hr>
<a name="R2"></a>
<h3>Read a selected JSON file and show contents</h3>
<p>
<table border=1 cellspacing=0 cellpadding=2 width="100%">
<tr><td>Command<td>"path of script file" "path of file"
<tr><td>Input<td>specify a JSON file
<tr><td>Action<td>
By setting <tt>/w</tt> option, par2j saves verification result on a JSON file.
This sample uses the JSON file.
<tr><td>Script file<td><tt>read_json.py</tt>
<tr><td>Caution<td>
In the JSON file, par2j writes <tt>/</tt> as directory separator.
</table>
</p>
<hr>
<a name="A1"></a>
<h3>Automate tasks after MultiPar GUI 's Creation</h3>
<p>&nbsp
MultiPar GUI can start script after creation.
The script file must be <tt>auto_c.py</tt> in the user's <tt>save</tt> folder.
A user may write any script in this file.
The script gets two parameters from GUI as below;<br>
<code>
%1 = Path of a recovery file<br>
%2 = Path of base directory of source files
</code>
</p>
<p>&nbsp
I put a sample in "<tt>tool\batch</tt>" folder.
<tt>auto_c.py</tt> shows two parameters only.
</p>
<hr>
<a name="A2"></a>
<h3>Automate tasks after MultiPar GUI 's Verification / Repair</h3>
<p>&nbsp
MultiPar GUI can start script after verification or repair.
The script file must be <tt>auto_v.py</tt> or <tt>auto_vl.py</tt> in the user's <tt>save</tt> folder.
A user may write any script in this file.
The script gets three parameters from GUI as below;<br>
<code>
%1 = Path of a recovery file<br>
%2 = Path of base directory of source files<br>
%3 = Exit code of the used client (refer the command-line manual)
</code>
</p>
<p>&nbsp
I put two samples in "<tt>tool\batch</tt>" folder.
<tt>auto_v.py</tt> shows three parameters only.
<tt>auto_vl.py</tt> shows lists of recovery files and source files, too.
</p>
</body>
</html>

View File

@@ -0,0 +1,38 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>ReadMe - Introduction</title>
</head>
<body>
Restore damaged or lost files with PAR recovery files.<br>
<font size=5>MultiPar</font> &nbsp (set of PAR clients and GUI)
<hr>
<h3>Introduction</h3>
<p>&nbsp
MultiPar was made as an alternative to <a href="http://www.quickpar.org.uk/" target="_blank" title="http://www.quickpar.org.uk/">QuickPar</a>.
The GUI is similar to QuickPar by getting agreement from Peter Clements.
While it looks like a multi-lingual version of QuickPar, there are some good features;
Unicode characters, directory-tree, faster repairing, smaller recovery files, batch scripting, and so on.
</p>
<h3>Feature</h3>
<p>&nbsp
MultiPar supports both PAR 1.0 and PAR 2.0 specifications.
See the <a href="http://parchive.sourceforge.net/" target="_blank" title="http://parchive.sourceforge.net/">Parchive project</a> for details of Parchive.
MultiPar uses UTF-8 or UTF-16 to treat filenames with non-ASCII characters.
While MultiPar and <a href="https://github.com/Parchive/par2cmdline" target="_blank" title="https://github.com/Parchive/par2cmdline">par2cmdline</a> can treat sub-directory and UTF-8 filename,
QuickPar and other PAR2 clients cannot treat them.
Almost all PAR2 clients don't support UTF-16 filename and comment.
Be careful to use those special features.
</p>
<h3>System requirement</h3>
<p>&nbsp
MultiPar requires a PC with Windows Vista or later (Windows 7, 8, 10).
</p>
</body>
</html>

View File

@@ -0,0 +1,50 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>ReadMe - Caution</title>
</head>
<body>
<h3>Failure, Fault or Mistake</h3>
<p>&nbsp
Use this application at your own risk, because I might miss something.
If you find something odd behavior, report the incident to me.
Some examples like output-log, screen-shot, file name, file size, your PC spec,
and detailes (when / where / what / how) are helpful to solve problems.
Please contain them as possible as you can.
Then, I will fix it at next version.
</p>
<h3>Security risk</h3>
<p>&nbsp
You should treat PAR files in a same security level as their source files.
When you have secret data on some files and encrypt them,
you must create PAR files from their encrypted files.
If you create PAR files from non-encrypted files, others may know how is the original secret data.
Even when there is no enough redundancy to recover it completely,
their PAR files may reveal useful information for a spy.
</p>
<p>&nbsp
Parchive doesn't prevent an intended modification.
Recovering with unknown PAR files is same as copying unknown files on your PC.
The reliability of recovered files depends on their PAR files.
PAR clients may modify original valid files into something invalid files,
when PAR files were modified by a malicious cracker.
For example, if someone created PAR files from his modified source files,
the PAR files will damage your complete source files.
</p>
<h3>PAR 3.0 is not finished yet</h3>
<p>&nbsp
PAR 3.0 in MultiPar is implemented only for personal testing purpose.
Because I modify its algorithm and format sometimes while writing the proposal,
current samples won't be compatible with future PAR 3.0 specifications.
Don't send current PAR3 files to others, who may not have the same version.
</p>
<p>&nbsp
Currently sample PAR3 isn't available, while the specification is being updated.
</p>
</body>
</html>

View File

@@ -0,0 +1,83 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>ReadMe - Installation</title>
</head>
<body>
<h3>Install or uninstall with installer package</h3>
<p>&nbsp
Double click setup file ( <tt>MultiPar131_setup.exe</tt> or something like this name ),
and follow the installer dialog.
At version up, if you want to use previous setting, overwrite install is possible.
Before overwrite install, you should un-check "Integrate MultiPar into Shell".
You may need to re-start OS after overwrite install or uninstall rarely.
To install under "<tt>Program Files</tt>" or "<tt>Program Files (x86)</tt>" directory,
you must start the installer with administrative privileges by selecting
"Run as administrator" on right-click menu.
</p>
<p>&nbsp
You can uninstall through the Windows OS's Control Panel,
or double click <tt>unins000.exe</tt> in a folder which MultiPar was installed.
Because uninstaller does not delete setting files or newly put files,
you may delete them by yourself.
</p>
<p>&nbsp
When you have used installer package, you should not move install folder.
Or else, you will fail to uninstall later.
</p>
<h3>Installation for multiple users by installer package</h3>
<p>&nbsp
If multiple users may log-on a PC, the administrator can install MultiPar for everyone.
By installing with administrative privileges, installer made Start Menu icon,
Desktop icon, and File association will be available for all users.
When he installed under "<tt>Program Files</tt>" directory, each user keeps individual setting.
When he installed in another folder, all users share same setting.
In either case, user made icons and association are available for the user only.
</p>
<hr>
<h3>Install with archive version</h3>
<p>&nbsp
Unpack compressed file ( <tt>MultiPar131.zip</tt> or something like this name ) in a folder.
<tt>MultiPar.exe</tt> is the interface of MultiPar.
</p>
<p>&nbsp
You can create short-cut icon or send-to link at Option window later.
If you associate PAR file extensions "<tt>.par</tt>" or "<tt>.par2</tt>" with MultiPar,
de-associate them from other application like QuickPar at first.
</p>
<h3>Un-install with archive version</h3>
<p>&nbsp
If you associate PAR file with MultiPar, de-associate them from this.
Delete all files in the install folder, in which you extract files.
If you installed MultiPar under "<tt>Program Files</tt>" directory,
setting data was saved in MultiPar folder under "<tt>Application Data</tt>" directory,
so you need to delete the folder.
</p>
<p>&nbsp
When you integrated MultiPar into shell at Option window,
you must clear the check before un-install.
If you have deleted <tt>MultiPar.exe</tt> already, you can un-install the DLL manually.
Open "Command Prompt" and change directory to MultiPar's folder,
then type "<tt>RegSvr32.exe /u MultiParShlExt64.dll</tt>" to remove shell extension.
You cannot delete "<tt>MultiParShlExt64.dll</tt>", while it is used by OS or Explorer.
You may log-off and log-on again to OS before deleting the file.
</p>
<h3>Change installed folder of archive version</h3>
<p>&nbsp
Move files in the install folder.
If you associated PAR file with MultiPar, de-associate once, and associate again.
If you want to use same setting at another PC, copy the setting file "<tt>MultiPar.ini</tt>".
If you move MultiPar into "Program Files" directory,
setting data is saved in MultiPar folder under "Application Data" directory,
so you need to move "<tt>MultiPar.ini</tt>" into the folder, too.
</p>
</body>
</html>

View File

@@ -0,0 +1,52 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="stylesheet" href="style.css">
<title>ReadMe - Support</title>
</head>
<body>
<h3>License</h3>
<p>&nbsp
MultiPar consists of PAR clients and GUI to control them.
They are written by Yutaka Sawada.
Though console applications are open source (PAR clients are GPL),
GUI application is closed source.
Some article are available at
<a href="https://hp.vector.co.jp/authors/VA021385/" target="_blank" title="Announcement page on Vector">my web site</a>.
There are source code packages on <a href="https://github.com/Yutaka-Sawada/MultiPar" target="_blank" title="GitHub page">GitHub</a>.
</p>
<hr>
<h3>Support</h3>
<p>&nbsp
I use <a href="https://github.com/Yutaka-Sawada/MultiPar/issues" target="_blank" title="issues on GitHub">GitHub issue's page</a> as a web-forum for MultiPar users.
</p>
<p>&nbsp
My name is Yutaka Sawada.
E-mail address is "tenfon (at mark) outlook.jp".
Or "multipar (at mark) outlook.jp" for PayPal usage and
"tenfon (at mark) users.sourceforge.net" for SourceForge users.
Because they use a same mail-box, don't send duplicate mails.
Though e-mail address had been "ten_fon (at mark) mail.goo.ne.jp" ago,
the mail service ended at March 2014, so don't send to there.
The (at mark) is format to avoid junk mails, and replace it with "@".
</p>
<p>&nbsp
I get many spam mails from oversea.
If an e-mail is detected as junk mail or suspicious,
mail server may delete it automatically, and I won't see it.
</p>
<h3>Link</h3>
<p>&nbsp
I use <i>vector.co.jp</i>'s <a href="https://hp.vector.co.jp/authors/VA021385/" target="_blank" title="Announcement page on Vector">author page</a> to introduce MultiPar.
Because there is another <a href="https://www.vector.co.jp/soft/dl/winnt/util/se460801.html" target="_blank" title="Download page on Vector">official download page</a>,
using direct link to files on the page isn't preferable.
When you write a link on somewhere, please don't include filename.
</p>
</body>
</html>

View File

@@ -0,0 +1,96 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style.css">
<title>Add recovery record</title>
</head>
<body>
<font size=5>How to add recovery record to ZIP or 7-Zip archive</font>
<hr>
<p>&nbsp
ZIP archive (extension <tt>.zip</tt>) is used widely and 7-Zip archive (extension <tt>.7z</tt>) is useful.
Because they don't have a feature of recovery record, someone might feel RAR archive is better.
But, by using Parchive, normal ZIP or 7-Zip archive can be protected with recovery record also.
</p>
<p>
<table border=0 cellspacing=0 cellpadding=1>
<tr><td>Step 1:</td>
<td>Create a ZIP or 7-Zip archive file.</td>
<td><table border=1 cellspacing=0 cellpadding=2>
<tr><td bgcolor="FFE0E0">ZIP or 7-Zip archive file</td></tr></table>
</td></tr>
<tr><td>Step 2:</td>
<td width="40%" nowrap>Create a single PAR2 file for the archive file.</td>
<td><table border=1 cellspacing=0 cellpadding=2>
<tr><td bgcolor="E0E0FF">PAR2 recovery file</td></tr></table>
</td></tr>
<tr><td nowrap>Step 3:</td>
<td colspan=2>With binary editor or Copy command, append the PAR2 file to the archive file.
Then, the appended archive file contains recovery record.
The construction of the file is like below;
</td></tr>
<tr>
<td colspan=3 align="center"><table border=1 cellspacing=0 cellpadding=2>
<tr><td bgcolor="FFE0E0">Original archive file</td><td bgcolor="E0E0FF">Appended PAR2 recovery data</td></tr></table>
</td></tr>
<tr><td colspan=3><br>Step 4 is required only for ZIP archive:</td></tr>
<tr><td></td><td colspan=2>
There is "end of central directory record" (starting with a byte sequence of: 0x06054b50) at the end of ZIP file.
With binary editor, copy the section (22-bytes or more) and append it to the end of recovery data.
The construction of the file is like below;
</td></tr>
<tr>
<td colspan=3 align="center"><table border=1 cellspacing=0 cellpadding=2>
<tr><td bgcolor="FFE0E0">Original ZIP archive file</td><td bgcolor="E0E0FF">Appended PAR2 recovery data</td>
<td bgcolor="FFE0FF">End of central directory record</td>
</tr></table>
</td></tr>
<tr><td></td><td colspan=2><br>
When the ZIP file is ZIP64 format,
there are "zip64 end of central directory record" (starting with a byte sequence of: 0x06064b50),
"zip64 end of central directory locator", and "end of central directory record" at the end of ZIP file.
With binary editor, copy the 3 sections (total 98-bytes or more) and append them to the end of recovery data.
</td></tr>
<tr>
<td colspan=3 align="center"><table border=1 cellspacing=0 cellpadding=2>
<tr><td bgcolor="FFE0E0">Original ZIP64 archive file</td><td bgcolor="E0E0FF">Appended PAR2 recovery data</td>
<td bgcolor="FFE0FF">The final 3 sections of ZIP64 format</td>
</tr></table>
</td></tr>
</table>
</p>
<p>&nbsp
Because the file header is still the one of archive, it's treated as an archive file,
and normal archiver software can extract inner files.
Because the file contains PAR2 packets, PAR2 client can treat it as PAR2 file also.
As MultiPar can treat a PAR2 file which has different extension from "<tt>.par2</tt>",
Drag&Drop the protected archive onto MultiPar short-cut icon will verify the archive file.
On the MultiPar GUI, the archive with recovery record is shown as "Appended" status,
when the original part of archive is complete.
</p>
<p>&nbsp
Note, if you repair the archive,
recovery record (appended PAR2 recovery data) will be removed.
When you want to keep the PAR2 recovery data,
you need to copy the file at first, and rename it to "<tt>something.par2</tt>",
then open the "<tt>something.par2</tt>" by MultiPar (or QuickPar).
Though you can split a protected archive into original part and recovery record by a binary editor,
it's not easy task for normal users.
</p>
<p>&nbsp
I think this method is useful to protect only one archive file.
It is same as having two files (an archive file and its PAR2 file),
but is convenient for transport / public / distribution as one ZIP/7-Zip file.
Normally freeware/shareware publication site accepts only one archive file.
If an archiver software has a built-in feature to append PAR2 recovery data to a created archive,
it may be useful.
</p>
</body>
</html>

View File

@@ -0,0 +1,161 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Recreate window</title>
</head>
<body>
<font size=5>Recreate window</font><br><font size=1><br></font>&nbsp
When you push "Extra" button on <a href="verify.htm">Verify window</a>, this window opens.
While Recreate window is alomst same as Create window, you cannot change source files.
<hr>
<h3>Source files</h3>
<p>&nbsp
The directory and selection of source files are same as the original recovery file.
Selected files are listed on the file-list, and the total data size and blocks are calculated.
You cannot change the block allocation, too.
</p>
<hr>
<h3>Recovery files</h3>
<dl><dt><b>
Base Filename
</b></dt><dd>&nbsp
If you don't want to over-write original files, you may change to a different name.
</dd></dl>
<dl><dt><b>
Comment</b> button
</dt><dd>&nbsp
You can enter newly, or you may change the previous comment.
</dd></dl>
<dl><dt><b>
Redundancy
</b></dt><dd>&nbsp
"Redundancy" is a rate of how much damage can be recovered.
For example, if you set 10% for source files of 500MB,
you will be able to recover damage or lost upto 50MB.
<b>Caution</b>, actual possibility of recovery depends on the distribution of damage.
In general, while dense damage in narrow area may be recovered with small redundancy,
sparse damage over wide area requires larger redundancy.
When you set 0%, only an index file to verify will be created.
</dd></dl>
<dl><dt><b>
First recovery block number
</b></dt><dd>&nbsp
If you want to add extra recovery blocks to the original recovery files,
by setting this starting number,
you can create recovery files from the previous block.
If this value is 0, all recovery blocks are recreated from first block.
</dd></dl>
<dl><dt><b>
Number of Recovery blocks
</b></dt><dd>&nbsp
You may input the number of recovery blocks directly.
You can set more blocks than the range of redundancy slider.
</dd></dl>
<dl><dt><b>
Sizing scheme</b> and <b>Number of recovery files
</b></dt><dd>&nbsp
"Sizing scheme" is how are the size of recovery files.
When "<b>All the same size</b>" or "<b>Variable size</b>" is selected,
you can set the number of recovery files.
Then, the specified number of recovery files of same size or different size will be created.
When "<b>Powers of 2 sizing scheme</b>" or "<b>Decimal weights sizing scheme</b>" is selected,
the number of recovery blocks in each recovery file will be
"1, 2, 4, 8, 16, 32, 64, 128..." or "1, 1, 2, 5, 10, 10, 20, 50...".
In the later two scheme, size of a recovery file is limited to size of the largest source file.
</dd></dl>
<p>&nbsp
Sample distribution of 500 blocks for each sizing scheme:<br>
<center><table border=1 cellspacing=0 cellpadding=2 width="98%">
<tr bgcolor="E0F0E0"><th>Sizing scheme<th colspan=2>How many blocks in each recovery file
<tr><td>All the same size<td>167, 167, 166 (when 3 files)<td>84, 84, 83, 83, 83, 83 (when 6 files)
<tr><td>Variable size<td>72, 144, 284 (when 3 files)<td>8, 16, 32, 64, 128, 252 (when 6 files)
<tr><td>Powers of 2 sizing scheme<td colspan=2>1, 2, 4, 8, 16, 32, 64, 128, 245 (total 9 files)
<tr><td>Decimal weights sizing scheme<td colspan=2>1, 1, 2, 5, 10, 10, 20, 50, 100, 100, 200, 1 (total 12 files)
</table></center>
</p>
<dl><dt><b>
Efficiency
</b></dt><dd>&nbsp
This is a rate of how much data the recovery files can recover.
For example, when the efficiency is 95% for recovery files of 200MB,
you will be able to recover upto 190MB.
</dd></dl>
<dl><dt><b>
Number of files that can be fully reconstructed if missing (Min - Max)
</b></dt><dd>&nbsp
You may refer these values to know the recoverying capability of recovery files.
When sizes of source files are largely different, recovering a file may require more redundancy than you thought.
</dd></dl>
<hr>
<dl><dt><b>
Open</b> button
</dt><dd>&nbsp
If you want to open an existing recovery file, push this to select which.
The current setting over Recreate window is not saved.
</dd></dl>
<dl><dt><b>
Exit</b> button
</dt><dd>&nbsp
You can close MultiPar by pushing this.
Be careful, because there is no warning before exit.
The current setting over Recreate window is not saved.
</dd></dl>
<dl><dt><b>
Options</b> button
</dt><dd>&nbsp
If you want to change settings, push this, then <a href="option.htm">Option window</a> will appear.
</dd></dl>
<dl><dt><b>
About</b> button
</dt><dd>&nbsp
By pushing this, you can see version number on About window.
You may launch this Help from there.
</dd></dl>
<dl><dt><b>
Preview</b> button
</dt><dd>&nbsp
If you want to know the size of each recovery file,
you can see <a href="preview.htm">Preview window</a> by pushing this.
</dd></dl>
<dl><dt><b>
Create</b> button
</dt><dd>&nbsp
After you selected source files and done every setting,
you push this to create recovery files.
<a href="creating.htm">Creating window</a> will open to show the progress.
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>

View File

@@ -0,0 +1,5 @@
* {
line-height:1.7;
text-underline-position:under;
}

View File

@@ -0,0 +1,21 @@
* {
line-height:1.7;
text-underline-position:under;
}
body {
padding: 0px 0px 0px 170px ;
}
div#left_area {
position: fixed !important;
position: absolute;
padding: 0px 0px 0px 10px ;
top: 0;
left: 0;
width: 160px;
height: 100%;
background-color: #fffbf0 ;
overflow: auto;
}

182
alpha/help/0409/verify.htm Normal file
View File

@@ -0,0 +1,182 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" href="style_panel.css">
<title>Verify window</title>
</head>
<body>
<font size=5>Verify window</font><br><font size=1><br></font>&nbsp
When you start MultiPar by selecting a recovery file, this window opens and verification is started.
You see which files are damaged or lost, and you can repair them if there is enough recovery data.
If you want to verify again newly, push "<b>F5-key</b>".
When multiple instances of MultiPar are running,
it waits finish of another instance's task, and will start next.
<hr>
<dl><dt><b>
Base directory</b> and <b>Browse</b> button
</dt><dd>&nbsp
This directory is the folder where source files exist.
If source files exist in a different folder from where recovery files exist,
all source files are treated as lost.
Then, you must select the folder by clicking "Browse" button,
Drag & Drop a folder, or double-click the path box.
</dd></dl>
<dl><dt><b>
Creator</b> and <b>Comment</b>
</dt><dd>&nbsp
"Creator" is a name of PAR client which was used to create the selected recovery file.
When a comment is saved in the file, it is shown, too.
</dd></dl>
<p>&nbsp
On the file-list, recovery files are put on upper side,
and source files are put on lower side.
Because Size and Status of each file are shown,
it is easy to know which is incomplete.
Total size and number of total blocks are shown, too.
</p>
<p>&nbsp
After verification, the result like number of files on each status is shown.
When source files are damaged or lost,
you can know whether it is possible to repair or not.
You may recognize the status easily by their icon color.
<font color="#009000">[green file]</font> indicates the file is complete.
<font color="#807800">[yellow file]</font> indicates the file is damaged or misnamed.
<font color="#C00000">[red file]</font> indicates the file is missing.
<font color="#807800">[yellow folder]</font> indicates the folder exists.
<font color="#C00000">[red folder]</font> indicates the folder is missing.
Manually added external files are shown as [white file].
</p>
<hr>
<dl><dt><b>
Display of progress
</b></dt><dd>&nbsp
Window title indicates which step now,
and Progress bar indicates the current position in the step.
Because there are some steps, bar moves sometimes until the whole process complete.
</dd></dl>
<dl><dt><b>
Meter of found blocks
</b></dt><dd>&nbsp
On the meter, each area represents the number of blocks by width;
<font color="#009000">[green area]</font> indicates available source blocks,
<font color="#807800">[yellow area]</font> indicates recoverable source blocks,
<font color="#C00000">[red area]</font> indicates how many blocks are lacking.
At a glance, you see how many blocks are lost, and you need how many blocks to repair.
</dd></dl>
<dl><dt><b>
Area of status text
</b></dt><dd>&nbsp
When you see an error message, the error is saved in log file.
Double-click here, then "<tt>save</tt>" folder will be opened.
</dd></dl>
<dl><dt><b>
Time left
</b></dt><dd>&nbsp
This is a required time to finish.
You may need to wait longer than this time, because the calculation is rough.
</dd></dl>
<hr>
<dl><dt><b>
Add</b> button
</dt><dd>&nbsp
By pushing this button or Drag&Drop files on list, you can add other files to be verified.
If you want to add external files out of base directory or recovery file's directory,
you need to add them by yourself.
The list of added files will be reset by selecting a new recovery file or changing base directory.
When you want to add all files under the base directory,
you would better set "<a href="option3.htm#verification_level">Verification level</a>" to "Additional verification".
</dd></dl>
<dl><dt><b>
Pause</b> or <b>Resume</b> button
</dt><dd>&nbsp
You may pause the process temporary by pushing "Pause" button.
While pausing, you can resume the process at the point by pushing "Resume" button.
You may push "<b>Pause-key</b>" to pause or resume, too.
</dd></dl>
<dl><dt><b>
Repair</b>, <b>Restore</b>, <b>Rename</b>, or <b>Verify</b> button
</dt><dd>&nbsp
You push this button to start verify and repair if possible.
The caption is varied by recovering beavior.
When total repair is possible, it's "Repair".
When easy correction and/or rejoin is possible, it's "Restore".
When rename is possible, it's "Rename".
When repair is impossible at all, it's "Verify".
</dd></dl>
<dl><dt><b>
Cancel</b> button
</dt><dd>&nbsp
If you want to cancel the verification or repair, push "Cancel" button.
You may push "<b>Escape-key</b>" to cancel, too.
</dd></dl>
<dl><dt><b>
Extra</b> button
</dt><dd>&nbsp
If you want to create extra recovery files or recreate recovery files against the same set of source files in the current recovery file,
push this to open <a href="recreate.htm">Recreate window</a>.
<b>Caution</b>, newly created files will overwrite existing files of same name.
</dd></dl>
<hr>
<dl><dt><b>
Open</b> button
</dt><dd>&nbsp
If you want to open another recovery file to verify, push this to select which.
If the selected file would not be recognized as a supported file,
you should set proper file extension for the file type.
</dd></dl>
<dl><dt><b>
New</b> button
</dt><dd>&nbsp
If you want to create new recovery files, push this to open <a href="create.htm">Create window</a>.
</dd></dl>
<dl><dt><b>
About</b> button
</dt><dd>&nbsp
By pushing this, you can see version number on About window.
You may launch this Help from there.
</dd></dl>
<dl><dt><b>
Options</b> button
</dt><dd>&nbsp
If you want to change settings, push this, then <a href="option.htm">Option window</a> will appear.
</dd></dl>
<dl><dt><b>
Exit</b> button
</dt><dd>&nbsp
You can close MultiPar by pushing this.
</dd></dl>
<div id="left_area">
<p><a href="index.htm">Help for MultiPar</a></p>
<a href="create.htm">Create window</a><br>
<a href="preview.htm">Preview window</a><br>
<a href="creating.htm">Creating window</a><br>
<a href="verify.htm">Verify window</a><br>
<a href="recreate.htm">Recreate window</a><br>
<a href="option.htm">Option window</a>
</div>
</body>
</html>