In America, probablyCan I sue Intel for emotional distress and anxiety for killing my Sandy Bridge dreams? Maybe a class action? :sneaky:
In America, probablyCan I sue Intel for emotional distress and anxiety for killing my Sandy Bridge dreams? Maybe a class action? :sneaky:
Can I sue Intel for emotional distress and anxiety for killing my Sandy Bridge dreams? Maybe a class action? :sneaky:
I wouldn't come to that conclusion. Doesn't make sense to sell any socket 1155 CPUs if there are no motherboards one can buy without having to worry about the defect.
So it's entirely consistent that the affected cpus&motherboards are pulled. The fact that the h67 motherboards are pulled implies that the problem does in fact include the h67 chips.
Anand's post explicitly includes h67 as well.
Plus, based on the language of that engadget post the smart money is that it was a misunderstanding coupled with wishful thinking. It looks like the rep just forgot to mention H67, I didn't see any quote with them specifically saying H67 wasn't affected...only a quote saying P67 was. The rep might not even know what they were talking about either, it wasn't a chat log with Intel's head engineer.
I was going to buy a H67 myself, but I'd assume it was broken as well until there is a concrete statement it isn't....aren't they basically the same chipset after all? I mean heck, now we have rumors flying around that the cpus are broken too. Best to sit on your hands for a few days regardless.
The board bricked itself after two weeks of OS development work (lots of reboots).
Was driver work that wouldn't be applicable under vmware. But thanks for askingI recommend doing that kind of thing in VMware. That's what I have with VS 2010 Ult. on Win Server 2008 R2. Works marvelously. Of course I'm always leery about loading up my working OS with all those dev libraries and SDKs and such.
I've missed that too. Probably another misunderstanding. Pulling sales of new 1155 based CPUs due to lack of 1155 motherboards to use them with != actual problem with the CPUs.i must have missed something. Where did the rumors that the cpu's are broken come from?
On the flip side of the coin, this could be good news for those people on the sidelines, since intel won't be able to sell the new CPUs, stockpiles go up, and then, we have a nice big sale when this matter is all fixed.
Hello $150 i5-2500K! :awe:
Was driver work that wouldn't be applicable under vmware. But thanks for asking
I am very upset. I have been waiting to put together a new PC for a long while. All the talk of how great the new 2600 chip is made me finally break my piggy bank and buy a new system. Did the deed on Saturday. Pretty high end system, now with a funky motherboard. My old Q6600 chip was chugging along fine, I thought I would treat myself. Instead I treated myself to a headache.
Paul
I think most people would be annoyed by the RMA time. If the board is part of someone's main/only rig, a week or two of downtime is a major setback.As NEWB as I am at this, is it really going to be that big of a headache?
I think most people would be annoyed by the RMA time. If the board is part of someone's main/only rig, a week or two of downtime is a major setback.
Fortunately for me, this new system is in addition to two other fully functional computers. I wasn't even planning to put it to any real work until it is successfully stress tested and running with a stable BIOS. An RMA won't kill me.
However, waiting two months for new a fixed board will. Superbiiz responded and told me not to open the package yet until they have more details on the recall. I await further instruction.
Sure, it's doable on a few individual cases of failure, but I doubt that any company would do that on a recall of this scale.Don't see why ASUS or whoever could not do that as well...