[span style='font-size:14pt;line-height:100%']To sum up:[/span]Method A (for those who like to keep the par2 set together with the files): A1) Create the directory structure in whatever way you like A2) Search for *.* and throw all files to QuickPar A3) Create as much recovery blocks as you can A4) Burn all the files and PAR2 sets in the same disc In case of disc failure: a1) Read the (possibly damaged) iso image of the disc with DVDDecrypter or IsoBuster a2) Create a copy of this iso and rename it to *.PAR2 a3) Double-click this "PAR2" and feed to QuickPar the ISO Alternative recovery process: a'1) Copy as many files you can either with explorer or with isobuster a'2) Double-click any of the par2 files a'3) Click "Add" button in quickpar and add all the files copied both the actual files and the par2, even the damaged ones. I recomend the a? recovery method since explorer cannot do partial copying.Method B (for those who like to keep the par2 set separately from the files): B1) Burn a cd/dvd with whatever data you like B2) Read the iso with DVDDecrypter or IsoBuster and create for that iso a par2 set or B'1) Create an iso of whatever data you like B'2) Burn the iso to a cd/dvd B'3) Read the iso with DVDDecrypter or IsoBuster and create for that iso a par2 set Remark: if you notice that iso's in B1 and B3 are identical (you can check that with fc /b command in the Command Prompt) then omit the reading of the iso in step B3. In case of disc failure: b1) Read the iso with DVDDecrypter or IsoBuster and try to repair using the separately stored par2 setsMethod C C1) Put all source files inside a truecrypt container C2) Create as much recovery blocks as you can for this truecrypt container C3) Burn both par2 set & truecrypt container in the same disc In case of disc failure: either a? or a'?Method C* Same as above except that you put all source files in an iso and burn it as a file along with the par2 set in a single cd/dvd.Short comparison of the 3 methods QuickPar pads all files in order to make their sizes an exact multiple of the block size. Hence, if you use method A and there are many small files then "source data" will be much more than the "actual data" resulting in lower recovery efficiency. Thus method B is more effective than A. C is somehow between A and B since everything is burned in a single disc and still all source files are treated as a single file. Moreover there are no problems with filename lengths.General remarks - The more recovery block the more time needed for par2 creation - The smaller the recovery block the more time needed for par2 creation - The more recovery block the greatest the recovery efficiency - The smaller the recovery block the greatest the recovery efficiency - Don't forget to set the following option: Preferred block size -> Exact: 2048 and check always the "restict block size to multiples..." checkbox in quickpar's main window.Method D ("Advanved method") This method is still in beta version! don't use it! D1) Create an iso of whatever data you like and name it "1.iso" D2) Create a par2 set for "1.iso" D3) Create an iso containg solely the par2 files and name it "2.iso" D4) Create the following cue-sheetFILE "1.ISO" BINARY TRACK 01 MODE1/2048 INDEX 01 00:00:00 POSTGAP 00:02:00 FILE "2.ISO" BINARY TRACK 02 MODE1/2048 INDEX 01 00:00:00 POSTGAP 00:02:00 and store it in the same directory as "1.iso" and "2.iso" D5) Burn the cue sheet In case of disc failure: d1) Open isobuster and save each of the two tracks in a separate iso (named: "1.iso", "2.iso") d2) Rename "2.iso" to "2.par2" d3) Double-click "2.iso" and feed "1.iso" to QuickPar I tag this method as a beta one because it seems it's not iso compliant. Windows will not read the second track (which is not necessarily bad) of the disc produced and nero cannot extract track 2 either. However, in all other respects (including recovery) this method is fine.