Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: par2 (file/archive recovery) released (Read 57440 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

par2 (file/archive recovery) released

Reply #100 –
Quote
Quote
The ability to store and use path information will be available in a future version of QuickPar.

When will it be released ?
We are all waiting !

My appologies for the delay.

I've spent a lot of the time recently working on localised versions of QuickPar.

I've also been trying to track down the cause of failed repairs that have been reported to me. So far the only cases where a cause has been found have turned out to be due to faulty RAM (either in the computer of the person that created the PAR2 files or the computer of the person attempting the repair). As a consequence of this, I been working on code to detect problems caused by faulty RAM.

I had hoped to include path handling in 0.8, but it might not get in until 0.9.

par2 (file/archive recovery) released

Reply #101 –
Hi Peter,

A small request for the UI:

Is there any chance that it could be set to remember "Number of recovery files" between sessions.

I tend to always set this to 1, so it would be nice if it didn't always reset to 10.  By the way, my reasoning for using 1 is that it seems tidier to have less par2 files hanging around in my folders.  I presume that it makes no difference to the total combined size of the par2 files and that lots of par2 files are only really useful if there will be a need to download them over an internet connection.  So for par2 files I will keep on my local hard disk this is not necessary.  Am I right about this or am I missing something?

Also, I like the change in 0.7 where the Base Filename is automatically set from the folder name.  Personally I am storing music files in a folder structure "My Music\Artist\Album" and it would be great if I could set it up to automatically use two levels of folders to create a base filename "Artist - Album".  But I can appreciate this might be a rather complicated change for what it's worth.

Thanks.
Tim.

par2 (file/archive recovery) released

Reply #102 –
I think for backupping any data on these big DVD media todays, or big Hds with a lot of subdirectories, the automatic creation of par files for included subdirectories ,
is very important nowadays.

Imagine the work for going through each (album) (or program) folder (either archiving music, or eg. installation files) for a backup on DVD.



I think, maybe there is a fast solution possible,
there is sweep.
maybe it needs only to be implemented somehow into the GUI of Quickpar ?

http://www.saunalahti.fi/cse/files/Sweep.zip

par2 (file/archive recovery) released

Reply #103 –
User,

Why not use a md5 file to check the entire contents of a DVD then apply your par2 recovery (if available) to fix any problems?
daefeatures.co.uk

par2 (file/archive recovery) released

Reply #104 –
well, the problem is the creation of the par2 files for the lot of various directories on HD or DVD.
I recall, that atici wrote at beginning of this thread, that he wnated to use sweep and quickpar as commandline in DOS-box.

Does somebody have a good commandline ?

par2 (file/archive recovery) released

Reply #105 –
Ensuring sweep.exe and par2.exe (the commandline version mentioned in first post) are in your /windows/system32/ dir (for NT, see equivilant for your OS) I believe you can do:

sweep "par2 c ./*"

adding whatever parameters you need for par2 after the c
daefeatures.co.uk

par2 (file/archive recovery) released

Reply #106 –
Quote
Hi Peter,

A small request for the UI:

Is there any chance that it could be set to remember "Number of recovery files" between sessions.

I tend to always set this to 1, so it would be nice if it didn't always reset to 10.  By the way, my reasoning for using 1 is that it seems tidier to have less par2 files hanging around in my folders.  I presume that it makes no difference to the total combined size of the par2 files and that lots of par2 files are only really useful if there will be a need to download them over an internet connection.  So for par2 files I will keep on my local hard disk this is not necessary.  Am I right about this or am I missing something?

Also, I like the change in 0.7 where the Base Filename is automatically set from the folder name.  Personally I am storing music files in a folder structure "My Music\Artist\Album" and it would be great if I could set it up to automatically use two levels of folders to create a base filename "Artist - Album".  But I can appreciate this might be a rather complicated change for what it's worth.

Thanks.
Tim.

The suggested value for "Number of recovery files" is calculated automatically depending on the number of recovery blocks being created and the choice made for "Recovery file size".

Because of this having QuickPar default to using the same value that was used last time might solve your problem, but would cause problems when you do waht to use multiple files.

A possible solution would be to add an "All recovery blocks on one file" choice to the "Recovery file size" option.

Ultimately I want to allow the creation of Profiles which would enable you to set all of the major settings in one go.

A single par2 file will actually be smaller than multiple par2 files containing the same number of recovery blocks. The reason is that every par2 file contains extra copies of the verification information. Large par2 files will contain multiple copies of this information to ensure that verification will still be possible even if the par2 files are severly damaged. The exact number of copies is equal to log2 of the number of recovery blocks. So, if you have two par2 files that each have 64 recovery blocks in them, then they will also each have 6 copies of the verification data (a total of 12 copies), but a single par2 file containing 128 blocks will only have 7 copies of the verification data.

par2 (file/archive recovery) released

Reply #107 –
Quote
A possible solution would be to add an "All recovery blocks on one file" choice to the "Recovery file size" option.

This would be ideal.  Thanks for the information.

par2 (file/archive recovery) released

Reply #108 –
par2cmdline-0.2.x86.win32.zip

is this the latest compile of cmdline version for dos-box in windows ?

par2 (file/archive recovery) released

Reply #109 –
User's report:

read here with pictures:  http://www.high-quality.ch.vu
and direct link:
http://www.angelfire.com/magic2/hq-audio/par2-guide.htm


Par2ing a lot directories & subdirectories in 1 step:




par2cmdline-0.2.x86.win32.zip
worked well together with sweep.exe in DOSbox.

get it here:
http://parchive.sourceforge.net/
or directly here:
http://prdownloads.sourceforge.net/parchiv...32.zip?download

get sweep from case's page:
http://www.saunalahti.fi/cse/files/Sweep.zip


Install:

Ensuring sweep.exe and par2.exe (the commandline version mentioned above are in your path :    /windows/system32/ dir (for NT, see equivilant for your OS)




Usage:

Every subdirectory was treated as single directory.

I tried eg. this commandline:

sweep par2 c -r15 -n1 -s384000 par2file *.*     

 



some remarks:

smaller blocksize than -s 380 kiloByte is better, but longer time.

r15 : 15% redundancy, variable
n = 1 : 1 par2 file, you can leave n option away
You could adjust r, n, s to your needs.
n does not affect the recovery quality,
r , s influence the recovery quality/computing time.


par2 c -r15 -n1 -s384000 par2file *.*



time = const. * r% * 1/s

Time is proportional to : redundancy * smaller_blocksize






Out of readme:

Naming, wildcards:



If test.mpg had been split into multiple RAR files, then you could use:

  par2 create test.mpg.rar.par2 test.mpg.part*.rar

The files filename "test.mpg.rar.par2" says what you want the par2 files to
be called and "test.mpg.part*.rar" should select all of the RAR files.








Addition:


Summary of commandlines:


Create par2:

sweep par2 c -r15 -n1 -s384000 par2file *.*


instead of s=384000, you can try smaller values, but the computing time will increase proportional , eg : 192000 ==>> twice the time than for s=384000.
same for R=15, amount of recovery data in %. eg. half amount in % ==>> half time.



Check:

sweep par2 v *.par2


Repair:

par2 r(epair) [options] <par2 file> [files]
 

par2 (file/archive recovery) released

Reply #110 –
I was reading the whole topic (5 pages of massive texts =])
And no conclusion was taken for the best setting for cd-r or dvd+-r backups.
But my question is not about recordable media backup.
I have a full tower and raid mobo.
I am going to buy some 120gb-200gb hard drives for storing all my cd collection Lossless (have not devided the format yet). I will also probably be taking friends cd's for storing it too =)
So , as those hd's are only going to be used for storage I guess it would not have a lot of probability of getting error ,  but you never know.
What would be the best setting of the par2 file to use for storing at hd's ?
I guess size is not really an issue.

Kind Regards , Tcmjr
Kind Regards , Tcmjr

Aka HellSnoopy

par2 (file/archive recovery) released

Reply #111 –
Quote
par2cmdline-0.2.x86.win32.zip

is this the latest compile of cmdline version for dos-box in windows ?

I've got v0.3 mingw compile here.

And here's a little batch that names pars after folder's name:

Quote
@echo off
set MASK=%1
set CMDLINE=%2 %3 %4 %5 %6 %7 %8
set PARENT=%cd%
for /r %%i in (.) do cd "%%~fi" & set NAME=%%~nxi.par2& call :process
cd "%PARENT%"
goto quit

:process
if exist %MASK% par2 c %CMDLINE% "%NAME%" %MASK%

:quit

So it goes like
parecur <mask> [par2 options].

par2 (file/archive recovery) released

Reply #112 –
I have added following summary to "user's report about par2ing subdirectories":




Create par2:

sweep par2 c -r15 -n1 -s384000 par2file *.*


instead of s=384000, you can try smaller values, but the computing time will increase proportional , eg : 192000 ==>> twice the time than for s=384000.
same for R=15, amount of recovery data in %. eg. half amount in % ==>> half time.



Check:

sweep par2 v *.par2


Repair:

par2 r(epair) [options] <par2 file> [files]

par2 (file/archive recovery) released

Reply #113 –
Quote
Quote
par2cmdline-0.2.x86.win32.zip

is this the latest compile of cmdline version for dos-box in windows ?

I've got v0.3 mingw compile here.




Comparison between cmdline versions, compiles win32 of v0.3 & v0.2


I have tried both, 0.2 and ak's 0.3 compile of the commandline versions, on a 60MB mpc album, with small file like playlist, and big mpc files (to have a typical mix, example).

following cmdline:


sweep par2 c -r15 -n1 -s70000 par2file *.*



Both resulted to same nearly identical output par2files, and later on identical  eg. repairing behaviour with quickpar latest version.

The difference between those par2files : was the version written at end of file, 0.2 and 0.3 of course.

But there were some other (obviously minor ?) differences in the output files, seen by binary comparison:

After the "end-header" of the par2files, there were some differences, (then were the versions written into those files.)
Have these differences any meaning ?