Auto-Boot Problem

[rrm74001]

I am trying to disable the "feature" that automatically launches a PS2 CD when the console first turns on. I have a SCPH-77001 PS2 and I have installed Free McBoot and ulaunchelf on my PS2. I tried using the Free McBoot Configurator to disable this feature.

I managed to make it so that it does not launch the PS2 CD, but it goes to the Browser, even though the "Go To Browser" option is set to OFF. However, if there is no PS2 CD inserted, then it does not go to Browser, but instead the PS2 Main Menu.

I was referred to this forum from the AfterDawn forums if you want to see how this situation unfolded:

http://forums.afterdawn.com/thread_view.cfm/736334

[dlanor]

I am trying to disable the "feature" that automatically launches a PS2 CD when the console first turns on. I have a SCPH-77001 PS2 and I have installed Free McBoot and ulaunchelf on my PS2. I tried using the Free McBoot Configurator to disable this feature.

I managed to make it so that it does not launch the PS2 CD, but it goes to the Browser, even though the "Go To Browser" option is set to OFF. However, if there is no PS2 CD inserted, then it does not go to Browser, but instead the PS2 Main Menu.

Unfortunately that is as good as it gets on these PStwo models. I have the same 'problem' myself with my SCPH-77004. This is due to a difference in how the original OSDSYS works on these models, making it necessary for FMCB to open the Browser to prevent the automatic disc boot procedure that the OSDSYS code would otherwise perform. There is no other way to make the OSDSYS program ignore a disc in tray on these models. The launch arguments used on older models to prevent it, without having to enter Browser, have no effect in the later models.

But if you want to 'land' in a directly usable homebrew menu, even with a disc in tray, then you can always configure uLaunchELF as your default boot program in the FMCB configurator, by setting the E1 launch key 'Auto' to launch "mc?:/BOOT/BOOT.ELF".

This is what I do myself, combined with setting the E1 triangle button to "OSDMENU" and the E1 'SELECT' button to "FASTBOOT" (these settings achieved by pressing SELECT repeatedly instead of browsing for a file to select)

The overall effect of this is that I normally boot directly into uLE, obviously my main homebrew menu program. From there I can then opt to use a shortcut button that will launch MISC/PS2Browser (the uLE name for OSDSYS), and if I then press down triangle during the OSDSYS launch this will override the default settings forcing FMCB to stay in menu mode (going to browser on 77004 if a disc is in tray), but if I instead press 'Select' during the OSDSYS launch the override act will be to boot any disc in tray.

So this way I have all options open for how to use FMCB, though mostly I only use it for the raw boot effect, as uLE can do most of the other stuff FMCB can, though differently. eg: MISC/FileBrowser is more capable than Sony Browser, and MISC/PS2Disc can boot almost every disc that FMCB can boot. (The exception is CDDA audio discs.)

This is how I like it myself, but there are lots of other ways to do it too, of course.

Best regards: dlanor

[rrm74001]

Okay sweet thanks for the reply! Just out of curiosity, if there was homebrew that specifically and ONLY booted the PS2 menu, and I set that as my default boot program, would that get around this issue?

[dlanor]

Okay sweet thanks for the reply! Just out of curiosity, if there was homebrew that specifically and ONLY booted the PS2 menu, and I set that as my default boot program, would that get around this issue?

If that were possible, then sure. But the problem is that the PS2 menu does not exist in 'stand-alone' form.

It can only be invoked as part of the OSDSYS program, which on a slim PStwo will inevitably attempt to launch any disc that happens to be in the tray, except when invoked with an argument telling it to enter the Browser instead. On older consoles similar arguments exist that prevent the disc booting without entering Browser, but on the newer slims those arguments have no effect at all. They are simply ignored.

The only way to achieve the effect you mean would be to write an entirely new program which works exactly like the menu sections of the OSDSYS program, so that FMCB could launch this new homebrew in a way similar to how it can launch uLE. But making that new menu program identical to the menu parts of OSDSYS would also make it illegal to distribute that elf, as OSDSYS is copyrighted software.

Current FMCB does not include any part of the OSDSYS in the FMCB package, but only modifies how the OSDSYS in your console works. That is why FMCB can do this legally. But yanking out the entire menu part of the OSDSYS program into a separate distributed file is a different matter, and highly illegal.

Also, it would waste execution time in the same way as when launching uLE, as it always costs time to launch an external file, which would make it slower for each boot to reach menu than with the current version (at least for those with fat PS2 consoles).

So my advice is that use of the FMCB menu is convenient mainly if you always boot with empty tray, or have a fat console. But for reaching a menu on a slim console with disc in tray the best alternative is to use uLE.

But then again, I'm obviously partial in favour of uLE.
That's just inevitable, all things considered...

Best regards: dlanor

[rrm74001]

I figured that would not work. I was just throwing it out there. Incredible replies by the way!