error 80020148

rus_pa · Post by **rus_pa** » Mon Jan 07, 2008 9:47 am

I'm getting this error while trying to play some of my eboots, I remember I was able to run them on cf 351, now I got 371 and I guess something has changed (and I left psp developement for months), maybe some incompatibilty of the new firmware, I was reading some stuff regarding the necessity of doing some prx now... Where can I read some good docs on this? I'm a bit stuck with this thing. Thanks!

Wally · Post by **Wally** » Mon Jan 07, 2008 10:03 am

Archaemic · Post by **Archaemic** » Mon Jan 07, 2008 10:09 am

Psst: he said error 80020148, not 80020321.

Either way, it's not development related and hence not the topic of this forum.

pspZorba · Post by **pspZorba** » Mon Jan 07, 2008 10:11 am

Excellent !

rus_pa · Post by **rus_pa** » Mon Jan 07, 2008 10:34 am

Wally4000 wrote:Here's the Solution

Oh and in the future go post somewhere else.. Like DCEmu or PSPupdates :)

Thanks

Some people seems not to be ashamed while showing off their stupidity in public.
I'm not talking of your games iso, you mr.comicity (I don't give a nickel about what the error number means either), I'm talking of my C compiled eboots, and not only mine but also some correctly compiled from the classic examples provided in the toolchain sdk.
Some starts some others not. On previous firmwares I never get this problem.
If you're not able to answer, simply don't reply. Please refrain from wasting the time of who like this forum.

Wally · Post by **Wally** » Mon Jan 07, 2008 10:44 am

rus_pa wrote:
Wally4000 wrote:Here's the Solution

Oh and in the future go post somewhere else.. Like DCEmu or PSPupdates :)

Thanks
Some people seems not to be ashamed while showing off their stupidity in public.
I'm not talking of your games iso, you mr.comicity (I don't give a nickel about what the error number means either), I'm talking of my C compiled eboots, and not only mine but also some correctly compiled from the classic examples provided in the toolchain sdk.
Some starts some others not. On previous firmwares I never get this problem.
If you're not able to answer, simply don't reply. Please refrain from wasting the time of who like this forum.

I apologise my good friend :) mondays suck.

Anyway, out of curiosity. Have you installed 1.50 Kernel on 3.71M33? That'd be the problem if you haven't installed it.

Again I apologise.

Wally

rus_pa · Post by **rus_pa** » Mon Jan 07, 2008 4:58 pm

never mind, I really wasn't in the mood yesterday :P
No I do not think I have 1.50 pieces in my new firmware, in fact all the eboots placed under game150 are not listed in the dash, and right. I'll look for how to add this 1.50 junkies :) Thanks!

Wally · Post by **Wally** » Mon Jan 07, 2008 8:13 pm

BTW 150 kernel doesn't work on the Slims

Anyway download this and Firmware 1.50

Read the instructions and away you go :P

Hellcat · Post by **Hellcat** » Sat Jan 12, 2008 10:45 pm

Maybe it's simply 'cause he compiled his stuff as static .ELF, not as .PRX module?
That gives a 80020148....

Since he said it's happening to compilations of the SDK samples, those are in 1.50 .ELF format IIRC....

Viper8896 · Post by **Viper8896** » Sun Jan 13, 2008 1:07 am

i thought rather than clog up the forums with more topics what about error 00000001 a lot of the time but not every time when i do new connection -> scan. this only started happening after cfw 3.71

Hellcat · Post by **Hellcat** » Mon Jan 14, 2008 9:04 pm

Viper8896 wrote:i thought rather than clog up the forums with more topics what about error 00000001 a lot of the time but not every time when i do new connection -> scan. this only started happening after cfw 3.71

AFAIK it's a bug in the FW (caused by Sony, also happening on plain OFW).
Happens when no APs are detected.
Everything works fine once there's at least one AP broadcasting it's ID.