Originally posted by Metal_Man88

---

It'd be hard to fake the Wiimote moving stuff; plus you could easily test it to see if it worked.

It looks like Wii Homebrew will become an eventuality at this point, although most of us already know how even the most insane protection eventually falls. (Consider the N64 and how it once stood as one of the few consoles able to fight piracy--of course, once people understood the cartridges it was about as powerful at preventing such as a rubber mallet, heh)

---

N64 had no real protection. Proprietary cartridges and a partial ROM checksum. A better comparison is Gamecube, which was touted as unhackable for so long and then like 80 million holes were found, one of which was so big you could drive a van through it.

____________________

I'd really like to know whether the hole requires Lego Star Wars or not. If so, I want to buy it ASAP, because you can bet it'll be snatched up and/or recalled pretty quick.

____________________

Of course, last I checked it was still possible to make your own mod chip for pretty damn cheap. Nearly free (cost: one printer cable) if you're willing to require using a PC to load the games and have a big cable hanging out of the system (or you could add a male DB25 connector).

Looks like I'll be opening my Wii after all. (It's always right next to a PC anyway... on the off chance I need to take it somewhere and want to play backups, I'll get a USB->parallel port adapter and use my laptop.)

---

Update: This should be interesting.

____________________

I'd say "Go buy Zelda", but why the hell don't you have it already?
Also, here and here are photos that haven't been crapped on. Notice the caption of the second image:
8054f8e0: 3e 80 34 56 lis r20,0x3456 (r20 = 0x34560000)
8054f8e4: 82 b4 77 88 lwz r21,0x7788(r20) (read word from (r20 + 0x7788) into r21)
0x34567788 is of course an invalid memory address, and if you check out the exception handler: r20 = 0x34560000, 'DAR' = 0x34567788. Although solid proof is still severely lacking, the implication is that they put those two instructions in to reference that invalid address, and the exception handler is showing an attempt to reference that address. About the simplest way to see if your exploit is working.

Apparently they've only managed to stick 4 instructions in there, but if you know the location of some other data from the save file, or a place in RAM that the game doesn't use, 4 is plenty enough for a jump to that location. (The unused RAM idea seems pretty farfetched, but consider that this is basically a port from the Gamecube, so it's not likely to use much more than 1/8th of available RAM, and previous exploits relied on the Wii not clearing RAM when loading things. If, say, the contents of a JPEG file you viewed in the photo channel didn't get erased, and were still there when the exploit was used, well, it's piss-easy to put whatever data you want inside a JPEG file without breaking it. )

____________________