XPost: comp.os.os2.networking.tcp-ip, comp.os.os2.apps   
   From: what.ever@neverm.ind   
      
    >> My ISP claims the poblem only happens with those files, the files   
    >> may be "corrupt" or it may have to do with the "algorithm".   
      
    >> Can the ISP be right?   
      
    > For certain values of "right".   
      
   So it's not guaranteed to be bogus.   
      
   I've transfered files with the same names quite often, my homepage is   
   in use for diff-backups.   
      
    > The content HTTP server might not support byte ranges.  Your   
    > WWW browser might be asking for gzip transfer encoding of an   
    > LZH archive.   
      
   If (!) it happens again, does anybody want me to reproduce the same   
   file? I cannot download it, but a file called ZIP2.002 was just   
   PMSplit's part 2 of ZIP2.LZH, which contained new files from Hobbes   
   and had the same size as ZIP2.001 (there were 3 parts).   
      
    > You might have asymmetric Internet connections, where the   
    > upstream bandwidth and downstream bandwidths are   
    > not the same.   
      
   Yes, ADSL2.   
      
    > no-one is going to be able to tell you what's actually going on.   
      
   Well, at least it isn't a certainty the ISP is making up problems at   
   my side (I'm happy with them, it's just an easy claim and it seems (!)   
   to be a normal situation).   
      
    > For all that we know, this is some wacky compression algorithm   
    > bug in the HTTP  transfer codecs at one or the other ends that   
    > only occurs when the current file pointer is past the 1GiB mark.   
      
   Understood, thanks.   
      
      
   --   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)