From owner-freebsd-bugs  Thu Feb  8 09:56:52 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA04415
          for bugs-outgoing; Thu, 8 Feb 1996 09:56:52 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA04405
          for <freebsd-bugs@FreeBSD.org>; Thu, 8 Feb 1996 09:56:37 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA28874; Fri, 9 Feb 1996 04:56:07 +1100
Date: Fri, 9 Feb 1996 04:56:07 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199602081756.EAA28874@godzilla.zeta.org.au>
To: hsu@clinet.fi, j@uriah.heep.sax.de
Subject: Re: bin/984
Cc: freebsd-bugs@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de
Sender: owner-bugs@FreeBSD.org
Precedence: bulk

>> if=/dev/sd0c of=/dev/sd0 from fixit floppy, as booteasy is just an extra
>> delay on boot for me.  If the de facto standard is that from motherboard to
>> motherboard the translation can either be the disk originated geometry or
>> /64/32 geometry, booteasy should probably try both.  In my case I was using
>> the same NCR controller, the NCR bios on the motherboards differed.

>Booteasy is at the mercy of your BIOS.  It's not booteasy that can
>decide about which translation to use.  Sorry, but *we* cannot fix
>this problem.  It's a braindamage inherent to PC BIOSes.

Actually it should be possible to fix it by running fdisk to set the new
C/H/S values.  The braindamage isn't inherent - it doesn't seem to be
present in the BT445C BIOS.  Is the NCR BIOS braindamaged?  I just got
one and something is to broken for it to work at all :-).

Bruce