If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#21
|
|||
|
|||
The last word on yEnc
On Fri, 27 Jul 2007 15:52:28 GMT, Maple1 wrote:
I did not use the term corrupt as a mater of fact I did not say that the files get corrupted I said there are few different methods of of codeing in YENC that is why in Thunderbird some are decode some are not. That's correct, you did not use the term "corrupt", you used the word "problems" which could mean anything, so instead of nit picking and splitting hairs over which word you did or didn't use, I will repeat what I said: Using Agent Forte, I download hundreds of yEnc files from many different newsgroups and I don't have any "problems" with any of them. If you choose to use cheap, dysfunctional software to access Usenet, then don't blame yEnc for your problems! And if Yenc saves so much bandwidth Why the Hell does it still send s JPG in a Multi Part File? For the same reason that large JPGs, which are NOT yEnc encoded, get sent in multiple parts. Unless, of course, you are suggesting that evil and malicious software vendors have done this terrible thing just to annoy people like you. On the 23rd of July a poster calling himself "me" sent a NON-yEnc JPG image to the aviation news group which consisted of 81 separate parts. The vast majority of posters in this group send very SMALL low resolution images so you don't see much in the way of multi-parts, but in some of the other picture news groups where files are very large, nearly all of them are split into many parts even though they have no special encoding, just plain, old fashioned UUencode. Why? Because if you try sending a LARGE file in one piece, there is an excellent chance that any error in transmission will cause the posting to fail. If you see something along the lines of (*/81) or [81/81] next to the file header - it can be any number, that tells you that the file was split into that many pieces when it was sent, even if on your news reader it only shows up as one file, because your software has automatically joined all the separate parts together... just like my software joins all the separate yEnc bits together. I have also read angry posts from people here who saw a NON-yEnc JPG which their software had not joined automatically into one file, claiming that it was a yEnc file simply because it came in many separate parts, which of course is absolute nonsense. Not understanding what's going on is not a sin, but lashing out in frustration and blaming things and people, who are not at fault, is a sin. As some one posted in another thread, it really does seem like it's in one ear and out the other. Elmo I wrote Here is a good reason YENC is not one encoding method there are a few different methods all called YENC The code is not cosistaint that is why even Thunderbird has problems with it. Ricardo replied That's strange. I have been downloading hundreds of yEnc images per month, using Forte Agent, from many different news groups for several years now and I can't recall the last time I had file corruption problems. If what you claim is true, then I would be having those problems too. Ricardo |
#22
|
|||
|
|||
The last word on yEnc
On Fri, 27 Jul 2007 23:10:57 GMT, "Glenn"
wrote: If you don't want to become a "computer freak", then perhaps watching TV would be more suitable for you. That has got to be one of the stupidest comments mate. Based on the "tone" of your comments, I would suggest that I am not your mate, bub. lot's of people are not computer geeks. nor do they want to be. I see a lot of geeks that are borderline addicts that have no social life. Before you start generalising which group you wish to belong to, accept that others use the internet as a tool and don't wish to become one. It's true, there are those who use the Internet as a tool, and then there are those who are not the sharpest tools in the shed, don't know how to use the Internet, and so set about blaming others for their own inadequacies... Yes, you are right, my comments are very stupid, and you are very wise for pointing this out to me. Elmo |
#23
|
|||
|
|||
The last word on yEnc
Why not start a news group dedicated strictly for
yEnc so we don't have to put up with it here -- John Crawford Everything I Like Is either immoral, Illegal, or Fattening |
#24
|
|||
|
|||
The last word on yEnc
If posters sent individual pictures the right size, no multi part would ever
be needed. This is not a Movie NG. It is a NG for aviation PICTURES. "Elmo von Thud" wrote in message news On Fri, 27 Jul 2007 15:52:28 GMT, Maple1 wrote: I did not use the term corrupt as a mater of fact I did not say that the files get corrupted I said there are few different methods of of codeing in YENC that is why in Thunderbird some are decode some are not. That's correct, you did not use the term "corrupt", you used the word "problems" which could mean anything, so instead of nit picking and splitting hairs over which word you did or didn't use, I will repeat what I said: Using Agent Forte, I download hundreds of yEnc files from many different newsgroups and I don't have any "problems" with any of them. If you choose to use cheap, dysfunctional software to access Usenet, then don't blame yEnc for your problems! And if Yenc saves so much bandwidth Why the Hell does it still send s JPG in a Multi Part File? For the same reason that large JPGs, which are NOT yEnc encoded, get sent in multiple parts. Unless, of course, you are suggesting that evil and malicious software vendors have done this terrible thing just to annoy people like you. On the 23rd of July a poster calling himself "me" sent a NON-yEnc JPG image to the aviation news group which consisted of 81 separate parts. The vast majority of posters in this group send very SMALL low resolution images so you don't see much in the way of multi-parts, but in some of the other picture news groups where files are very large, nearly all of them are split into many parts even though they have no special encoding, just plain, old fashioned UUencode. Why? Because if you try sending a LARGE file in one piece, there is an excellent chance that any error in transmission will cause the posting to fail. If you see something along the lines of (*/81) or [81/81] next to the file header - it can be any number, that tells you that the file was split into that many pieces when it was sent, even if on your news reader it only shows up as one file, because your software has automatically joined all the separate parts together... just like my software joins all the separate yEnc bits together. I have also read angry posts from people here who saw a NON-yEnc JPG which their software had not joined automatically into one file, claiming that it was a yEnc file simply because it came in many separate parts, which of course is absolute nonsense. Not understanding what's going on is not a sin, but lashing out in frustration and blaming things and people, who are not at fault, is a sin. As some one posted in another thread, it really does seem like it's in one ear and out the other. Elmo I wrote Here is a good reason YENC is not one encoding method there are a few different methods all called YENC The code is not cosistaint that is why even Thunderbird has problems with it. Ricardo replied That's strange. I have been downloading hundreds of yEnc images per month, using Forte Agent, from many different news groups for several years now and I can't recall the last time I had file corruption problems. If what you claim is true, then I would be having those problems too. Ricardo |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
The E Word | Michelle P | Piloting | 45 | November 4th 05 02:10 PM |
New Word 'SOARING' | Ray Lovinggood | Soaring | 29 | February 5th 05 12:45 AM |
Read This Carefully please; word for word | Dudley Henriques | Military Aviation | 16 | September 6th 04 02:40 PM |
Hiroshima. The final word. | ArtKramr | Military Aviation | 10 | January 12th 04 12:20 PM |