Menu ▾ ▴

Included Par2.exe issues

2006-10-10
2013-04-25
  • S. Jamison Wilde

    If you are having problems with repairs using the included par2.exe ('repair completed but the files still appear damaged'), I am looking into this.  I have recompiled par2.exe with Visual Studio 2003 instead of 2005, and that seems to help. I will be making another release with this version shortly.

    There is another bug in par2.exe where files that get joined using the par2 repair will give this message even though the repaired and joined file is actually fine.  (For example files like my_show.ts.001, 002, 003 that when they are repaired in par2 or QuickPar just end up with a file called my_show.ts)  Not sure if I will be able to fix that one or not.

     
    • S. Jamison Wilde

      An Update:

      I have removed my patched version of par2.exe and am just including the standard par2.exe that comes from the parchive.sourceforge.net download.

      Simply put, I am unable to get a version of par2.exe to compile that actually works from the source zip that is downloadable from there as well.  And unfortunately the current CVS version is linux only due to some linux only threading that was added with no attempt at cross platform support.

      When I compile par2, I get an identically sized file, but not an identical file. I am going to try to compile it on a virgin box soon, to see if that makes a difference. Or I may statically link the C/C++ libraries to see if that helps.

      But for all intents and purposes both par2 and QuickPar are abandoned projects it would seem.

       
    • S. Jamison Wilde

      I've found that the version 0.2 of par2cmdline actually works fine, so if you are having troubles, install that version in the ExQueues folder instead.   I will probably cut a release with that version.

      Note: par2.exe doesn't like joined files when repairing, ie.  some files are released as one large file that has been spilt into .001, .002 etc files that are NOT a RAR archive.  Par2.exe will successfully repair these, but its verify after will result in the 'files still appear to be damaged' message. Since I am unable to compile a working version of par2cmdline there's not much I can do about that.

      Anyway, this should help out a lot.
      http://prdownloads.sourceforge.net/parchive/par2cmdline-0.2.x86.win32.zip?download

       
    • S. Jamison Wilde

      Ok, so scratch all that lol.  I finally think I know what the issue is.  It has to do with how I am calling par2.exe. 

      For a parset called archive.par2, I am calling it with archive.* so pick up files that may need to be joined or have been misnamed slightly.  However, this  is causing problems because par2 tries to open the files twice and doesnt realize that one of the archive.* files has actaully been renamed for repair.

      Anyway, I should have a solution soon, though it may be at the cost of being able to handle joined file repairs (where the repair joins a bunch of 001, 002 files into one).  Par2,exe doesnt find the 00# files...

       
    • S. Jamison Wilde

      The latest version appears to solve all of the par2.exe issues. Thank god

       

Log in to post a comment.