From owner-freebsd-current Sun Jun 28 17:31:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04424 for freebsd-current-outgoing; Sun, 28 Jun 1998 17:31:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles355.castles.com [208.214.167.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04390 for ; Sun, 28 Jun 1998 17:31:39 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA21403; Sun, 28 Jun 1998 17:31:31 -0700 (PDT) Message-Id: <199806290031.RAA21403@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: joelh@gnu.org (Joel Ray Holveck), jkh@time.cdrom.com, thyerm@camtech.net.au, mike@smith.net.au, Matthew.Thyer@dsto.defence.gov.au, jlemon@americantv.com, current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) In-reply-to: Your message of "Sun, 28 Jun 1998 22:29:20 -0000." <199806282229.PAA12693@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Jun 1998 17:31:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > So, given all of that, I will now work to remove all references to > > > fbsdboot.exe in our installation instructions and simply recommend > > > that a boot floppy be used in *all* installation cases. > > > > I'm rather unclear on whether you are serious in this idea or not. > > But if so, don't some devices need initialization code that only > > a config.sys / fbsdboot combination can provide? (I thought that was > > in the handbook or something.) > > Yes. This is the only way to make some "compatability mode" sound > cards function. Many of these are actually supported "properly" now with Luigi's code. (Now if he'd just finish it... 8) > It is also useful for emulation drivers to be loaded at the top of 640, > and the memory size returned adjusted down, since BSD now respects this > for APM support. Unfortunately, this isn't the case. A DOS-mode driver doesn't adjust the BIOS memory tables (for obvious reasons), and most DOS-mode drivers are going to want to have resources vectored to them that are simply not available. It was a nice idea when we were talking about it before, but basically by the time you've reverse-engineered a driver enough to provide it with an adequate emulation environment, you might as well rewrite it properly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message