From owner-freebsd-hackers Mon Dec 18 23:39:21 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA28106 for hackers-outgoing; Mon, 18 Dec 1995 23:39:21 -0800 (PST) Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA28101 for ; Mon, 18 Dec 1995 23:39:14 -0800 (PST) Received: (from julian@localhost) by jhome.DIALix.COM (8.7.3/8.7.3) id PAA13516; Tue, 19 Dec 1995 15:35:46 +0800 (WST) From: Julian Elischer Message-Id: <199512190735.PAA13516@jhome.DIALix.COM> Subject: Re: CD WORM To: gpalmer@westhill.cdrom.com Date: Tue, 19 Dec 1995 15:35:46 +0800 (WST) Cc: ag@leo.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de In-Reply-To: <12675.819308557@westhill.cdrom.com> from "gpalmer@westhill.cdrom.com" at Dec 18, 95 09:42:37 am X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk The burner that jordan leant me is broken.. it won't load a disk.. when I get back (Jan 10) jordan os going to give me another to try. and I hope to get further with it.. > > > Armin Gruner wrote in message ID > : > > sorry for intruding the list without being on it :-) but we've the following > > problem here: We tried to connect a WORM to our FreeBSD machine, but have > > no luck so far. I both tried 2.1 with NEW_SCSICONF, and -current as of 12/18. > > Okay. The story generally is ``it don't work''. Julian (Elischer) had > Jordan's burner, but I think he's debunked back to Oz, so I'm not sure > what's happening. > > > (aha0:4:0): "PINNACLE RCD-1000 1.33" type 4 removable SCSI 2 > > worm0(aha0:4:0): Write-Once - UNTESTED > > worm0(aha0:4:0): NOT READY asc:4,1 > > worm0(aha0:4:0): Logical unit is in process of becoming ready > > worm0: oops not queued > > > > worm0(aha0:4:0): could not get size > > - can't get capacity. > > That's better than I got the last time I tried (admittedly ~5 months > ago) - it panic'd the machine! (Although I do seem to remember that > being fixed) I got the burner here to the point where I was about ready to write.. but it keeps spitting out the disk.. so..... the 'oops not queued' message must be from 2.1 right? I am sure I fixed that (false) message.. it MIGHT be ready to write at this stage..(under -current) did you try write to it..? julian > > Gary > >