LaunchELF Config Explanation

[HypERSoniC]

Here is how LAUNCHELF.CNF is comprised if anyone is interested:

Default (path)
Circle (path)
Cross (path)
Square (path)
Triangle (path)
L1 (path)
R1 (path)
L2 (path)
R2 (path)
L3 (path)
R3 (path)
START (path)
TImeout (INT)
Print Screen Name Only (0/1)
Colour 1
Colour 2
Colour 3
Colour 4
Screen X (INT)
Screen Y (INT)
Disc Control(0/1)

[dlanor]

Using multiple config files for extended LaunchELF menus:

LaunchELF was made to be compatible with most other PS2 homebrews, and for this reason it is able to accept being launched in various manners itself, and can search for its config file differently according to its launch method. I use this to extend the menu choices of LaunchELF by linking 3 different config files to each other. Each of these config files loses one menu entry for linking to the next menu, but all other entries are free and may be completely different in each of the three config files. It is possible to use even more config files to similar effect, but I choose not to do that (more on why below...)

Some reasons why I chose to use precisely 3 config files are these:

1: I have a mod-chip which allows Dev1 booting, using mc0:/BOOT/BOOT.ELF, and when this is in fact LaunchELF renamed, it will load LAUNCHELF.CNF from that same folder.

2: I experiment with exploits too, using mc0:/BEDATA-SYSTEM/BOOT.ELF, and here too LaunchELF (renamed) will load LAUNCHELF.CNF from the same folder as itself.

3: Having a copy of LaunchELF on HDD as well wastes no memory card space, except for the small amount taken up by LAUNCHELF.CNF, which will then be loaded from mc0:/SYS-CONF/.

Adding more than these would require either a special CD/DVD disk, which I dislike for general booting purposes, or adding more copies of LAUNCHELF.ELF to the memory card, which I dislike for wasting memory card space.

With the above-mentioned instances of LaunchELF installed, I configure each one of them to link to the 'next' when I press R1. Pressing this 3 times always gets me back to the starting point, so there is no need for a reverse link. Since each instance has 11 menu keys for starting programs, one of which is 'consumed' by this linking, I end up with 30 different menu entries for other programs.

Best regards: dlanor

[HypERSoniC]

interesting i thought launchelf would bork itself if you tried to reboot it like that.. i'll give that a try now

[gravelhead44]

Does anyone know what the "Default" is used for in the Launchelf config? Also, Dlanor, does simply putting the Launchelf.cnf in the same directory as LaunchELF let you make the menus connect? Seems my HDD copy of LaunchELF looks to mc0:/SYS-CONF/LAUNCHELF.CNF for configuration. That's where I already have my copy I run for the exploit. I have an unmodded V7 using the MC exploit.
Any help would be appreciated, Thx in advance.

[dlanor]

Does anyone know what the "Default" is used for in the Launchelf config?

The 'Default' path is used together with the 'Timeout' value, and the ELF it specifies will be launched when that timeout (in seconds from startup) is reached, unless you press some controller button before that, in which case the automatic launch is aborted.

You can use this with a very short timeout if you don't want any menus, or with a rather long timeout to provide a twelfth launch shortcut, chosen simply by not pressing any buttons.

Also, Dlanor, does simply putting the Launchelf.cnf in the same directory as LaunchELF let you make the menus connect?

Yes it should, since it's based on the standard argv[0] of normal C programming. Unfortunately this has not been consistently implemented for the PS2 drivers/launchers, so you can't rely on it for HDD, and each HDD-based application must 'know' where to find its config file(s). Commonly the folder "mc0:/SYS-CONF/" is used for such files, though some applications use specific HDD partitions instead.

Seems my HDD copy of LaunchELF looks to mc0:/SYS-CONF/LAUNCHELF.CNF for configuration. That's where I already have my copy I run for the exploit. I have an unmodded V7 using the MC exploit.
Any help would be appreciated, Thx in advance.

When LaunchELF is launched from memory card, then it will read its CNF file from the same folder if present. If no such file exists, it may proceed to read the one from SYS-CONF instead.

Just place a copy of the CNF file from SYS-CONF into the same mc0: folder as your exploit copy of LaunchELF, and it should use the new copy in future.

Best regards: dlanor

[omegatron]

is this project still being developed

[dlanor]

is this project still being developed

I believe so, though it's hard to be certain without direct contact with the LaunchELF author. But the latest release (v3.4b2) was made fairly recently, leading me to think that the project still 'lives'. I certainly hope it does, as it's the best program of its kind that I've seen.

Best regards: dlanor

[gravelhead44]

Dlanor, Thanks for the info and quick response. I'll give it a try again. For no mods it's definitely my favorite launcher because of the fact it basically writes its config from the ELF. I like not having to FTP every time I want to launch a different app. And its pretty darn quick too.

Would it be ok if I include your info and give you credit for it in an English readme I'm trying to piece togther for noobs like myself in the forums at:

LaunchELF Ver 3.4b Releaed

I have a feeling some of it is off. The timeout portion and default portion (as well as one of the HDD Sections)didn't translate well from my software. This info ties together some of the loose ends for me.

[dlanor]

Would it be ok if I include your info and give you credit for it in an English readme I'm trying to piece togther for noobs like myself in the forums at:

LaunchELF Ver 3.4b Releaed

Sure, you may quote me. Just make sure you do it properly. The important thing for me is not so much to be credited with the stuff I said, but rather NOT to be credited (or blamed ) for stuff that I didn't say...

Best regards: dlanor

[gravelhead44]

Thanks, I will probably just cut and paste your first paragraph, but point to this thread, as it contains some very helpful info. Hopefully that will avoid any confusion.