Open sajattack opened 3 years ago
PSP 1000 6.60 ME-2.3 cant get to run :
hello guys, Could you give a try to the samples after the latest toolchain upgrade? maybe now they are fixed.
Thanks
psp 1000 6.60 pro
Prx loader Prx template Kdumper Profiler Exception
All don't work
Psp 1000 6.61 LME-2.3
I'm using the lastest psp toolchain.
(My psp wifi works fine, I can use the web browser)
Here's the list of status of all the samples.
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
The game could not be started (8002013c)
Hello World
then immediately exitThe game could not be started (8002013c)
A connection error has occurred. (8010860E)
appears after the loading(like a connecting)@diamant3 nice work, I'll see if I can fix any of these
PSP-3000 6.60 LME-2.3
I think the 8002013c means that kernel calls are made, which are not allowed in user mode applications. I'm guessing previous firmware versions were a bit easier about that.
This is correct. The issue here is that these demos were made back in FW 1.5 days when this was possible.
On Wed, May 29, 2024 at 12:25 PM Wouter Wijsman @.***> wrote:
I think the 8002013c means that kernel calls are made, which are not allowed in user mode applications. I'm guessing previous firmware versions were a bit easier about that.
— Reply to this email directly, view it on GitHub https://github.com/pspdev/pspsdk/issues/45#issuecomment-2137813900, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADCSVSOB4ZJZFWM2VAARDTZEX6RJAVCNFSM4SEJ73I2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJTG44DCMZZGAYA . You are receiving this because you commented.Message ID: @.***>
How should we deal with the samples that require kernel mode? We could decide to add a readme which states that it won't work for newer firmwares or we could decide to implement workarounds to make them work. Think splitting them up into a prx and an elf/eboot. That would add complexity, but it would show people how to make these things work.
msgdialog works just fine.
How should we deal with the samples that require kernel mode? We could decide to add a readme which states that it won't work for newer firmwares or we could decide to implement workarounds to make them work. Think splitting them up into a prx and an elf/eboot. That would add complexity, but it would show people how to make these things work.
IMO we should split them, although that might be costly. Maybe we can write a single lib for each "category" of samples.
Tracking issue for broken samples (of which there are many) Checking the box indicates the sample has been fixed. Please comment on this issue rather than filing a separate one for a broken sample.