From owner-freebsd-scsi  Wed Nov  6 15:23:21 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA06781
          for freebsd-scsi-outgoing; Wed, 6 Nov 1996 15:23:21 -0800 (PST)
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA06774;
          Wed, 6 Nov 1996 15:23:16 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA23930; Thu, 7 Nov 1996 00:21:57 +0100
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA18953; Thu, 7 Nov 1996 00:21:57 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA22415; Thu, 7 Nov 1996 00:07:43 +0100 (MET)
From: J Wunsch <j@uriah.heep.sax.de>
Message-Id: <199611062307.AAA22415@uriah.heep.sax.de>
Subject: Re: INSITE floptical anybody ???
To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list)
Date: Thu, 7 Nov 1996 00:07:42 +0100 (MET)
Cc: sos@FreeBSD.org
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199611062253.XAA02949@ravenock.cybercity.dk> from "sos@FreeBSD.org" at "Nov 6, 96 11:53:39 pm"
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E 
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

(Redirected to -scsi)

As sos@FreeBSD.org wrote:

> I just had one of those drop on my table so I hooked it
> up to the SCSI system, and well, its found but then it
> hangs the SCSI subsystem. I glanced through some other
> systems scsi files, and saw that the INSITE floptical
> needs some kind of "unlock" sequence in order to 
> work proberly, anybody allready done the nessesary
> magic ?? or will I have to get my fingers dirty in the
> SCSI code too...

I've once tried, too, and eventually gave up. :-(  These parts
came along with our SGI Indys, but don't worry, they basically
turned out to be the worst crap i've ever seen in this area.
Don't spend too much time into that driver, or the drive will be
dead before you finished polishing the SCSI code... :-((

Hint: pick the `od' driver to start with, it is already better in
supporting unit attention conditions etc.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)