webMAN Classics Maker

PS3 webMan Classics Maker: Launch ISOs straight from XMB 3.0.0-beta3

jacobsson

Senior Member
webMAN Classics Maker
...More videos here
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

AHBXvnK.png
Written in python for multi-platform support

Why this over a regular PS2 Classic?
  • PS2 compatibility: Prioritizes hardware over software emu when possible (PS2_EMU > PS2_GXEMU > PS2_NETEMU)
  • One-press-play: Starts yours ISO directly from the XMB in one button press
  • Organize ISOs on the XMB: Looks exactly like installed titles on the XMB
  • PS2 USB-peripherals on BC models: Buzzers, Lightguns, Singstar mics, Guitar Hero guitars
  • Works with all platforms (PSP/PSX/PS2/PS3)
  • (HEN users should use PS2 Classic)
  • Works with ISOs on USB
How to use
  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 ans wait (be patient)
  8. Choose a game in the list, all info will be filled in automatically
  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
PS3 ISO and Title Ids [READ ME]
Many PS3 games have game updates that installs to your HDD.
To avoid these updates to overwriting your game launcher title-ids are now installed with a W prefix instead: e.g. BLUS12345 will be installed as WLUS12345.
Troubleshooting
  • My PS3 gives me tripple beeps when running my game launcher:
This means the package itself has been built correctly, but the path or the iso filename is not correct, triple check it!​
  • My game launcher is suddenly gone from the XMB:
    You probably installed an PS3 game update which overwrote your game launcher. Use a different title_id when making the PS3 webman PKG, e.g. your PS3 game title_id = SLUS12345, then use WLUS12345 in classics maker (W for webman, easy to distinguish from real installments)

Future development
  • [DONE] Fetch images from ISO files over FTP
  • [DONE] New all-in-one graphical interface
  • [DONE] Build the pkgcrypt module for Python 3.x
  • [DONE] Python 3 port
  • [HELP NEEDED]I have some graphical art ideas that is above my skill level, contact me if you can help :)
  • [DONE] Custom webcommands
  • [TODO] Game meta-data scraper (need to organize the xml's)
  • [ONGOING] Embedded image cropping tool for pkg art
  • [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

Not tested yet

  • Running ISOs from network path
Special thanks to flatz naehrwert @aldostools @kozarovv @pinky @STLcardsWS @sandungas @psykosis



LEGACY METHOD (NO GUI)
Pre-requisites: Downloads
    • Install Python 2.7.15 (32bit/x86 version), add it to your environment variables
    • Install a hex editor, preferably HxD
Project setup: Files & structure
    • 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
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
U4cHMBU.png

2. EDIT PARAM.SFO
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
mXfV2Gl.png

3. EDIT launch.txt
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
q2c4eer.png

4. RESIGN EBOOT.BIN
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
    D2nsHt1.png

  5. In resigner.exe choose "3. Resign to NPDRM EBOOT" and it gives you a new EBOOT.BIN
    gDvAvS5.png
  6. Replace your old EBOOT.BIN in the PKG folder with the new one

5. RUN CREATE_PKG.bat
DONE

Don't forget to leave a like :encouragement:
 
Last edited:
@aldostools
Hi Aldo,I'm currently in the works of building a easy to use Webman Classics PKG-maker tool (might be a cool addition for your toolbox), it's come a long way, but depends it heavily depends on sending key strokes to flatz toolbox TrueAncestor resigner.exe (v 1.98).

My question is this: Do you know what tools (and parameters) are used/automated when choosing: 3, followed by A and "content-id" like the image below? Really really appreciate your help!
gDvAvS5.png
 
My question is this: Do you know what tools (and parameters) are used/automated when choosing: 3, followed by A and "content-id" like the image below? Really really appreciate your help!

You could try using a batch file that execute naehrwert's scetool to decrypt the EBOOT and resign it with the new content ID passed as parameter of the batch file.

In my ps3 tools collection there are some batch files in the folder "scetool" that you could check to use as base for your script.

Indeed you could improve the script automating the other steps too...
 
You could try using a batch file that execute naehrwert's scetool to decrypt the EBOOT and resign it with the new content ID passed as parameter of the batch file.

In my ps3 tools collection there are some batch files in the folder "scetool" that you could check to use as base for your script.

Indeed you could improve the script automating the other steps too...

You're the man! I'll check em out right away and come back to you, hopefully with a functional tool.
 
@aldostools
I solved the last piece with help of your last post, brilliant!

I'd love to hear your thoughts on the new tool "webman classics maker" that I uploaded in the first post. I also need to know if you're OK with me making a github repo for it including your param_sfo_editor?

@complexusername
There is now a tool in the first post for every ones convenience, all feedback is welcome.
 
Last edited:
Hi buddy.
Did you manage to solve your problem?

If not:
1. Are you using the latest WebMAN Classics Maker from github?
2. What are the symtoms, black screen, triple beeps?

Firstly, thanks for reply me
well:
1. I used webMAN Classics Maker v1.1.3 from this link: https://github.com/Roet-Ivar/Webman-Classics-Maker/releases/
2. the symptom is triple beeps. And I don't know why it happens, because only I put the TITLE, the Title ID and the FILE_PATH (/dev_hdd0/PS2ISO/crash.iso) in Edit_Param_SFO.exe. And next, I started Build_Webman_PKG.exe and I installed the pkg made, but when I started it on my PS3, the Iso didn't load and sounded triple beeps
Can you help me please? I don't know what I did wrong.
 
@ManuelHD1980

No worries my friend!
Triple beeps indicates that the filepath is faulty (remember that it's case sensitive and watch out for any hidden spaces).

However, you could get your ISO game list with exact paths using the FTP_Game_List.exe, it will generate a text file which you can copy from.

Let me know if it helps.
 
@ManuelHD1980

No worries my friend!
Triple beeps indicates that the filepath is faulty (remember that it's case sensitive and watch out for any hidden spaces).

However, you could get your ISO game list with exact paths using the FTP_Game_List.exe, it will generate a text file which you can copy from.

Let me know if it helps.

I have to say that I used FTP_Game_List.exe to get the path.
Sin título.jpg
 
@ManuelHD1980
OK. Interesting!
Your path should be good, but I highly recommend using notepad++ instead for correct formatting of the game list.

Have you tested another ISO than the "crash.iso" mentioned above?
If not, please try another game ISO (w/o any config files) and see if you end up with the same result.
 
Last edited:

Similar threads

Back
Top