http://www.seeklogo.com/images/N/NET...eklogo.com.gifhttp://www.brandsoftheworld.com/bran...0859/brand.gif
Updated: 7.8.12
DON'T PM with problems about this guide... Post Questions here and WAIT patiently for a answer
Recently Updated Netflix via Nintendo Shop Channel: Instructions Below!!
If you installed Netflix prior to 11.22.11, you will be prompted to update. Accepting this Netflix update is OK, HOWEVER many users have reported that the GUI is very "choppy". This is not a problem with your Wii and it does not affect playback of the streaming content. It seems as over time and use, this "choppiness" seems to subside. This could be due to the larger amount of data (cover thumbs, etc) that must be downloaded. Once this data has been downloaded it is stored in a save file on your Wii. Performance should increase substantially as these files are cached.
Update 7.8.12
Netflix has released a 2 block update for the Wii. This update is safe to accept. As of 7.8.12 there is no change log available. I have contacted Netflix regarding this, and the only info they could provide was that it included "video playback enhancements" and "functionality enhancements". They would not/could not give specifics as to what was changed, and stated that a change log was not available anywhere online as of present moment. The person I spoke to also stated that they could not tell the difference, as was my observation. I did however find some interesting info on their tech forum that could be related to this update. For those may be interested see the spoiler below.
The Netflix Tech Blog: July 2012
Overview
On Friday, June 29th, we experienced one of the most significant outages in over a year. It started at about 8 PM Pacific Time and lasted for about three hours, affecting Netflix members in the Americas. We’ve written frequently about our resiliency efforts and our experience with the Amazon cloud. In the past, we’ve been able to withstand Amazon Web Services (AWS) availability zone outages with minimal impact. We wanted to take this opportunity to share our findings about why this particular zone outage had such an impact.
For background, you can read about Amazon’s root-cause analysis of their outage here: Summary of the AWS Service Event in the US East Region. The short version is that one of Amazon’s Availability Zones (AZs) failed on Friday evening due to a power outage that was caused by a severe storm. Power was restored 20 minutes later. However, the Elastic Load Balancing (ELB) service suffered from capacity problems and an API backlog, which slowed recovery.
Our own root-cause analysis uncovered some interesting findings, including an edge-case in our internal mid-tier load-balancing service. This caused unhealthy instances to fail to deregister from the load-balancer which black-holed a large amount of traffic into the unavailable zone. In addition, the network calls to the instances in the unavailable zone were hanging, rather than returning no route to host.
As part of this outage we have identified a number of things that both we and Amazon can do better, and we are working with them on improvements.
Middle-tier Load Balancing
In our middle tier load-balancing, we had a cascading failure that was caused by a feature we had implemented to account for other types of failures. The service that keeps track of the state of the world has a fail-safe mode where it will not remove unhealthy instances in the event that a significant portion appears to fail simultaneously. This was done to deal with network partition events and was intended to be a short-term freeze until someone could investigate the large-scale issue. Unfortunately, getting out of this state proved both cumbersome and time consuming, causing services to continue to try and use servers that were no longer alive due to the power outage
Gridlock
Clients trying to connect to servers that were no longer available led to a second-order issue. All of the client threads were taken up by attempted connections and there were very few threads that could process requests. This essentially caused gridlock inside most of our services as they tried to traverse our middle-tier. We are working to make our systems resilient to these kinds of edge cases. We continue to investigate why these connections were timing out during connect, rather than quickly determining that there was no route to the unavailable hosts and failing quickly.
Summary
Netflix made the decision to move from the data center to the cloud several years ago [1]. While it’s easy and common to blame the cloud for outages because it’s outside of our control, we found that our overall availability over the past several years has steadily improved. When we dig into the root-causes of our biggest outages, we find that we can typically put in resiliency patterns to mitigate service disruption.
There were aspects of our resiliency architecture that worked well:
- Regional isolation contained the problem to users being served out of the US-EAST region. Our European members were unaffected.
- Cassandra, our distributed cloud persistence store which is distributed across all zones and regions, dealt with the loss of one third of its regional nodes without any loss of data or availability.
- Chaos Gorilla, the Simian Army member tasked with simulating the loss of an availability zone, was built for exactly this purpose. This outage highlighted the need for additional tools and use cases for both Chaos Gorilla and other parts of the Simian Army.
The state of the cloud will continue to mature and improve over time. We’re working closely with Amazon on ways that they can improve their systems, focusing our efforts on eliminating single points of failure that can cause region-wide outages and isolating the failures of individual zones.
We take our availability very seriously and strive to provide an uninterrupted service to all our members. We’re still bullish on the cloud and continue to work hard to insulate our members from service disruptions in our infrastructure.
SOURCE - Netflix Tech Blog
Features added with update on 11.28.11:
1. New "Just For Kids" section - Kids can browse this section without parents having to worry about them running across "adult" material.
2. All genres now have 75 titles to scroll through
Registering Netflix Account:
USA Instructions:
1. If you have never had a Netflix account, you will receive a FREE 1 month TRIAL. You can sign up following the on screen instructions, or you can sign up using your computer. SIGNUP HERE
2. You HAVE to put in Credit Card info and a Valid US Street Address
3. When you are done creating your account, thats it for now....
CANADA Instructions:
1. If you have never had a Netflix account, you will receive a FREE 1 month TRIAL. You can sign up following the on screen instructions, or you can sign up using your computer. SIGNUP HERE
2. Then Follow the Links on that page to login once account is created...
Disk Instructions:
----------------------------------------------------
Disk Instructions no longer apply. Download the app using the Wii Shop Channel.
----------------------------------------------------
Wii Shop Channel Instructions:
WARNING: Anybody who posts anything in regards to updating the Shop Channel, their posts will be deleted and you will be infracted...
How to update your shop channel can be found here: Update Shop Channel Guide
1. After you get everything updated via the guide above:
2. Make sure you have WIFI - Enabled and connected to your network
3. Make sure you have 60 Free Blocks of Wii Memory
4. Launch your Nintendo Shop Channel
5. Netflix will be under the main screen
6. Click and Download the Channel as it is FREE
7. When everything is done you will have to exit to system menu and you will have a Netflix Channel listed on the page...
8. If you have not logged in before you will be asked to follow on-screen instructions to activate the service on your wii.... Takes 5min MAX
9. DONE!!!!
Error #204036 - HELP! I can't install the updated Netflix Channel !!!!!
Some users may encounter this error when attempting to install the newest version of netflix. If you have already followed ALL OF THE ABOVE INSTRUCTIONS and you still get the above error:
1. Download THIS and extract it directly to the WAD folder on your SD card.
2. Launch Wad Manager 1.7 or MMM and install IOS56 v5662 patched.wad
3. Repeat the steps for downloading Netflix from the Shop Channel.
PAL Notes
Other Notes:Quote:
Originally Posted by Zyrtec Bro
- The country settings must be correct in your Wii to be able to download and launch the Netflix Channel. If the settings are correct and you cannot find Netflix in Wii Shop, it is not yet available in your region.
- As of 11.16.11 Nextflix has signed licensing agreements with Mirimax, MGM and Lionsgate in advance of a planned early 2012 launch in the UK, Spain and Ireland.
A HUGE THANKS goes out to Emuhack for writing this guide in the first place! Find one of his posts and give him a Thanks!
