Hi Guys,
I'd like to know if there's some flag that can be reset to remove the boot logo
that is appearing after my screensaver program.
Currently, a user mode plugin starts a kernel mode plugin that in turn starts the
screensaver eboot with the SDK launch eboot sample.
Than the eboot is made to exit at any button press to return to the XMB.
Problem is the SCE boot logo (as in coldboot intro) is shown whether or not it is turned off in recovery mode
(I don't know why). It would be a big improvement to get rid of it, and appear to exit like a normal homebrew.
Thanks.
Art.
Getting rid of boot logo after eboot?
Getting rid of boot logo after eboot?
If not actually, then potentially.
The problem is that the EBOOT is not being launched by the vsh, hence when the EBOOT exits, the correct vshparams are not being returned to the vsh.
You will need to manually set them when you exit to XMB using one of the exitvsh functions. You need to set the vshargp and vshargs. If you leave it blank it will show the coldboot, not to mention the XMB will forget its current positions in the music,video,photo, etc.
The exact argc for skip cold boot alone is there in the 1.50 POC source, or 3.10/40 source. I don't know how you will maintain the xmb positions in the music/video etc though, unless you can capture the original vshparams somehow.
Alternatively try using sctrlKernelLoadExecVSHMs1 with NULL for the vshparams. It might automatically send the vshparams.
You will need to manually set them when you exit to XMB using one of the exitvsh functions. You need to set the vshargp and vshargs. If you leave it blank it will show the coldboot, not to mention the XMB will forget its current positions in the music,video,photo, etc.
The exact argc for skip cold boot alone is there in the 1.50 POC source, or 3.10/40 source. I don't know how you will maintain the xmb positions in the music/video etc though, unless you can capture the original vshparams somehow.
Alternatively try using sctrlKernelLoadExecVSHMs1 with NULL for the vshparams. It might automatically send the vshparams.
One of the VSHBridge exports should be a ku bridged sceKernelLoadExecVSHMs1.
http://silverspring.lan.st/3.5x/kd/vshbridge.xml
Maybe that one will automatically handle the params... You will be able to call it from user mode directly as well.
Ask moonlight if he knows he knows which one. He might have come across it cos he has to do the vsh patches.
http://silverspring.lan.st/3.5x/kd/vshbridge.xml
Maybe that one will automatically handle the params... You will be able to call it from user mode directly as well.
Ask moonlight if he knows he knows which one. He might have come across it cos he has to do the vsh patches.