Language Selection

English French German Italian Portuguese Spanish

Microsoft denies Xbox issues

Filed under
Microsoft

Microsoft has denied a report in the British tech publication The Register, that last month's recall of power cords for 14.1 million Xboxes was connected to broken solder joints inside early Xbox consoles.

Charlotte Stuyvenberg, director of global communications for the Xbox, said the report was incorrect. The problem with the power cord and the solder joints were mutually exclusive, she said.

A Microsoft statement sent earlier said: "In rare cases, solder joints have broken. This issue is not associated with the power cord replacement program..."

The statement came the same day that The Register reported that an Xbox had blown up in a user's face in Sweden even though the power cord had been replaced.

Ms Stuyvenberg said this incident was being dealt with separately. "Our people have got hold of this console to investigate the circumstances which caused it," she said.

According to hardware experts quoted in The Register, the problem is not with the power cable, but rather with the power supply on certain models.

The experts were quoted as saying that the new cable only made the problem worse; the meltdown and fire risk were caused by wear and tear on the power supply used in early models and the new replacement cables only contained a trip that reduced the risk of a fire but left users with a console which was literally fried.

In enthusiast forums, such as the Xbox Scene, there are plenty of complaints about the problem.
Postings are accompanied by screenshots to show the areas where owners claim the solder has worn off in earlier models and caused the problem.

Ms Stuvyenberg said the Swedish case was a "one of a kind situation," and there was nothing wrong with the Foxline power supplies, the ones which users have named as being those from which solder was wearing off and posing a fire risk.

She said the question of broken solder joints would be covered under a warranty. All Xbox consoles had been designed so that a broken solder joint did not present any safety issue.
Several Xbox users have reported that the v1.0 and v1.1 power supplies, not the cable, is to blame for the issue. Users of later Xbox versions are also getting replacement cables even though the machines aren't faulty.

An online petition, which claims that the recall of the power cords is a cover-up of the real problem, has now collected 1779 signatures.
A Swedish newspaper appears to have been the first to publicise the actual problem.

There have been problems with the Xbox in the past. In February 2002, soon after the console went on sale in Japan, there were complaints from customers about it scratching game and film discs.

The discs and DVD movies came out scratched after being removed from the Xbox, though in most cases the discs were still playable.

At the timer Microsoft said that the scratching affected "significantly less than 1 percent of systems sold."

The complaints in Japan came after a few reports of defective units in North America, where the Xbox went on sale in November 2001.

Source.

More in Tux Machines

Ask Safia: How do I move from a proprietary software background into open source?

Your inexperience with open source tools definitely is not going to prevent you from participating in the open source community. Regardless of the closed nature of the platforms that you’ve worked with previously, you have all the skills needed to be a valuable open source contributor. If you’ve learned a thing or two about documentation, consider addressing documentation issues on projects. If you had experience in QA or testing, you can start off by user testing the software and identifying areas for improvement or for improving code coverage. Valuing your skill set and the nature of the environments that you have worked in is important. Read more

How Do You Support Your Distro?

I think of them as our own little personal supernovas. There’s a brilliant flash when a Linux distro tosses in the towel and calls it quits. But whenever a distro goes away, it leaves behind the people who’ve used and worked with it on a daily basis. While there’s no formation of a black hole, there is hole at the center of users’ work schedules and that disruption can do serious damage to those relying upon the distro’s stability. And while getting a new distro installed and running isn’t the nightmare it used to be, it’s still a pain. Read more

Rygel Open-Source Media Server Gets Hack to Support AVI Playback on Philips TVs

The open-source Rygel DLNA (Digital Living Network Alliance) media server software has been updated earlier, May 23, 2016, to stable version 0.30.3 and development build 0.31.1. Read more

GNOME News

  • GNOME.Asia Summit 2016
    This year summit held at Manav Rachna International University (MRIU), which is located in the Faridabad district Delhi, it’s a quiet, beautiful and very very hot place. It gave me a lot of wonderful memories.
  • Endless and Codethink team up for GNOME on ARM
    A couple of months ago Alberto Ruiz issued a Call to Arms here on planet GNOME. This was met with with an influx of eager contributions including a wide variety of server grade ARM hardware, rack space and sponsorship to help make GNOME on ARM a reality.
  • External Plugins in GNOME Software (5)
    There’s a lot of flexibility in the gnome-software plugin structure; a plugin can add custom applications and handle things like search and icon loading in a totally custom way. Most of the time you don’t care about how search is implemented or how icons are going to be loaded, and you can re-use a lot of the existing code in the appstream plugin. To do this you just save an AppStream-format XML file in either /usr/share/app-info/xmls/, /var/cache/app-info/xmls/ or ~/.local/share/app-info/xmls/. GNOME Software will immediately notice any new files, or changes to existing files as it has set up the various inotify watches.
  • External Plugins in GNOME Software (6)
    This is my last post about the gnome-software plugin structure. If you want more, join the mailing list and ask a question. If you’re not sure how something works then I’ve done a poor job on the docs, and I’m happy to explain as much as required.
  • Week 1 of May-August Outreachy
    The Outreachy internship requires that interns maintain a blog, writing at least every other week. This shouldn't be a problem for the usability project. For the first few weeks, I'll essentially give a research topic for Diana, Ciarrai and Renata to look into and write about on their blogs. I've structured the topics so that we'll build up to building our usability tests.