QuickPar 0.8 Release Notes (January 27, 2004) Top
Bugs fixed  
  • If an error occured during the creation of PAR2 files or whilst using them to repair data files, the error would not be correctly reported. This is especially noticeable if a repair fails as QuickPar would simply say that it was ready to repair again.
  • Some of the International versions of QuickPar did not include the Windows Common Control manifest. This meant that they failed to use Windows XP Themes.
  • When verifying data files (especially if monitoring a download), if the newsreader software modified a file just as QuickPar was about to scan it, the scan would fail and QuickPar sometimes failed to make further attempts to scan that file. Under those circumstances it was necessary to use F5 to force a rescan.
  • Creating PAR2 files from data files on a network patch should now work correctly.
Changes  
  • When creating PAR2 files and when using them to repair damaged data files, QuickPar will attempt to detect data corruptions caused by faulty memory. It does this by carrying out write/read tests on the memory buffers it uses, and confirming that checksums for recovery data match values that are precomputed.
  • After verifying data files, if the only problem detected is that some files have the wrong filename, then QuickPar will tell you how many files are incorrectly named, and relable the "Repair" button to "Rename".
  • After verifying data files, if all data blocks have been found but some of the data files do not verify correctly (possibly because the file set has been split), then QuickPar will tell you how many files are affected and relable the "Repair" button to "Rejoin".
  • In the verification dialogue, the "Clear" button has been removed and replaced by the "Open" button. The original (dual use) "Open/Add" button is now used only as the "Add" button.
  • QuickPar can now open and use .MD5 and .SFV files to verify data files. When using these files, QuickPar will not list the file size of any data file. It will also not automatically search for missnamed versions of any files. You must use the "Add" button to have QuickPar check missnamed files.
  • In the PAR2 creation dialogue, QuickPar now calculates and displays the total size of the resulting PAR2 files instead of the size of the recovery data within the PAR2 files.
  • The efficiency rating displayed when creating PAR2 files has been updated so that it shows the effect of both file size to block size rounding and the overhead caused by packet headers and verification data in the PAR2 files. This means that the displayed efficiency rating will drop if you use either very large or very small block sizes.
  • When verifying data files in a folder with many unrelated files, QuickPar should avoid scanning files unecessarily.
  • The About dialogue now includes clickable hyperlinks.
  • Italian and Danish have been added to the list of localised versions. Thanks to Armando La Mura and Jens Hyllegaard for their assistance in translating the text.
Known problems  
  • Unchanged.

QuickPar 0.7.5 Release Notes (October 19, 2003) Top
Bugs fixed  
  • If someone creates extra par2 files from a damaged set of source files and the damage was beyond the first 16k of the file, then the par2 set would have the same set-hash-id. QuickPar would mistakenly use the par2 files created from the damaged and undamaged source files when attempting to repair. Such repairs would of course fail. QuickPar now detects this and will report the extra par2 files as damaged.
Changes  
  • Localised versions of QuickPar are now available in Dutch, French, German, Norwegian, Portugese, Spanish, and Swedish. Thanks to Etraman, Stefan Pleiner, Thore Harald Høye, Stéphane Simson, José Mira, Imanol Espasa, and Fabian Siegel for their work in translating the text. Anyone willing to assist in the creation of versions for other languages should let me know (email me at sourceforge - you'll find my address on the parchive home page).
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 and 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. This problem also occurs if you use the Add button to add par2 files that do not belong to the set.

QuickPar 0.7 Release Notes (September 24, 2003) Top
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 par1cmdline 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.
  • When creating par2 files, if the block size is set too large the efficiency rating may drop. If the limit drops below a limit (set in the Options dialogue) warn the user when the Create button is pressed.
Changes  
  • When verifying, par1 files whose base name is different from the first par file will be automatically detected and loaded.
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 and 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. This problem also occurs if you use the Add button to add par2 files that do not belong to the set.

 

Copyright © 2003 Peter B. Clements. All Rights Reserved.