LaunchElf 3.59 freezes when opened for the second time...

[bootsector]

Hi folks!

I have a skinned LaunchElf 3.59 as my EXPLOIT start point. From there, I can start HDD Explorer, which presents me a menu with a large list of files. I have LaunchElf 3.59 on this list too, so if I want to exit HDD Explorer, all I have to do is select LaunchElf from this list and press X, then it will be re-executed.

The problem is it won't be executed! It just freezes! The strange part is that this method used to work on version 3.51 (which didn't support skins).

I really need this to work on LaunchElf 3.59. Any clues what can be wrong?

Hope to get some help soon!

Regards,

bootsector

[Jones23]

@ bootsector:

Read this thread to see the problems with the exit function and compatibilities between different homebrew apps. Start with post #560 by dlanor and read the following correspondation between dlanor and EEUG.
Try LaunchELF v3.60, maybe it works with that.

regards Jones23

[bootsector]

LE 3.60 didn't work as well It's complicated to put dlanor's new launcher on HDD Explorer, because it's not open source

@ bootsector:

Read this thread to see the problems with the exit function and compatibilities between different homebrew apps. Start with post #560 by dlanor and read the following correspondation between dlanor and EEUG.
Try LaunchELF v3.60, maybe it works with that.

regards Jones23

[dlanor]

LE 3.60 didn't work as well It's complicated to put dlanor's new launcher on HDD Explorer, because it's not open source

There could be other problems too. Are you sure that you have properly enabled IOP reset in LAUNCHELF.CNF ?

Lack of IOP reset is a common cause for problems when there is a conflict between IRX modules needed by a program and those needed by a second program launched by the first one. The second program must then use IOP reset to clean out old modules, and in uLaunchELF there's a configurable option for this (in "STARTUP SETTINGS" submenu).

The reason why IOP reset is just an option, and not a mandatory action, is that sometimes it is necessary to keep the IRX modules that were active before uLaunchELF was started. One such case is when using PS2Link (or similar) to start uLaunchELF for debugging purposes.

Best regards: dlanor

[bootsector]

Yes, it's enabled:

Init_Reset_IOP = 1

The weird part is that it works with LE 3.51

There could be other problems too. Are you sure that you have properly enabled IOP reset in LAUNCHELF.CNF ?

Lack of IOP reset is a common cause for problems when there is a conflict between IRX modules needed by a program and those needed by a second program launched by the first one. The second program must then use IOP reset to clean out old modules, and in uLaunchELF there's a configurable option for this (in "STARTUP SETTINGS" submenu).

The reason why IOP reset is just an option, and not a mandatory action, is that sometimes it is necessary to keep the IRX modules that were active before uLaunchELF was started. One such case is when using PS2Link (or similar) to start uLaunchELF for debugging purposes.

Best regards: dlanor

[E P]

Yes, it's enabled:

Init_Reset_IOP = 1

The weird part is that it works with LE 3.51

Yeah, I've discussed this before many times. It's simply "hit and miss" with loaders in that sometimes it works and sometimes it does not. Take ps2mp3 for example, its "exit to BOOT.ELF" works sometimes but varies from LaunchELF release to release. Oh and it's not just a launchELF issue as the loader that executes LaunchELF may have an issue with it's own loader or even just an issue with the compressed ELF binary in general. That is why we have always made two releases: the original binary and the compressed binary made with PS2-Packer version 1.0rc2.

I would like to see the issue truely fixed. Many people are aware of it but no one really understands what is going wrong. I believe that it cannot be fixed on just one side of the equation though. In other words, if launchELF is part of the problem it alone isn't the sole cause of the problem. All programs will need to be changed in order to really resolve this issue. BTW: It's usually programs that use a generic loader function that have the most problems with getting launchELF to startup.

Edit: Just tried the "exit to BOOT.ELF" function with the following: ps2mp3, mcformat, SMS, KaylaKaze infoGB, and KaylaKaze infoNES. The function works fine in all of those noted programs with uLaunchELF v3.60.