From owner-freebsd-questions  Fri Apr 18 11:28:03 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA24006
          for questions-outgoing; Fri, 18 Apr 1997 11:28:03 -0700 (PDT)
Received: from eac.iafrica.com (196-31-98-111.iafrica.com [196.31.98.111])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23983
          for <questions@freebsd.org>; Fri, 18 Apr 1997 11:27:58 -0700 (PDT)
Received: (from rnordier@localhost) by eac.iafrica.com (8.8.5/8.6.12) id UAA19621; Fri, 18 Apr 1997 20:21:28 +0200 (SAT)
From: Robert Nordier <rnordier@iafrica.com>
Message-Id: <199704181821.UAA19621@eac.iafrica.com>
Subject: Re: Creating FreeBSD boot floppy
In-Reply-To: <199704181357.GAA26493@f42.hotmail.com> from Michael Hampton at "Apr 18, 97 06:57:23 am"
To: hamptonm@hotmail.com (Michael Hampton)
Date: Fri, 18 Apr 1997 20:21:27 +0200 (SAT)
Cc: questions@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Michael Hampton wrote:

> I am having trouble creating and/or using a FreeBSD boot floppy on my PC.  It's 
> a 486DX/66.  I am pretty sure the problem is in the creation of the boot disk 
> using fdimage.  At the DOS prompt I entered the following line:
> 
> fdimage -f 1.44M -v boot.flp a:
> 
> I got the prompt to enter a floppy in drive a: (which I did), and then the 
> information regarding the formatting of the various tracks.  When it got to the 
> point of the operation regarding writing, I got the following lines:
> 
> Writing cyl 0 hd 0
> Sector not found

The most obvious explanation is a suspect floppy disk/drive.  Questions:
Did you try to create a boot floppy more than once, using different floppy
disks?  Can you DOS format the disks without errors?  Is this a 1.44M or
2.88M drive?

> When I tried to boot my machine with this disk, the PC kept rebooting after 
> telling me that it couldn't find the kernel.  Any ideas?

As there was an error creating the boot image, this isn't too surprising. :-)

-- 
Robert Nordier