Date: Tue, 21 Apr 2009 01:27:01 -0400 From: Michael Powell <nightrecon@verizon.net> To: freebsd-questions@freebsd.org Subject: Re: Dump | Restore Message-ID: <gsjld3$48s$1@ger.gmane.org> References: <E8298C3B2FC1CC43B3FBAC70544780A602D45118@EXCH-01.mbint.multibanka.com> <ade45ae90904202033v4bae8ec5k38f23a41525ec09e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gsjld3$48s$1>