PL3 Updated – MOH Now Running Without Need of Game Updates

[tpmjb]

I can't seem to find it but I know somebody has posted about it. After updating to PL3 from Hermes v1, Gaia manager won't show any of my games. It just gives the title of the folder and that's it. It says "eboot.bin not found" when I try to launch it and I can't view it in ftp.

This is related to permissions right? To fix I just have to delete and re-copy over?

Edit: Doesn't seem I can even delete them using PL3. So apparently I have to reflash the old firmware, delete all the games, then re-transfer them.

Fun.

Before I spend hours doing this, anyone wanna comment?

[Everblue]

Try Evilsperm .hex

PSGroove Payload_No_Unauth_Syscall Hex Codes
PS3 NEWS - PlayStation 3 News - PS3 Forums

I have Minimus too and works fine.

Does not work either. Stuck on 0% on INSTALLING GAME DATA FILES.

Do you confirm of playing this game from INTERNAL, not external?

[MetalPhreak]

Well i've spent a fair amount of time porting both the hermes releases and PL3 to the PIC18F boards. Illness has done an incredible amount of work porting it across and setting up hexes for a large number of board configurations. I find it hard to believe he accomplished all that without ever looking at the source code

You can hate kakaroto all you like for his arrogant rant. I'm only basing my opinion on the code right in front of my eyes. Just because I agree with some of what he said does not mean I am simply regurgitating what he said. I am more than capable of forming my own opinion thanks.

Back onto the topic:

MOH refuses to boot for me on the internal HDD with either PL3 or the latest Hermes. External HDD works fine. Bit of a weird issue but the game isn't that great anyway

I'd also avoid using the no_unauth_syscall PL3 payload. Its the same as the normal default payload but with the controller patches removed (patches 6+7. 5 is also removed but I don't know what it does) (F1 etc will probably be broken again).

[MetalPhreak]

Before I spend hours doing this, anyone wanna comment?

Use a hex file that uses the standard PL3 payload. I had this same problem with the no_unauth_syscall payload. Reformatting the HDD did NOT fix it! Going back to the standard payload (which still patches the >3.42 error!) fixed it fine.

So far I can only boot MOH from an external HDD.

[tpmjb]

I'm using pic 1842455, so since I'm too lazy to compile the hex myself I'm using illness's latest compilation (1.0c). So you're using the PL3 payload without the MoH patch built in?

Edit: yeah, you're right...weird. 1.0b works just fine, yet 1.0c only boots 2 games.

Wonder if we'll get an app to fix permissions?

[MetalPhreak]

I'm using pic 1842455, so since I'm too lazy to compile the hex myself I'm using illness's latest compilation (1.0c). So you're using the PL3 payload without the MoH patch built in?

Edit: yeah, you're right...weird. 1.0b works just fine, yet 1.0c only boots 2 games.

Nah the latest PL3 has the "MOH patch". There's also a new payload version "no_unauth_syscall" which nobody seems to understand what it does (it has 3 patches missing that the normal payload has...). It would seem people are either having no issues whatsoever with it, or they are having the problems you and I have. I'm just using the normal payload which has the MOH patch and the 3 patches which are missing from "no_unauth_syscall". Obviously there is something more to it than just file permissions and whats on the harddrive. I suspect it'll be some kind of difference on the flash partition.

[tsb]

some testing

got a new internal hard drive, installed it and did a system restore

neither PL3(latest/evilsperm) nor Hermes V4 will run EyePet properly unless it is copied to the internal hard drive with patched mode enabled

I did fresh restores between each try to take out any possible conflicts

[chriscross]

What folder do you create on your external drive for gamez to be used in OM 2.1?

[tsb]

Gamez

[evilsperm]

Here is an updated zip with led's fixed for minimus v1
psgroove-all-no-unauth-syscall.zip