Read my post to Yenc. There is nothing wrong with yenc's posts using
either Agent or XNews. The problem is with either how you are d/l, how
you are combining the files, or how you are using Truecrypt. Use the
keyfile stated in the Heading of the post. You don't even need to
change the file name (.txt).
OG
On Thu, 10 Nov 2011 15:42:41 -0800, diamond@gem.com wrote:
>On Thu, 10 Nov 2011 13:40:01 -0800, Joe Btfsplk
><joe_btfsplk@nowhere.com> wrote:
>Little bit of troubleshooting here :
>So, are there others in this group that are able to open these ("New
>Text Document.txt) postings files and are also using Agent to do it
>??.
>>On Thu, 10 Nov 2011 11:57:31 -0800, Yp <anon@anon.com> wrote:
>>Wow, another wrench in the wheel.
>>I was never aware of this.
>>Do you know if this is common with all that post from
>>"YENC-POWER-POST-A&A-v11b" ?. Just wondering if we can expect this
>>from those newsreaders. Probably something everyone should be aware of
>>by reading the entire header info, especially if those doing the
>>dowloading are using Agent, unless there is some specific setting in
>>Agent to allow for XNews posts......
>>Tnx for the info.
>>>This has nothing to do with the extension. TC does not care about file
>>>extensions. A TC container can be named anything at all and it would
>>>decode just the same.
>>>
>>>This problem has to do with the program you use to download and decode
>>>your binaries. Try downloading XNews and decoding using that. I know
>>>for a fact a popular newsreader like Agent cannot combine this file
>>>properly because of the way the header is constructed.
>>>
>>>
>>>
>>>On Thu, 10 Nov 2011 11:06:30 -0800, Joe Btfsplk
>>><joe_btfsplk@nowhere.com> wrote:
>>>
>>>>On Thu, 10 Nov 2011 19:40:39 +0200, coolchap <none@themoment.net>
>>>>wrote:
>>>>
>>>>>Yeah weird..no luck...it's unbelievable that the rest and I can't :D
>>>>>anyway... 10x
>>>>Same issue here for these particular files from poster "Yenc-PP-A&A"
>>>>posted on the 8th & 10th..
>>>> Deleted the (.txt) extension, then attempted to mount volume with
>>>>specified key file but will not open. Also funny that the (par) file
>>>>posted was not even recognized as a par file by the OS. Maybe we can
>>>>figure this out here.
>>>> My version of TC is 7.0. What version R U using? It probably should
>>>>not matter, but it's a start.
|
|