On Fri, 13 Jun 2008 06:59:35 -0700 (PDT), "void.no.spam.com@gmail.com"
<void.no.spam.com@gmail.com> wrote:

>I have a 120 GB hard drive that my RAID controller encountered an
>error with, so I am trying to wipe it and return it to the
>manufacturer. But when I use Copywipe to wipe it, Copywipe encounters
>an error at 52%. It asks me if I want to continue, and I enter Y, but
>then Copywipe freezes the system.

I get freezes over the years (and in my previous thread here) for
various reasons, and I've never understood all these freezes.

Shouldn't properly written software intercept bad return codes from
subroutines, including system subroutines, display an error message,
and keep going? Even if they can't complete the assigned task.

I've only written software for IBM mainframes, but if I didn't check
if I was dividing by zero before I divided, it was MY fault. If I
called a subroutine and didn't check for a bad return code as soon as
the subroutine ended, it was MY fault. If I wrote a subroutine that
could crash, it was MY fault. I prevented this by careful reviewing
of the code and by careful testing, including with bad data. And by
fixing it after the user found that I hadn't adequately tested it,
which was rare, but it was MY fault.

And nothing I could do would crash the OS because it had been tested
too, by IBM.

So how come there are so many crashes and freezes in the PC world?
People, including MS, eager to get their products on the market
without adequate testing?

> So it looks like Copywipe will only
>be able to wipe half the drive. Any way I can get past that error and
>wipe the rest of it? Any other wiping software that can handle a bad
>drive?


If you are inclined to email me
for some reason, remove NOPSAM :-)