No.


Don't try screwing around with the flash0 either. I've got a rough idea how DarkAlex got this firmware made but it aint very simple at all. All i do know is that it is NOT LIKE OTHER FIRMWARE's technically. What it does is load 1.5 firmware, then half the libraries are replaced/patched with 2.71 versions basically. They are not completely replaced, but 'upgraded' so to speak, so there are a bunch of hacked/unique files in flash0 that are completely different to anything we'eve ever seen.

It is sad that Dark-Alex did not implement PRX loading features, but he probably has a good reason for this. I would assume that the structure of 2.71 SE-A makes it a lot harder to load PRX's, and is probably not compatible with current 1.5 PRX mods. PRX modules, are, run when the firmware boots. At what stage this is, i do not know. But depending on this, there are two possible reasons why PRX loading is not feasable with 2.71 SE-A.

1. Lets say the PRX's HAVE to be loaded before the 1.5 bootstrap kicks in the 2.71 firmware-mod. This would be hard to implement. This would not work with current PRX's because the PRX's loaded would have invalid/mismatched memory handles after the 2.71 mod kicks in, because a mega-change in memory pooling has just occured so it wouldnt know where the code in RAM is to execute (for the PRX).

2. The other possible reason, is IF the PRX's have to be loaded AFTER the 1.5 bootstrap kicks-in the 2.71-mod FW. In this case, it would just be plain-incompatible. PRX's for a firmware based on 1.5 will not work on 2.71 for various reasons, i'll save you from the reasons.




Ok, so you may be saying, "but this is 2.71 firmware that can 1.5 EBOOT's! Why can't it run 1.5 PRX's???"

Well this is a simple answer. EBOOT's are user-mode applications. Yes i know u hear all this about 'kernal-mode' in EBOOT's and such, but that's not what i'm talking about. When an EBOOT is executed, it is initiated from user mode, as is basically EVERYTHING that you 'choose' to do in the XMB and such. In this way, many things cannot exist in JUST the kernal-space and not the user-space. No EBOOT's do anyway. The reason why this is compatible is because when an EBOOT is run, it is assigned some memory in user-mode, then the PSP kernal natively allocates hard-mode memory pools to the EBOOT when requested, if requested, etc. Basically, the PSP KNOWS WHT TO DO. But with PRX's, a PRX DIRECTLY PATCHES A PART OF THE KERNAL MODE MEMORY POOL. And since the hard-mode of 2.71 firmware is mich different that 1.50, the PRX's are just plain incompatible.




All this is speculation, i don't know HEAPS about PSP hacking and such but all that is kind of a collaboration of my PSP programmnig knowledge and computing knowledge. I know that all that is similar to how the DreamCast works (i used to do programming for DreamCast too), as is PC's, so it's probably teh same for pretty much every complex machine likea computer or a console.


Hope that makes sense.

Oh P.S.....

Soft-mode = User mode
Hard-mode = Kernal Mode

__________________

use devhook and manuch the flash firmware with the prx. it should work.

__________________

Erm.. i dont know what that says (lawl) but i assume you mean.. load the PRX with DevHook....? If that's what you mean that kind of defeats the purpose. THe whole point of having a PRX addon for the firmware is to enhance the firmware, such as giving the ability to autoload an EBOOT on startup, or show an intro video PMF file when you turn the PSP on. There isn't really any fun emulating it is there :P

I assume he asks because he wants to mod 2.71 SE-A some more basically (correct me if i'm wrong). But yeah.... ur not the only one who wants this feature, i did a lot of research and stuff trying to find a way, but there just isn't yet

We'll havta wait for 2.71 SE-B then ay? ;D

__________________