misc,comp.sys.ibm.pc.hardware.chips   
   UUvF+Ii/P6zqJmew";   
   er.org";	posting-account="U2FsdGVkX1/zAvpKH62Qres+s5bSTHSp"   
   Gecko/20110616 Thunderbird/3.1.11   
   .os2.apps:1866 comp.os.os2.setup.misc:573 comp.sys.ibm.pc.hardware.chips:1314   
   From: Peter Flass    
      
   On 8/9/2011 5:39 AM, Jonathan de Boyne Pollard wrote:   
   >>> My machine is NOT configured to support ACPI, however, setting my   
   >>> BIOS to ACPI enabled and using MPS map 1.4 seems to produce an   
   >>> otherwise pretty darn stable system. [...]   
   >>   
   >> So you have ACPI disabled even though having it enabled is more stable?   
   >   
   > The last time around, M. Piatkowski said APIC, not ACPI. I pointed out   
   > then that xe shouldn't be mixing up xyr initialisms. Disabling the   
   > Advanced Configuration and Power Interface is a very different kettle of   
   > fish to disabling any use of Advanced Programmable Interrupt   
   > Controllers. It's actually the latter that M. Piatkowski is doing.   
   >   
   > In an AMIBIOS machine, the setting that M. Piatkowski was talking about   
   > earlier is named "ACPI APIC Support" and it deals with APICs. In   
   > AWARD-Phoenix firmwares, the equivalent setting is named "APIC Mode". It   
   > almost goes without saying that if one disables the use of APICs   
   > entirely, by setting APIC mode to "disabled", then I/O APICs are as a   
   > consequence unavailable. If all local APICs are switched off during POST   
   > (as essentially all that this setting has to do), then whatever I/O   
   > APICs may do is entirely irrelevant: there is no-one listening to them.   
      
   It's unfortunate that these two acronyms are so easily confused.   
      
   --- Internet Rex 2.31   
    * Origin: A noiseless patient Spider (1:261/20.999)