Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!think.com!unixland!bill
From: bill@unixland.uucp (Bill Heiser)
Newsgroups: comp.periphs.scsi
Subject: Re: WHAT IS SCSICNTL.EXE
Message-ID: <1991Mar20.031334.11326@unixland.uucp>
Date: 20 Mar 91 03:13:34 GMT
References: <2@lehigh.bitnet> <283400075@adaptx1>
Organization: Think_Tank BBS & Public Access Unix
Lines: 33

In article <283400075@adaptx1> neese@adaptx1.UUCP writes:
>
>>I don't mean to knock the scsicntl program, but use it with care!
>
>Uhmmm.  Whenever anyone has a problem with SCSICNTL, I would like to hear
>about it.  Please Email me.  I test it with quite a few devices before I
>
>As far as this particular incident goes.  I find it interesting.  The Wren
>IV was one of the first drives I developed SCSICNTL for.  I have used it on
>this drive since the drive first came out.  I am at a loss as to what
>SCSICNTL could have done to cause this problem.  What version of SCSICNTL
>are you using?
>

Roy,

This *was* a pretty strange incident.  The funny part was that although
I was changing a parameter on the CDC Wren, it was another drive on the
chain (a Toshiba MK-156FB I believe) that got corrupted!

If you're interested in more details, let me know, and I'll send e-mail.

As I said in my original posting, I definitely don't mean to knock
SCSICNTL.EXE.  It is a great (and VERY useful) program, and thanks for
making it available!

Bill

-- 
home:	bill@unixland.uucp         The Think_Tank BBS & Public Access Unix
	...!uunet!think!unixland!bill
	...!{uunet,bloom-beacon,esegue}!world!unixland!bill
508-655-3848 (2400)   508-651-8723 (9600-HST)   508-651-8733 (9600-PEP-V32)