From owner-freebsd-hackers  Mon Aug 26 23:34:42 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA16518
          for hackers-outgoing; Mon, 26 Aug 1996 23:34:42 -0700 (PDT)
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA16503
          for <freebsd-hackers@freebsd.org>; Mon, 26 Aug 1996 23:34:37 -0700 (PDT)
Received: by gvr.win.tue.nl (8.6.13/1.53)
    id IAA11231; Tue, 27 Aug 1996 08:34:26 +0200
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199608270634.IAA11231@gvr.win.tue.nl>
Subject: Re: 2.1.5 install failure: booting from fd0 in stead of sd0
To: joerg_wunsch@uriah.heep.sax.de
Date: Tue, 27 Aug 1996 08:34:26 +0200 (MET DST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199608270524.HAA22579@uriah.heep.sax.de> from J Wunsch at "Aug 27, 96 07:24:18 am"
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

J Wunsch wrote:
> Herein lies the rub.  dosdev == 0 means it's a floppy disk.  boot.c
> converts this into `maj = 2'.  Only if the 0x80 flag is set, it will
> move to maj = 0 (wd) or maj = 4 (sd).
> 
> If i read the code right, it looks as if your BIOS doesn't pass the
> correct value in %dl down to the bootstrap.  (It apparently passes
> 0 there as opposed to the boot drive BIOS ID.)  Call it ``broken''...
> 
> Your only chance short of replacing the BIOS is to hack the bootcode
> on your harddisk so it will never try booting off a floppy again.

I concluded the same. However, how can it be that a previously installed
NT on a FAT filesystem does boot?

-Guido