On 1/24/04 3:18, "Robert Nicholson" wrote: > What I did was a little stupid but I actually force quit the program > whilst it was testing > the drives controller I this this is an important thing to mention. Can't be a good idea to mess around with a program doing low level hardware work. > I never expect software of any kind to permanently damage > hardware. I wouldn't say the software did in this case, at least it doesn't seem to be the software's fault. That said, I'm sorry for the loss of your drive. Maybe someone at the developer can help you get it back. (Oh, and I seem to remember being able to blow out a sound chip on a Commodore 64 with the right (or better wrong) software command, though it was nothing a regular user would do by mistake.) -- Roger