About config file (LAUNCHELF.CNF) loading...

[bootsector]

Hi folks!

Does LaunchELF v3.57 load its configuration file (LAUNCHELF.CNF) from current directory (if exists)? Or does it load ONLY from 'mc0:/SYS-CONF'??

Regards,

bootsector

[E P]

Hi folks!

Does LaunchELF v3.57 load its configuration file (LAUNCHELF.CNF) from current directory (if exists)? Or does it load ONLY from 'mc0:/SYS-CONF'??

Regards,

bootsector

Yes, it loads it from the current directory if it exists. If the LAUNCHELF.CNF is not found, then it looks for it in mc0:/SYS-CONF.

[bootsector]

Thank you very much for the info, E P!

Regards

[shiro08]

I've got ulaunchelf booting in dev2 mode using my matrix infinity. I understand ulaunchelf looks for launchelf.cnf in the same directory it was loaded from first, then defaults to mc0:/SYS-CONF/. However, I've never gotten that to work when booting in dev2. I tried copying launchelf.cnf to the __boot partition since that's where dev2 looks for boot.elf. Am I setting this up correctly? There isn't much documentation on the infinity team website on how dev2 launches boot.elf. Ultimately, I want to be able to run ulaunchelf totally off the hdd.

Normally, I wouldn't be complaining about storing launchelf.cnf on the memory card, but it starts to become a hassle when you have three roommates with their own cards and one ps2. Then keeping the all the configs consistent takes alot of shuffling. If I could get launchelf.cnf to load off the hdd, I wouldn't have to go through copying and pasting the file to three other memory cards. I know many homebrew authors want to promote SYS-CONF as the primary location for storing config files, but it would be a nice feature to specify your own location. Perhaps the downside is the hdd modules would have to be started by default if that's where the cnf is located. I don't know how well that would work for hdd-less people, not to mention the extra 10 secs loading hdd modules others won't even use.

[hip725]

If i install a new Launchelf, does the old config file still work with the new ULE?

[JNABK]

it has for me v3.59 to v3.60
All my skin settings were intact. You may have to adjust for the new implimentations, like the popups opaque with color1 as this affects the small popup menus background.

[hip725]

Well currently, I am using 3.55, so if I update to 3.60, will it work?

[ps2dragon]

Well currently, I am using 3.55, so if I update to 3.60, will it work?

Yea you should be fine, those new settings will just be added to your old LAUNCHELF.CNF, and your old settings will be intact going from v3.55 to v3.60. No need to do anything to the CNF file... just leave it where it is.

[dlanor]

Well currently, I am using 3.55, so if I update to 3.60, will it work?

The new CNF system was introduced in v3.41t, so basically all versions since then will accept any CNF that is not older than v3.41t. Obviously, the older CNFs will lack settings for many of the new features, but for most cases this only means that sensible defaults will be used instead of real user settings.

With v3.58 the new higher resolutions were introduced, with different defaults for PAL and NTSC. This may cause trouble for a few people who use NTSC consoles with PAL TVs or vice versa, but for most people the transition should be problem-free. Just don't use v3.58, which had some bugs, but go directly for v3.60 instead which has all the latests bugfixes and improvements.

If you still feel unsafe upgrading, it's always a good idea to make a backup of your currently bootable MC setup first (if you have more than one MC).

Best regards: dlanor

[bootsector]

dlanor, can you confirm this issue? LaunchElf cannot load LAUNCHELF.CNF from __boot partition when boot via DEV2???

Thanks in advance!

bootsector

I've got ulaunchelf booting in dev2 mode using my matrix infinity. I understand ulaunchelf looks for launchelf.cnf in the same directory it was loaded from first, then defaults to mc0:/SYS-CONF/. However, I've never gotten that to work when booting in dev2. I tried copying launchelf.cnf to the __boot partition since that's where dev2 looks for boot.elf. Am I setting this up correctly? There isn't much documentation on the infinity team website on how dev2 launches boot.elf. Ultimately, I want to be able to run ulaunchelf totally off the hdd.

Normally, I wouldn't be complaining about storing launchelf.cnf on the memory card, but it starts to become a hassle when you have three roommates with their own cards and one ps2. Then keeping the all the configs consistent takes alot of shuffling. If I could get launchelf.cnf to load off the hdd, I wouldn't have to go through copying and pasting the file to three other memory cards. I know many homebrew authors want to promote SYS-CONF as the primary location for storing config files, but it would be a nice feature to specify your own location. Perhaps the downside is the hdd modules would have to be started by default if that's where the cnf is located. I don't know how well that would work for hdd-less people, not to mention the extra 10 secs loading hdd modules others won't even use.