@[member='AbdallahTerro']
While it's perfect possible to create a dol that launches neek2o with a specific nand, it's not possible to do it without manipulating either nandcfg.bin or nandpath.bin. neek2o checks those files and loads a nand according to their contents. If postloader adjusts those as well before it launches neek2o, everything should work fine and without conflicts. I still don't get the problem in manipulating those files?
You have a problem now because the neek2o channel isn't touching them, if I understand well?
@[member='danielkraak']
The problem is that sneek uses the sd card for it's emulated nand like uneek is using the harddisk for it.
So basically, neek is taking ownership of those devices, and homebrew trying to acces it as well fails to do so.
I wrote a wrapper routine that redirects the calls to neek, but homebrews need some minor modifications for it to work.
The progress on this is slow but still going on..
While it's perfect possible to create a dol that launches neek2o with a specific nand, it's not possible to do it without manipulating either nandcfg.bin or nandpath.bin. neek2o checks those files and loads a nand according to their contents. If postloader adjusts those as well before it launches neek2o, everything should work fine and without conflicts. I still don't get the problem in manipulating those files?
You have a problem now because the neek2o channel isn't touching them, if I understand well?
@[member='danielkraak']
The problem is that sneek uses the sd card for it's emulated nand like uneek is using the harddisk for it.
So basically, neek is taking ownership of those devices, and homebrew trying to acces it as well fails to do so.
I wrote a wrapper routine that redirects the calls to neek, but homebrews need some minor modifications for it to work.
The progress on this is slow but still going on..