open source recovery menu

[devshelper]

Advertising

can you modify my source code and then post it here?
because i am a little confused with what you said and when i try it the result is the same

[waratte]

Advertising

Of course there are better methods. They are called "debugging", which is almost as important as programming.

I was referring to methods that help you find errors without a debugger.

can you modify my source code and then post it here?
because i am a little confused with what you said and when i try it the result is the same

Copy and remove the return statement at the end of your main. Add it to the beginning of your while loop. Compile and run the eboot on your psp. Wait a few seconds and press down the home key(on the psp). If that grey "exit game" screen appears, then your code works until that point. Go back to your code and move the return statement down one time. Run your new code. Check to see if the grey screen appears again. If it doesn't, the line above your return statement may be the line that crashes the programme. Otherwise, keep doing this until it stops working. When it stops working, the line above the return statement may be the line that breaks the code. I would have tried to do this myself but, you are including files that aren't on my computer.

[devshelper]

ok!
i put return 0 after flipscreen and i can see the menu items, but i can navigate into the menu

[m0skit0]

I was referring to methods that help you find errors without a debugger.

I didn't mention a "debugger" anywhere, did I? Anyway, best option is to use GDB to debug, it's there for a reason. Also you have alternative methods, such as printing (on the screen and/or file and/or psplink). And why not use a debugger, are you afraid of it?

Copy and remove the return statement at the end of your main. Add it to the beginning of your while loop. Compile and run the eboot on your psp. Wait a few seconds and press down the home key(on the psp). If that grey "exit game" screen appears, then your code works until that point. Go back to your code and move the return statement down one time. Run your new code. Check to see if the grey screen appears again. If it doesn't, the line above your return statement may be the line that crashes the programme. Otherwise, keep doing this until it stops working. When it stops working, the line above the return statement may be the line that breaks the code. I would have tried to do this myself but, you are including files that aren't on my computer.

Really awful and slow method. Better do some output or better yet use PSPLINK and GDB.

[devshelper]

i am on win7, so i cant setup PSPLINK

[JJS]

i am on win7, so i cant setup PSPLINK

Of course you can. If you have MinPSPW, it is actually already installed. Look in the PSPSDK directory.

[devshelper]

yeah, but only the psp files are there, not any pc file

[JJS]

They are in the "bin" subdirectory.

[devshelper]

ok!
i am on 6.20 tn hen permanent.
which files should i copy to ms0:/psp/game/psplink?
(1.0 , 1.5 or 1.5 no_corrupt)?

[JJS]

(1.0 , 1.5 or 1.5 no_corrupt)

None of those . You need the files in "OE". But there is a problem with running the PSPLink Eboot on 6.20 TN. You should rather copy the files to your seplugins folder and enable "psplink.prx" in game.txt.