It is highly likely that Microsoft knew that the ?360 could overheat but after weighing up the many market variables decided to get to market and deal with the problem later. I would be surprised if they neglected to perform accelerated life tests and research the likely usage patterns and environment.
When will the dimwits that moan about forum English stop wasting post space and everyones time. As usual the moaning posts are full of mistakes as well. English grammar and spelling are not fixed ? it is a continously evolving language.
Work to Ride, RIde to Work...
You never finish a sentence with a semi-colon. Also "who moderates and validates the information on forums." is a question, not a statement and requires a question mark, not a full stop.
If you're going to be a pedantic at least do it properly!
Oh and FYI, Tablot = Tabloid
For starters there was no "recall". Microsoft merely admitted that they had a major problem and extended the warranty (for the 3RROD only) from 12-months to 3-years from original purchase date. So suck on that byte sized fact.
I was going to say the same thing. Microsoft has not and never will give a recall, they just sweap it under the rug and have 'fixed' the problem for their future units so they can lower their failure rate. It should have been recalled but they wont do it.
If the speaker was trying to refer to "the former ATI Technologies", why would they refer to "an unnamed ASIC vendor based in the United States"? Wouldn't that be more likely to refer to a company that, say, designs graphics chips in the US?
...well the gpu in the xbox 360 is actually and ATI chip designed by ATI, and had nothing to do with the cause of the failures, that was do to a bad cooling system design. Also there was never a recall, just a warranty extension for the particular problem that was caused by a cooling system issue. Good to see people still toss articles together without doing any wasteful research.
Drack, it wood be so much easier to take you seriously if you spent a little more time in English class instead of the computer lab.
its = it's ;
plan = plain ;
were = where ;
u = you ;
i = I ;
write = writer ;
probally = probably ;
tablot = ? ;
there = their ;
acuall = actual ;
And oh, by the way, who moderates and validates the information on forums. They are notoriously inaccurate with loads of information from self-described experts. It takes a discriminating eye and intimate knowledge of the subject to separate the wheat from the chaff on forums.
Well, at least we know that Microsoft's hardware quality is consistent with their software quality.......;-(
All joking aside, my 360 just died 2 days ago with a near-useless diagnostic message (E 74), and a few months past the 1 year warranty, so I'll probably have to foot the bill to get it repaired. I never received any word of a product recall of my unit. If Microsoft knowingly withheld relevant information affecting a recall until after a large quantity of units lapsed beyond their warranty period, for example units sold around a holday gift season, it's great fodder for a class-action suit.
Making chips that can last at least few years isn't rocket science; we've been doing it in high-volume for decades now. But it does require discipline and paying attention to details.
Makes me yearn for the "good ole days" when you could take your box of vacuum tubes down to Radio Shack, pop them on the tester, and fix the problem yourself. Sigh, my wife wont let me put a deep-submicron fab line and a BGA rework station in the garage.....
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.