ulaunchelf 4.40 + patched codebreaker issues.

[Dracari]

i know i just really nee dto patch my codebreaker 9.2 to use CB_Launch.elf but instead i have it load ulaunchelf..

i've been using 4.30 for the longest time. today i updated it to 4.40 now codebreaker wont properly exit to ulaunchelf. it will if i use 4.30 or older. but not 4.40

Any ideas? as i do NOT like the idea of keeping two copies of ulaunchelf on my FMCB memcard (it holds FMCB, ESR, SMS,uLaunchELF and CB 9.2 so i dont haveto worry about loosing my pendrives since i use my 4GB pendrive as a multi-boot rescue tool (linux for file recovery then hiren's boot CD (in USB mode) 10.0 for others)

[amp2006]

i have only tried CB so i dont know much about it but i think you need to delete the old LaunchELF.CNF from 4.30 and save the new one from 4.40

[dlanor]

i know i just really nee dto patch my codebreaker 9.2 to use CB_Launch.elf but instead i have it load ulaunchelf..

i've been using 4.30 for the longest time. today i updated it to 4.40 now codebreaker wont properly exit to ulaunchelf. it will if i use 4.30 or older. but not 4.40

I really don't know what the real cause for that is, as I just tested it myself using uLE v4.40b, and it works perfectly here. This was with a CB elf patched to exit via "mc0:/BOOT/BOOT.ELF", which I assume is exactly what you wanted to do. And I did it using CB v9.2 just like you mentioned using.

Any ideas? as i do NOT like the idea of keeping two copies of ulaunchelf on my FMCB memcard (it holds FMCB, ESR, SMS,uLaunchELF and CB 9.2

I have similar setups on my memory cards too, and considering the vast size of the CodeBreaker files (with the built-in database) these setups do waste a lot of space as it is, even when avoiding duplication. So I naturally sympathize with that.

Since it works for me, but not for you, using the same versions of CB and uLE, the only thing I can think of as causing it is some difference in the patch options.

But if you already know that the CB_launch exit method works better (though I don't see why), then perhaps that is the best way to go.

However:
It is remotely possible that this is an issue related to the new MC modules used in the new uLE version. I made a special beta precisely to test such issues, which is identical to v4.40b in all respects except for using the MC modules of the console bios (thus unable to rename objects on MC, which was one of the new features of uLE v4.40b). This test version is not really intended for normal use, but only for special testing of these cases. You can find it by going to the list of threads for this forum and click on the paperclip icon in the title box of the main release thread. This will open a popup window listing all attachments of this thread (tons) and if you scroll down a bit in this list you will find the uLE v4.40c beta I made for another user who reported odd errors. Please test the same CB operations with that beta version of uLE and report your results here (whether differing from old results or not).

Best regards: dlanor

[Dracari]

I really don't know what the real cause for that is, as I just tested it myself using uLE v4.40b, and it works perfectly here. This was with a CB elf patched to exit via "mc0:/BOOT/BOOT.ELF", which I assume is exactly what you wanted to do. And I did it using CB v9.2 just like you mentioned using.

yea i had it point to MC0:/BOOT/BOOT.ELF as only idea i can POSSIBLY THINK OF.. i had my 2GB "attache" pendrive in.

[dlanor]

yea i had it point to MC0:/BOOT/BOOT.ELF as only idea i can POSSIBLY THINK OF.. i had my 2GB "attache" pendrive in.

If you wrote that pathname for the CB patch exactly as you wrote it in this post, then that would make a correct exit to uLE impossible.

There is no valid PS2 device with the name "MC0:".
The correct name is "mc0:", using lower-case letters.

But if that was the problem then it would not work with any other version of uLE either...

Did you try the other uLE beta I mentioned yet ?

Best regards: dlanor

[Dracari]

If you wrote that pathname for the CB patch exactly as you wrote it in this post, then that would make a correct exit to uLE impossible.

There is no valid PS2 device with the name "MC0:".
The correct name is "mc0:", using lower-case letters.

But if that was the problem then it would not work with any other version of uLE either...

Did you try the other uLE beta I mentioned yet ?

Best regards: dlanor

mybad didnt realise i had hit caps but its indeed mc0: but when i updated it i copied 4.40's bootelf from the archive to the memcard and no i havent yet. as im no where Near an Orgin Mirror (save) in Okami atm