Yes, it does sound like maybe a betworking problem, but you might also want
to check that the bunzip on both sides is the same version or that they are
using the same encryption algo if not.  It might also be worth checking if
they are processing the same (IOW, if one is a 64 bit machine and the other
32, it seems inconceivable that bunzip might get different answers for 1,2,3
byte chunks but could if not coded to handle the difference).

NTL, it does seem more like network issues and the actual transfer protocol
issues.

On 9/13/06, Eric Shubes <plug@shubes.net> wrote:
>
> Victor Odhner wrote:
> > Is there a file transfer protocol that will verify
> > the data as it comes across, and retry any failed
> > blocks?  Apparently sftp is not doing this.
> >
> > I have a 1.5 GB .bz2 file on one computer that I am
> > trying to transfer to another nearby, via a local
> > router.  I don't have DVD drives.  (Both boxes have
> > USB ports, would that work better?)
> >
> > In two attempts (30 minutes each), the number of
> > bytes received at least has been right.  But the
> > files arrive broken (according to bunzip2 -t) and
> > md5sum has given non-matching results.
> >
> > The two wrong results have differed from each other,
> > so I will try once again . . .  Each try takes
> > 30+ minutes.
> >
> > Thanks,
> >
> > Vic
>
> This is really sounding like a networking problem to me. I'd try using a
> crossover cable to connect the two machines directly.
>
> In addition, Alex's split/cat'ing it suggestion is a good one.
>
> --
> -Eric 'shubes'
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
Be who you are and say what you feel, because those who mind don't matter
and those who matter don't mind.  - Dr. Seuss