From owner-freebsd-questions  Fri Oct 20 08:18:24 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA07408
          for questions-outgoing; Fri, 20 Oct 1995 08:18:24 -0700
Received: from dekalb.vf.mmc.com (dekalb.vf.mmc.com [192.35.35.21])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA07401
          for <freebsd-questions@freebsd.org>; Fri, 20 Oct 1995 08:18:15 -0700
From: bosch@meadow.mdso.vf.ge.com
Received: from franklin.vf.mmc.com (franklin.VF.GE.COM [166.17.5.51]) by dekalb.vf.mmc.com (8.6.12/8.6.12) with ESMTP id LAA24897 for <freebsd-questions@freebsd.org>; Fri, 20 Oct 1995 11:18:10 -0400
Received: from ccc2.meadow.mdso.vf.ge.com (ccc2.meadow.mdso.vf.ge.com [3.9.16.2]) by franklin.vf.mmc.com (8.6.12/8.6.10) with SMTP id LAA00484 for <freebsd-questions@freebsd.org>; Fri, 20 Oct 1995 11:18:07 -0400
Received: from opus.meadow.mdso.vf.ge.com by ccc2.meadow.mdso.vf.ge.com (4.1/MMC Sun server D-3.3)
	id AA09995; Fri, 20 Oct 95 11:13:50 EDT
Received: by opus.meadow.mdso.vf.ge.com (4.1/GEA Sun client 1.19B)
	id AA06090; Fri, 20 Oct 95 11:15:29 EDT
Date: Fri, 20 Oct 95 11:15:29 EDT
Message-Id: <9510201515.AA06090@opus.meadow.mdso.vf.ge.com>
To: freebsd-questions@freebsd.org
Subject: Re: Western Digital Caviar 1.28Gig HDD?
Sender: owner-questions@freebsd.org
Precedence: bulk

>Obviously, because of the old bios, he has to use "Ontrack Disk Manager"
>to even get DOS running. He cannot seem to locate the BIOS chipset on
>this particular No-name motherboard.
>
>The most logical choice would be to buy an EIDE board and hopefully, the
>board's bios will take over.
>
>>To those of you who have ran into the bios' limit of 528Meg, what kind of
>EIDE board(s) did you get? We would appreciate any insight that you may
>share with us.

I just ran into to this as well.  However, I didn't use "Ontrack"
although I have the exact same drive (Western Digital 1.28Gig Caviar).
What I did was to make sure my DOS partition was a
FreeBSD-root-partion-size less than the 1024 cylinder (~500 MB) limit
(in my case I made this 32 MB less) so that when allocated, the root
partition was within the 1024 cyclinder limit and, therefore, the boot
manager could access and execute the kernel.  With the kernel running,
FreeBSD has no trouble accessing the rest of the disk even though the
"raw" BIOS can't.

By the way - I did it the hard way, I used fdisk to repartion disk to
the new size and therefore lost my entire DOS partion - no suprise.  (I
did, however, first make backups).  I found out later that there is a
utility on the FreeBSD CDROM (or ftp site I assume) called "FIPS.EXE"
that will allow you to adjust the size of a HD partition WITHOUT losing
the data.  I haven't tried it, however.

Never the less, I would be interested to know how FreeBSD works with
the "Ontrack Disk Manager".  For instance, does it still require the
root partition to be within the 1024 limit?

#include <standard.disclaimer>

  ___     ___ ___      ___  Charles T. Bosch (bosch@meadow.mdso.vf.mmc.com)
 /   /__//__//__//   //__   Lockheed Martin Corporation 
/__ /  //  // \ /__ //___   Valley Forge, Pennsylvania USA
==========================================================================
Reporter, n.:
	A writer who guesses his way to the truth and dispels it with a
tempest of words.
		-- Ambrose Bierce, "The Devil's Dictionary"
--------------------------------------------------------------------------