• PS3HEN is now supporting 4.93 Firmware

    View Official Release Post for additional information HERE

PS3HEN [Support Thread] PS3HEN Bugs, Problems, and Other Issues

If the issue was caused by memory allocation we would get debug logs as I remember adding DPRINTFs for this situation or at worst maybe a crash as I might have missed a check for null pointer somewhere.
I see no logs in the sample that was sent to me by pm, nor crash. However I see app_home mapping added and deleted more than once...

Regarding newer usage, I am aware, I mean I made the remapping changes with dynamic allocation because people asked for better support than just a handful of remaps for games.

The memory allocation and the mutex are the bigger differences between this implementation and Cobra.
I remember having issues with remaps in Cobra when it was using dynamic memory allocation in versions 8.3 and lower.

If you discard the memory allocation as a possible cause, I don't have other ideas about the origin of the bug.
 
The memory allocation and the mutex are the bigger differences between this implementation and Cobra.
I remember having issues with remaps in Cobra when it was using dynamic memory allocation in versions 8.3 and lower.

If you discard the memory allocation as a possible cause, I don't have other ideas about the origin of the bug.
Yeah.
Well I will double check the code when I have a minute, however it would be nice if someone could post the HEN debug logs I requested.
 
sorry but i cant take it anymore, this version is horrendously broken

first time doing it and everything worked fine along everything

and next day its just dont, ive reinstalled everything already 3 times its like if the files corrupted themselves or something

tried the mario youtube channel tutorial and nothing

hen is trapped in a endless loop and any app literally crash

1 time thinking ive fixed this i got a black screen jesus i got tired trying to make it work literally nothing works


and its seems thats happening to 90% of us

i cleaned my ps3 super slim knowing that now ps3 is capable of being hacked only to arrive at the worst time possible

i hope you guys can fix this mess..............
 
sorry but i cant take it anymore, this version is horrendously broken

first time doing it and everything worked fine along everything

and next day its just dont, ive reinstalled everything already 3 times its like if the files corrupted themselves or something

tried the mario youtube channel tutorial and nothing

hen is trapped in a endless loop and any app literally crash

1 time thinking ive fixed this i got a black screen jesus i got tired trying to make it work literally nothing works


and its seems thats happening to 90% of us

i cleaned my ps3 super slim knowing that now ps3 is capable of being hacked only to arrive at the worst time possible

i hope you guys can fix this mess..............
You signed up in this forum to let devs know how annoyed you are with their "horrendously broken" work while providing no relevant data to even describe properly and in detail the issue you are having?
That's a good one.. [emoji23]

Should we assume from the scant info that you're referring to the issue caused when more than one USB device is plugged in at the same time which leads to an infinite loop during HEN loading?
If so, that should have been fixed on 22/04, in this commit .
If not, I suggest you provide a better description of the issue, some screenshots and HEN debug logs.
 
@aldostools

I am reviewing the mapping code, corrected a few minor errors.
esc0 provided me with the HEN logs for multiman mounting and wMM mounting.
I think I found the cause for the app_home discrepancy.

It comes from the various mappings made in wMM which don't exist in multiman.
In multiman there's ONLY one app_home redirection for the root so it works all the time, in wMM you remap the root, the PS3_GAME folder, then delete the root and replace it with a remap to the USRDIR folder etc.. of course some of those remaps are redundant and may clash with each other depending on which order they're processed in.

I am not sure why you found all those remaps necessary, if it was to work around the old mapping system limitations or whether you needed this for specific features that don't exist in multiman.
Depending on the situation, you may or may not want to review that code.

At my end, I made a test version where I tweaked the mapping code so as to keep wMM working with your code as is and keep legacy stuff compatible, waiting for esc0 to test it. I will keep you posted.
 
Last edited:
@aldostools

I am reviewing the mapping code, corrected a few minor errors.
esc0 provided me with the HEN logs for multiman mounting and wMM mounting.
I think I found the cause for the app_home discrepancy.

It comes from the various mappings made in wMM which don't exist in multiman.
In multiman there's ONLY one app_home redirection for the root so it works all the time, in wMM you remap the root, the PS3_GAME folder, then delete the root and replace it with a remap to the USRDIR folder etc.. of course some of those remaps are redundant and may clash with each other depending on which order they're processed in.

I am not sure why you found all those remaps necessary, if it was to work around the old mapping system limitations or whether you needed this for specific features that don't exist in multiman.
Depending on the situation, you may or may not want to review that code.

At my end, I made a test version where I tweaked the mapping code so as to keep wMM working with your code as is and keep legacy stuff compatible, waiting for esc0 to test it. I will keep you posted.

The multiple remappings is a workaround to the old mapping system*, where there is not a priority for mappings.
/app_home has priority over /app_home/PS3_GAME and /app_home/USRDIR. So I have to do multiple mapping to ensure the right paths are mapped.

On multiMAN that workaround is not necessary, because unlike webMAN MOD, it clears all the existing mappings.

Also multiMAN only needs to map /app_home to /dev_bdvd, and /app_home/PS3_GAME gets mapped automatically due the folder structure of the PS3 game. Unlinke multiMAN, webMAN MOD also supports mounting NP games through app_home. These games don't have a PS3_GAME folder, so /app_home/PS3_GAME and /app_home/USRDIR should be mapped individually.

*webMAN MOD anyway needs to support the "old" mapping system, because it is used on old firmware versions with old payloads that haven't been updated.
 
Last edited:
Sorry about my crappy complain but where do i can get the debug logs?

I don't know if i can even get them because I can't access anything hen related because it's doesn't work

Also no USB connected if you ask too
 
Sorry about my crappy complain but where do i can get the debug logs?

I don't know if i can even get them because I can't access anything hen related because it's doesn't work

Also no USB connected if you ask too

Are you installing "Stores" ?

Most of them installs a custom category_game.xml that is version dependent (not really, the fw check can be easily removed, but they don't care) and it causes hen to be in "a loop".

Most of people that complains about it are the ones who installed the so called custom stores
 
The multiple remappings is a workaround to the old mapping system*, where there is not a priority for mappings.
/app_home has priority over /app_home/PS3_GAME and /app_home/USRDIR. So I have to do multiple mapping to ensure the right paths are mapped.

On multiMAN that workaround is not necessary, because unlike webMAN MOD, it clears all the existing mappings.

Also multiMAN only needs to map /app_home to /dev_bdvd, and /app_home/PS3_GAME gets mapped automatically due the folder structure of the PS3 game. Unlinke multiMAN, webMAN MOD also supports mounting NP games through app_home. These games don't have a PS3_GAME folder, so /app_home/PS3_GAME and /app_home/USRDIR should be mapped individually.

*webMAN MOD anyway needs to support the "old" mapping system, because it is used on old firmware versions with old payloads that haven't been updated.
I can see 2 ways forward, tell me what you think.

1. Use the best possible mapping in the array instead of the first one matching depending on mapping items order.
For instance if the requested file is
/app_home/PS3_GAME/SND.AT3
it will always match to the
/app_home/PS3_GAME mapping
rather than the
/app_home mapping
even if the app_home mapping is found first in the mappings array.

It would fix app_home issues in wMM, not sure about orher such workarounds devs including yourself may have used.

2. Modify the code and remove all improvements such as existing mapping entry updates, replaced with deleteMapping/createMapping etc..
It will be a little slower but worse imho, it will force people to keep using dodgy workarounds but legacy compatibility should be guaranteed.

It's always the same problem at the core, we spoke about this already last year, we should never have developed stuff relying on an unfinished, imperfect mapping system in the first place, now we are in a situation where we cannot move forward in order to keep legacy support, it's frustrating..
 
Last edited:
Custom stores?

Something like pkgi?

Well I installed that....

But everything worked fine the first time and now nothing does

Maybe i forgot to format fat 32 my new hdd manually because many people told me that the PS3 do it itself
 
Last edited:
I can see 2 ways forward, tell me what you think.

1. Use the best possible mapping in the array instead of the first one matching depending on mapping items order.
For instance if the requested file is
/app_home/PS3_GAME/SND.AT3
it will always match to the
/app_home/PS3_GAME mapping
rather than the
/app_home mapping
even if the app_home mapping is found first in the mappings array.

It would fix app_home issues in wMM, not sure about orher such workarounds devs including yourself may have used.

2. Modify the code and remove all improvements such as existing mapping entry updates, replaced with deleteMapping/createMapping etc..
It will be slower but worse yet imho, it will force people to keep using dodgy workarounds but legacy compatibility should be guaranteed.

It's always the same problem at the core, we spoke about this already last year, we should never have developed stuff relying on an unfinished, imperfect mapping system in the first place, now we are in a situation where we cannot move forward in order to keep legacy support, it's frustrating..

I agree that it can be frustrating when you want to keep backward compatibility on your software.

The scenario 1 doesn't guarantee the backward compatibility. The change may work better in newer firmwares, but if the homebrews rely on that new behavior, they may not work correctly on older payloads.

The scenario 2 would send the new improvements to the trash.

A third scenario would be keep both behaviors in the payload and set a flag for "legacy mode"; or use a totally new API interface for the new improvements. That way the homebrew developer could decide how the mapping should behave. This scenario would require "duplicated" functionality in the payload and a larger memory footprint.

Given the large number of users still using old firmware versions, the scenario 2 looks like the more viable option.
Or just ignore webMAN MOD, and let future developments take the advantage of the improvements already made to the payload.
I think webMAN MOD is the only homebrew with issues with app_home. All others clear the mappings when they start.
 
Hi guys! What's up!?

I don't know if this is the right place or maybe is HFW 4.90.1 (Hybrid Firmware) discussion, but here it goes.

I just update my PS3 on HFW 4.90.1 and HEN on 3.2.2, my Webman MOD is up to date too on version 1.47.43, normally everything is ok but my game freezes a lot! Freezes when I try to enable HEN, when I try to open Irisman (I don't use Multiman becasuse someone told me that have some incompatibility with Webman MOD, this is real?), freezes when I try to open YouTube and freezes when I try to open a game, folder format ou pkg.

Sometimes I have to "hard reset" the PS3 3 or 4 times until stop freezes. I've read a lot about this and I know it's a kind "normally" happen, BUT ALL THIS TIMES!?

Also told me that "best version" to have HEN it's on 4.86, that is real too? There's something I can do about it or just accept the fate that is HEN really freezes a lot? :(

Thanks!
 
Hi guys! What's up!?

I don't know if this is the right place or maybe is HFW 4.90.1 (Hybrid Firmware) discussion, but here it goes.

I just update my PS3 on HFW 4.90.1 and HEN on 3.2.2, my Webman MOD is up to date too on version 1.47.43, normally everything is ok but my game freezes a lot! Freezes when I try to enable HEN, when I try to open Irisman (I don't use Multiman becasuse someone told me that have some incompatibility with Webman MOD, this is real?), freezes when I try to open YouTube and freezes when I try to open a game, folder format ou pkg.

Sometimes I have to "hard reset" the PS3 3 or 4 times until stop freezes. I've read a lot about this and I know it's a kind "normally" happen, BUT ALL THIS TIMES!?

Also told me that "best version" to have HEN it's on 4.86, that is real too? There's something I can do about it or just accept the fate that is HEN really freezes a lot? :(

Thanks!

Your webMAN MOD is *NOT* up to date to the latest version. Your issues are fixed in the latest release:
https://github.com/aldostools/webMAN-MOD/releases/latest
 
Where do i can get the debug log of hen? Or you need other tools with hen?

Because I can't enter any hen and pretty much i reinstalled everything but without webman
 
I agree that it can be frustrating when you want to keep backward compatibility on your software.

The scenario 1 doesn't guarantee the backward compatibility. The change may work better in newer firmwares, but if the homebrews rely on that new behavior, they may not work correctly on older payloads.

The scenario 2 would send the new improvements to the trash.

A third scenario would be keep both behaviors in the payload and set a flag for "legacy mode"; or use a totally new API interface for the new improvements. That way the homebrew developer could decide how the mapping should behave. This scenario would require "duplicated" functionality in the payload and a larger memory footprint.

Given the large number of users still using old firmware versions, the scenario 2 looks like the more viable option.
Or just ignore webMAN MOD, and let future developments take the advantage of the improvements already made to the payload.
I think webMAN MOD is the only homebrew with issues with app_home. All others clear the mappings when they start.
Only Irisman and wMM currently have issues apparently.
Spent quite a few hours trying to find a solution, finally got app_home and reloadXMB working on wMM, without impacting new mapping functionalities too much.

However I still have problems with Irisman app_home mounting.The /dev_bdvd mounting is fine, the disc icon works with jb folder games, but not app_home as it seems no redirections are being added to the hen/cobra mappings table.

I am not familiar with the Irisman code, I could see code that maps the app_home paths through syscall 38 (skye payload?) and a table copied to kernel space however I didn't see any syscall 8 calls for jb folder games app_home redirections through Cobra/HEN anywhere other than calls to remove the app_home mapping (ie setting it to null).


Any tips or suggestions that could help?
 
Last edited:
Where do i can get the debug log of hen? Or you need other tools with hen?

Because I can't enter any hen and pretty much i reinstalled everything but without webman
Just launch HEN and go to HFW Tools->Developer->Switch HEN Mode. Click on Debug Mode and then reboot. HEN will now output over UDP and you can use socat or another tool to capture. Here is a sample socat line to use in command prompt

socat -lu stdout udp-recv:18194,reuseaddr | tee socat.txt
 
Hey!

Sorry, I typed the wrong version, actually I'm on 1.47.44. Updated yesterday (same day that I installed HFW 4.90.1 and HEN 3.2.2). The freezes came long before that, when I used 4.89, but looks like "intensificated" more now.
In 3.2.2, you can now try to also use the Uninstall HEN option under HFW Tools->Maintenance. This should be done if problems arise, then you can reinstall without issues from a clean start
 
can we test it too? can you see the changes?
Not yet, I need esc0 to do some preliminary testing first, and I am waiting for Aldo to comment on the Irisman situation as well, I would rather fix that now too (if I can) so as to close the app_home issue down completely.

When we are satisfied with the basics and deem this new version worthy to be tested more widely, esc0 will post a build.
 
Back
Top