Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
Games

Submission + - Wii Update 4.2 tries (and fails) to block homebrew (hackmii.com) 3

marcansoft writes: "On September 28, Nintendo released a Wii update, titled 4.2. This update was targeted squarely at homebrew, performing sweeping changes throughout the system. It hardly achieved that goal, though, because just two days later a new version of the HackMii installer was released that brings full homebrew capabilities back to all Wii consoles, including unmodified consoles running 4.2.

However, as part of their attempt to annoy homebrew users, Nintendo updated the lowest level updateable component of the Wii software stack: boot2 (part of the system bootloader chain). Homebrew users have been using BootMii to patch boot2 in order to gain low level system access and recovery functions (running Linux natively, fixing bricks, etc). The update hasn't hindered this, as users can simply reinstall BootMii after updating (it is compatible with the update). But there's a much bigger problem: Nintendo's boot2 update code is buggy. Boot2 had never been updated in retail consoles until now. During BootMii's development, its authors noticed that Nintendo's code had critical bugs and could sometimes permanently brick a console by writing incorrect or unchecked data to flash memory, so they decided to write their own, much safer flashing code. Now, Nintendo has pushed a boot2 update to all Wii users, and the results are what was expected: users are reporting bricks after installing 4.2 on unmodified consoles. Nintendo is currently attempting to censor posts and remove references to homebrew.

It is worth noting that the new boot2 does not attempt to block anything or offer any additional protection or functionality. Its sole purpose is to simply replace current versions which may or may not have been modified with BootMii. Another interesting tidbit is that Nintendo is not believed to have any method to repair this kind of brick at a factory, short of replacing the entire motherboard."

The Internet

How Piracy Affected the Launch of Demigod 613

Demigod is an RTS/RPG hybrid developed by Gas Powered Games and published by Stardock, a company notable for their progressive and lenient stance on DRM. The game was set to be released on April 14th, and shipped without any form of copy protection. Unfortunately, retailer Gamestop broke the street date and released it earlier in the week. A day after pointing this out, Gas Powered Games posted some numbers about the players hitting their servers. Roughly 18,000 connections were made from legitimately purchased copies; over 100,000 were made from pirated copies. Meanwhile, the servers, which were not yet ready for that level of traffic, buckled under the strain, resulting in poor experiences for people trying to participate in multiplayer. While some reviews were positive, others criticized the game for the connectivity issues. After another day, they were able to stabilize the servers to the point they'd planned on for the original launch.
The Internet

Lobby Groups Launch Full Assault For Canadian DMCA 135

An anonymous reader writes "Bill C-61, the previous attempt at a Canadian DMCA, may have failed, but it is clear that the music, movie, and business software industries are engaged in putting massive pressure on the Canadian government to bring it back. Lobbying records show several meetings each week with Government Ministers for CRIA, CMPDA, and Microsoft over the past month. Meanwhile, the CRIA is preparing a grassroots campaign in support of new copyright laws, even claiming that the current rules are costing jobs to truck drivers delivering CDs and DVDs."
Privacy

Questionable Data Mining Concerns IRC Community 306

jessekeys writes "Two days ago an article on TechCrunch about IRSeeK revealed to the community that a service logs conversations of public IRC channels and put them into a public searchable database. What is especially shocking for the community is that the logging bots are very hard to identify. They have human-like nicks, connect via anonymous Tor nodes and authenticate as mIRC clients. IRSeeK never asked for permission and violates the privacy terms of networks and users. A lot of chatters were deeply disturbed finding themselves on the search engine in logs which could date back to 2005. As a result, Freenode, the largest FOSS IRC network in existence, immediately banned all tor connections while the community gathered and set up a public wiki page to share knowledge and news about IRSeeK. The demands are clear: remove all existing logs and stop covert operations in our channels and networks. Right now, the IRSeeK search is unavailable as there are talks talking place with Freenode Staff."

Slashdot Top Deals

E = MC ** 2 +- 3db

Working...