Release note of v1.2.0 tree

[Yutaka Sawada]

 Because I changed many points, there may be some bugs, even though I tested most usage. If you find bug, problem or something odd behavior, please notice me. Some new text on GUI are not translated yet, as I would change them more.

 In this release, sample PAR3 isn't available by default, as the specification is being updated. For backward compatibility, I put PAR3 client of old spec (par3j_old.exe) in "tool" folder. If you want to use old PAR3 files, rename par3j_old.exe to par3j.exe and move in the parent folder.


[ Changes from 1.1.9.6 to 1.2.0.0 ]

* GUI update
Bug fix at Create window
 A failure of updating changed text in Edit-Box before selecting Create/Preview/Fit button by short-cut key was fixed.

Bug fix at Verify window
 A fault in updating file-list after joining splited files was fixed.
 A failure of updating some numbers on file-list while verification was fixed.
 A failure of showing property-dialog for an external file in different directory was fixed.

Improvement
 When a log file becomes too large, next output is saved in another log file. (MultiPar.#.log)
 MultiPar.ini file is encoded by Unicode.

Improvement at Create window
 When a user types an extension for PAR2 file like ".par2" in "Base Filename" box,
it is removed automatically in the edit-box, because the standard extension will be added later.
 When a filename is too long at searching, the relative-path of the file is shown to a user.

Improvement at Verify window
 Batch script after Verification/Repair gets Exit code as "%3" parameter.
 It is possible to set a period of re-using results of previous verification.

New
 Simplified Chinese language UI (translated by Donghui Li) is added.
 It is possible to erase all log files by pushing a button on Option window.

New at Verify window
 While scanning files at verification, each filenames are shown.

* Client update
Bug fix
 A failure of sending a broken file to Recyle-Bin was fixed, when some data is appended to the file.
 A fault in detecting blocks in a broken file was fixed.
 A fault in sanitizing invalid filename was fixed.
 A failure of detecting splited files with sub-directory was fixed.
 A failure of showing wrong status as missing for a broken file was fixed.
 A failure of using broken parity blocks for recovery in par3j.exe was fixed.

Improvement
 Result message and Exit code of each PAR clients becomes easier to understand.
 Splited files with double numbering extension are not scaned twice.
 A usability of re-using previous verification results is refined.

New
 SFV/MD5 client supports re-use of previous verification results.
 Repaired files will inherit some attributes of their broken files.


[ Hash value ]

MultiPar1200.7z
MD5 : 2D6282A209A7A012F505A11C5A89999E
SHA-1 : 492947187FDCF8727105A639ACAF97005ECF8FA2

MultiPar1200_setup.exe
MD5 : CD0019668A4F1034D069E4CA64A72409
SHA-1 : 5DDE2E299809A46A54A64348BD47BC6C6999ADF6

[badon]

Thank you for another excellent release!

[The_Great_Beast]

will old par3 files be backwards compatible with the new par3 specification, or if not could there be a detection method within multipar telling it what par3 version to use, or will there be any output telling the user they must use an older version?

[offthewall]

thanks for the new release. i'm also curious about backward compatibility and if possible, it would be a dream come true to utilize that feature without user interaction

[Yutaka Sawada]

from The_Great_Beast

will old par3 files be backwards compatible with the new par3 specification

 No, it will not. I will change the format of packet header.

could there be a detection method within multipar telling it what par3 version to use

 I have no plan yet. I may try, if the method is not so complex.

will there be any output telling the user they must use an older version?

 If I don't add any special feature for compatibiliy, it cannot recognize the old file as a proper recovery file, and it will just say "The specified file is not valid.".

[The_Great_Beast]

Any reason why you could not just call the new specification "par4" and have it be an entirely different entity on its own with a similar .pa4 extension with its own par4j.exe? That may be a viable solution to the compatibility issue. as far as I know nobody has any 'trademark' on par, par2, or any other recovery names/ extensions, you could vary-well call it whatever you like.

No matter what you shall decide, I will continue to enjoy using multipar and testing out all of your contributions, thanks.

[badon]

Par3 should only be used for testing, since not even the specification was ever ready for production use. I only use par2 for my important things, and just play around with par3 from time to time.

[The_Great_Beast]

Par3 should only be used for testing, since not even the specification was ever ready for production use. I only use par2 for my important things, and just play around with par3 from time to time.

yes of course, I always keep a copy of multipar with the data I have used par3 on. Mostly backup dvd-rs.

[William Berzoff]

yes of course, I always keep a copy of multipar with the data I have used par3 on. Mostly backup dvd-rs.

Ofcourse testing Par3 and reporting your findings will help advance the development sooner...

[Yutaka Sawada]

At first, my PAR3 sample application is just a suggestion of new specification and working sample to test new feature. I public / update / modify those samples sometimes. The specification has been changed 4 or 5 times without compatibility. I put a notice "Caution" subject on readme / help of MultiPar. Because I know that mine is not complete, I recommend to use par2_tbb or RSC32, when someone requests speed. I did not finish my PAR3 proposal yet and want to complete it. Just the development is very slow... this is my defect, I am sorry.

[Yutaka Sawada]

 While some users don't know how to perform queue task, I wrote sample batch scripts in help. It is "Batch script" subject on manual, and "batch.htm" file in help folder. Though I am not a specialist of batch processing, I learn and write as possible as I can. Before ask/request about automatic task/job, you should read the page. You may write your own batch script easily by modifying my samples.

 I changed the process of verification in par2j.exe. In this new version, "searching blocks in a broken file" is started from a damaged block, which was found by "checking a complete file". While this method may increase speed for very large broken files, it might cause unknown bug in un-tested setting. If you find bug at verification in any setting, please notice me.


[ Changes from 1.2.0.0 to 1.2.0.1 ]

* GUI update
Improvement
 Shell Extension DLL tries not to use file-list as possible as it can.
 Shell Extension DLL contains Chinese text.

* Client update
Bug fix
 At creation, supplied PAR filename is checked not to contain invalid characters.

Improvement
 It is possible to set partial filename with "*" or "?" for wildcard matching at verification.
 In PAR2 client, verification speed for large broken files becomes faster.


[ Hash value ]

MultiPar1201.7z
MD5 : 5DB13384ED6ADB400C255CA1F767E707
SHA-1 : 7B6B0D38BD72144F6236DA64105420CA6E9FBE35

MultiPar1201_setup.exe
MD5 : DD8B8C8AAAB7AE249266A3D261A2D1F1
SHA-1 : 602AE018EC35F092D9FC3DD6360BB60A70968D5C

[mictlan]

par2j randomly crashes on file verification:


Problem signature:
  Problem Event Name:   BEX
  Application Name:   par2j.exe
  Application Version:   0.0.0.0
  Application Timestamp:   4f3c6b2d
  Fault Module Name:   StackHash_e98d
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Offset:   00000000
  Exception Code:   c0000005
  Exception Data:   00000008
  OS Version:   6.1.7601.2.1.0.768.3

[Yutaka Sawada]

par2j randomly crashes on file verification:

 Some users reported this bug; Buffer Overflow Exception. I found that there was a chance of buffer over-run (stack overflow) in v1.2.0.1's par2j.exe. It is happened, when a source file is smaller than 16KB, and block size is over 64KB larger than the file size. I fixed this problem and post the fixed version here. Please test with this.

 If your case does not match my description, and you get crash problem still, write details of your incident.

[mictlan]

Thx.

Will reinstall 1.2.0.1 with updated par2j and report back!

[mictlan]

Did a full retest on all files were previous par2j crashed:
With build par2j_2012-02-21 no crashes occur.
All is ok!

Thx for the fix!!!

[Yutaka Sawada]

 This is an emergency update only to solve problem of par2j.exe. As I wrote a thread of previous version, the crush problem was happened, when a source file is smaller than 16KB, and block size is over 64KB larger than the file size. I public this new package which contains the fixed version of par2j.exe, because fixed version is downloaded many times. (I did not think that many users use so small file with larger block size...) If someone find other bugs, please let me know.


[ Changes from 1.2.0.1 to 1.2.0.2 ]

* GUI update
Improvement
 The size of recovery data is tested before actual creation at Extra (Re-create) window.

New
 French language UI is added.

* Client update
Bug fix
 A crush problem while verifying very small files (less than 16KB) is fixed.


[ Hash value ]

MultiPar1202.7z
MD5 : 247216D239FD03580527A330FB4F196C
SHA-1 : ED3DD8C5D5199FA1C178D36B428F05224629CDA1

MultiPar1202_setup.exe
MD5 : 2BDDC9A23E8B74FBE8AEE2E78C996E51
SHA-1 : F7C030E8A22624722F266A7C448411A174FB31A7

[Yutaka Sawada]

 While I changed many point of MultiPar GUI, I don't know how it looks on Windows Vista/7. If something is odd, please let me know the problem. Some new text on GUI are not translated yet, as I would change them more.


[ Changes from 1.2.0.2 to 1.2.0.3 ]

* GUI update
Improvement
 Some status text after verification is changed for easy distinction.
 File-list on Verify window looks a little more obvious.
 Small icons (16*16) were refined.
 When a progress was ended by Cancel or Error, the result is shown on Title-bar.
 The state of "Pause" and "Monitor" are shown at the right of "Elapsed time" obviously.

* Client update
Bug fix
 A fault of accepting input files of same filename as the creating PAR files was fixed.

Improvement
 Because it is difficult to distinguish some incomplete status, they are shown as "Damaged".
 When a PAR2 file does not contain valid packet of the Recovery Set, the file is shown as "Useless".
 If SFV/MD5 checker gets IO Error while verifying a file, the file becomes "Damaged" status.
 The existence of missing files are noted in exit code of SFV/MD5 checker.
 At creating PAR files, the default extension is appended automatically, unless it exists.

New
 If you don't set [input files] to create PAR2 files, the filename of <par file> without extension will be used as a single input file.


[ Hash value ]

MultiPar1203.7z
MD5 : C5D6CB21A7F8CF0FB91584D8EFE2A64D
SHA-1 : 7CE3B72D05BFFE13601754DCFBCA3ADFC245C27D

MultiPar1203_setup.exe
MD5 : E94320DB72C6C197DFB2892381B273DA
SHA-1 : 7FE0A1024CB0610140A781F2845458E48A6C3D0D

[badon]

Another great release, thanks! There are about 400 downloads already. I remember when I would get excited when there were 30 or 40 downloads :)

[Yutaka Sawada]

 There were many small updates, and too long period from the last v1.1.9. Next version 1.2.0.5 will be the last release of v1.2.0 tree. I plan that next version is minor update only, like translate some new text. Though I am making a new PAR3 sample application a little, I need to test many things. I will concentrate PAR3 after releasing of stable version. (until someone find serious bug, hehe.)


[ Changes from 1.2.0.3 to 1.2.0.4 ]

* Installer update
 Chinese and French are possible to select as installation language.

* GUI update
Bug fix
 When a client happens to end while a user attempt to pause, GUI will resume and parse remaining output.
 A wrong status text on block-rate-bar after verification which ignores misnamed/moved files was fixed.

Improvement
 Option window doesn't use a default title-bar text of Property-Sheet dialog.
 RGB color of item index on file-list differs from background color by 16 or more.
 When a client runs very fast, GUI doesn't wait 1 second at the first/last update.

* Client update
Bug fix
 When creating recovery blocks by setting first block number, the total block count is checked properly.
 A fault of accepting pause/cancel after terminated loop was fixed.

Improvement
 SFV/MD5 client supports one more MD5 file format, which may be common over UNIX.


[ Hash value ]

MultiPar1204.7z
MD5 : 994D6B19038430ADFBCC8459AA044994
SHA-1 : A2F9B89026B727C2692C702A1261B074CF5CE913

MultiPar1204_setup.exe
MD5 : 9402A6CF7B5D661DE8F9CB652103E621
SHA-1 : 0D38D08A0B6500D7C4E87B832FD2DF1015E30E65

[Yutaka Sawada]

 This is the last release of v1.2.0 tree. Both ZIP archive version and Installer version are downloadable from official download page.


[ Changes from 1.2.0.4 to 1.2.0.5 ]

* GUI update
Bug fix
 When a client process was terminated by an unhandled exception, GUI shows a status of failed result.
 If a file exists in file-list already on Verify window, the file cannot be added as a new external file.

Improvement
 A color of item index on file-list is made from a background color of dialog-box.
 A status text of deleting recovery files was removed, because the progress is too fast to see.
 When a specified recovery file don't have a standard extension, recovery files will not be deleted automatically after repair.
 An useless recovery file like wrong set will not be deleted automatically after repair.

* Client update
Bug fix
 It is possible to remove appended recovery data from a source file, even when there are other recovery files.

Improvement
 SFV/MD5 client supports MD5 file format of BSD/OpenSSL.


[ Hash value ]

MultiPar120.zip
MD5 : 1DC452F92895F6D09740EB6A4C069378
SHA-1 : 48B24659242F40A93F47DBDD49C591E841597F54

MultiPar120_setup.exe
MD5 : 33E434680727864E09A457552B358CD7
SHA-1 : 45D6E23B3D188F1B2069F4B9F3FC8091BB755E69

[somdofritz]

ERROR-ERROR-ERROR-ERROR-ERROR-ERROR-ERROR!!!


<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="MultiPar.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="MultiPar.exe" SIZE="248832" CHECKSUM="0x177EF928" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="MultiPar.exe" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="04/10/2012 09:18:22" UPTO_LINK_DATE="04/10/2012 09:18:22" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="MultiParShlExt.dll" SIZE="53248" CHECKSUM="0x23CE3E87" BIN_FILE_VERSION="1.2.0.1" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="32-bit Shell Extension for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.1" ORIGINAL_FILENAME="MultiParShlExt.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xEC3F" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.1" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="02/12/2012 14:57:37" UPTO_LINK_DATE="02/12/2012 14:57:37" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="MultiParShlExt64.dll" SIZE="59392" CHECKSUM="0x336F062F" BIN_FILE_VERSION="1.1.9.1" BIN_PRODUCT_VERSION="1.1.9.1" PRODUCT_VERSION="1.1.9.1" FILE_DESCRIPTION="64-bit Shell Extension for MultiPar" FILE_VERSION="1.1.9.1" ORIGINAL_FILENAME="MultiParShlExt.dll" LEGAL_COPYRIGHT="Copyright (C) 2011 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x10869" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.1.9.1" UPTO_BIN_PRODUCT_VERSION="1.1.9.1" LINK_DATE="07/15/2011 19:47:22" UPTO_LINK_DATE="07/15/2011 19:47:22" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="par1j.exe" SIZE="83456" CHECKSUM="0x77B00C34" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="04/02/2012 06:27:06" UPTO_LINK_DATE="04/02/2012 06:27:06" />
    <MATCHING_FILE NAME="par2j.exe" SIZE="160768" CHECKSUM="0xB6C213BC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="04/10/2012 07:58:45" UPTO_LINK_DATE="04/10/2012 07:58:45" />
    <MATCHING_FILE NAME="par3j.exe" SIZE="180736" CHECKSUM="0x26009682" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="11/09/2011 04:31:37" UPTO_LINK_DATE="11/09/2011 04:31:37" />
    <MATCHING_FILE NAME="sfv_md5.exe" SIZE="65536" CHECKSUM="0xCB65B10F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="04/05/2012 03:12:24" UPTO_LINK_DATE="04/05/2012 03:12:24" />
    <MATCHING_FILE NAME="unins000.exe" SIZE="1174979" CHECKSUM="0x578C21CC" BIN_FILE_VERSION="51.1052.0.0" BIN_PRODUCT_VERSION="0.0.0.0" FILE_DESCRIPTION="Setup/Uninstall" FILE_VERSION="51.1052.0.0" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="51.1052.0.0" UPTO_BIN_PRODUCT_VERSION="0.0.0.0" LINK_DATE="12/20/2011 14:16:51" UPTO_LINK_DATE="12/20/2011 14:16:51" VER_LANGUAGE="Language Neutral [0x0]" />
    <MATCHING_FILE NAME="tool\par2_rename.exe" SIZE="39424" CHECKSUM="0x22F66A0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="06/16/2011 10:02:07" UPTO_LINK_DATE="06/16/2011 10:02:07" />
    <MATCHING_FILE NAME="tool\par3j_old.exe" SIZE="185856" CHECKSUM="0xA14550F7" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="04/10/2012 07:58:33" UPTO_LINK_DATE="04/10/2012 07:58:33" />
    <MATCHING_FILE NAME="ui\0409.dll" SIZE="24576" CHECKSUM="0xDBA9CC5C" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="English UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="0409.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="04/06/2012 05:10:27" UPTO_LINK_DATE="04/06/2012 05:10:27" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="ui\040c.dll" SIZE="27136" CHECKSUM="0x7213C8D3" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="French UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="040c.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="11/08/2011 08:01:28" UPTO_LINK_DATE="11/08/2011 08:01:28" VER_LANGUAGE="French (France) [0x40c]" />
    <MATCHING_FILE NAME="ui\0410.dll" SIZE="26112" CHECKSUM="0x6A875DC4" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="Italian UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="0410.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="09/05/2011 23:41:53" UPTO_LINK_DATE="09/05/2011 23:41:53" VER_LANGUAGE="Italian (Italy) [0x410]" />
    <MATCHING_FILE NAME="ui\0411.dll" SIZE="19968" CHECKSUM="0xA8416E84" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="Japanese UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="0411.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="04/06/2012 05:10:23" UPTO_LINK_DATE="04/06/2012 05:10:23" VER_LANGUAGE="Japanese [0x411]" />
    <MATCHING_FILE NAME="ui\0413.dll" SIZE="26112" CHECKSUM="0x5876ACA0" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="Dutch UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="0413.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="09/07/2011 06:11:01" UPTO_LINK_DATE="09/07/2011 06:11:01" VER_LANGUAGE="Dutch (Netherlands) [0x413]" />
    <MATCHING_FILE NAME="ui\0419.dll" SIZE="32768" CHECKSUM="0xFFD59274" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="Russian UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="0419.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x11450" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="11/25/2010 11:04:11" UPTO_LINK_DATE="11/25/2010 11:04:11" VER_LANGUAGE="Russian [0x419]" />
    <MATCHING_FILE NAME="ui\0804.dll" SIZE="18944" CHECKSUM="0xF8B858D4" BIN_FILE_VERSION="1.2.0.5" BIN_PRODUCT_VERSION="1.2.0.0" PRODUCT_VERSION="1.2.0" FILE_DESCRIPTION="Simplified Chinese UI for MultiPar" PRODUCT_NAME="MultiPar" FILE_VERSION="1.2.0.5" ORIGINAL_FILENAME="0804.dll" LEGAL_COPYRIGHT="Copyright (C) 2012 Yutaka Sawada" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.0.5" UPTO_BIN_PRODUCT_VERSION="1.2.0.0" LINK_DATE="11/08/2011 08:03:01" UPTO_LINK_DATE="11/08/2011 08:03:01" VER_LANGUAGE="Chinese (PRC) [0x804]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="1014272" CHECKSUM="0xBD64AD9E" BIN_FILE_VERSION="5.2.3790.4480" BIN_PRODUCT_VERSION="5.2.3790.4480" PRODUCT_VERSION="5.2.3790.4480" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.2.3790.4480 (srv03_sp2_qfe.090321-1244)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x106DA2" LINKER_VERSION="0x50002" UPTO_BIN_FILE_VERSION="5.2.3790.4480" UPTO_BIN_PRODUCT_VERSION="5.2.3790.4480" LINK_DATE="03/21/2009 17:06:15" UPTO_LINK_DATE="03/21/2009 17:06:15" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

[Yutaka Sawada]

 You should post what error was happen when you do what. Your post shows only your using application is MultiPar v1.2.0.5. Screen-shot shows the error is "Access Violation" by MultiPar.exe. Something data seems to be larger than buffer size. The interesting point is that, it is only a GUI instead of actual verifying par2j.exe. That error might be caused by something large output from par2j.exe like, too many files, too many total filenames, too long filename, or too long error message.

 Will you verify the PAR2 files by calling par2j.exe directly on DOS-prompt ? The command-line may be like;
par2j.exe v "path of a PAR2 file" > output.txt
(options depends on your setting)

 Then post the output here or send to me by E-mail. If par2j.exe shows error also, send a smallest PAR2 file to me. (don't send big files, please.)

[somdofritz]

OUTPUT.TXT


Parchive 2.0 client version 1.2.0.5 by Yutaka Sawada

Base Directory: "I:\Documents and Settings\Administrator\Desktop\lixo\"
Recovery File : "I:\Documents and Settings\Administrator\Desktop\lixo\lixo.pa3"
CPU number    : 4 (MMX)
Memory usage  : Auto (1088MB)

valid file is not found

[Yutaka Sawada]

 Your PAR files are sample PAR3 format. You need to test with par3j.exe instead of par2j.exe. Because you didn't write error details, you could not get proper reply. While I tested your posted PAR files, there is no error on my PC (Windows 2000). What OS do you use ?

 Will you try with par3j.exe ? Because your files contain Unicode characters, add "/uo" option in command-line like;
par3j.exe v /uo "path of PAR3 file" > output.txt
If par3j.exe does not show error message, and the output contains right files, no need to post the output. (the output is too big for web-forum.)

 Also, will you test the PAR3 file without source files ? At first, check an option; "Options" -> "Client behavior" -> "Log output of clients". Then, copy a PAR3 file into a folder without another files, and open it by MultiPar. In this case, there is no verification of source files, but list-up filenames only. Does same error happen, too ?

 If so, the error happen at which step ? MultiPar GUI's status text area was hided on your screen-shot. It is odd that "Creator: Unknown" means error before showing PAR files, as the creator name must be shown in a first step. The error might be caused at calling PAR client, like the length of path of PAR client and command-line is too long. (I assume that 256 is a max path length in GUI.) The command and output is saved in MultiPar.log. If something error message or too long line was written in the log, post it please.

[somdofritz]

http://www.youtube.com/watch?v=BzrLQSQAAT4

Open PA3 file without another files - Produce identical ERROR.

[Yutaka Sawada]

Produce identical ERROR

 I found one odd thing from your "output.txt", you use par3j.exe v1.1.9.6 while GUI is v1.2.0.5. You should use versions in same package, as command-line/output format may be changed at updates. The PAR client v1.1.9.6 is too old (different format) for the latest GUI. Then, the GUI failed to parse the output, and too long un-parsed output caused out-of-buffer error. I modified next version GUI to show error message, when the output format is different.

 I post the sample version of new GUI. You may test it and it will show "cannot parse output" error, if you use too old version client. When you use proper version client in the same package of GUI & client, there must be no error. If you get problem still, post the incident with details.

[somdofritz]

Test New GUI

ERROR

[somdofritz]

After total uninstall, delete files, and reinstall, problem solved.
The new GUI is also operating.
OK - problem solved.