From owner-freebsd-questions  Tue Nov 28 12:19:47 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA01743
          for questions-outgoing; Tue, 28 Nov 1995 12:19:47 -0800
Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA01738
          for <questions@FreeBSD.org>; Tue, 28 Nov 1995 12:19:46 -0800
Received: (hlew@localhost) by vegemite.Stanford.EDU (8.7.1/8.6.4) id MAA18311; Tue, 28 Nov 1995 12:19:35 -0800 (PST)
Date: Tue, 28 Nov 1995 12:19:35 -0800 (PST)
From: Howard Lew <hlew@genome.Stanford.EDU>
To: Julian Elischer <julian@ref.tfs.com>
cc: questions@FreeBSD.org
Subject: Re: 2.1.0-RELEASE problems...
In-Reply-To: <199511220049.QAA07480@ref.tfs.com>
Message-ID: <Pine.SUN.3.91.951128121814.18253D-100000@vegemite.Stanford.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.org
Precedence: bulk

On Tue, 21 Nov 1995, Julian Elischer wrote:

> actually you should still be able to install FreeBSD with the
> drives disabled from the BIOS, as we don't USE the Bios..
> 
> note the geometry assigned to the disks when you DO have them for the BIOS
> so you can inform the install code of this geometry when you are doing
> the SLICING menu (option 'G' I believe)...
> you should be able to install as per usual..
> booting is another question....
> but it's worth a try..
> 
> make sure that you install the win95 first..
> it overwrites other system's bootmanagers (gee thanks usoft..)
> 
> if it doesn't work, it'd be worth booting and using the 'fixit' option to
> get a shell and examining the output of fdisk and disklabel
> 
> 


Thanks for the help.  It works great now.... Although the DTC2278 EB 
controller wouldn't boot with the boot manager, I can boot up freebsd 
with the fbsdboot.exe in Win 95 Dos mode.