PS3 webMAN v1.46n - New XMB Game Mounting Improvements (using wm_proxy/xai_plugin) by deank

Following the recent updates from legendary developer deank that improved NTFS support a great deal in the webMAN plugin, and the recent Cobra Update (stage2.bin) that allows you to play Games & Media from burnt optical disc. The developer has been busy with yet another trick up his sleeves, as we showed yesterday deank has been working on a new test feature for webMAN , now the test feature has been introduced officially in webMAN v1.46n. this new feature utilizes the source code release for the custom xai_plugin (by mysis) and mounting games is much faster and cleaner from the XMB as the web-browser trick is no longer needed as deank adapts the custom xai_plugin in a great way. Checkout all the details and a video demo of the new game loading in the details/changelog provided by deank..

Release Quote Video Demo

• 
  
  webMAN 1.46n Changes
  1) Mounting games is now faster
  2) After game/video is mounted the focus will move to the respective XMB column
  3) Reduced memory consumption
  4) Includes NTFS and NETSRV support
  
  
  Thanks to @mysis for sharing details on how to create custom xai_plugin.​
  
  Dean
  
• 
  

Download: webMAN_1.46.zip

Source: psx-place.com​

 

The popup appears after webMAN is loaded. It should appear only once after system boots completely. If it appears later/again it means that webMAN plugin is loaded again (probably on different slot). I have no idea why whould it happen otherwise.

 

@Zwei IRISMAN now auto-starts webMAN if it is not running and the plugin is detected in the path indicated in the file /dev_hdd0/game/IRISMAN00/USRDIR/settings.ini

Change that value to a non-existing path if you don't want that IRISMAN start webMAN.

The reason of the change in the fan speed is because webMAN's fan control is competing with your other fan setting in IRISMAN.

By default IRISMAN's fan control is disabled in favor of webMAN's dynamic fan control.

 

@Zwei IRISMAN now auto-starts webMAN if it is not running and the plugin is detected in the path indicated in the file /dev_hdd0/game/IRISMAN00/USRDIR/settings.ini

Change that value to a non-existing path if you don't want that IRISMAN start webMAN.

OK but webman 1.47n is already running in his case... Irisman has no reason to load its own webftp_server.sprx if there is one in memory already, does it?
It does not happen on my machine, I tried to reproduce & I cannot. My Irisman settings also have a path to webftp_server.sprx but the app does not try to load it....
???

 

1. OK but webman 1.47n is already running in his case... Irisman has no reason to load its own webftp_server.sprx, does it?

It does not happen on my machine, I tried to reproduce & I cannot. My Irisman settings also have a path to webftp_server.sprx but the app does not try to load it....
???

IRISMAN first checks if the thread "wwwd" is running.
If it is not running, it starts the plugin indicated in the webMAN key of settings.ini
This is the default path: webMAN = /dev_hdd0/plugins/webftp_server.sprx

EDIT: Sorry for the thread hijack... @bguerville Please move the messages related to IRISMAN to a new thread....

 

webMAN: Improved FTP memory usage and performance - it will not constantly allocate/deallocate memory for each file transfer, but do it once per ftp session. This also improves transfer speed along with the increased 256KB buffer.

VSH free memory is now 2204KB with one plugin - (webMAN w/ NTFS) and 2068KB with both sLaunch and webMAN. This is more than before adding ntfs library to webMAN.

I've got 1988KB with both slaunch and webman. Down to 1796KB with psnpatch loaded. I don't know where the 80KB more you've got gone at my side. It is still a pretty good improvement

 

@aldostools: webMAN will respond to connection on port 80 with "webMAN x.xx" and will close the connection if you request something else than "GET /....".

 

@freddy38510: Did you use the latest (from just few minutes ago)? It may depend on your firmware/theme/etc. I'm using habib's 4.81 with the classic theme with classic background, rounded font - it has been that way for 10 years .

 

This also improves transfer speed along with the increased 256KB buffer.

Just curious... have you measured the improvement using 256KB vs 128KB?

While I was developing the ps3netsrv for wMM I found something weird: The transfer was way more faster when I used a buffer of 64KB than when I used large buffers. ATM I don't have access to my PS3, but it would be interesting to compare.

 

@freddy38510: Did you use the latest (from just few minutes ago)? It may depend on your firmware/theme/etc. I'm using habib's 4.81 with the classic theme with classic background, rounded font - it has been that way for 10 years .

I re-downloaded webman 1.47n just to be sure. I also changed the theme to classic with classic background and rounded font then reboot the console. Still 1796KB with webman/slaunch/psnpatch loaded.

I'm using cfw rebug 4.81.2, this could explain this.

 

It depends on the direction (sending/receiving) and also on the fragmentation of the hdd you're sending to/receiving from).

I tested the other day with 1GBit connection directly to my PC, which is using SSD HDD. I'll do another test with 128KB and 256KB in both directions.

 

@aldostools: webMAN will respond to connection on port 80 with "webMAN x.xx" and will close the connection if you request something else than "GET /....".

Unless you have some use responding "webMAN x.xx", I opted to respond with a proper http error and headers:

http_response(conn_s, header, param, CODE_BAD_REQUEST, "400 Bad Request");

Regarding the memory allocation in the FTP server, the buffer now is allocated from the Memory Containter and if it fails, it will use sys_memory_allocate. If a LIST or SITE command is used, the allocated memory will be freed without have to close the FTP session.

 

Allocating from memory container for the FTP is not good idea, because it will either crash a loaded game or won't let it start (crash at load), which makes ftp useless while playing a game. Also too frequent alloc/free of mc memory causes fragmentation and is not a good practice. Although allocating just 128-256KB may not be a problem, still VSH crashes because it can't destroy the container on game-launch. This is the reason I decided to use MC In wM only for quick tasks and at system boot for xml/slauncher.bin creation, when it is certain there is no game played, for ftp - standard memory, for www-requests - only when possible.

Still the problem exists if you decide to download a big file using a PC browser (from wM's web interface) and while downloading (when MC is already allocated) staring a game. In most cases it will crash the system. Of course it won't crash if transfer is started via FTP.

 

Allocating from memory container for the FTP is not good idea, because it will either crash a loaded game or won't let it start (crash at load), which makes ftp useless while playing a game. Also too frequent alloc/free of mc memory causes fragmentation and is not a good practice. Although allocating just 128-256KB may not be a problem, still VSH crashes because it can't destroy the container on game-launch. This is the reason I decided to use MC In wM only for quick tasks and at system boot for xml/slauncher.bin creation, when it is certain there is no game played, for ftp - standard memory, for www-requests - only when possible.

Still the problem exists if you decide to download a big file using a PC browser (from wM's web interface) and while downloading (when MC is already allocated) staring a game. In most cases it will crash the system. Of course it won't crash if transfer is started via FTP.

Thank you for share your knowledge with us I appreciate it very much!

I changed the code in github, so the FTP transfers will allocate from MC only if they are performed from XMB. The first session will always use the standard memory allocation and MC for and for concurrent transfers.

The issue that you mention still exists if the user starts a game doing concurrent ftp transfers. For transfers through a single session, it should work without issues.

IMO the benefit of MC in FTP is that several concurrent ftp transfers can be used from XMB.

 

I re-downloaded webman 1.47n just to be sure. I also changed the theme to classic with classic background and rounded font then reboot the console. Still 1796KB with webman/slaunch/psnpatch loaded.

I'm using cfw rebug 4.81.2, this could explain this.

You should get even more free memory if you update webMAN.

I tested it with NTFS+NETISO, game loaded from network and playing, while transferring a file via FTP from ntfs drive and downloading one via the PC webbrowser, so it is stable enough.

 

@Zwei
For the webMAN 1.47n pop-up to be displayed, webman must get loaded! There is no other way...
So somehow when you load Irisman,, the webMAN daemon gets loaded again...???
Into another slot I assume because I doubt the first webman instance got unloaded first...
@deank ? How does this make sense? Any idea?

The best solution was to format the internal hd of ps3
problem solved

 

That was a tad radical... Lol
There were much easier ways to stop the problem from happening though... NVM

 

That was a tad radical... Lol
There were much easier ways to stop the problem from happening though... NVM

At least the problem is over xD

 

Spil ISO files on fat32 usb hdds?

Yeah, that's the one.. Took me a while to figure out why some games had covers and others didn't... Just re downloaded it again this morning and everything is working well again. Thanks

 

@deank
CFW rebug 4.81.2
webMAN 1.47n
It is possible to add a shortcut to refresh xml.
Button sequence.

@Joonie
Is there any way to refresh the webman?
I switched the webman mod to the deank webman and it disappeared from the xmb but the command works.

@bguerville
Any tips, idea?

 

@Zwei try using prepNTFS 1.10 to rescan the xml/html


Sent from my iPhone using Tapatalk