Havn't updated uLaunch in forever

[Agent Moose]

I haven't updated my ulaunch.elf in forever, so I can't remember how to do it.

Would I need to remove the whole FMBC from my memory card and then re-install it with the new version?

[JNABK]

Its simple to update uLaunchELF:


Place the new BOOT.ELF onto a USB stick and then insert it in your PS2
Launch uLaunchELF and open FileBrowser
goto mass:/BOOT.ELF and press X to mark the file
next press R1 to open the submenu and select 'copy'
next press triangle to return to Filebrowser and select your MC
goto mc0:/BOOT and press R1 again in the BOOT folder to select 'paste' from the submenu
confirm the paste and it will over-write the old BOOT.ELF

Thats it, next ps2 bootup it will be the new version.

[ps2dragon]

What version is your current uLE? If you're using a really old version of uLE, I would suggest you first backup your mc0:/SYS-CONF/LAUNCHELF.CNF file to another location, then delete the original LAUNCHELF.CNF before upgrading uLE. The reason being is because there are different versions of the LAUNCHELF.CNF file, and you may have problems getting uLE to load if it can't read the older LAUNCHELF.CNF. I could be wrong, but I remember reading a thread about this before, and it turned out the problem with uLE was due to it trying to use the older LAUNCHELF.CNF on startup.

[Agent Moose]

Alright.

Thanks. I did what JNABK said, and it worked perfectly

[JNABK]

Yea, i kinda figured you had a fairly recent version , since you said your using FMCB.

[JoeUser38]

Yea, i kinda figured you had a fairly recent version , since you said your using FMCB.

With the newer Free MC Boot, it can be set up where updating is VERY simple.

I don't put any ELF files on my memory card anymore, they are all on my USB stick in \BOOT. So, pull the flash drive out, put it in the computer, copy the new BOOT.ELF to \BOOT\BOOT.ELF, put it back in the PS2, and good to go. The LAUNCHELF.CNF and skin files are in in mass:BOOT\ also, and I used uLE: syntax to find all files. MC0:BOOT is empty (suppose I could delete it if I wanted).

Having all the ELF files on the memory card (along with using the smaller DVD file for embedding) frees up enough space that I went ahead and installed Free MC Boot on all my memory cards (less confusion on which to boot with, and LOTS of backups in case something happens to one).

[Agent Moose]

I can't boot up my ps2 with my flash drive because it is a kingston.

Also, this is off-topic, but I don't want to make another topic about it:
1. Whats the difference between uLaunchELF.cbs and LAUNCHELF.CNF?

2. I was looking at the skinning tutorial and I was trying to create my own .cnf. When it gets to this part:

SKIN_FILE = uLE:/skinname.jpg
GUI_SKIN_FILE = uLE:/gui_name.jpg

Would I just have to put the file anywhere on the memory card?

[JNABK]

1- .cbs is for codebreaker to use and the .CNF file is the configuration file used by uLaunchELF.

2- yep, the uLE:/ is so uLaunchELF will search both MCs for that named file. But its best to place it into a folder, any folder, so it doesnt display as corrupted data on the MC browser of the console.

[JoeUser38]

1- .cbs is for codebreaker to use and the .CNF file is the configuration file used by uLaunchELF.

2- yep, the uLE:/ is so uLaunchELF will search both MCs for that named file. But its best to place it into a folder, any folder, so it doesnt display as corrupted data on the MC browser of the console.

The uLE:/ syntax will also have it search in the same folder as uLaunchELF, and I believe MC?:SYS-CONF as a last resort (not sure about that, but I believe it does). I use it so it finds all the files in the same location as BOOT.ELF, which in my case is usually in mass:BOOT.

[JNABK]

The uLE:/ syntax will also have it search in the same folder as uLaunchELF, and I believe MC?:SYS-CONF as a last resort (not sure about that, but I believe it does). I use it so it finds all the files in the same location as BOOT.ELF, which in my case is usually in mass:BOOT.

Yes, that is true............i only stated about the MC part, as he said he couldnt use his USB device, so i was just answering his question.