🚀 go-pugleaf

In article <504bnn$6...@cloud9.net>
kenb...@cloud9.net (Kenneth Brody) writes:


> Because it wasn't a defective disk.  It was a data disk, and they were
> having problems with some function of the program with that data.  We asked
> for a copy of the disk, rather than the original, so they would still be
> able to run everything else.  What came in the mail was a Xerox(tm) copy
> of the diskette.

Also, I've recovered data from several 5 1/4 floppy disks for people. I
always started by requesting a copy of the disk created by doing a
track level copy (it's been awhile, so I might not have the term
right). This gives an image of all the data on the disk. In over 95% of
the disks I received the damage was to the pointers in the catalog,
which means that my copy had enough data to work with. I'd rebuild the
catalog on a byte level and retrieve the files. 
As to the idea of "stupid lusers", I don't buy it. Yes, I get problems
with users who refuse to read the manuals or follow instructions, but
that's fairly rare.  The majority of the problems in our school are
caused by incomplete and inaccurate instructions. When I install a new
service to our networks I know how it works. I know the ins and outs.
But I'm not a teacher. It's very difficult for me to pass on the
information in a useable way, and even more difficult to not
rationalize the problems by thinking "stupid luser",  but I'm working
on it.
I get to kill the rare ones that really are stupid, so that helps.

Bob Church