Robert Lane
February 9th, 2010, 12:11 PM
Although many have wanted to either dismiss or refuse to acknowledge this issue, Apple continues to have major problems with it's Nehalem chipset:
Apple acknowledging, investigating Mac Pro problems? | MacNN (http://www.macnn.com/articles/10/02/09/temporary.workaround.requires.extra.hardware/)
Although I often work with third-party developers to help rectify global issues this one in particular is something Apple has been keeping close the their chest.
The caveat is that with the soon-to-be-released new hardware releases from Apple - along with how they choose to finally address this particular issue - it would be very wise *not* to make any investment in Nehalem-based hardware until either they find a global, proven fix to this problem and/or wait for the new "next-gen" hardware to be released and see if it too suffers from the malady.
Caveat emptor, my friends.
Apple acknowledging, investigating Mac Pro problems? | MacNN (http://www.macnn.com/articles/10/02/09/temporary.workaround.requires.extra.hardware/)
Although I often work with third-party developers to help rectify global issues this one in particular is something Apple has been keeping close the their chest.
The caveat is that with the soon-to-be-released new hardware releases from Apple - along with how they choose to finally address this particular issue - it would be very wise *not* to make any investment in Nehalem-based hardware until either they find a global, proven fix to this problem and/or wait for the new "next-gen" hardware to be released and see if it too suffers from the malady.
Caveat emptor, my friends.