🚀 go-pugleaf

Picture this:  it's been a long day, and in my late night stupor, 
I still need to get ready to teach a course the next day.  I pull
the disk I used last semester, and bring up my brand new copy
of PCTOOLs V8, to do a disk copy.  Put the source disk in, get some
pretty characters changing as the data is read.  Put the target 
disk in, and immediately get a message about a CRC error.

Stop, try formatting the disk, using both PCTOOLS and DOS format.
No go, everything locks up.  So I say to myself, "must be a bad
disk, mumble, mumble, and get a new one.  Same result.  Had I been
awake, I would have stopped here, but of course, I get another disk
from a different package, and try again, and now have three,
apparently permanently, destroyed HD disks.  Finally it occurs to
me to check my source disk, when I discover that it is fine, but it
IS a DD disk.  Apparently, PCTOOLS happily tried to copy a DD to a
HD with no warning message, and destroyed the HD in the process.

I'm willing to accept the cost of three floppies as payment for my
stupidity, but I do have a few questions you all might be able to 
help with:

1)  What exactly happened?

2)  Isn't this somewhat user-hostile behavior for an expensive tool
	supposed to make my life easier?

3)  Is there a way to recover these disks?  None of the tools I have,
	including diskfix, etc, would touch them.

4)  Why do I always wait till the last minute to do this stuff?

Peace, 

Al F.


+-------------------------------------------------------------------+
| Al Folsom                 | Object Oriented Programming?  We've   |
| Fischer & Porter Co.      | been doing that for years...          |
| ...uunet!bigmax!folsom    |                                       |
| also folsom@decus.org     | When the customer objects to the way  |
| KY3T@WA3TSW (Ham)         | it works, we go program some more!    |
+-------------------------------------------------------------------+