10 Commits

Author SHA1 Message Date
Yutaka-Sawada
3ffc9d484b Release note of version 1.3.2.1 2022-01-22 13:01:18 +09:00
Yutaka-Sawada
c9705d6cee add version 1.3.2.1 files 2022-01-22 12:55:08 +09:00
Yutaka-Sawada
7fbac2be16 Delete MultiPar_par2j_1320.7z 2022-01-22 12:54:10 +09:00
Yutaka-Sawada
b24afc1a24 Delete MultiPar_par1j_1318.7z 2022-01-22 12:54:04 +09:00
Yutaka-Sawada
95f35b14ac Delete MultiPar_sfv_md5_1318.7z 2022-01-22 12:53:56 +09:00
Yutaka-Sawada
2189612c65 Release note of version 1.3.2.0 2021-12-20 13:40:26 +09:00
Yutaka-Sawada
59d062ed77 Add files via upload 2021-12-20 13:14:14 +09:00
Yutaka-Sawada
5870f732c9 Delete MultiPar_par2j_1319.7z 2021-12-20 13:13:45 +09:00
Yutaka-Sawada
c0239c578c Delete MultiPar_ShlExt_1318.7z 2021-12-20 13:13:37 +09:00
Yutaka-Sawada
03e8567358 Delete MultiPar_Help_1319.7z 2021-12-20 13:13:29 +09:00
11 changed files with 56 additions and 66 deletions

122
README.md
View File

@@ -1,73 +1,63 @@
# MultiPar
v1.3.1.9 is public
v1.3.2.1 is public
  This is the final release of v1.3.1 tree.
There would be no serious problem.
While I fixed some rare bugs and improved a bit, it's hard to test all possible cases.
When you see a bug, odd incident, or strange behavior, please let me know.
I will fix as possible as I can.
  This includes some bug fix and a sample of new feature.
I found a problem in my old code, and fixed them.
Because they are 32-bit version PAR2 client and PAR1 client, nobody saw them for long time.
Thanks [Safihre for finding the bug](https://github.com/Yutaka-Sawada/MultiPar/issues/55).
  I tested verification of multiple source files on my new PC.
From the result, I set max number of threads for NVMe SSD to 4 threads,
when CPU has 6 or more logical cores.
This will improve speed at verifying complete source files.
(It doesn't affect for PAR files nor damaged files.)
SATA SSD : It will verify max 2 files at once.
NVMe SSD : It will verify max 3 or 4 files at once.
I changed some behavior of handling invalid filenames on Windows OS.
In previous version, those bad filenames were sanitized automatically.
But, it might be strange and confused users of other OSes.
Thanks [Danilo for reporting the issue](https://github.com/Yutaka-Sawada/MultiPar/issues/58).
Now, this version warns such incompatible filenames only.
Because it's difficult to rename some bad fileanames on Windows Explorer,
I made a simple tool to rename invalid filenames, too.
The [tool "Rename7" is available on my GitHub page](https://github.com/Yutaka-Sawada/Rename7).
  When many input file slices are same, their checksums become same, too.
There was a bug in my sorting function.
Nobody found the error for over than 10 years, and I solved this problem at last.
Thanks [NilEinne](https://github.com/Yutaka-Sawada/MultiPar/issues/36) for reporting the very rare incident.
  When a file includes duplicated data, it's difficult to find slices in proper position.
In old versions, it might ignore overlap of slices for speed.
Then, it happend to fail finding some slices.
I implemented more complex method, and it will work well in most cases.
Thanks [swarup459](https://github.com/Yutaka-Sawada/MultiPar/issues/42) for bug report, offering samples, and many tests.
  It's possible to add PAR2 recovery record to a ZIP file.
When I wrote the instructions ago, 4 GB over ZIP file was not common so much.
Because recent Windows OS supports ZIP64 format, I updated the text for compatibility.
You may read the "Add recovery record" page of MultiPar's Help documents.
Or, you may read [the article on my web-site](http://hp.vector.co.jp/authors/VA021385/record.htm).
Now, MultiPar supports large ZIP file with ZIP64 format.
Thanks [Dwaine Gonyier](https://github.com/Yutaka-Sawada/MultiPar/issues/44) for noticing the potential problem.
Some [users requested a queue repair feature](https://github.com/Yutaka-Sawada/MultiPar/issues/57) ago.
I didn't make such utility, because there were some tools for the usage.
But, it seems to be old, or it's not updated so much.
So, I implemented a feature to repair multiple PAR2 recovery sets in queue.
Currently, it's a simple tool and will be changed more.
If a user is interested in the feature,
please read "Command_Queue.txt" in "help" folder.
Because it's sample, there may be a problem or fault.
I will improve later, when users tested the behavior.
[ Changes from 1.3.1.8 to 1.3.1.9 ]
Installer update
- Inno Setup was updated from v6.1.2 to v6.2.0.
[ Changes from 1.3.2.0 to 1.3.2.1 ]
GUI update
- New
- For a folder with PAR2 files, MultiPar may invoke ParQueue.
- Change
- Clickable link to access author's page becomes SSL.
- Appending recovery record supports 2 GB over file size.
- In command-line, it uses "/" for each option instead of "-".
PAR2 clients update
All clients update
- Change
- When source files are on NVMe SSD, verification may become faster.
- Appending recovery record supports ZIP64 format.
- Improvement
- Simple verification will find a short slice in a tiny file.
- It will warn incompatible filenames on Windows OS.
PAR1 client update
- Bug fix
- A stack overflow problem in quick sort function was removed.
- A bug of searching slices in a file with repeated content was fixed.
- Failure in setting a file pointer was fixed.
PAR2 client update
- Bug fix
- Possible stack overflow at searching missing files was fixed.
[ Hash value ]
MultiPar131.zip
MD5: EF3486BB39724EF6A4109F5B02D4E027
SHA1: D935BFAFF5156C9460FB45639271339D1068F522
MultiPar1321.zip
MD5: FC155A166F5C31F7FA2373F06A866427
SHA1: 2E4DF4FF1DDEC301A51A9FA33C4F66B41D1F24C2
MultiPar131_setup.exe
MD5: E2F6EF68AEB9BE0CCDD4D5ABF2A3F318
SHA1: C2615960B9B28223BC174FC1175CAAECCC8A713A
MultiPar1321_setup.exe
MD5: B4D94783D4CB3A72EEBF51A893C1ED39
SHA1: B22AE13319FD3856BD4E9D7CC042119FDF6A4E34
  To install under "Program Files" or "Program Files (x86)" directory,
you must start the installer with administrative privileges by selecting
"Run as administrator" on right-click menu.
@@ -78,26 +68,26 @@ you must start the installer with administrative privileges by selecting
[GitHub](https://github.com/Yutaka-Sawada/MultiPar/releases) or
[OneDrive](https://1drv.ms/u/s!AtGhNMUyvbWOaSo1n_R8awJ_hg0?e=4V0gXu).
MultiPar_par2j_1319.7z
MD5: 9AC4C38762E2DBF64D6D3A738CD7CCD6
SHA1: FFC0DA1A0BBCAD08489C5499154DAA0216E10F51
MultiPar_par2j_1321.7z
MD5: 4853C852E6DAEB8BCC034595C46CFE87
SHA1: 24027B8E91DD32EF3A16931091BBD84D88EDBDBF
MultiPar_par1j_1318.7z
MD5: F66285403BA0AD856BA6A8CCD922EBF5
SHA1: 4CF5D819B16E60F1BBD82415D5F68CB46D3F53C3
MultiPar_par1j_1321.7z
MD5: 2BE9BCCA25672BD7FC6773B6D5C3A831
SHA1: 2F3759136922627ADFC6197D0CA3911508104694
MultiPar_sfv_md5_1318.7z
MD5: 4E6433808625C088E2773C961BBEBBD2
SHA1: 68B54D178BA58637F63CC3E0CC656C96D4472A33
MultiPar_sfv_md5_1321.7z
MD5: 5CD627C2D768290EF574230259A19487
SHA1: E768B38783DF56289549BBAA3D65DBDAE679213B
MultiPar_ShlExt_1318.7z
MD5: 57E79698A53458681CD19842391A202F
SHA1: 646145F1B429C1CF592F907614889C98FBE7E756
MultiPar_ShlExt_1320.7z
MD5: C413655ABF85BCFF3D4B349BAAADC24B
SHA1: 8552E6CCF647B065D91E494D2751567C144ABD36
MultiPar_ResUI_1319.7z
MD5: E03B90A433466C945D726B5A49B4E547
SHA1: E30FB11B8F121D44CC1CC368E8D91F06CFC15551
MultiPar_Help_1319.7z
MD5: 37547FA074DC24491D1696F6F0DB7452
SHA1: 8069C5745F9C7660236F17E3E087B4F7324382ED
MultiPar_Help_1320.7z
MD5: 1F8CC009B1A5F11EFBA999C7225E4311
SHA1: 6E392602F82A96E3015FEA65A590E08D2B6E39CB

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.