Page 1 of 1

yenc crash due to those new "encrypted" filenames.

PostPosted: Sat Oct 18, 2014 8:21 am
by Obecalp
As mentioned in this thread: forums.newsbin.com/viewtopic.php?f=20&t=35660 some releases are now being encrypted/encoded and it seems Newsbin is having a hard time with some of them, I tried to download 4 parts of a series, 1-3 were fine, the 4th failed and in logging I see the following:

Code: Select all
[13:02:53]  ERROR FileDecodeThread - internal crash
[13:02:56]  ERROR FileDecodeThread - internal crash
[13:03:03]  ERROR FileDecodeThread - internal crash
[13:03:09]  ERROR FileDecodeThread - internal crash
[13:03:13]  HIGH  DecodeYenc - YEnc Data format error:0hn8lty6ubgicx5nz9rsaljvowh0jbne
[13:03:16]  ERROR FileDecodeThread - internal crash


All parts are downloaded it seems but par repair doesn't work and winrar is reporting a faulty file so basically there's nothing I can do with it. For one faulty file there should be enough pars to repair but quickpar is also now working with it (obviously not your problem).

Re: yenc crash due to those new "encrypted" filenames.

PostPosted: Sat Oct 18, 2014 8:49 am
by Quade
You tried quickpar too?

How about emailing the NZB to ts@newsbin.com

Re: yenc crash due to those new "encrypted" filenames.

PostPosted: Sat Oct 18, 2014 8:53 am
by Obecalp
Quade wrote:You tried quickpar too?

How about emailing the NZB to ts@newsbin.com


Yeah tried Quickpar and because of those weird filenames it par checks the pars but acts as if there's no actual files for the rest of the archive, thanks I'll email it to you now :)

Re: yenc crash due to those new "encrypted" filenames.

PostPosted: Sat Oct 18, 2014 3:49 pm
by Quade
Got the NZB. I'll try tonight.

Thanks.

Re: yenc crash due to those new "encrypted" filenames.

PostPosted: Mon Oct 20, 2014 11:49 am
by Quade
Looks like there's something screwy with the PAR files. One of the RAR files is listed as zero bytes. Quickpar can't id files as even being part of this set. It didn't crash for me (I'm trying a different version) but, it didn't work correctly either. I'll try again in 6.54.