On Wed, 26 Jan 2011 10:56:50 -0600, knugel <number313@hotmail.com>
In a totally off-topic waste of bandwidth bloviated thusly:
>
> Default User <user@default.ru> wrote in
> news:4d3ec8e5$0$3414$c3e8da3$12bcf670@news.astraweb.com:
>
> > On 2011-01-24 03:31:38 -0500, Elteluk24 <norfolkandchance@hotmail.com>
> > said:
> >
> >> I use Windows (and I'm not in a position to change that for various
> >> reasons) and Usenet. I get many errors from Yenc. Is there anything I
> >> can do to improve the number of files that I actually get through? I
> >> keep getting y_Enc CRCerror part 2. Cheers!
> >
> > I don't think the problem has anything to do with the fact that you
> > are using Windows. A CRC error indicates that the file in question is
> > corrupt.
> >
> > What sort of files are you talking about? Picture files? Archive
> > files? Here's a thought...refer us to a file that gives you the error
> > and see if others have the same issue.
> >
> >
>
>
> It happens to me, also.
> I ALWAYS get those extra zero bytes files when I downloading (decoding)
> posts from the poster "sanfan".
> From other posters there are NO problems.
>
> The zero bytes file is named:
> filename.jpg__yEnc_CRCerror_part_2.txt
>
> And some of sanfan's posts are always corrupted (the first 600 000 bytes
> part is the only available. So it seems that the second part is missing in
> the post)
>
> Last posts with errors, for reference: Stella#088 (posted by Sanfan)
> Where the two files IMG_5116.JPG and IMG_5115.JPG are corrupted.
>
>
> /knugel
BELOW IS A TECH REPOST REGARDING SANFAN'S POSTS:
The error is evident in Newsbin 5.54 and is fixed in 5.55.
Agent 4.2 flags the error during extraction but the user can ignore it.
(Newsbin <=5.53 was even more yenc malformed.)
===>
>> Subject: hope ur chickens R all Plump!!!! #66 "IMG_0891.JPG" (*/2) yEnc 675668 Bytes
>>
>> =ybegin part=1 total=2 size=675668 line=128 name=IMG_0891.JPG
>> =ypart begin=1 end=600000
>>
>> =yend size=600000 part=0 pcrc32=1
<===
Part should be 1 and pcrc should be the valid checksum of the part.
Instead, pcrc contains the part#.
===>
>> =ybegin part=2 total=2 size=675668 line=128 name=IMG_0891.JPG
>> =ypart begin=600001 end=675668
>>
>> =yend size=75668 part=0 pcrc32=2 crc32=49E54131
<===
Part should be 2 and pcrc should be the valid checksum of the part.
Instead, pcrc contains the part#.
Since the pcrc's are invalid, Agent correctly flags the error.
In single part attachments, the crc32 is invalid (0):
===>
>> =ybegin size=575348 line=128 name=IMG_0865.JPG
>>
>> =yend size=575348 crc32=0
<===
In Newsbin <=5.53, the part begin, end and size, as well as the final
checksum, were also invalid and Agent did not allow multipart extraction at
all. Many readers could not extract them but some, particularly Newsbin
itself, could.
Readers that don't bother to validate against the yenc prefix and suffix
parameters have no problem extracting - regardless of whether parts are
corrupt or incomplete. I have encountered such, especially when the news
server does not reject incomplete or broken transmission articles/parts.
|
|