From owner-freebsd-questions Tue Oct 8 21:22:22 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA03905 for questions-outgoing; Tue, 8 Oct 1996 21:22:22 -0700 (PDT) Received: from earth.gaianet.net (earth.gaianet.net [206.171.98.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA03896 for ; Tue, 8 Oct 1996 21:22:18 -0700 (PDT) Received: from localhost (vince@localhost) by earth.gaianet.net (8.7.6/8.6.12) with SMTP id VAA04713; Tue, 8 Oct 1996 21:21:48 -0700 (PDT) Date: Tue, 8 Oct 1996 21:21:48 -0700 (PDT) From: -Vince- To: dwhite@resnet.uoregon.edu cc: questions@freebsd.org Subject: Re: BootEasy In-Reply-To: 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, Doug White wrote: > > > They don't -- the BIOS doesn't support it. > > > > Shouldn't the second HD be able to boot if the BIOS of the > > motherboard supports both primary and secondary interfaces? > > The SECOND HARD DRIVE in the system, yes. (I can't remember if it must be > on the primary controller or not.) The THIRD DRIVE no. The BIOS contains > two identifiers for boot disks: 0x80 and 0x81. These are assigned to the > first two disks found (except on some scsi controllers which can control > which designation is put on each disk). The second drive is on the primary controller since it won't make sense to put the second drive on another controller. I wonder what made the Booteasy menu change to not support the second drive when the third drive is connected to the secondary controller... Vince - GaiaNet Corporation Unix Networking Admin