MicroNut
January 26th, 2007, 03:19
I have been using Future Cop LAPD to test the creation of an eboot.pbp using the new popstation and data.psar.
Primarily because its the only game I own that requires the 3.02 plug-in.
And I have run into a strange problem.
I have the new DATA.PSP (edit: not .PSAR) in the same folder as the base.pbp and new popstation.exe
My understanding is that the new data.psar is supposed to allow the use of psx eboots without the Keys.bin file.
Well that's the part I am not sure about.
I can launch the newly created Future Cop LAPD eboot and start a new game.
However the game crashes in the exact same way as it did in 3.03 without the 3.02 plug-in.
Thinking that all i needed to do was go in and reset the 3.02 plug-in, in the recovery mode, I started my journey.
I reset the plug-in and the game still crashed loading the first level (without the keys.bin file.)
Exactly as it does in 3.03 without the plug-in.
I put the keys.bin file back into the game folder
and the game crashed at the same spot again.
I then reset the 3.02 plug-in registry and the game loads and seems to play again without problems.
This is repeatable.
-Delete the keys.bin
-Game crashes same spot.
-Replace keys.bin
-Game crashes same spot.
-Reset 3.02 plug-in
-Game loads first level like it should.
Do I not have the DATA.PSAR in the right location?
What else am I doing to cause this?
Is this expected behavior based on this statement in the 3.03OE-C popstation read me?
"Note: these EBOOT.PBP cannot work in versions prior to 3.03 OE-C due to a bug that those versions had."
If I read this correctly games that are known not to work in 3.03 will always need a keys.bin file.
(the keys.bin file is still created with the new pops.)
Deleting the keys.bin file then launching the game forces the 3.02 plug-in registry entry to fail,
until its disabled and enabled again.
Primarily because its the only game I own that requires the 3.02 plug-in.
And I have run into a strange problem.
I have the new DATA.PSP (edit: not .PSAR) in the same folder as the base.pbp and new popstation.exe
My understanding is that the new data.psar is supposed to allow the use of psx eboots without the Keys.bin file.
Well that's the part I am not sure about.
I can launch the newly created Future Cop LAPD eboot and start a new game.
However the game crashes in the exact same way as it did in 3.03 without the 3.02 plug-in.
Thinking that all i needed to do was go in and reset the 3.02 plug-in, in the recovery mode, I started my journey.
I reset the plug-in and the game still crashed loading the first level (without the keys.bin file.)
Exactly as it does in 3.03 without the plug-in.
I put the keys.bin file back into the game folder
and the game crashed at the same spot again.
I then reset the 3.02 plug-in registry and the game loads and seems to play again without problems.
This is repeatable.
-Delete the keys.bin
-Game crashes same spot.
-Replace keys.bin
-Game crashes same spot.
-Reset 3.02 plug-in
-Game loads first level like it should.
Do I not have the DATA.PSAR in the right location?
What else am I doing to cause this?
Is this expected behavior based on this statement in the 3.03OE-C popstation read me?
"Note: these EBOOT.PBP cannot work in versions prior to 3.03 OE-C due to a bug that those versions had."
If I read this correctly games that are known not to work in 3.03 will always need a keys.bin file.
(the keys.bin file is still created with the new pops.)
Deleting the keys.bin file then launching the game forces the 3.02 plug-in registry entry to fail,
until its disabled and enabled again.