procfw
procfw copied to clipboard
PSX game error 800100002 after pops loader is used
What steps will reproduce the problem?
1. psx game xenogears freeze after intro without pops
2. after installing pops error appears after using any version of pops
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
6.60 b10 on psp 3000
Please provide any additional information below.
installed popsloader latest and when pressed r upon game intro pops version
selection appears, after selecting any, just stays dark then error 800100002
appears.
without pops xenogears just freezes after intro in first battle scene.
i was aware that most players on the net say version 3.72 pops works best but i
cant get it to work
anyone got a link for a pops i can use that would run? i might be doing
something wrong that im not aware of with the pops thing...
Original issue reported on code.google.com by [email protected]
on 20 Mar 2012 at 4:31
1. You shouldnt need a separete Popsloader since one is already implemented in
the cfw.
2. If that doesent work - You should get a popsloader for your CFW and fill it
up with all the required files YOU HAVE TO OBTAIN BY YOURSELF because they are
copyrighted. List of all files and an instruction on how to obtain them is
included in the ReadMe file you probably got along with popsloader plugin.
Original comment by piotrekhenry
on 20 Mar 2012 at 6:30
I already have all the files in the list on the readme and its on the proper
folder but after i run the pops it says game cannot be started error 80010002
Original comment by [email protected]
on 20 Mar 2012 at 6:36
@Kejmak well try this: backup all your saves, i mean all of them, same goes for
your isos & eboots,format the memory stick, reinstall the plugins you had.
Original comment by [email protected]
on 20 Mar 2012 at 6:44
or select original from flash, it worked fine for me with no glitches.
Original comment by [email protected]
on 20 Mar 2012 at 6:48
Decide on one popsloader then. Either disable the one you installed yourself
and try the one implemented in PRO CFW (it's enabled by default). Or disable
the implemented one from the Recovery menu and enable the one you installed.
Original comment by piotrekhenry
on 21 Mar 2012 at 2:10