There are many people interested in the PSPAR but it has been concluded that they have most likely signed their own EBOOTs in a similar manner to Sony. There is a fairly long topic on lan.st
as well as mformature
regarding the new PSPAR. Just a warning though, there is source code for a keygen in the mformature thread and if it is used your console ID is blacklisted which will prevent you from being able to use PSPAR if you ever decide to purchase it.
The problem is the new PSPAR doesn't accept input from any external files so there is not much that can be done with it. However the format of the code file used by the new PSPAR is the same as the battery PSPAR but instead of being a file on the memory stick it is stored in the DATA.PSP of the EBOOT. This is a problem because if the EBOOT is edited it won't work on OFW. By design it also doesn't work on CFW (no in-game menu) so there is no point decrypting the EBOOT and patching in the code file to have custom PSPAR codes in CFW.
From the time I've spent looking at the battery PSPAR code file the most notable details are:
- The code types for the PSPAR are the same as the DS Action Replay, was probably already known but whatever.
- Codes are not encrypted in the code file, was probably already known but whatever.
- The PSPAR code file has a checksum in the header and the checksum is checked against a value computed from the entire code file (excluding the header data) so if anything is altered and the checksum isn't corrected it will throw a hissy fit (I think the battery PSPAR crashes but can't remember for certain).
In regards to PSPAR related tools and stuff there is...
- A custom PSPAR code file - only works with battery PSPAR for reasons stated above.
- PSPAR to CWCheat converter - converts a pspar_codes1.bin to CWCheat format (public version supports constant write and single pointer codes only).
- I also made a web script for private use which converts CWCheat codes to PSPAR format and can create a pspar_codes1.bin file from user input however it is only of use to battery PSPAR users so I have no intention of releasing it until it can be used with the new PSPAR (if that were to ever happen).
Anyway the reason Datel chose to do this however is fairly obvious... If the new PSPAR could use an external code file then people would use it to exploit the PSP and Sony would try harder to stop it from working. Seeing as Datel are running a business and a lot of effort went into making the PSPAR they want to keep it working as long as possible so they can continue to make sales. And it is fairly obvious Sony don't really care too much about the PSPAR since it took them 6 months to release an update to block it and the only reason they probably even done that was because of the Patapon 2 exploit.
Saying that though I agree that it's disappointing that the PSPAR doesn't work on CFW or use external code files. In my opinion the best thing about a cheat engine is making your own codes which has been taken away in the new PSPAR.
EDIT: Damn if only I posted this 2 weeks ago I could have made my first post exactly 1 year after I joined.