Loading and Starting prx's in hbl?

[KaZ]

well i know you cannot load prx's in hbl, ive tried it and it will fail ( i put in a error message)
but then i tried this command "LINE EDITED AND DELETED" and my error message never came up but it loaded the plugin successfully but ofcourse i can't use the hold.prx plugin it needs kernel access + i was on my psp go (not supported)

i'm not sure if this could be usefull but maybe it could help you guys

Advertising

[JJS]

What you did was infact loading a prx through HBL.

sceKernelLoadModule() is hooked in HBL and pspSdkLoadStartModule() is just a wrapper around that function together with sceKernelStartModule(). Of course it won't do any good to load a kernel mode module into user space. Actually I don't understand why HBL didn't return an error message when it detected that the module is kernel mode.

You cannot load any module (user or kernel) from the memory stick on OFW, only from flash0 or from an UMD. That is why HBL has to do all module loading by itself without help from the kernel.

So nothing new on that front.

Advertising

[KaZ]

What you did was infact loading a prx through HBL.

sceKernelLoadModule() is hooked in HBL and pspSdkLoadStartModule() is just a wrapper around that function together with sceKernelStartModule(). Of course it won't do any good to load a kernel mode module into user space. Actually I don't understand why HBL didn't return an error message when it detected that the module is kernel mode.

You cannot load any module (user or kernel) from the memory stick on OFW, only from flash0 or from an UMD. That is why HBL has to do all module loading by itself without help from the kernel.

So nothing new on that front.

i've tried alot of prx loading functions that i knew would fail, but hbl never ever showed me a error message, perhaps u want to work on this? its just a suggestion though

[FrEdDy]

What you did was infact loading a prx through HBL.

sceKernelLoadModule() is hooked in HBL and pspSdkLoadStartModule() is just a wrapper around that function together with sceKernelStartModule(). Of course it won't do any good to load a kernel mode module into user space. Actually I don't understand why HBL didn't return an error message when it detected that the module is kernel mode.

You cannot load any module (user or kernel) from the memory stick on OFW, only from flash0 or from an UMD. That is why HBL has to do all module loading by itself without help from the kernel.

So nothing new on that front.

i've tried alot of prx loading functions that i knew would fail, but hbl never ever showed me a error message, perhaps u want to work on this? its just a suggestion though

http://code.google.com/p/valentine-hbl/ ... tail?id=31

[KaZ]

What you did was infact loading a prx through HBL.

sceKernelLoadModule() is hooked in HBL and pspSdkLoadStartModule() is just a wrapper around that function together with sceKernelStartModule(). Of course it won't do any good to load a kernel mode module into user space. Actually I don't understand why HBL didn't return an error message when it detected that the module is kernel mode.

You cannot load any module (user or kernel) from the memory stick on OFW, only from flash0 or from an UMD. That is why HBL has to do all module loading by itself without help from the kernel.

So nothing new on that front.

i've tried alot of prx loading functions that i knew would fail, but hbl never ever showed me a error message, perhaps u want to work on this? its just a suggestion though

http://code.google.com/p/valentine-hbl/ ... tail?id=31

Yeah i know this, im talking about the error code hbl is supposed to give off or something.

[m0skit0]

In fact the "external" PRXs are loaded, relocated and ran correctly by HBL. They're the same as PRXs that homebrews are made of, and are loaded the same way these are (and in fact they do). The problem I found when coding and testing this is that because of some reason, the data section of the PRX is loaded with strange values, and the creation of the main thread (created automatically by PSPSDK) fails because of the values used. This means the PRX is loaded, relocated and running. I didn't dig too much on it but I think if someone's able to find why this corruption happens (dang stack most likely), the PRXs should run fine (still with the HBL user-mode-only restrictions of course).

Maybe a memory allocation system done by HBL instead of relying on the PSP kernel would solve this (I think wololo asked what this would solve somewhere on this forum...).

About the HBL informing about it, it does on the debug log. That's far enough.

[KaZ]

ok, sorry for making you type a long paragraph btw

[m0skit0]

I don't have any problem typìng as long as required. Please abstain of posting that's off-topic on this forum.