Client Update: QuickPar v0.7 avail.

Version 0.7 of QuickPar is now available for everyone to download.

Please visit http://www.pbclements.co.uk/QuickPar/ to download the
new version.

The list of bug fixes and other changes since version 0.6 are as
follows:

Bugs fixed:

* When verifying a set of files in the same folder as a previous set
with the same base filename, QuickPar would mistakenly use cached
information from the previous verification and the recovery files
would be ignored.
* Verifying using par1 files created by par1 programs that list non
recoverable files only in the .PAR file is now possible.
Previously QuickPar required that the file lists in all par files
be identical.
* After verifying files, if you click the "New" button to create
more par2 files, the window would open with an incorrect size (and
could not be resized).
* If you create a set of par2 files in a folder and verify it and
then create a second set of par2 files in the same folder with the
same filename, QuickPar will mistakenly use the information in the
cache file from the first par2 set. QuickPar now deletes the
existing cache file when creating new par2 files.
* When verifying par2 files, if the par2 client name was an exact
multiple of 4 characters in length it would not display correctly.

Changes:

* When verifying, par1 files whose base name is different from the
first par file will be automatically detected and loaded.

Feature Requests:

* Include option to allow the limit for par2 files to be set to the
average data file size instead of the largest data file size.
* When repairing, if there is no small .par2 file, create one.
* Automatically verify after par2 files have been created (with
option to not do so).
* The ability to include non-recoverable files when creating PAR2
files.
* Allow auto-repair to be set by default.
* Add option to not cache the results of verification.
* Add option to place all of the critical packets in a par2 file
that has recover blocks at the end of the file (in which case if
the end of the file is damaged, verification and repair would not
be possible unless copies of the critical packets can be obtained
from another par2 file). Possibly include a variation to not
include any critical packets at all (this would again require the
critical packets to be obtained from another source).
* Add the ability to handle the same command line options that
par2cmdline uses.
* Add automatic check for new versions (or reminder telling user
their version is "out of date").
* Permit the selection of Folders when using the shell context menu
in Windows Explorer.
* Store and use path information in the PAR2 files so that files in
subfolders can be correctly found and repaired.
* Add the ability to queue PAR creation requests so that they will
be processed one after another in the background.
* Ensure that only one copy of QuickPar is running so that
simultaneous create/verify tasks do not compete with each other
for CPU time.
* Add the ability to "pause" PAR creation, save the intermediate
results to disk and resume later.
* Allow drag selection and use of the delete key in the listbox when
selecting the files to create recovery data file.
* Support Unicode filenames.
* Support reading from partly unreadable files (e.g. a file on a CD
with a scratch).
* Allow the selection of an alternate location to put repaired files
(e.g if the originals are on CD).
* Remember the actual compute speed achieved and use that when
displaying the estimate when choosing the options for a new PAR2
file. QuickPar currently makes a speed estimate on startup and
uses that.
* Add an option to always store the cache files with the recovery
files.
* When repairing, ensure that files are read in the reverse order
from that which they were verified to maximise the chance that
there data will still be in the Windows' file cache.

Known Problems:

* Yenc PowerPost 2000 A&A version 10A creates .par and .par2 files
with invalid MD5 Hash values. When QuickPar tries to use them to
verify the associated data files, some of the data files may be
reported as invalid when they are not damaged. Such files will
still be reported as damaged after a repair attempt.
* If two sets of par2 files with the same base filename are placed
in one folder, then QuickPar does not indicate in the file list
which ones belong to which set and the total recovery block count
displayed there will be incorrect. In the lower display, QuickPar
does give the correct number of recovery blocks required (if there
are not enough) and repair works correctly.

Please use the Tracker at Sourceforge to report problems:

http://sourceforge.net/tracker/?func=add&group_id=30568&atid=560745

Please use the forums at PArchive for any other feedback and
discussions.

http://sourceforge.net/forum/?group_id=30568