This is silly. There must be a million different ways a file could be
corrupted in transit, and not detected by 'unpack'. UNPACK simply wasn't
designed to detect file corruption in transit. You should use a CRC hash
or something like that to detect corruption in transit.

Alan Ackerman
[email protected]
-----Original Message-----

That gives no report of a corrupted file; it quietly pretends it's OK.
It's effective if the only mechanism by which a file gets corrupted is
by having a few characters added at the end ("the problem at hand").
But what if a few characters were deleted, or added at the beginning?

Not the way I like to work.

-- gil

Reply via email to