I too would like to know what this is?
be carefull asking you might get moaned at for it lol DSP patching is gonna help out alot if it can be used with nintedont (sound/audio with games)
I too would like to know what this is?
Seems crediar pointed out that if a dev wanted 'he' could take the patches from devolution and add them to nintendont with a lil reverse engineering I assumeI too would like to know what this is?
So, just a simple redirection then?This has little to do with DSP patches for Nintendont. It means that Devolution's RAW kernel has been dumped. If somebody takes bytes 0x3200000-0x3219A9F of crediar's dump, makes a loader that puts it at 0xB3200000 in the Wii's RAM, passes arguments to it properly and launches it, Devolution no longer has DRM (or if it does, it can probably be bypassed with a simple branch command since all the encryption garbage is gone).
(That is a lot more likely and probably easier than gleaning any DSP patch/other useful code).
Looked like from earlier posts that the intention was to get game patches not break DRM , but I'm not schooled in thatThis has little to do with DSP patches for Nintendont. It means that Devolution's RAW kernel has been dumped. If somebody takes bytes 0x3200000-0x3219A9F of crediar's dump, makes a loader that puts it at 0xB3200000 in the Wii's RAM, passes arguments to it properly and launches it, Devolution no longer has DRM (or if it does, it can probably be bypassed with a simple branch command since all the encryption garbage is gone).
(That is a lot more likely and probably easier than gleaning any DSP patch/other useful code).
Wii U? First, make sure you've got HID on in the Nintendont settings, second, use the HIDtest app and fix your controller.ini as per the instructions found in its readme... I've only just started using this and also got the -3 at first.. I was originally using a PS1-usb adaptor and just assumed the values are the same as ps2With my classic controller to usb adapter, I keep getting error -3 when trying to boot a game.
Anyone else have this problem, and how can I fix the controller.ini so it boots up into a game, since it has two ports in it?
Wii U? First, make sure you've got HID on in the Nintendont settings, second, use the HIDtest app and fix your controller.ini as per the instructions found in its readme... I've only just started using this and also got the -3 at first.. I was originally using a PS1-usb adaptor and just assumed the values are the same as ps2
Speaking of which: Nintendo Puzzle Collection, both .iso and compressed just give a black screen (and my disc is too old/scratched to be used in Devo *weeps* )
More information: Apparently 0xB3200000 is a valid address on a Wii U devkit's vWii. I'd wager that a prefix of 0x8, 0x9, 0xC, or 0xD instead of 0xB would probably work. I do not know much about Wii development, but if anyone knows how to allocate memory/load stuff into it, PM me and I'll send the extracted kernel.
Also, r197 will probably work on the Wii U because the DRM was really the only thing preventing it (that and the fact that crediar probably got it to load). Only other thing missing from r197 is PS3 controller support, so Wii U users can only use a classic controller and equivalent.
Bytes 0x3200000 to 0x3219A9F of crediar's ram dump. Loaded properly (should) = no DRM.What do you mean with "extracted kernel"?
crediars MEM2 dump is around 16 MB, devos loader.bin is only 95 KB. So there's a lot of crap in this dump, which isn't needed. Further, if the loader got loaded into MEM2, why should the DRM be disabled?Bytes 0x3200000 to 0x3219A9F of crediar's ram dump. Loaded properly (should) = no DRM.
For the size, that's why I said devolution is between bytes 0x3200000 to 0x3219A9F inclusive (~102KB) in the MEM2 dump. This is the raw loader, the thing that actually runs GameCube games so there is a lot less of this: http://imageshack.us/a/img96/6462/wupe.pngcrediars MEM2 dump is around 16 MB, devos loader.bin is only 95 KB. So there's a lot of crap in this dump, which isn't needed. Further, if the loader got loaded into MEM2, why should the DRM be disabled?
Exciting conceptual news here. Either way hints & clues have been given. We'll have to wait until capable coders can pick up the pieces and do the rest. I don't care what happens with the DRM from Devo, as long as the info is there to help Nintendont become a better and more complete program, it's good enough for me.
Because why bother learning things for yourself when you can just take other people's work, right?