From owner-freebsd-questions Thu Oct 23 21:36:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA21086 for questions-outgoing; Thu, 23 Oct 1997 21:36:40 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA21069 for ; Thu, 23 Oct 1997 21:36:33 -0700 (PDT) (envelope-from jcwells@u.washington.edu) Received: from saul3.u.washington.edu (root@saul3.u.washington.edu [140.142.83.1]) by jason02.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA36942 for ; Thu, 23 Oct 1997 21:36:31 -0700 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP id VAA10545 for ; Thu, 23 Oct 1997 21:36:30 -0700 (PDT) Message-Id: <3.0.3.32.19971024043954.007cd400@jcwells.deskmail.washington.edu> X-Sender: jcwells@jcwells.deskmail.washington.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 24 Oct 1997 04:39:54 +0000 To: freebsd-questions@freebsd.org From: Jason Wells Subject: Brokeness of floppy images Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk These are general questions. This message egocentrically assumes that my machine is not a cause of this problem. I do not think this is too far fetched because the 3.0-SNAP images work fine and other folks have had this trouble as well. I have had trouble with the brokeness of my boot.flp images for 2.2.2. This trouble occurs on a downloaded image. It occurs on the boot.flp image from my CDROM. It even occurs using the install.bat file on the CDROM. This leads me to believe that this image was broke on the day it was born. (Yes, I know... the other common denominator is my computer.) I know there is a workaround. I have used it succesfully. My primary concern is that the very first contact many people will get with FreeBSD is "panic double fault". Is this problem sporadic? Is a fix in the works? Could the website reflect that there is a small problem so that people don't get scared off by nasty error messages? I submit that even if this is not a high priority item that at least the unsuspecting user could be warned or forced to use a modified install procedure with a 3.0-SNAP image. I realize that there may be more to this issue than I am privy to. I am just calling it as I see it from an enduser perspective. Thanks, Jason Wells