• PS3HEN is now supporting 4.93 Firmware

    View Official Release Post for additional information HERE

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

just a side note. When testing yesterday, i noticed that the package manager still stutters when using xml to hide and show on 4.89. Its almost "random" as from my earlier tests it would not stutter when directly enabling hen and going to package manager, but it did stutter a couple times after testing multiple reboots and tries.

That's strange. here it doesn't stutter at all (using map_path) ,I just tested 15 times in a row and no stutters.
 
That's strange. here it doesn't stutter at all (using map_path) ,I just tested 15 times in a row and no stutters.
We are currently trying to improve the map_path system, I added a mutex and debug output to investigate any issues.

Could you please clarify one thing for us to help us test the various use cases found to be problematic until now?

You reported that some /dev_flash remappings didn't work except with the AAA folder. Are those remapping problems occurring when you remap to dev_flash OR from dev_flash?

Could you post the list of remappings you had trouble with?
And any files we may need to go with it?
 
We are currently trying to improve the map_path system, I added a mutex and debug output to investigate any issues.

Could you please clarify one thing for us to help us test the various use cases found to be problematic until now?

You reported that some /dev_flash remappings didn't work except with the AAA folder. Are those remapping problems occurring when you remap to dev_flash OR from dev_flash?

Could you post the list of remappings you had trouble with?
And any files we may need to go with it?


I saw the new build of HEN, but I haven't had time to check it out yet, i'll provide some tests and logs as soon as possible.

But one thing that me and @DeViL303 never managed to do was remapping files from flash to flash, just the AAA folder works for images/rcos/sprxs also e.g mapping game_category.xml to any other xml in flash doesn't work, you can log the open_path to see that vsh/resource/explore/xmb/ xml files are not listed on it
 
I saw the new build of HEN, but I haven't had time to check it out yet, i'll provide some tests and logs as soon as possible.

But one thing that me and @DeViL303 never managed to do was remapping files from flash to flash, just the AAA folder works for images/rcos/sprxs also e.g mapping game_category.xml to any other xml in flash doesn't work, you can log the open_path to see that vsh/resource/explore/xmb/ xml files are not listed on it
Thanks.
FYI
The builds posted in that test thread don't contain the mutex and other changes I made, just extra logs I added for debugging AFAIK.
We are currently testing the new changes I made to map_path, esc0 might post a build whenever we are satisfied with alpha testing.
 
you can log the open_path to see that vsh/resource/explore/xmb/ xml files are not listed on it
This is true, some files never seem to appear in socat output logs. I wonder is the remapping of category xmls in particular, not working as those are not handled like normal files, are they maybe served with some kind of web/ftp server and that is why we see all the "//localhost" type links for them. idk.
 
Yes it contains other things to test, just not the map_path implementation changes.

An example is

I needed to use a hdd path for the HEN Enabler

<Queryclass="type:x-xmb/folder-pixmap"key="hen_xmb"attr="hen_xmb"src="xmb://localhost/dev_hdd0/hen/hen_enabler.xml#seg_hen_enabler"/>

and then

map_path_slot("/dev_hdd0/hen/hen_enabler.xml","/dev_flash/hen/xml/hen_enabled.xml",6)

Otherwise it won't work, flash to flash xmls doesn't work

This is true, some files never seem to appear in socat output logs. I wonder is the remapping of category xmls in particular, not working as those are not handled like normal files, are they maybe served with some kind of web/ftp server and that is why we see all the "//localhost" type links for them. idk.

Any flash to flash xml doesn't work, even if it's a cutom one, @esc0rtd3w also tried this in his alternative hen build last year and ended up like me placing the source file in hdd0 and the one to be mapped in flash
 
Last edited:
This is true, some files never seem to appear in socat output logs. I wonder is the remapping of category xmls in particular, not working as those are not handled like normal files, are they maybe served with some kind of web/ftp server and that is why we see all the "//localhost" type links for them. idk.
It's possible that those files are 'served' but I think that even if it were the case, the server would still have to open the file in order to send it and use open_path in theory... unless there's an alternate open_path function dedicated to this server???

It could also be that the open_path hook function exits before the open_path printf statement is executed so you don't get to see any socat output, iirc the open_path printf is located at the very end of the function and there are several return statements that can be executed for one reason or another before then.
I suppose the easiest way to find out is to add a debug printf statement at open_path hook function start.

The other thing is we know that the current map_path implementation is buggy and can potentially lead to undefined behaviour, so it's hard to draw definitive conclusions from test results. That's why we decided to investigate, to get answers and hopefully fix the mapping problems once and for all if we can.
 
Last edited:
t's possible that those files are 'served' but I think that even if it were the case, the server would still have to open the file in order to send it and use open_path in theory... unless there's an alternate open_path function dedicated to this server???
Maybe, I do not know enough to speculate on this really but it does seem like it uses a different method, I always found it strange that even when reloading the XMB via logging the user out, or entering then exiting Remote Play, or exiting a game etc, The category xmls never appear in socat logs. As far as I remember the registory.xml never appears there either.

Probably not that important overall but It would be nice if this could be sorted out so xml access was logged, also kind of a different issue, but similar, it would cool if any URLs being accessed by the system were also logged in real time too.
 
Maybe, I do not know enough to speculate on this really but it does seem like it uses a different method, I always found it strange that even when reloading the XMB via logging the user out, or entering then exiting Remote Play, or exiting a game etc, The category xmls never appear in socat logs. As far as I remember the registory.xml never appears there either.

Probably not that important overall but It would be nice if this could be sorted out so xml access was logged, also kind of a different issue, but similar, it would cool if any URLs being accessed by the system were also logged in real time too.
Hmmm, and registory.xml too...
I must admit it does look like a pattern.
 
@esc0rtd3w i think all this RCOs can be removed from all HEN installers, because are identical in between OFW484, OFW489 and HEN489 (probably in all previous HEN installers too, is needed to check that to be sure that can be deleted in all them)

explore_category_psn.rco (MD5 AFCDD7AB77294747F9681BD8672220D9)
explore_category_video.rco (MD5 825AA07B4FB0E5B13890BEC3963DAE52)
wboard_plugin.rco (MD5 01013194C96A3A501D7B4C9A2664C2F8)
xmb_ingame.rco (MD5 04ED4ECCA76C6927154470CC8E497B83)
xmb_plugin_normal.rco (MD5 9EDEFC55FDF0403B98A0BCE3AD71F3D6)

The other day when i was reviewing the RCOs i didnt cared much about them because are not in the list of RCOs updated by sony in OFW489 (so are fine, are not causing any incompatibility)... i just assumed they had custom edits, and whatever was that edits nobody complained in the previous HEN releases, so was working fine, etc...
But now im realizing this 5 RCOs doesnt have any custom edit, are official (and are not replaced by the .TAR swap required to do a HFW) so the HEN installer doesnt needs to "restore" them, right ?
 
Last edited:
Package Manager has more bugs than I think before.
HEN disabled:
Install -> System Storage has an empty screen without text (I don't have PKGs here) [bug?]
Install -> Package Directory has an empty screen without text (I do have PKGs here) [bug?]
Install -> Standard content directory is missing/infinite loading (as already known) [bug!]
Install -> Package Linker the only item with "No package files found." text inside
Delete -> System Storage the only item with "No package files found." text inside
Delete -> Package Directory has an empty screen without text [bug?]
Delete -> Standard has an empty screen without text [bug?]
HEN enabled:
Install -> System Storage has "No package files found." text inside (I don't have PKGs here)
Install -> Package Directory has a list of PKGs on my USB drive (I do have PKGs here)
Install -> Standard is present and has "No package files found." text inside (I don't have PKGs here)
Install -> Package Linker has "No package files found." text inside (I don't have PKGs here)
Delete -> System Storage has "No package files found." text inside (I don't have PKGs here)
Delete -> Package Directory has infinite loading icon on every PKG inside and empty screen after pressing X [bug!]
Delete -> Standard has "No package files found." text inside (I don't have PKGs here)
 
@esc0rtd3w basically, you only need to keep the RCOs with custom edits, that are:

explore_category_game.rco
Contains 1 downgraded string (pointless)
Contains 1 custom string for rebug package manager

explore_plugin_full.rco
Contains 1 custom icon for rebug package manager
Contains 20 custom strings (translated to 20 languages) for rebug package manager

software_update_plugin.rco
Contains 1 custom patch to block network updates
Contains 1 updated string for the network error

xai_plugin.rco
100% custom

The (pointless) downgraded string inside explore_category_game.rco is replacing this:
Code:
<Text name="msg_about_game_ps3_content">Library programs ©Sony Interactive Entertainment Inc. Licensed for play on the PlayStation®3 Computer Entertainment System or authorized PlayStation®3 format systems. For full terms and conditions see the user's manual. This product is authorized and produced under license from Sony Interactive Entertainment Inc. Use is subject to the copyright laws and the terms and conditions of the user's license.</Text>
By this string:
Code:
<Text name="msg_about_game_ps3_content">Library programs ©Sony Computer Entertainment Inc. Licensed for play on the PlayStation®3 Computer Entertainment System or authorized PlayStation®3 format systems. For full terms and conditions see the user's manual. This product is authorized and produced under license from Sony Computer Entertainment Inc. Use is subject to the copyright laws and the terms and conditions of the user's license.</Text>
And the custom (added) string is:
Code:
<Text name="msg_tool_package_file"><![CDATA[★ Package Manager]]></Text>
 
Last edited:
@esc0rtd3w i think all this RCOs can be removed from all HEN installers, because are identical in between OFW484, OFW489 and HEN489 (probably in all previous HEN installers too, is needed to check that to be sure that can be deleted in all them)

explore_category_psn.rco (MD5 AFCDD7AB77294747F9681BD8672220D9)
explore_category_video.rco (MD5 825AA07B4FB0E5B13890BEC3963DAE52)
wboard_plugin.rco (MD5 01013194C96A3A501D7B4C9A2664C2F8)
xmb_ingame.rco (MD5 04ED4ECCA76C6927154470CC8E497B83)
xmb_plugin_normal.rco (MD5 9EDEFC55FDF0403B98A0BCE3AD71F3D6)

The other day when i was reviewing the RCOs i didnt cared much about them because are not in the list of RCOs updated by sony in OFW489 (so are fine, are not causing any incompatibility)... i just assumed they had custom edits, and whatever was that edits nobody complained in the previous HEN releases, so was working fine, etc...
But now im realizing this 5 RCOs doesnt have any custom edit, are official (and are not replaced by the .TAR swap required to do a HFW) so the HEN installer doesnt needs to "restore" them, right ?
Thanks for also checking those! But its already been done in 3.1.1 :)

upload_2022-5-24_21-26-59.png
 
Package Manager has more bugs than I think before.
HEN disabled:
Install -> System Storage has an empty screen without text (I don't have PKGs here) [bug?]
Install -> Package Directory has an empty screen without text (I do have PKGs here) [bug?]
Install -> Standard content directory is missing/infinite loading (as already known) [bug!]
Install -> Package Linker the only item with "No package files found." text inside
Delete -> System Storage the only item with "No package files found." text inside
Delete -> Package Directory has an empty screen without text [bug?]
Delete -> Standard has an empty screen without text [bug?]
HEN enabled:
Install -> System Storage has "No package files found." text inside (I don't have PKGs here)
Install -> Package Directory has a list of PKGs on my USB drive (I do have PKGs here)
Install -> Standard is present and has "No package files found." text inside (I don't have PKGs here)
Install -> Package Linker has "No package files found." text inside (I don't have PKGs here)
Delete -> System Storage has "No package files found." text inside (I don't have PKGs here)
Delete -> Package Directory has infinite loading icon on every PKG inside and empty screen after pressing X [bug!]
Delete -> Standard has "No package files found." text inside (I don't have PKGs here)
I can confirm that System Storage and Standard shows packages with HEN enabled.

EDIT: The package manager will be hidden until HEN enabled, like HFW Tools, in next released version. Also there will be a BETA package posted at some point that also has this, for testing in public.

EDIT2: I guess the other option would be leaving only the Playstation Network folder under Package Manager, and just hide the others until HEN enabled.

EDIT3: An option could be added to xai for toggling PSN Only and Hidden Package manager, on boot
 
Last edited:
Trying to think outside the box: wouldn't be better just to replace some of the files from 4.89 with the ones from 4.88 spoofed to 4.89?

AFAIK 4.89 doesn't offer practically any new feature, except big bugs and removed features.

4.88 was working fine practically without any issues. It allows PSN login with ps3-updatelist.txt. IMHO 4.88 is a better option than recommend HEN users to update to 4.89.
 
Back
Top