webMAN MOD

PS3 webMAN MOD - General Information Thread 1.47.48q

If wm_vsh_menu does not show a pop up at boot then it's probably not loading.
Check the /dev_hdd0/boot_plugins.txt.
Is there a path to wm_vsh_menu.sprx? Like /dev_hdd0/plugins/wm_vsh_menu.sprx?
If not add it yourself & save the file...

syscon is the original ofw fan mode. The settings are very low & the fan never goes above 30%. The CPU temp generally remains around 75C to 80C. Emergency shutdown is at 85C.
The issue here is to try to keep the temp lower than intended to avoid ylod & other consequences due to heating up common with syscon setting while managing noise to an acceptable level.
After I deleted wm_config.bin, wmconfig. Bin and reinstalled the webMAN,the VSH Returned to be reloaded,now it shows the pop up on the XMB :)
I have confused now with your explanation on the SYSCON.
I always found that the auto configuration in was the OFW mode.
We set a value, and after these value becomes OFW mode.
Is that it?
 
After I deleted wm_config.bin, wmconfig. Bin and reinstalled the webMAN,the VSH Returned to be reloaded,now it shows the pop up on the XMB :)
I have confused now with your explanation on the SYSCON.
I always found that the auto configuration in was the OFW mode.
We set a value, and after these value becomes OFW mode.
Is that it?
There's nothing confusing about syscon. Read my post again, I never said it was a manual mode (it's automated) or that you could set values (you cannot set values, those are hard coded) ...

Syscon is the normal fan mode of a console on OFW. When you choose syscon with wMM on CFW, the fan will behave as if you were on OFW. That's all.
On syscon, you do not set a fan value, fan values are automated with the maximum fan at 30% when the CPU reaches 73C & above. On syscon, the fan will never go faster than 30% so if the temp reaches 85C, the console shuts down.
Look at the syscon automated fan values here:
http://www.psdevwiki.com/ps3/Thermal
The fan values are in hexadecimal & the temps in Celsius.
For reference, on wMM temp page, the hexadecimal value is written beside its percentage equivalent.

Syscon works fine of course but we generally prefer to use higher fan settings to avoid overheating. There are so many ylod consoles out there... Using higher values for fan settings means having to use another fan mode like manual or dynamic.

In wMM, you can toggle between manual, dynamic & syscon modes. That's all.
 
Last edited:
There's nothing confusing about syscon. Read my post again, I never said it was a manual mode (it's automated) or that you could set values (you cannot set values, those are hard coded) ...

Syscon is the normal fan mode of a console on OFW. When you choose syscon with wMM on CFW, the fan will behave as if you were on OFW. That's all.
On syscon, you do not set a fan value, fan values are automated with the maximum fan at 30% when the CPU reaches 73C & above. On syscon, the fan will never go faster than 30% so if the temp reaches 85C, the console shuts down.
Look at the syscon automated fan values here:
http://www.psdevwiki.com/ps3/Thermal
The fan values are in hexadecimal & the temps in Celsius.
For reference, on wMM temp page, the hexadecimal value is written beside its percentage equivalent.

Syscon works fine of course but we generally prefer to use higher fan settings to avoid overheating. There are so many ylod consoles out there... Using higher values for fan settings means having to use another fan mode like manual or dynamic.

In wMM, you can toggle between manual, dynamic & syscon modes. That's all.
I always use the manual mode at a value of 43 because I consider a sound that does not get too loud, my PS3 gets a temperature of 67 ° at the most. I also use a good paste thermal to aid in dissipating the heat. I used Formerly the Control Fan,but I like the webMAN because the cooler already starts with the value that you established, there is still much to explore in the webMAN, I am learning one step at a time and I have Learned a lot with you.
Thank you for the patience to explain me.
 
A fan at 43% is already quite loud... [emoji6]

Just for reference, I keep my 2 slims in dynamic control with 66 to 68C maximum temperature.
Usually the fan remains around 37% & rises to 40% during gameplay.
One of my slims, a CECH210x, heats up a bit more overall than the other, a CECH250x.
On my 250x console the RSX is always 10C below the CPU & on the 210x the CPU & RSX are generally around the same temps...
 
A fan at 43% is already quite loud... [emoji6]

Just for reference, I keep my 2 slims in dynamic control with 66 to 68C maximum temperature.
Usually the fan remains around 37% & rises to 40% during gameplay.
One of my slims, a CECH210x, heats up a bit more overall than the other, a CECH250x.
On my 250x console the RSX is always 10C below the CPU & on the 210x the CPU & RSX are generally around the same temps...

You won't hear the fans if you put the volume of the music of the TV or home theater to the max :)

BTW this should fix your download issue (it's updated with the latest commit):
https://github.com/aldostools/webMAN-MOD/releases/latest
 
Slightly off-topic but what is the recommended max temperature for a CECHB01? I do run the fan control utility at max 64 degrees celcius.


EDIT: Hey @aldostools is it possible to add an option to hide the ISO locations from view when looking at games from the XMB menu?
 
Slightly off-topic but what is the recommended max temperature for a CECHB01? I do run the fan control utility at max 64 degrees celcius.


EDIT: Hey @aldostools is it possible to add an option to hide the ISO locations from view when looking at games from the XMB menu?
The situation is different on every console, not just between models. Depending on the current state of the hardware & the environment in which you use the console, the ideal settings would differ.
I would usually recommend to keep the CPU under 70C, as a general rule the colder a CPU runs at, the better.... But there is the noise factor to consider...
If keeping the console at 64C is too noisy, you might consider using a slightly higher average temperature.
Note that consoles on OFW or using syscon settings often run between 75C & 82C on average...
 
Yes, it is possible, but before I would like to understand why you need such feature...
There are many other places where the path is also visible.

Thanks for the reply @aldostools, I can't express how appreciative I am that you take the time to reply to us.

It's purely for cosmetic reasons. I feel like my XMB would look cleaner if I did not have to see where the games are mounted. Since I am the "sysadmin" of my PS3, I don't need to know where my games are located.
 
I disagree. We need to keep the path, even as sysadmin.
What happens when you have the same game twice? One on ps3netsrv & one locally stored...? Or even simply the same game in iso & JB format locally?
Personally I want to know if a game is internally stored, on the network, on an external hdd... When I have a game in both iso & JB format, I want to know which is which. Same thing for games copied on different locations like net0. I want to know that mounting the game will require the network... Etc...

Imho not showing the path is only a good option for people using one kind of game format, in one location only & without duplicates.
 
Last edited:
I disagree. We need to keep the path, even as sysadmin.
What happens when you have the same game twice? One on ps3netsrv & one locally stored...? Or even simply the same game in iso & JB format locally?
Personally I want to know if a game is internally stored, on the network, on an external hdd...

I can see why that would be something that someone would like, but that's the beauty in having the functionality of being able to turn on & off! I might be anal but I know where all of my games are located (doesn't help i'm a sysadmin in real life).
 
If Aldo has time to implement a toggle why not...
However I doubt that many people will use it to toggle the path visibility off...

Fair enough. It's nothing that should be rushed to be implemented. There are other things that should be worked on before my request. I'm already beyond appreciative for the awesome FREE plug-in and support from aldo!
 
If Aldo has time to implement a toggle why not...
However I doubt that many people will use it to toggle the path visibility off...

I would use this. I mount nearly all my games internally or via USB, so there's no confusion about where they are located in my case. It just looks a little cleaner without the path. It's *absolutely* necessary to be on by default (it helped me notice a case-sensitivity issue), but once everything is setup the paths are just extraneous information.
 
Remove psnpatch plugin
Go into webman mod
Next to the "disable cfw syscalls and delete history files on start up" there is an option for "lock psn"
Now if you tick that then you cannot go onto psn
So far so good
But if you press R2 + Triangle
You get the syscalls disabled message but it doesn't unlock psn access
Can this be added to the R2 + triangle shortcut


Sent from my iPhone using Tapatalk
 
In wmm 1.45.05 on Rebug 4.81, some ROMS stored in usb001 are being sorted into the PS3 category on the XMB.

For example, A-D are in ROMs, while J-Z are in PS3. part of D, and subsequent letters D-F, are missing entirely.

The ROMs category also reports an incorrect number of files within (displays 14, total lists 32). PS3 category total with ROMs is accurate however. Looking closer, it seems that when scanning for media the scan progresses normally, however in my largest folder (about 60 SNES files) some files get skipped, and the remainder are then sorted into the PS3 category. All files still launch properly regardless.

Whatever is causing it results in about 10 files being skipped over, and the remainder being miscategorized. Testing this a few times by renaming some files, causes *some* files to be re-detected and moved to the PS3 category, while other new files go missing. Issue is new in 1.45.05. Will attempt downgrading to 45.04 to see if it resolves it.

Edit: ROMs are detected in HTML view, and viewable under the "ROMs" filter under Games, and also included under "PS3" and "Games" filters as well. So this seems to be an XML related issue.
 
Last edited:
In wmm 1.45.05 on Rebug 4.81, some ROMS stored in usb001 are being sorted into the PS3 category on the XMB.

For example, A-D are in ROMs, while J-Z are in PS3. part of D, and subsequent letters D-F, are missing entirely.

The ROMs category also reports an incorrect number of files within (displays 14, total lists 32). PS3 category total with ROMs is accurate however. Looking closer, it seems that when scanning for media the scan progresses normally, however in my largest folder (about 60 SNES files) some files get skipped, and the remainder are then sorted into the PS3 category. All files still launch properly regardless.

Whatever is causing it results in about 10 files being skipped over, and the remainder being miscategorized. Testing this a few times by renaming some files, causes *some* files to be re-detected and moved to the PS3 category, while other new files go missing. Issue is new in 1.45.05. Will attempt downgrading to 45.04 to see if it resolves it.

Edit: ROMs are detected in HTML view, and viewable under the "ROMs" filter under Games, and also included under "PS3" and "Games" filters as well. So this seems to be an XML related issue.
Remember the various grouping settings you can try... It's always good for us to know what works & what does not... If you don't mind check grouping/disable grouping....

Also remember to tweak the memory usage settings of the plugin in the setup page, increase it if you use many games...

Looking forward to your report....
 
Back
Top