Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!nosc!crash!pro-graphics.cts.com!elund
From: elund@pro-graphics.cts.com (Eric Lund)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Hard drive problem (SPINRITE II)
Message-ID: <1643@crash.cts.com>
Date: 24 Feb 90 09:56:11 GMT
Sender: root@crash.cts.com
Lines: 29

> In article <1617@crash.cts.com> elund@pro-graphics.cts.com (Eric Lund) writes:
>> I never thought I'd be one to look for room to plug Spinrite II.  I've heard
>> of a lot of problems using the program.  Stopping the program (by following
>> the instructions) can be dangerous and you risk losing boot capability and
>> maybe some data.  That is a scary factor, but it may help to know I had been
> 
> I have been using Spinrite II ever since it was available, and have never
> had problems interrupting it and restarting it.  Where did you hear this?
> Perhaps you are thinking of the original Spinrite version?

No, this was definitely Spinrite II.  I talked with several users (and saw the
frustration on their faces) as they tried to fix their drives.  The worst case
was an AT&T computer user who interupted the program as instructed, exited the
program, and turned off the machine.  Later, it wouldn't boot.  He had a hell
of a time (since it was an old AT&T dos) getting it up and running again.  He
had to install a new DOS on the system, and his old DOS didn't take kindly to
that idea.  He did get his system working, but it consumed several hours.

This incident is undeniably linked to Spinrite II, but if it was the
"interrupting" that did it, or the main program that did it, who knows.  I
also suspect his old system didn't help matters, but I'd rather believe the
fault lied in his interruption of the program.  

Eric

 ProLine: elund@pro-graphics
    UUCP: ...crash!pro-graphics!elund
ARPA/DDN: pro-graphics!elund@nosc.mil
Internet: elund@pro-graphics.cts.com