From owner-freebsd-questions@FreeBSD.ORG Tue Apr 21 05:26:10 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EB391065670 for ; Tue, 21 Apr 2009 05:26:10 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 055768FC22 for ; Tue, 21 Apr 2009 05:26:09 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Lw8Uh-0002pu-6k for freebsd-questions@freebsd.org; Tue, 21 Apr 2009 05:26:07 +0000 Received: from pool-72-75-50-18.washdc.east.verizon.net ([72.75.50.18]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Apr 2009 05:26:07 +0000 Received: from nightrecon by pool-72-75-50-18.washdc.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Apr 2009 05:26:07 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Tue, 21 Apr 2009 01:27:01 -0400 Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-75-50-18.washdc.east.verizon.net User-Agent: KNode/0.99.01 Sender: news Subject: Re: Dump | Restore X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nightrecon@verizon.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2009 05:26:10 -0000 Tim Judd wrote: [snip] > Long story short, BTX is what brings the PC BIOS/CMOS code execution from > 16-bit real mode, to 32-bit protected mode. > > I've had repeated problems with name-brand PCs that result in a BTX > halted. Whiteboxes/custom builds tend to work the best (and IMHO, last the > longest). [snip] Often the so called "name-brand" PCs have quirky and inferior BIOS, as well as minor hardware glitches that sometimes get ironed out with subsequent chipset steppings. Since these are primarily manufactured and sold for the Windows crowd, Windows will mask many of these deficiencies. Have problem xyz-1001 with $mfr model blah and many times the answer is "download $mfr driver revision so and so". This is where a known small hardware defect can be worked around in driver code to mask and hide the problem. This is Windows centric and if you're not using Windows then you're not supported. -Mike