wLaunchELF 4.43x_ISR

PS2 wLaunchELF 4.43x_ISR Rev 234 - mmce

Still great. Especially to someone who direct booting to OPL/uLE avoiding OSDSYS/HDD OSD.

BTW: I'm not sure if this is good place for that question but why did You split project into "ISR" and "ISR HDD"?

Isr_hdd uses a newer toolchain (v1.2.0), and since it is based on newer uLaunchELF commit it has more issues with file management

One of the points of isr is maintaining stability. For that it needs toolchain V1.0
 
THX for the implementation @alexparrado!

Do you have time to look at the SMB-implementation? I think that would be useful for users!

I also think that your and @El_isra's stuff (maybe not all) should be merged into the official wLE-repo!
 
This support for DS3 and DS4 controllers works via USB and BT or only via USB?
If also via BT is there any additional options to pair a controller?
It works through BT with previously paired controller in OPL. Some users have reported it.

There is no pairing functionality so far, anyway once I have the time, I think to add such feature.

THX for the implementation @alexparrado!

Do you have time to look at the SMB-implementation? I think that would be useful for users!

I also think that your and @El_isra's stuff (maybe not all) should be merged into the official wLE-repo!

It's my pleasure, I want to add pairing feature once I have the time. SMB, maybe later, my job is highly demanding these days.
 
Last edited by a moderator:
Why so may versions?
BOOT-DS34.ELF
BOOT-DS34-NO_NETWORK.ELF
BOOT-DS34-NO_NETWORK-SIO_DEBUG.ELF
BOOT-DS34-NO_NETWORK-XFROM.ELF
BOOT-DS34-NO_NETWORK-XFROM-SIO_DEBUG.ELF
BOOT-DS34-SIO_DEBUG.ELF
BOOT-DS34-XFROM.ELF
BOOT-DS34-XFROM-SIO_DEBUG.ELF
BOOT.ELF
BOOT-EXFAT-DS34.ELF
BOOT-EXFAT-DS34-NO_NETWORK.ELF
BOOT-EXFAT-DS34-NO_NETWORK-SIO_DEBUG.ELF
BOOT-EXFAT-DS34-NO_NETWORK-XFROM.ELF
BOOT-EXFAT-DS34-NO_NETWORK-XFROM-SIO_DEBUG.ELF
BOOT-EXFAT-DS34-SIO_DEBUG.ELF
BOOT-EXFAT-DS34-XFROM.ELF
BOOT-EXFAT-DS34-XFROM-SIO_DEBUG.ELF
BOOT-EXFAT.ELF
BOOT-EXFAT-NO_NETWORK.ELF
BOOT-EXFAT-NO_NETWORK-SIO_DEBUG.ELF
BOOT-EXFAT-NO_NETWORK-XFROM.ELF
BOOT-EXFAT-NO_NETWORK-XFROM-SIO_DEBUG.ELF
BOOT-EXFAT-SIO_DEBUG.ELF
BOOT-EXFAT-XFROM.ELF
BOOT-EXFAT-XFROM-SIO_DEBUG.ELF
BOOT-NO_NETWORK.ELF
BOOT-NO_NETWORK-SIO_DEBUG.ELF
BOOT-NO_NETWORK-XFROM.ELF
BOOT-NO_NETWORK-XFROM-SIO_DEBUG.ELF
BOOT-SIO_DEBUG.ELF
BOOT-XFROM.ELF
BOOT-XFROM-SIO_DEBUG.ELF
I'm a bit lost. Does "BOOT.ELF" is all in one version?
 
Why so may versions?

I'm a bit lost. Does "BOOT.ELF" is all in one version?
because most of the extra features are coded with the capability of being disabled/enabled on compilation.

that spawns all possible combos.

upload_2023-1-26_20-45-36.png
 

Is it compatible with chip matrix infinity? I was using "wLaunchELF 41e4ebe (14\01\2019)", since it's the last i know is working with no problems. I suppose there is no problem if i use this wlaunchELF with matrix infinity, there is not?

Ups, sorry, i think it's related to FMCB v1.966. FMCB v1.965 works fine with my chip matrix infinity.

The feature for DS3 support is really very nice since i get problems with ace combat on pressing the accelerator button (so much pression needed with my dualshock).

Thanks.
 
Last edited:
Is it compatible with chip matrix infinity? I was using "wLaunchELF 41e4ebe (14\01\2019)", since it's the last i know is working with no problems.

Thanks.
I haven't heard any complains...
This mod is based on that commit that you use, but with some enhancements and compiled with newer toolchain.
 
I haven't heard any complains...
This mod is based on that commit that you use, but with some enhancements and compiled with newer toolchain.

Thanks.

One thing about the title.cfg: it generates one file per app or it add one app into the already existed "conf_app.cfg" from OPL? Or it's other thing?

I have this on my OPL "conf_apps.cfg":
Code:
uLaunchELF=pfs0:/APPS/Ule_443.ELF
OpenLoader=pfs0:/APPS/BOOT.ELF
Ps2rd_0.5.4_v2=pfs0:/APPS/Ps2rd_0.5.4_v2.ELF
GSM v0.38=pfs0:/APPS/GSM_038.ELF
MC Annihilator=pfs0:/APPS/MCAnnihilator/mca_v20.elf
HDDChecker=pfs0:/APPS/HDDChecker/HDDChecker.elf
PadTest=pfs0:/APPS/PadTest.elf
Free MCBoot Configurator=pfs0:/APPS/FMCB_CFG.ELF



Since Dualshock 3 doesn't works on OSDSYS, the "auto" load is the only way to load OPL or wlaunchELF

Ps: do you remember how to launch directly Opl manager? FreeMCB.CNF >> LK_Auto_E1 = OPL.elf ??
 
Last edited:
El_isra updated wLaunchELF 4.43x_ISR with a new update entry:

MX4SIO support

  • Remove references to DVRP feature
  • Added MX4SIO support (mapped as mass#:/)
  • Disable builds with EE sio from public releases

IMPORTANT NOTE:
To add MX4SIO, the SIO2MAN and PADMAN drivers had to be replaced (wLaunchELF was using console built-in versions of them. Now uses homebrew ones). Therefore, I strongly encourage you to report any issue related to DualShock or memory card

Read the rest of this update entry...
 
Why "mass#:/" instead to i.e "mx4sio:/"? It could be confusing with "mass:/".

So this build don't have support of "hdd_dvr:/" and "xfrom:/"?
 
Why "mass#:/" instead to i.e "mx4sio:/"? It could be confusing with "mass:/".

So this build don't have support of "hdd_dvr:/" and "xfrom:/"?
Because the IRX that maps the new device isn't MX4SIO_BD.IRX, it's BDM.IRX

XFROM support remains, DVR HDD area was actually never supported because it needs a replacement for all the HDD related IRX, Wich I won't do
 
What about adding Firewire (mass)?

If the driver gets updated in the SDK and more devices are supported, it would automatically get the support as well, if it is built automatically (and I think it is).
 

Similar threads

Back
Top