From owner-freebsd-questions Tue Oct 8 08:49:56 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03242 for questions-outgoing; Tue, 8 Oct 1996 08:49:56 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03232; Tue, 8 Oct 1996 08:49:48 -0700 (PDT) Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.7.5/8.6.12) id RAA13342; Tue, 8 Oct 1996 17:47:49 +0200 (IST) Date: Tue, 8 Oct 1996 17:47:49 +0200 (IST) From: Nadav Eiron To: Frank Varnell cc: questions@freebsd.org, isp@freebsd.org Subject: Re: atapi In-Reply-To: <325A6445.52E@sd.znet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Oct 1996, Frank Varnell wrote: > I have been unable to install freebsd on my new computer. > I have a Compaq 133Mhz Presario #4706. It has 2.5MB hard disk and > an 8x IDE CDROM (I don't know which brand).Also has Windows95. > I bought the Walnut Creek 2.1.5 Aug '96 release. It didn't have > the ATAPI.flp files mentioned in the book. So, I went back to the > 2.1 release which I had successfully installed on another > machine (dell w/ atapi). There is no atapi.flp in 2.1.5R because with this release the ATAPI support is built into the standard install floppy. You can use it just the same. > One of the reasons I bought this machine was that I thought a popular, > mainstream machine would make an easy BSD install. Well, from what I've heard, Compaqs are known PCI trouble makers, so that's not such a good choice. > > Yes, I checked the archives (for hours!). Lot's of similar questions > but no answers that I could find. > > Here is the problem. Running the install either from CD or 2.1 > atapi.flp, after specifying the install parameters (disk > partition,x11 preferences, etc.) when the install program asks for > install medium and I specify CDROM, it tells me it can't find the > CDROM device. Make sure that the CDROM is connected as the slave on the primary EIDE controller. Look at the boot messages and see if it is being recognized (it'll say something about atapi and wcd0). If not - try moving it to the master position on the secondary controller. In any case, have the CD loaded when the machine boots. Sometimes it matters. > Anyone able to help here? Pleeeze! > I also saw some references on patches to the driver that make it compatible with some more CDROM drives. Look in the archives for the hackers list, and search for atapi (if I remeber correctly). Good luck, Nadav