Release note of v1.1.9 tree

[BobFX]

I rebooted my PC, and now the right-click creation works!

Weird, sorry to have wasted your time.

Thanks.

[Yutaka Sawada]

from BobFX

Weird, sorry to have wasted your time.

No problem. Odd bug happens many times and OS causes it often. For example, new Option window by property-sheet has see-through bug on Windows 2000...

[Gallico]

But drag&drop into file-list don't work anymore?

[Optixyz]

Thank you for new version :)

[Yutaka Sawada]

from Gallico

But drag&drop into file-list don't work anymore?

This Drag&Drop bug is fixed at next version, too. While I updated GUI resource, I changed some part of existing dialog, and it caused this bug. If you cannot wait the next release, or want to confirm that the bug part was fixed correctly, send mail to get current sample version.

[apsen]

MultiPar fails with "filename aaa: bbb  is not valid" when the file name inside the par2 contains colon ":". QuickPar handles this just fine.

On the file system the file name is actually "aaa_ bbb".

BTW Multipar 1.1.9.3 does not show version number in the 'About' box.

[Yutaka Sawada]

from apsen

On the file system the file name is actually "aaa_ bbb".

The character ":" is not allowed in filename on Windows OS. While QuickPar has a feature to replace invalid characters automatically, it may sometimes misname filename of non-ASCII characters. MultiPar's PAR2 client does not sanitize (replace or remove) invalid characters, because there is no official rule. Should MultiPar contain those automatic replace feature as same as QuickPar ? What application renamed the invalid filename by based on what rule ?

As the filename "aaa_ bbb" on the disk is different from original filename "aaa: bbb" in PAR2 file, the status should be "Misnamed", but cannot correct the filename over Windows OS. You would better to use renaming tool in "tool" folder of MultiPar. You can modify filenames in PAR2 files. Also, you may ask the creator of PAR2 files, to set a compatible filename for transportable files. When he send a files to you, he should set proper names for the files.

[Yutaka Sawada]

from apsen

QuickPar handles this just fine.

 When a PAR2 file contains a filename of "aaa: bbb", QuickPar renames it to " bbb". Because this renaming rule is different from your case "aaa_ bbb", I am not sure what is fine. Maybe filename itself is not so important. I implemented a sample sanitize routine in next v1.1.9.4. Thouh there is a chance of invalid filename error still,it works well in most case.

[noelharper]

I have a feature request: control multipar's 2 input and 2 output files separately with the GUI

1. you don't need to copy the data from the CD to HDD
2. you can have data file and recovery files on different places
3. you can write output file to a different place
4. you can use hyperdrive/ramdrive/ssd for the temporary file

I have some files damaged by hard drive failure, but because I used a separate location for par2 files they are safe, but the par2 files use a very small block size and the memory cannot be allocated to recover :(, is there a 64-bit version ?

[Yutaka Sawada]

from noelharper

1. you don't need to copy the data from the CD to HDD
2. you can have data file and recovery files on different places

 I am not sure what you want. There are 2 input already.
1) base directory of source files (read & write)
2) directory of recovery files (read only)
You may change the "base directory" by "Browse" button to the place of source files.

3. you can write output file to a different place
4. you can use hyperdrive/ramdrive/ssd for the temporary file

 Some users requested this feature ago. Basically, output file and temporary file are same in my PAR clients. When a repair ends succressfully, temporary file becomes the output(repaired) file. It is possible to implement to put temporary file on different drive, but the merit would be very limited, because the space/speed/balance is varied by the environment. It is difficult to find/set/select best setting for all case.

but the par2 files use a very small block size and the memory cannot be allocated to recover

 You should write what is the exact problem. The memory problem has nothing to do with your request... I suspect that your case might be too large matrix. My PAR2 client requires max 2GB memory for matrix to recover 32000 blocks. (and it beyond the limit of memory area for 32-bit application.) You may try 64-bit version of par2_tbb, as waiting progress is better than cannot.