From owner-freebsd-doc Sat Feb 2 16:31:50 2002 Delivered-To: freebsd-doc@freebsd.org Received: from blueyonder.co.uk (pcow058o.blueyonder.co.uk [195.188.53.98]) by hub.freebsd.org (Postfix) with ESMTP id F2F2F37B417; Sat, 2 Feb 2002 16:31:43 -0800 (PST) Received: from pcow058m.blueyonder.co.uk ([127.0.0.1]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.757.75); Sun, 3 Feb 2002 00:31:42 +0000 Received: from fluoxetine.lan (unverified [62.31.193.116]) by pcow058m.blueyonder.co.uk (Content Technologies SMTPRS 4.2.9) with ESMTP id ; Sun, 3 Feb 2002 00:31:42 +0000 Date: Sun, 3 Feb 2002 00:32:32 +0000 (GMT) From: Andrew McKay X-X-Sender: andy@fluoxetine.lan To: freebsd-doc@freebsd.org Cc: freebsd-gnats-submit@freebsd.org Subject: Re: docs/34524: [PATCH] - Add important pre-installation notice In-Reply-To: <20020202054810.A26652@blackhelicopters.org> Message-ID: <20020203002804.N68626-100000@fluoxetine.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 2 Feb 2002, Michael Lucas wrote: > One minor nit: you combine an emphasis and CAPITALS. I'd just use > . Combining italics and capitals isn't very > professional-looking. It's like the use of multiple exclamation > points. This should, therefore, be the best patch ever...being as it is the combined efforts of me, Gary and Michael. And yeah, I had reservations about the combination of and CAPS but I went with it because you can never have too much stress...or something :) -- also at: http://www.openirc.co.uk/freebsd/install.diff --- chapter.sgml Sat Feb 2 12:18:14 2002 +++ chapter.sgml.new Sat Feb 2 12:22:45 2002 @@ -4553,6 +4553,18 @@ questions and answers for people wishing to dual-boot FreeBSD with MS-DOS. + + Some installation problems can be avoided or alleviated by + updating the firmware on various hardware components, most notably the + motherboard. If the installation fails then updating the BIOS may + solve the problem. Refer to your motherboard manufacturer's website + for information on BIOS revisions and upgrade instructions. + Most manufacturers strongly advise against upgrading motherboard + BIOSs unless you have a good reason for doing so. The + process can go wrong, causing the BIOS to be + permanently destroyed. + + What to Do If Something Goes Wrong... -- -- Andrew McKay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message