From owner-freebsd-questions  Mon Feb 10 09:49:29 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA14429
          for questions-outgoing; Mon, 10 Feb 1997 09:49:29 -0800 (PST)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14418
          for <freebsd-questions@freebsd.org>; Mon, 10 Feb 1997 09:49:23 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id JAA00214; Mon, 10 Feb 1997 09:49:15 -0800 (PST)
Date: Mon, 10 Feb 1997 09:49:15 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Thabet Birro <tbirro@bb.iu.net>
cc: freebsd-questions@freebsd.org
Subject: Re: atapi.flp (where is it?)
In-Reply-To: <Pine.SUN.3.90.970210084710.20904A-100000@bb.iu.net>
Message-ID: <Pine.BSI.3.94.970210094750.195D-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 10 Feb 1997, Thabet Birro wrote:

> I have recently attempted to install 2.1.6 (Walnut Creek) using
> the CD-ROM version, to no avail.  I have an atapi cd.  The Docs
> indicates the need for an atapi.flp instead of the boot.flp (at
> least for 2.1.5, which is the version discussed in the hard
> copy docs I am referring to).

It doesn't exist anymore.  The atapi driver is built into the regular
boot.flp.

> The install doc for 2.1.6 doesn't say anything about atapi.flp,
> however.  But it does mention an early support for atapi devices
> named wcd.  Well, the device is not there when I generate the
> boot floppy (using boot.flp of 2.1.6) and there is no atapi.flp
> on the cd-rom.  So how are we supposed to get the wcd device?

Your CD was not detected.  Try moving it to the slave position on the
primary IDE controller.

> Also, does anyone know if the Walnut Creek 2.1.6 release has the
> fix for the setlocale problem?

No.  2.1.6 was the affected release; it has been pulled until a new, fixed
2.1.7 is released. 

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major