Because other Module Loading Functions fail to execute.
I found the hint to use this ku function in a old topic of yours aswell. It doesn't crash, thus I think it's the right function to use, but the just mentioned Module Manager is busy stuff pops up.
First attempt was to call it in module_start but I figured that this might be the problem because module_start still belongs to the Module Manager Initialization...
So I moved it to the Main Thread by moving it into main. But still no different.
I even coded a few debug routines to output me what's happening...
Here goes the tracelog...
Code: Select all
Entering int main(int argc, char * argv[])
Entering int initPlayNet(void)
Leaving int initPlayNet(void)
Entering int hookModules(void)
Entering SceUID loadModule(const char * path, SceUID mpid, uint32 maxattempts)
Leaving int SceUID loadModule(const char * path, SceUID mpid, uint32 maxattempts)
Leaving int hookModules(void)
And here the debuglog...
Code: Select all
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #1
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #2
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #3
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #4
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #5
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #6
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #7
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #8
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #9
ms0:/seplugins/adhocwrapper/usermodule.prx Load Attempt #10
ms0:/seplugins/adhocwrapper/usermodule.prx Load Failed - 80020143
ms0:/seplugins/adhocwrapper/usermodule.prx Failed to load
Don't wonder about main not leaving properly... I did a while(1) loop in there with sceKernelDelayThread to keep the thread alive.
I did a few wrapper functions for everything, to have a easier time calling complex stuff without having to triple check every error possibility.
There are two wrappers, namely loadModule and startModule... startModule only get's called when loadModule did it's job properly... judging from the debuglog we can see it doesn't.
From the tracelog you can figure out the calling conventions too, not that they are important but the more info the better I suppose.
Been gone for some time. Now I'm back. Someone mind getting me up-2-date?