From owner-freebsd-hardware  Tue Aug 20 14:41:03 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA06420
          for hardware-outgoing; Tue, 20 Aug 1996 14:41:03 -0700 (PDT)
Received: from shelby.visix.com (shelby-102.visix.com [149.62.102.251])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA06415
          for <freebsd-hardware@freebsd.org>; Tue, 20 Aug 1996 14:40:58 -0700 (PDT)
Received: from neptune.visix.com.visix.com (neptune.visix.com [149.62.106.32]) by shelby.visix.com (8.6.12/8.6.12) with SMTP id RAA13662 for <freebsd-hardware@freebsd.org>; Tue, 20 Aug 1996 17:40:28 -0400
Received: by neptune.visix.com.visix.com (4.1/SMI-4.1)
	id AA16804; Tue, 20 Aug 96 17:39:28 EDT
Date: Tue, 20 Aug 96 17:39:28 EDT
From: wes@visix.com (Wes Doonan)
Message-Id: <9608202139.AA16804@neptune.visix.com.visix.com>
To: freebsd-hardware@freebsd.org
Subject: ATAPI nemesis
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>From perusing the mail archives I gather that 2.1.0 and earlier versions
had difficulty with ATAPI cdrom drives -- are they still to be avoided
with the 2.1.5 release?  I don't see the wcd0 device being probed during
boot, suggests the driver was removed from the kernel.  Also, the special
atapi.flp boot image is gone from the 2.1.5 distribution.

FAQ and hardware.txt don't say too much about ATAPI; anyone successful
bringing up an ATAPI cdrom under version 2.1.5 and like to share some
hints?  Thanks much,


Wes Doonan
Visix Software Inc.