From owner-freebsd-questions  Mon Feb 10 09:34:30 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA13597
          for questions-outgoing; Mon, 10 Feb 1997 09:34:30 -0800 (PST)
Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA13591
          for <freebsd-questions@freebsd.org>; Mon, 10 Feb 1997 09:34:16 -0800 (PST)
Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.7.5/8.6.12) id TAA13198; Mon, 10 Feb 1997 19:33:57 +0200 (IST)
Date: Mon, 10 Feb 1997 19:33:56 +0200 (IST)
From: Nadav Eiron <nadav@barcode.co.il>
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.BSF.3.91.970210193112.13190A-100000@gatekeeper.barcode.co.il>
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:

> 
> Hello all,
> 
> 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).

The doc's on atapi.flp date back to 2.1.0. It's not required for neither 
2.1.5 nor 2.1.6. Just use the standard 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?

What do you mean the device is not there? It will not show up in the 
configuration editor. Make sure your ATAPI CD is connected to either the 
slave position on the primary controller or the master position on the 
secondary controller, boot, and check to see if the kernel shows a 
message showing that your drive is detected. You'll want to have the CD 
in the drive when you turn the power on. Sometimes it helps.

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

2.1.6R has the buggy version. Consult the web site for the way to patch 
it up once you get your system up and running.

> 
> Thanks,
> Thabet Birro <tbirro@iu.net>
> p.s. please cc me on your response as I am not subscribed to this
> list.
> 
Nadav