PS3 [UPDATE] webMAN MOD 1.46.00 - Games mounted from XMB without webbrowser_plugin (using idle_plugin)

Update (2/2/17/) -- v1.46.01
Original Article (Jan 31, 2017) Plugin development continues on the PS3 for Custom firmware users, this week alone we have seen some new features added lin PSNpatch by KW (w./ Homebrew Blocker) and we have seen deank back with new updates to webMAN that added NTFS Support / a new XMB game loading that no longer uses the web browser trick (webbrowser_plugin), in other words the flash you see when mounting a game on the XMB In,webMAN MOD v1.46.00 the plugin incorporates that function but in a different way, this is due to the differences under the hood of the plugin. As webMAN MOD contain different support for various add-on/features that the original project by deank does not support/contain so the usage and handling of things has to be done differently to fit each project the best, for an explanation that is far better then i could offer i suggest checking out the differences between the implementation by deank and then by aldostools as its very well explained in our forums by
@bguerville .​

​

Update (2/2/17) v1.46.01 v1.46.00 Additional Info. / Support

• 
  Update (2/2/17) webMAN MOD 1.46.01
  
  • FTP Server uses again the same algorithm on all editions.
    In 1.46.00, the FTP Server in full edition was based on the original webMAN due initial issues with NTFS library. The issue now has been fixed
• 
  webMAN MOD 1.46.00
  
  • Games now are mounted directly from XMB without the webbrowser_plugin
  Thanks to deank for the new XMB proxy included in webMAN 1.46
  
  • Re-structured the project : Moved all the sub-projects to _ Projects _ folder
  
  via Aldostols
  

  I have updated wm_proxy, which now is 40% smaller only 2968 bytes.
  SRC: https://github.com/aldostools/webMAN-MOD/tree/master/_Projects_/wm_proxy
  
  In my tests I had issues opening the Internet Search option (found under Network.menu of XMB). So in wMM 1.46.00, I used idle_plugin, instead of kensaku_plugin or xai_plugin (which is already used by CFW Settings menu). According to psdevwiki, this idle_plugin doesn't have subs in the interfaces, so I guess it is safe to remap it.
  
  I also omitted the mapping of .rco, because it's redundant (there is one file in dev_flash). This saves a few extra bytes in code.

  
  
  Spoiler: previous update

  webMAN MOD 1.45.11
  

  • Added direct NTFS support to 'Full Edition'
  • Thanks to deank, freddy38510, bguerville, Zar, Joonie, Estwald.
    
    • Added support for auto-mount game when an USB drive is connected
      • 'Check for AUTOBOOT.ISO on startup' must be checked
      • The USB drives to be checked are the ones selected in /setup.ps3 (except /dev_ntfs)
      • The game must be named AUTOMOUNT.ISO or a JB game copied to the root of the drive
    • Added /minver.ps3
• 
  
  
  • webMAN MOD Forum

Download: via Release Page

Source(s): github.com/aldostools/ / psx-place.com​

 

ok ill wait thanks for all your work aldo and deank of course

 

I believe there is something wrong with the very first 1.47.00 test pkg because when I install the full edition, the xmb freezes automatically when the games column loads, everything is down, both the http & ftp servers, I had no external hdd plugged in during these tests.
Back to 1.46.02 & the games column loads fine again, no freezes & no server down.

Please try again with the latest test build of 1.47.00 (should be more stable & faster in some cases):
http://www.mediafire.com/file/72x0jq27jdehu81/webMAN_MOD_1.47.00_Updater.pkg
http://www.mediafire.com/file/9oxhxw18rj5c4mv/webMAN_MOD_1.47.00_Updater_metalification_theme.pkg

Changelog:
https://github.com/aldostools/webMAN-MOD/commits/master

PS. Thanks again to deank

EDIT: Uploaded a new build with fixed size of the stack buffer for the threads: poll_thread and update_xml_thread.

The combos SELECT+L3, SELECT+R1 and SELECT+L1 should work again.

 

The stack sizes in webMAN are optimized for its functions, hence smaller values work. wMM needs higher values, but have in mind that you can use sizes of *16KB (0x1000) and not necessarily big 128KB chunks if not needed.

Sent from my Lenovo P1a42 using Tapatalk

 

@aldostools: Just a tip for launching ROMS with PKGLAUNCH - you can always map /app_home to the same path and execute explorer_plugin's commands:

close_all_list, focus_category game, focus_segment_index seg_gamedebug, exec_push

It will work on FWs where app_home is still present of course. It should take a second or two and the rom will be loaded in the emulator without the need to wait for the automounter and the game disc to appear on the XMB.

 

@aldostools I tested the latest build knows how to shortcut SELECT + L3 NOT working properly (scans but no games) - Choose SELECT + R1 + L1 working properly

EDIT:
@aldostools sorry Is worked :P

@deank I have a request if you could see slaunch in terms of screen 720p because the display cover and the lower menu as if it were a higher screen resolution

 

The stack sizes in webMAN are optimized for its functions, hence smaller values work. wMM needs higher values, but have in mind that you can use sizes of *16KB (0x1000) and not necessarily big 128KB chunks if not needed.

Thank you for the tip I tried 16K & 96K respectively but the plugin was still crashing with these values due the recent additions increased the memory requirement in the stack. 32K & 128K seem to be the minimal values.

@aldostools: Just a tip for launching ROMS with PKGLAUNCH - you can always map /app_home to the same path and execute explorer_plugin's commands:

close_all_list, focus_category game, focus_segment_index seg_gamedebug, exec_push

It will work on FWs where app_home is still present of course. It should take a second or two and the rom will be loaded in the emulator without the need to wait for the automounter and the game disc to appear on the XMB.

Great idea!

EDIT: I just tested it and now I remember that I already tried implementing the ROMS using app_home, but I had issues starting some emulators. Some also require to map /app_home/USRDIR, but even adding that mapping some emulators still fail at launch.

I think that an alternative could be to make that the "PKG/ROMS Launcher" install into Network column. The idea of the Network column is because the icons in that column cannot be collapsed into folders like in Game column, which would be more difficult to focus the icon.

 

@maniek6666 The problem is your TV overscan setting. You're way over the 10% of maximum overscan for most TV sets. Check you tv settings and depending on your model you should disable "overscan", "16:9 scan", "fit to screen" or anything that messes up with the display resolution. Just make sure that you tv outputs true 1280x720 and is not in some zoomed in mode.

I just noticed that you're using a pc monitor, so check its settings and disable any overscan/zoom you may have enabled.

It is a total waste of pixels, causes blurred images - I really have no idea why people use overscan modes. 1:1 pixel representation on modern Plasma/LCD/LED TVs provides crisper and much better picture.

Looking at your screen it seems you're losing about 200 pixels horizontaly, which is almost 16% lost from 1280 pixels.

 

@aldostools - No, don't start the emulators from the app_home - just start your wm_url_launcher the way it works at the moment (the difference is that now you can start it directly and not make the user wait for the game-disc-icon).

 

Hi Aldo, I accidently press L1 when launch a game from Webman Mod. Suddenly, it shows that cfw syscall disabled and history deleted. As a result I cannot unmount the game as well as launch a new game. After I restart my ps3, I can launch a new game but the same message.shows, therefore my cfw is disabled again..

I already try to disable the webman Mod and enable it again but the problem remains.

So, how can I overcome this problem. thanks in advance

 

Hi Aldo, I accidently press L1 when launch a game from webman MOd. Suddenly, it shows that cfw syscall disabled and history deleted. As a result I cannot unmount the game as well as launch a new game. After I restart my ps3, I can launch a new game but the same message.shows.

I already try to disable the webman Mod and enable it again but the problem remains.

So, how I can overcome this problem. thanks in advance

Unless you have created a custom combo for select_l1, the syscalls are disabled with R2+TRIANGLE or with an option that disables the syscall at start up.

Check your settings in /setup.ps3 or delete /dev_hdd0/tmp/wm_config.bin and restart the console to reset the settings to their default values.

Now, when the syscalls are disabled, the syscall8 is removed too. If you want to keep the syscall 8 continue working (as in earlier versions) go to /setup.ps3 and set "PS3MAPI" to ENABLED in the combo box next to R2+TRIANGLE.

 

Wow, thanks for the very fast reply Aldo. I also confused why pressing L1 caused cfw syscall disabled.

So what I have to do is delete /dev_hdd0/tmp/wm_config.bin in order to make cfw syscall enable.
Fyi, I do not plan to disable cfw syscall again since my ps3 is already been banned

 

Wow, thanks for the very fast reply Aldo. I also confused why pressing L1 caused cfw syscall disabled.

So what I have to do is delete /dev_hdd0/tmp/wm_config.bin in order to make cfw syscall enable.
Fyi, I do not plan to disable cfw syscall again since my ps3 is already been banned

You can disable the combo R2+TRIANGLE in /setup.ps3 or if you prefer, you can compile your own custom version with REMOVE_SYSCALLS flag commented out.

 

Wow, thanks for the very fast reply Aldo. I also confused why pressing L1 caused cfw syscall disabled.

So what I have to do is delete /dev_hdd0/tmp/wm_config.bin in order to make cfw syscall enable.
Fyi, I do not plan to disable cfw syscall again since my ps3 is already been banned

L1 alone? Very strange...
The L1 button on its own cannot disable syscalls unless it is part of a custom combo that was created to do so.
FYI the custom combos are defined in the /dev_hdd0/tmp/wm_combo folder. They can be deleted manually.

It's very easy to delete the wm_config.bin configuration file, just use the link to do so in the webMAN-MOD setup page, the "delete wmconfig" link is in the plugin memory usage section.
Just click on the wmconfig link & reboot.
Of course you will need to reconfigure wMM setup because afterwards, all settings will be set back to default including the fan settings.

In any case, settings related to syscalls should not be used in wMM for regular use, stick to psnpatch for this kind of things, it's made for that.

Remember that at the bottom of the wMM setup page you can disable the combos. You could try disabling the syscalls combo, save & reboot...

As to your console being banned, it's easy enough to acquire another set of ids to spoof. A ylod console only costs 10 bucks!

 

please please if someone reads this help meee

running dex 4.81.2
psn patch 2017.2b

updated to webman modz 1.46.2

now when i load games from my hdd the games dont work and it askes me to reset the ps3 ive pressed refresh xml everything still dont work whats going on ????

someone must know please

 

Thanks for the help guys. I already deleted the wm_config.bin via file manager in mmCM. And everything back to normal. I also notice later on that in wenman Mod /setup has the feature to delete it.

 

I have uploaded a new test build of wMM 1.47.00
http://www.mediafire.com/file/72x0jq27jdehu81/webMAN_MOD_1.47.00_Updater.pkg
http://www.mediafire.com/file/9oxhxw18rj5c4mv/webMAN_MOD_1.47.00_Updater_metalification_theme.pkg
http://www.mediafire.com/file/5ov4u5bblhlve2e/webMAN_MOD_1.47.00_Updater_rebugification_theme.pkg

Changes/SRC: https://github.com/aldostools/webMAN-MOD/commit/5fa85e4a6712a8c96633eaddb6ce0bb4aa4c6980

Please report any issue with this build here or on github...

NOTE: If the new memory allocation from the application memory container cause freezes, try disabling the new option "3072KB [MC]" on /setup.ps3

 

@aldostools

Is PS3XPAD incoporated/integrated in wMM or is that something that @OsirisX configured as an alternative installation choice ?

 

@aldostools

Is PS3XPAD incoporated/integrated in wMM or is that something that @OsirisX configured as an alternative installation choice ?

Nothing to do with wMM.
Look at our resources section.. All the information is available there...
http://www.psx-place.com/resources/ps3xpad.22/

 

Nothing to do with wMM.
Look at our resources section.. All the information is available there...
http://www.psx-place.com/resources/ps3xpad.22/

Appreciate the link, but I'm familiar with it. My main concern while I was reading through the info, particullary Version 0.5, I noticed @OsirisX compiled his own wMM for it. Wasn't sure if it was seperate or has been added.

 

It's completely separate...