PS3 webMAN Classics Maker v2.0 - GUI Release

PSX-Place's own @jacobsson has put together a wonderful project for all the PS3 users in the scene called webMAN Classics Maker v2.0. This project started out as a tutorial to help users create self-booting XMB webMAN Classics, and has evolved into a GUI program that will do most of the work for you. With this tool, you will be able to create self-booting versions of all of you favorite PSP, PS1, PS2 and PS3 games, which will be able to play from either your HDD or USB (USB not yet tested). There are many reasons for wanting to create your own XMB webMAN Classics, including: better PS2 compatibility, starting your ISOs directly from the XMB, organizing your ISOs on the XMB, and USB device compatibility (lightguns, microphones, etc., etc.). Besides a copy webMAN Classics Maker v2.0 for Windows or Linux, you will also need to latest version of @aldostools webMAN Mod (currently at version 1.47.30). If you need any assistance with this program, click the link at the bottom of this article to be taken directly to @jacobsson's release thread, where you will be able to discuss this release and much more.

Features How to Use PKG Images Future Updates Troubleshooting Not Yet Tested Thank Yous Video Examples Old Guide

• 
  
  • Better PS2 compatibility: it prioritize BC hardware over software (PS2_EMU -> PS2_GXEMU -> PS2_NETEMU)
  • One-press-play: Starts yours ISOs directly from the XMB
  • Organize ISOs on the XMB: Looks exactly like a regular installed title on the XMB
  • USB-peripherals: Buzzers, Lightguns, Singstar, GuitarHero all work (PS2 Classics can't do this)
  • Compatible with all ISOs (PSX/PS2/PS3)
• 
  
  1. Download webman classics maker from github
  2. Download and Install the latest webMan-mod on your PS3 (hold L1 for full installation in second step)
  3. Upload or dump ISO backups of your games to the usual webman folders (PSXISO/PS2ISO etc)
  4. Find your PS3 IP-address (shows up in VHS menu of your PS3)
  5. Run Webman_Classics_Maker
     
  6. Enter the IP-address in the PS3-IP field
  7. Press Fetch to get your game list, be patient
  8. Choose a game in the list, all info will be filled in
  9. [optional] Click and swap any images such as ICON0 and PIC1 to your liking
  10. Press Build to make your new game pkg and install it on your PS3
  11. $Profit
• 
  If you want a nice icon and background image for your package, make sure to replace ICON0.PNG and PIC1.PNG (case-sensitive filenames!) inside the PKG-folder. Use paint.net and look at the file in /resources/images/ICON0.PDN
  
• 
  
  • • [DONE] A New GUI!
    • [HELP NEEDED] Port the project from Py 2.7 to Py 3.7
    • [TODO] Game meta data online scraping
    • [TODO] Image scraping functionality
    • [TODO] Embedded image cropping tool
    • [TODO] Investigate if multi-disc support possible through web commands
    • [DONE] Port the project to x64
      
    • [DONE] Make build scripts for SCETOOL and OSCETOOL (for both linux and win support)
    • [DONE] FTP GAME & ISO list generator
    • [DONE] create github-repo https://github.com/Roet-Ivar/Webman-Classics-Maker
    • [DONE] Remove python dependencies from win binaries
• 
  
  • My PS3 gives tripple beeps:
    This means the package itself has been built correctly, but the path or the iso filename is not correct, triple check it!
    
    
  • My webman game is suddenly gone from the XMB:
    Your PS3 game installed an update which overwrote your webman game folder. Use a different title_id when making the PS3 webman PKG, e.g. your PS3 game title_id = SLUS12345, then use WMUS12345 in classics maker (WM for webman, easy to distinguish)
• 
  
  • Running ISOs from USB
  • Running ISOs from network path
• 
  webMAN classics maker wouldn't exist w/o naehrwert's scetool 0.2.9 / flatz NP local license
  and @aldostools webMan-mod + PARAM.SFO.Editor
  
  Special thanks to flatz naehrwert @aldostools @kozarovv @pinky @STLcardsWS @sandungas @psykosis
• 
  
  ...
  
• 
  
  Pre-requisites: Downloads
  
  Spoiler

  • 
    
    
    • Webman source code (This guide used v1.47.09)
    • PS3 Tools Collection (This guide used v4.8.1)

  
  

  • 
    
    
    • True ancestor (This guide used v1.98)

  
  

  • 
    
    
    • Install Python 2.7.15 (32bit/x86 version), add it to your environment variables

  
  

  • 
    
    
    • Install a hex editor, preferably HxD
  Project setup: Files & structure
  
  Spoiler

  • 
    
    
    • Make a folder called MY_XMB_ISO_SHORTCUTS

  
  

  • 
    
    
    • Extract the folder \_Projects_\wm_url_launcher\ from webMAN-MOD-zip:
      \MY_XMB_ISO_SHORTCUTS\wm_url_launcher\

  
  

  • 
    
    
    • Extract the folder \tools\make_pkgs\bin\ from Aldo Tools.rar:
      \MY_XMB_ISO_SHORTCUTS\wm_url_launcher\bin\

  
  

  • 
    
    
    • Extract \tools\PARAM_SFO_Editor.exe from Aldo Tools.rar:
      \MY_XMB_ISO_SHORTCUTS\PARAM_SFO_Editor.exe
    • Extract all content from TrueAncestor_SELF_Resigner_v1.98.zip:
      \MY_XMB_ISO_SHORTCUTS\true_ancestor\
  
  ---------------------------------------------------------------------------------------------------------------
  LET'S START
  From here I'lll assume you have found good content ID for your package, otherwise look at psxdatacenter.
  For this example let's call it SLUS12345
  
  1. EDIT CREATE_PKG.BAT
  
  Spoiler

  Edit \_XMB_ISO_SHORTCUTS\CREATE_PKG.BAT with a text editor and replace "PKGLAUNCH" on row 15

  set CONTENTID=UP0001-PKGLAUNCH_00-0000000000000000

  with SLUS12345:
  

  set CONTENTID=UP0001-SLUS12345_00-0000000000000000

  
  
  2. EDIT PARAM.SFO
  
  Spoiler

  Edit \_XMB_ISO_SHORTCUTS\wm_url_launcher\pkg\PARAM.SFO using the PARAM_SFO_Editor.exe:
  
  

  Title id = PKGLAUNCH

  TITLE = PKG/ROM Launcher

  
  

  Title id = SLUS12345

  TITLE = Name of the game

  
  
  3. EDIT launch.txt
  
  Spoiler

  Edit \_XMB_ISO_SHORTCUTS\wm_url_launcher\pkg\USRDIR\launch.txt with a text editor and replace

  /dev_hdd0/game/HTSS00003/USRDIR/movian.self

  with

  /play.ps3/dev_hdd0/PS2ISO/nameOfTheGame.iso

  
  4. RESIGN EBOOT.BIN
  
  Spoiler

  Copy \_XMB_ISO_SHORTCUTS\wm_url_launcher\pkg\USRDIR\EBOOT.BIN
  to \MY_XMB_ISO_SHORTCUTS\true
  

  

  
  _ancestor\
  

  
  

  1. Execute resigner.exe
  2. Choose "1. Decrypt EBOOT.BIN Only" => extracts EBOOT.ELF
  3. Open EBOOT.ELF in HxD (or similar hex editor)
  4. Find "PKGLAUNCH" and edit

     0/game/PKGLAUNCH

     to

     0/game/SLUS12345

     , do this on two places
     
     
     
  5. In resigner.exe choose "3. Resign to NPDRM EBOOT" and it gives you a new EBOOT.BIN
     
  6. Replace your old EBOOT.BIN in the PKG folder with the new one
  
  5. RUN CREATE_PKG.bat
  DONE
  
  

DOWNLOAD & PSX-PLACE RELEASE THREAD:
GUIDE: Self-booting XMB Webman Classics​

 

There is no more end-user-centric solution? , I fear that manually replacing system files may cause a brick.

Latest webMAN MOD 1.47.30 already install/swap the psp_emulator if a decrypted MINIS.EDAT is detected. Make sure that you unmount the game before shutdown the console to let webMAN restore the original psp_emulator.

 

Latest webMAN MOD 1.47.30 already install/swap the psp_emulator if a decrypted MINIS.EDAT is detected. Make sure that you unmount the game before shutdown the console to let webMAN restore the original psp_emulator.

Maybe my problem is because I am not using any MINIS.EDAT file
I only have one ISO call:
Monster_Hunter_Portable_3rd_HD_ENG.iso
with an MD5: 44761df383bd7e23c43911da0d82020a

 

Does it work on HEN 3.0.1?

 

nice, ill wait for that Scraping feature to work before I use this tool, its way too hassle to do it on my library (100+games).

 

Maybe my problem is because I am not using any MINIS.EDAT file
I only have one ISO call:
Monster_Hunter_Portable_3rd_HD_ENG.iso
with an MD5: 44761df383bd7e23c43911da0d82020a

This game needs the MINIS.EDAT in the attachment (extract the 2 files in the ZIP)

This is the code in the 2 text files:

VERSION = 0xFFFFFFFF
S3D.ENABLE = 2
SDRAM_SIZE = 02800000
MIPS_CODE_BLOCK_SIZE = 8192

 

Latest webMAN MOD 1.47.30 already install/swap the psp_emulator if a decrypted MINIS.EDAT is detected. Make sure that you unmount the game before shutdown the console to let webMAN restore the original psp_emulator.

What happen if i don't unmount the psp game before shutdown? softbrick or hardbrick?

 

Is the "better ps2 compatibility" referred only to fat and slim models, or also for superslim? (If I understood well, superslim has only ps2 netemu and it wasn't compatible with some games e.g. Need for Speed: Underground 2)

 

Is the "better ps2 compatibility" referred only to fat and slim models, or also for superslim? (If I understood well, superslim has only ps2 netemu and it wasn't compatible with some games e.g. Need for Speed: Underground 2)

early fats (cech-a to e models) have better ps2 compatability. all other phats as well as all slims and supers can only use netemu (ps2classics). search for "ps2 on ps3 compatabilty list" on goggle to find the page on psdevwiki site. some games need config files.

 

Is the "better ps2 compatibility" referred only to fat and slim models, or also for superslim? (If I understood well, superslim has only ps2 netemu and it wasn't compatible with some games e.g. Need for Speed: Underground 2)

I think that sentence refers to the fact that webMAN MOD automatically applies the CONFIG from the PS2CONFIG database (if there isn't one already).

This improves the compatibility of several games.

For HEN, it is recommended to install the PS2CONFIG database which includes the encrypted CONFIG files for PS2 Classics.

The CONFIGs for PS2ISO are installed with webMAN MOD.

 

Yes, i have ver. 1.47.30, that it should be latest one. Mhh do you know a way to readd /app_home/ps3_game?

I mean the latest commit from last night

 

This game needs the MINIS.EDAT in the attachment (extract the 2 files in the ZIP)

This is the code in the 2 text files:

VERSION = 0xFFFFFFFF
S3D.ENABLE = 2
SDRAM_SIZE = 02800000
MIPS_CODE_BLOCK_SIZE = 8192

Thanks again, where should I place these files? Please note that I do not have a CFW, I am a HFW PS3 Super Slim user.

 

Thanks again, where should I place these files? Please note that I do not have a CFW, I am a HFW PS3 Super Slim user.

Only PS2ISO is not supported on HEN due VSH is replaced by ps2_netemu

PSPISO is supported on both HEN / CFW. Just put the 2 decrypted files in the same directory of the ISO in /dev_hdd0/PSPISO

Scan the content & refresh XMB. Select the game and start it with PSP Remaster Launcher.

Make sure that you exit to XMB then unmount the game before turn off the console.
This should restore the original psp_emulator.self. To be sure you can do it manually too.

 

I think that sentence refers to the fact that webMAN MOD automatically applies the CONFIG from the PS2CONFIG database (if there isn't one already).

This improves the compatibility of several games.

For HEN, it is recommended to install the PS2CONFIG database which includes the encrypted CONFIG files for PS2 Classics.

The CONFIGs for PS2ISO are installed with webMAN MOD.

Thanks, but does this mean that is the same thing of converting the iso in pkg via the ps2Classics placeholder gui? I mean at least in terms of compatibility with the superslim that only has the netemu.

 

Thanks, but does this mean that is the same thing of converting the iso in pkg via the ps2Classics placeholder gui? I mean at least in terms of compatibility with the superslim that only has the netemu.

Yes, the compatibility is the same using PS2ISO or PS2 Classics. The CONFIG files for ISO is a feature that @habib added to Cobra 8.1. Read the Note 2 below. However, the PS2ISO is only supported on CFW. HEN users still require to use encrypted images .BIN.ENC + PS2 Classics Launcher (aka placeholder). The reason of this is that VSH / LV2 kernel is replaced by ps2_netemu when it's loaded, resulting in a lost of the PS3HEN payload.

COBRA 8.1 PS2 Features (4.84 Cobra)

PlayStation 2 on NON-BC Consoles

Software (SW) Emulation:Support for PS2 ISOs in non BC consoles was removed in Cobra 4.30 (usb), due tops2_softemu missing. It has been re-enabled now by hacking of ps2_netemu. You can use it in the same way as before, just load an ISO and launch from disc icon, Cobra core takes care of rest. No need for encrypted isos, isos patched with limg sectors, etc. Just your normal PS2 isos dumped from discs. However, there is NO SUPPORT for Optical Discs in PS2_NETEMU. Note 1: Don't forget to set the memory cards in XMB, in the old memory card utility for PS/PS2, as ps2_netemu won't let you assign them in game as long as you use the new ps2 launcher. Note 2: Decrypted Config can now be used , place the CONFIG file in the same game path. An example below : dev_hdd0/PS2ISO/God of WAR2.ISO dev_hdd0/PS2ISO/God of WAR2.ISO.CONFIG

Decrypted CONFIG files are available via PSDEVWIKI [or here]

PlayStation 2 on BC and Semi-BC ConsolesHardware (HW) Emulation:
PS3 Models: CECHA, CECHB, CECHC and CECHE Backwards Compatible (BC) Consoles will still use their respetive emulators(ps2_emu, ps2_gxemu), which have much better compatibility and also support optical discs, original or backup.

 

Only PS2ISO is not supported on HEN due VSH is replaced by ps2_netemu

PSPISO is supported on both HEN / CFW. Just put the 2 decrypted files in the same directory of the ISO in /dev_hdd0/PSPISO [...]

I tried to do what you said, but I got the same result. The next thing I will do is reinstall the HFW to delete HAN and webMAN, and I will reinstall both things to see if I can finally run the game in ISO format. The funny thing is that it works if I convert the ISO to PKG and then install it, but then I have the problem that in a certain area the game gets stuck in a loading screen. It seems that people who run the ISO directly without converting it do not suffer from this problem, although all of them are only CFW users so far.

 

I tried to do what you said, but I got the same result. The next thing I will do is reinstall the HFW to delete HAN and webMAN, and I will reinstall both things to see if I can finally run the game in ISO format. The funny thing is that it works if I convert the ISO to PKG and then install it, but then I have the problem that in a certain area the game gets stuck in a loading screen. It seems that people who run the ISO directly without converting it do not suffer from this problem, although all of them are only CFW users so far.

I understand... I cannot help more than what I have done... I'm on CFW too.

 

I just wanted to announce to all of you that still run a windows 32-bit machine that I released a separate built version using a VM for you: https://github.com/Roet-Ivar/Webman...r_v2.0.2/webman_classics_maker_v2.0.2_win.zip

 

I just would like to confirm the process of this... so you would need to :


Have latest webman installed
transfer the iso from your pc to ps3
then with this, the iso transfers from ps3 back to the pc?
then once its a pkg, then transfer it back to ps3?

is that correct? and if that is correct, will there be a version of this
that does NOT require webman and connecting to the ps3? where
everything is done on the pc with your iso.

And if those steps above are correct, what is/are the key benefit/s of using this as opposed to just making the iso into a pkg on your pc using one of the classics managers and/or other tools, where you can even remove dummy files, install cheats in the iso (like with ps2), webman is not needed and the file only needs to be transferred once...right into the ps3 instead of 3 times back and forth? (if i'm understanding how this works correctly)

Just curious to see if I'd be doing a tutorial on it and all the questions I just asked ... I'm sure are going to be asked in the comments and on discord...etc
thanks

 

I just would like to confirm the process of this... so you would need to :


Have latest webman installed
transfer the iso from your pc to ps3
then with this, the iso transfers from ps3 back to the pc?
then once its a pkg, then transfer it back to ps3?

is that correct? and if that is correct, will there be a version of this
that does NOT require webman and connecting to the ps3? where
everything is done on the pc with your iso.

And if those steps above are correct, what is/are the key benefit/s of using this as opposed to just making the iso into a pkg on your pc using one of the classics managers and/or other tools, where you can even remove dummy files, install cheats in the iso (like with ps2), webman is not needed and the file only needs to be transferred once...right into the ps3 instead of 3 times back and forth? (if i'm understanding how this works correctly)

Just curious to see if I'd be doing a tutorial on it and all the questions I just asked ... I'm sure are going to be asked in the comments and on discord...etc
thanks

Hi man, watch your channel, good stuff! (if it's you).
Yes webman mod installed. You only need to upload your iso's to the PS3, my ftp implementation fetches a little snipped of each iso just enough to get some info of what title id is in the ISO. Then webman Classics Maker looks it up against a local DB to get the full name etc. to enrich the eboot of the pkg.

There are more nice stuff coming, but hey I totally understand it's niche so it's not for everybody.

 

Hi man, watch your channel, good stuff! (if it's you).
Yes webman mod installed. You only need to upload your iso's to the PS3, my ftp implementation fetches a little snipped of each iso just enough to get some info of what title id is in the ISO. Then webman Classics Maker looks it up against a local DB to get the full name etc. to enrich the eboot of the pkg.

There are more nice stuff coming, but hey I totally understand it's niche so it's not for everybody.

yes thats me and thanks!
Ok I get it... so it doesn't extract the entire game from the ps3?
so is it basically making like a forwarder for the game? When you
install the pkg, you are not installing the whole game back into the
ps3? You're basically creating like a shortcut to the game but via
an xmb icon?