the original iso might have been fine, but that a.b.f post was one
huge mongolian clusterfuck complete with multiple encoding errors and
bad filesizes.
i tried getting it from three different servers, and each time i got
sick of trying to piece the damn thing back together and finally just
gave up and deleted it. i mean, once 'humpty dumpty' took that
nosedive off the wall...
i'm guessing someone tried to post the thing from a dial-up or
somethin'. that would certainly explain all the apparent 'burps'.
Do you do a lot of usenet binaries of 600MB file sizes? Were you using
Agent for the D/L and are you aware of Agent's buggy behaviour in
respect of incomplete yEnc posts? Do you know what par2 files are? I
didn't bother to check what encoding overheads added to the D/L size
but I doubt it was more than 50MB - hardly 'huge'.
Which were the three servers you tried with?
I monitored the upload on 4 servers:
Octanews
Claranews
Teranews
Supernews
Claranews and Teranews fell over during the upload, so I would expect
anyone using those servers to report problems - except they would
notice problems across the board.
I was initially uploading on Clara untill it fell over. At this point
I switched to Octa, reposted the stuff Clara had eaten, and completed
the post.
Octa and Supernews were flawless and I had good reports from a few
other servers. The only other negative report I have had was from a
poster whose newsserver carries a.b.f in name only. Spookily enough he
seemed to think this was my fault also. It takes but a brief look at
the posting times to tell you whether or not I am posting on dial up.
Another time you have problems of this sort I suggest you post asking
for assistance rather than throwing your dummy out of the pram and
doing a newbie bitch fest. This would serve two purposes: you might
learn something, and it would improve my monitoring of the upload.
