From owner-freebsd-questions Sun Jun 7 10:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08790 for freebsd-questions-outgoing; Sun, 7 Jun 1998 10:43:14 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from server1.isupply.net (server1.isupply.net [209.125.244.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08729 for ; Sun, 7 Jun 1998 10:42:50 -0700 (PDT) (envelope-from chado@isupply.net) From: chado@isupply.net Received: from jshipper.isupply.net (workstation.isupply.net [209.125.244.3]) by server1.isupply.net (8.8.8/8.8.8) with SMTP id NAA28513 for ; Sun, 7 Jun 1998 13:42:48 -0400 (EDT) Message-Id: <199806071742.NAA28513@server1.isupply.net> X-Sender: jshipper@popmail.isupply.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 07 Jun 1998 13:46:28 -0400 To: "questions@freebsd.org" Subject: Boot Disk Follow Up Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all those who made suggestions on how to rectify this problem but I found it had nothing to do with the files or even hardware. I only submit this information to the list in hopes that it prevents someone else from overlooking the not so obvious. The specific mother board CMOS that I have allows you to choose whether to boot to the floppy drive or not. I, unfortunately, enabled this thinking it was the same as the boot up sequence ( A, C on most systems ). Well, it wasn't and apparently made it impossible to use the boot disk that I had created. Only after disabling this in the CMOS did the machine accept the boot disk. So, thanks again and keep up the great work. JS Jeff Shipper InterNetwork Systems Administrator Internet Supply, Inc. C.A.T. Internet Services, Inc. admin@isupply.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message