From owner-freebsd-bugs  Fri Dec 13 22:18:03 1996
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA13002
          for bugs-outgoing; Fri, 13 Dec 1996 22:18:03 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA12985
          for <freebsd-bugs@freebsd.org>; Fri, 13 Dec 1996 22:18:01 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id WAA17069; Fri, 13 Dec 1996 22:18:00 -0800 (PST)
To: miketsho@erols.com
cc: freebsd-bugs@freebsd.org
Subject: Re: bin/2107 Request for info 
In-reply-to: Your message of "Fri, 13 Dec 1996 17:29:19 PST."
             <32B202EF.7BF3@erols.com> 
Date: Fri, 13 Dec 1996 22:17:59 -0800
Message-ID: <17065.850544279@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Just throught I would check to see if you had any progress with this
> problem. I know that you guys are busy but wanted to see if you had
> any ideas on what maybe happening. I have been trying to solve this

Fixing this will probably require that either one of two things happen:

1. Our IDE CDROM guy gets ahold of one of these drives (somehow) and
   figures out what's happening.

2. Our IDE CDROM guy fixes your drive by sheer luck in the process
   of fixing something else.

Either way, you're probably going to have to track the progress of
2.2 and 3.0-current since that's where all the IDE CDROM driver
development is now happening.

					Jordan