I found something on 3dbrew: http://3dbrew.org/wiki/MPI found that System Transfer uses that service, but there is nothing about it on 3dbrew. Does anyone knows what is this useful for ?
I think it's used when transferring from a DSi.I found that System Transfer uses that service, but there is nothing about it on 3dbrew. Does anyone knows what is this useful for ?
It seems like mp:u is used for the actual communication between the DSi and 3DS in order to transfer data (after validating it with Nintendo's servers, of course), though cfg:nor may be used to write parts of that data to the 3DS, as according to 3dbrew it's used to access the WiFi NVRAM/SPI flash. Maybe to write DS/DSi-mode wifi configuration or something else.Oh, okay, thanks a lot. I thought that cfg:nor did that instead
Not sure about that, I didn't see it at all in the MSET permissions. (I added these to 3dbrew btw)It seems like mp:u is used for the actual communication between the DSi and 3DS in order to transfer data (after validating it with Nintendo's servers, of course), though cfg:nor may be used to write parts of that data to the 3DS, as according to 3dbrew it's used to access the WiFi NVRAM/SPI flash. Maybe to write DS/DSi-mode wifi configuration or something else.
It was a joke. (right?)Hes asking if there is any documentation. Unless you intend on bringing something worthwhile to the thread then gtfo scrub.
System Transfer is a separate title, I believe.Not sure about that, I didn't see it at all in the MSET permissions. (I added these to 3dbrew btw)
Yeah, of course, but System Settings can access DS NVRAM too for WiFi SettingsSystem Transfer is a separate title, I believe.
It was, geez, some people just don't have a sense of humor around here.It was a joke. (right?)