Slashdot Mirror
WiiConnect24 Update Causing Issues For Wii Owners
An anonymous reader writes to mention coverage on IGN of an ongoing issue with a WiiConnect update. A faulty update may be causing some Wii consoles to become inoperative. Nintendo is replacing affected consoles, free of charge. From the article: "Several error codes have been reported so far, but the most prevalent of them are 110213 and 32002. We contacted Nintendo about this issue, and they filled us in on what you should do if you find yourself in this predicament. Currently, Nintendo has two options in place to resolve the problem. If you do not have any data saved to your system that is important to keep, then you can contact Nintendo customer service and they will ship a new console to you in 3-4 business days. However, if you do have important data saved to your system, then things get a little trickier"
Nintendo arn't perfect, no one would claim so.
The difference is the rate of failure with Nintendo is usually much lower and they have an excellent returns policy. I'll give you an example.
About 10 years ago my SNES broke a week before Christian. We contacted nintendo and they sent us a new one no questions asked and you know what really sold me? They gave me a couple of t-shirts, a huge bag of badges and stickers. All because it died just before Christmas.
When Sony give a fuck about their customers like I saw Nintendo did then we'll talk about the bad press. Untill then I'll judge Sony on their actions.
I like muppets.
Computers do NOT do that for firmware except for a few high-end motherboards. In this situation, firmware is exactly what's being updated.
However, there is a catch to this particular story. According to the reports, Nintendo is telling Wii owners that it's not the firmware update itself or anything the owner did. Some of the units apparently have defects. When the firmware update is applied, it's exasperating the defect, causing strange behavior. The reports of the problem seem to confirm this, as the system doesn't completely brick. (i.e. it still boots into the menus) But since it is unable to play games, it might as well be bricked.
Javascript + Nintendo DSi = DSiCade
I had the 32002 for the first day. Their description for the error code says it is a problem getting stuff from the server, and to try again later. I figured it was due to release day overload. In the end, I followed their advice and changed my WiFi channel from the default 6 to 11 and now it works fine.
j.goforth
Except that it will still work in "offline" mode. You can play any games you want; you just can't go online.
If you called Nintendo customer service, they essentially give you one of two choices:
1) Give them your credit card number over the phone. They send a replacement Wii along with a postage-paid box to you, you put your old Wii in the box and ship it back. You won't have to spend a day without the Wii.
2) If you want to keep your original Wii, you can ship it back, they fix it, and overnight it back to you. In this case you WOULD be without your Wii for a few days.
My bet is most would go for Option 1. Option 2 is for if you have a lot of stuff on internal storage they can't live without (which is fairly unlikely this soon after launch).
I had the same problem, and it got stuck that way for 5 hours. Try to update,fail,reboot,update,fail,etc.
My brother found a mention on the Nintendo.com site that their wireless implementation hates channel 4, and works best on 1 and 11 (?).
After switching the AP over to 1, it updates in less than 30 seconds.
So try doing that, even if you're not doing updates. It seems the connection is just horribly slow when on channel 4 (which was the default for my WRT54G router).
I respond to your sigs
The word you want here is they're," not "their." They're similar, but "their" is possessive while "they're" is a contraction of "they are."
First posting isn't trolling. It's...first posting.