Path: news.nzbot.com!spool1.sonic-news.com!news-out.sonic-news.com!not.news-service.com!not.alt.net!not.highwinds-media.com!border5.newsrouter.astraweb.com!news.astraweb.com!border3.a.newsrouter.astraweb.com!multikabel.net!newsfeed10.multikabel.net!feeder.news-service.com!cyclone01.ams2.highwinds-media.com!news.highwinds-media.com!npeersf02.ams.highwinds-media.com!newsfe06.ams2.POSTED!03785932!not-for-mail
From: cherryade<@blossom.com>
Newsgroups: alt.binaries.crafts.pictures
Subject: Re: bluerope81:thank you
Message-ID: <pl9je59opi93ond8ib5rbqmig5u04or9k2@4ax.com>
References: <9dvge59jds6sl2bmede1sea4nqku962ecb@4ax.com> <0064b8a6$0$23484$c3e8da3@news.astraweb.com>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 140
X-Complaints-To: http://support.highwinds-media.com
NNTP-Posting-Date: Thu, 29 Oct 2009 14:39:08 UTC
Date: Thu, 29 Oct 2009 14:39:08 +0000
Xref: news.nzbot.com alt.binaries.crafts.pictures:10601
On Thu, 29 Oct 2009 10:50:37 +1000, hopper
<Troll5layer@acting.invalid> wrote:
> From: cherryade<@blossom.com>
Newsgroups: alt.binaries.crafts.pictures
> Subject: bluerope81:thank you
> Message-ID: <9dvge59jds6sl2bmede1sea4nqku962ecb@4ax.com>
>
>Ms. Cherryade...
>Is it so unreasonable to ask you to quit with thanking a Spammer
>for what they inject into this group, deliberately, as Spam?
>Show us, convince us, this is an unreasonable request.
>
>The BR poster has been approached by a number of people,
>in different ways, for months. The BR poster refuses to hear
>any of it.
>It can be reasonably concluded the BR posts are being used
>as a"hammer" to create confusion for the downloader
>(like Ging - as a recent example).
>Are you then in agreeance with such methods of disrupting this NG?
>
>There is nothing new here in the action of BR.
>Below is the attempt by Herb and myself to sort the BR posts to a solution.
>Take note of the posting date.
>
>
>
>For the audience;
>In the content of the text below is my "work-around" for decoding
>BR posts. Whilst the info is public domain I would discourage anyone from
>posting a "thank you" to the Spammer. Hundreds/thousands of people having to
>apply "patches" to get downloads from posts made by people who are intent on
>destroying groups (and thereby Usenet itself) is not the way forward.
>
>thank you for listening.
thank you for your post. I am not as eloquent as you so this is a
short note. I had not seen Herb's solution to BR posts, thanks for
that.I did not used to thank anyone at for anything, but that seems to
put new posters off. So untill next time a small pretty please ease up
for now or you will end up with a heart attack or worse and as you are
very helpful putting usall in the know. thanks again
cherryade
>
>++++++++++++++++++++++++++++++++++++++++++++++
>From: Herb <Herb@the.herb.garden>
>Subject: Re: What to do with SOME corrupted attachments
>References: <%QcAl.75265$UR4.45057@en-nntp-09.dc1.easynews.com>
><i6s2t4p6jufb3iqqdvkr7fdjcfjtoh6isf@4ax.com>
>Message-ID: <gFeAl.104515$9j5.21477@en-nntp-01.dc1.easynews.com>
>Date: Mon, 30 Mar 2009 18:50:02 -0700
>
>hopper wrote:
>
>> From: Herb <Herb@the.herb.garden>
>>
>>>If the attachment is a Rar archive file it can usually be repaired.
>>>
>>>1) Save the attachment - and remember where you saved it :)
>>>2) Open WinRar
>>> Do NOT double click on the file - that will fail.
>>> Just go directly to a WinRar icon and open the program.
>>>3) Navigate to the folder where you saved the attachment.
>>>4) RIGHT-click on the attachment and select 'repair archive'
>>> (alternatively, just select it and press Alt-R)
>>>
>>>Answer yes or ok or continue to all the messages, no matter how
>>>ominous they sound.
>>>
>>>You will now have a file with the word "Rebuilt." ahead of the rar
>>>file name. You can now open this or extract or save or whatever you
>>>would have done originally.
>>>
>>>Some of the included contents might be lost, or they might all be
>>>there. In the case of BlueRope's posts, everything is there. He or she
>>>appears to be using NewsBin Pro 5.51, which is a good news READing
>>>program, but a less than optimum news POSTing program.
>>>
>>> - Herb
>>
>> Herb, your description only works where the "put recovery record"
>> option is ticked/set by the poster.
>
>Working on the 869 post ...
>'LittleMissMe' said that Winrar gave up with 'no recovery record
>found'. Don't yet know what version of Winrar she's using,
>But with 3.71 it sailed through and fixed it.
>> By default Winrar is not installed with that option as a positive value.
>
>Is there a way to get the properties of a .rar archive that shows
>things like whether or not it has a recovery record, built 'solid' and
>other attributes?
>
>> A method that works for *every* corrupted archive, where it is the
>> crc value that is creating the error dialog, is to save the file as a
>> unix text file then manually comb through the file to remove the
>> faulty code, or join with good code as the case may be.
>> Importing the repaired file to Agent will list the archive for
>> decoding by Agent.
>
>Pretty tricky for most! In this case, when winrar recovers it, it
>states that the archive header is corrupt.
>
>Interestingly, if I tell it to treat the archive as 'solid' it creates
> one folder. If I say not to, it creates the contents as a folder
>within a folder. The source of BlueRopes problem may be that his/her
>version of Winrar doesn't handle nested folders well.
>
>> Given some are not able to set the recovery option in the first place
>> (so easy to do) then the above method is likely impractical for the
>> downloaders here.
>> [ps] I have seen "thank you" posted for files which are incomplete
>> [ps]or not recoverable at all. Those thank you posts help nobody.
>
>Agree.
>
>> For the yEnc posts pointed to there exists an easy method to
>> recover the files.
>> Again, save the archive as a unix text file and feed it to this yEnc tool.
>> http://www.yenc32.com/
>> The tool will decode the archive from raw text and deliver the
>> files as they were packed.
>> Observation shows many posters are using yEnc encoded posting
>> so the above method may deliver more product than relying on
>> Winrar rebuilds.
>> Why it is yEnc is so popular in uploads of designs is a mystery.
>> The files are too small to warrant using that encoding.
>
>I agree. There are enough Outlook Express and Mozilla based
>newsreaders being used that yEnc posting generally hurts more than it
>helps. OTOH, many European users pay by the byte so it saves them a
>few bits here and there.
>
>
>> But what do I know :)
>
>Quite a bit, it would seem!
>
> --- Herb
|
|