wLaunchELF 4.43x_ISR

PS2 wLaunchELF 4.43x_ISR Rev 234 - mmce

Go to download
Overview Extra info Updates (20) Reviews (9) History Discussion
Mr.Ash said:
Unfortunately, I have to say at this point that the current version of wLaunchELF 4.43x_isr is nerly completely unusable.

Although exFAT and MX4SIO are supported, the program runs anything but smoothly.
Click to expand...
Not wLE ISR fault

Mr.Ash said:
- Memory cards in slot 2 (mc1) are not recognized
Click to expand...

MX4SIO driver interceps any incomming/outcomming information for mc1:/ that the SIO2MAN recieves in order to work, making it impossible to access normal cards on that slot AFTER the MX4SIO driver is up and running

Mr.Ash said:
- After a certain time, the program always goes into "auto fire" mode, in which keystrokes are suddenly executed several times (making navigation impossible)
Click to expand...
A problem of the DS34 (Dualshock 3/4) feature that we havent been able to solve, that is why this is an optional feature. only clue we have is that PAL systems are prone to this more than NTSC....

Mr.Ash said:
- MX4SIO adapters are only recognized if you plug them in and out several times (funnily enough, this also works in memory card slot 2)
Click to expand...
MX4SIO driver issue, OPL Users complain of a similar thing (having to reinsert MX4SIO driver after IGR else it doesnt get detected again) my guess is that MX4SIO is somehow leaving messed up SIO2 Register values or something like that,,,,

anyways, your comment reminded me I had this in my to-do list
 
Last edited:
Thank you for your answers.

But what I still can't really understand is, if the problems described are known, why is this not mentioned anywhere? A simple readme with the known limitations would suffice and eliminate many complaints and questions.

In particular, the fact that you can't actually swap files between two real memory cards is a huge limitation for me. Of course I could copy the data from the first MC to the MX4SIO, then swap the MC and then copy from MX4SIO to the new MC. But this is rather cumbersome and takes twice as long.

In any case, it is clear to me that I will no longer use wLaunchELF 4.43x_isr. The few additional features such as exFAT and MX4SIO are virtually nullified by other limitations and bugs.
 
Mr.Ash said:
Thank you for your answers.

But what I still can't really understand is, if the problems described are known, why is this not mentioned anywhere? A simple readme with the known limitations would suffice and eliminate many complaints and questions.

In particular, the fact that you can't actually swap files between two real memory cards is a huge limitation for me. Of course I could copy the data from the first MC to the MX4SIO, then swap the MC and then copy from MX4SIO to the new MC. But this is rather cumbersome and takes twice as long.

In any case, it is clear to me that I will no longer use wLaunchELF 4.43x_isr. The few additional features such as exFAT and MX4SIO are virtually nullified by other limitations and bugs.
Click to expand...
just use a version without MX4SIO nor DS3/4 and stop complaining
 
El_isra said:
just use a version without MX4SIO nor DS3/4 and stop complaining
Click to expand...

This should be a constructive criticism in order to eliminate the shortcomings mentioned in the future.

I actually assumed that developers of software (whether free or not) take a certain pride in their products. That's why I can't really understand why criticism is only seen as stupid complaining and you should shut up if you don't like it...
 
Mr.Ash said:
This should be a constructive criticism in order to eliminate the shortcomings mentioned in the future.

I actually assumed that developers of software (whether free or not) take a certain pride in their products. That's why I can't really understand why criticism is only seen as stupid complaining and you should shut up if you don't like it...
Click to expand...
well, if you say my most successfull contribution to the scene "is nerly completely unusable." because of already known bugs comming from external drivers related to OPTIONAL features I wont be happy about it.

simply dont call a whole program "nerly completely unusable." because an external driver has an issue that cant be easily dealt with
 
El_isra updated wLaunchELF 4.43x_ISR with a new update entry:

FreeDVDBoot support and other tweaks

  • allow secondary search path for ps2smap.irx
  • supress IRX compilation commands if not debugging
  • add ioptrap.irx build option for debugging
  • Add debugging via PowerPC UART
  • Hide mc1:/ if MX4SIO driver loaded successfully
  • replace all `ďż˝` with `\xff`
  • update cdfs.irx to support browsing FreeDVDBoot disc images (or any DVD Movie)
  • rename libcdvd helper macros to avoid name crash with RPCs
Click to expand...

Read the rest of this update entry...
 
Big fan!
I have a suggestion, my dumbass posted it on the wrong github repo and then I didn't want to spam your github with a duplciate - so I come here to post my suggestion/request/wish :D

Would be super useful to be able to "create .psu" and "extract .psu" anywhere on any device.
Currently I would have to psuPaste to the MC to extract the contents of a .psu, and it would be a huge improvement to have more freedom with these functions.
 
Ripto said:
Big fan!
I have a suggestion, my dumbass posted it on the wrong github repo and then I didn't want to spam your github with a duplciate - so I come here to post my suggestion/request/wish :D

Would be super useful to be able to "create .psu" and "extract .psu" anywhere on any device.
Currently I would have to psuPaste to the MC to extract the contents of a .psu, and it would be a huge improvement to have more freedom with these functions.
Click to expand...
that would require significant changes on the code base since the create PSU features are directly pulling the MCFS attributes via MCSERV.
 
El_isra said:
wLaunchELF 4.43x_ISR
Click to expand...

Hi.
I have a problem with the latest build downloaded (even today)
from here: https://israpps.github.io/projects/wlaunchelf-isr.
down.png


Once I open the Text Editor (MISC/TextEditor).
Open any file on a memory card (e.g. mc0:/Neutrino/nhddl.yaml).
Close it.
I cannot enter a memory card anymore through browser (e.g. mc:0/).
It just shows a content of a memory card for a second and it back to the "main" scrren.
Something like this:
def.png


I have also tried a version with or without MX4SIO.
 
jolek said:
Hi.
I have a problem with the latest build downloaded (even today)
from here: https://israpps.github.io/projects/wlaunchelf-isr.
down.png


Once I open the Text Editor (MISC/TextEditor).
Open any file on a memory card (e.g. mc0:/Neutrino/nhddl.yaml).
Close it.
I cannot enter a memory card anymore through browser (e.g. mc:0/).
It just shows a content of a memory card for a second and it back to the "main" scrren.
Something like this:
def.png


I have also tried a version with or without MX4SIO.
Click to expand...
The DS34 feature is to blame there
 
El_isra said:
The DS34 feature is to blame there
Click to expand...

Yea.
You are right.
I re-downloaded a version without DS34 support and everything is ok.

Are you planing to add some kind of a fix\patch?

BTW I forgot to mention that I even did not use DS3 or DS4 gamepad.
Only DS2.
It was was just for future...
 
jolek said:
Yea.
You are right.
I re-downloaded a version without DS34 support and everything is ok.

Are you planing to add some kind of a fix\patch?

BTW I forgot to mention that I even did not use DS3 or DS4 gamepad.
Only DS2.
It was was just for future...
Click to expand...
Yes. The DS34 Feature not only adds the IRX drivers to read the DS34/DS4

It also adds a custom version of the RPC handling on the EE so it checks both DS2 and DS34 at the same time.

It must be some timing issue or something similar
 
The github mentions
>Support for accessing EXFAT filesystems from BDM devices (USB & MX4SIO)
Is HDD not possible?
 
You must log in or register to reply here.

Similar threads

Back
Top