🚀 go-pugleaf

posted to demon.tech.mac, comp.text.pdf


I've been using Macs since '88 (so what!), in that time I have never come
across files that have become corrupted in transfer from Mac to Mac, via
AppleShare, the files have either been corrupt in the first place, or the
transfer will not complete due to a protocol error, and you'll get an
error dialogue in the Finder.

That was "never", until a couple of months ago, when transfering an
Acrobat file from our server (AppleShare 4.0.1) via thin-net to my Mac,
file transfer complete without error, try to open the file, "this file is
damaged and is being repaired" (not an uncommon error with Acrobat if you
have been editing them via a text interface [Think C]), but then "This
file is damaged and cannot be repaired 14", - this file is "really"
damaged.

I then opened the file directly from the server, no problems, then I
transfered it again, no problems. I ignore the problem it doesn't happen
again, until a couple of days ago...

The only difference now is that I am maybe transferring 20-30 files at a
time (total size 20Mb+), and I'll get a whole batch go bad, I presume the
files get transferred in alfa-numeric order, presuming that, 4-5 files go
bad from the middle of the transfer, in sequence. Then the rest are ok.

I haven't tried the process from another Mac, as the testing of the
documents would be *extremely* boring, and there is a spanner to throw in
the works, which none of the other Macs have, RunShare, I haven't
installed it anywhere except the server and my Q950, in an attempt to test
for exactly this kind of problem. Though this is confusing since it only
seems to effect Acrobat files.

Any ideas, do you think that it is RunShare, or something else?

Thanks.


Clive Bruton (AKA The Typonaut)

clive@d-supp.demon.co.uk