Page 1 of 1
par2.temp
Posted: August 20th, 2012, 5:22 am
by KrikKrak
Hi,
Is there a way to use recovery files with the additional extension temp: all par files end with par2.temp. Right now these files are reported as damaged by Quickpar.
Searching on binseach.net shows that it is quit common that files ending on par2.temp are posted. Maybe something went wrong with Yenc Powerpost program. Is there a way to repair these files (after downloading 10 gig

)?
Re: par2.temp
Posted: August 20th, 2012, 5:52 am
by shypike
After downloading and the failure of post-processing,
go to the download folder and rename the par2.temp files to par2.
Then set SABnzbd to paused, click retry in History.
The job will go back to the queue.
Click on the queue entry and remove all par2.temp files
(otherwise they will be downloaded again).
The job should go automatically to post processing, if not set the priority to "stop".
I can confirm that binsearch shows a lot of this kind of posts.
The average skill level of posters is decreasing lately

If this becomes a trend, it's time to look for a solution.
Re: par2.temp
Posted: August 21st, 2012, 2:09 am
by KrikKrak
Thanks for your reply. Unfortunately, it did not work. Maybe because the poster split the post into two parts: the rar files and later the (perhaps not encoded) par files.
Therefore the par downloading was successful and there was no administration folder in de complete folder.
If I click on retry a screen pops up asking whether I want to use an additional nzb. If I click on retry a repairing automatically starts and results in a failure.
The job does not reappear in the queue.
Maybe it helps if I give you additional details: in binsearch.net it can be found searching for "ozi" and the poster name is:"theDutchies".
Is there an alternative way to use these par files?
Re: par2.temp
Posted: August 21st, 2012, 3:17 am
by shypike
I tried a few of these jobs.
Even after renaming the par2.temp files to par2, QuickPar still found no use for these files.
I'd say: poster screw-up.