boot priorities with FMCB+ESR

[dmcbudman]

ok this is what i want to do
so please correct me if something is wrong (these boot priorities are starting to confuse me)
embed ESR and put it in BxEXEC-DVDPLAYER (with needed files)
install FMCB ('LK_Auto_E1 = OSDSYS' & 'LK_R1_E1 = mc?/BOOT/BOOT1.ELF' & AutoBoot_Disc = 1)
will it work like this?
if dvdv patched disc then ESR
if original disc then autoplay
if no disc then OSDSYS
if dvdv/original + R1 then BOOT1.ELF (is this right?)
if no disc + R1 then BOOT1.ELF

thanks in advance

[TnA]

ESR will ever start, if you do it this way and insert a DVD-Video, or patched disc, in PS2-Browser/OSDSYS.
FMCB may interferer with it, because it has some problems, when you try to boot a disc from PS2Browser.

Can you try to embed ESR to the "BxEXEC-DVDPLAYER"-Folder, before installing FMCB and test it on a NoMod-PS2?

Your guesses are right.

[dmcbudman]

i can (more than likely) do the embeding
but the testing is another story, as i dont have a working laser
but ill see what i can do to get a friend to bring their ps2 over to try it out (after i get the memory card all set up)

[Bootlegninja]

I still feel that the CNF isn't needed. I've taken some time to mess about with it.

I do like the option to enter the OSDSYS, but with it set to autoboot straight from install becomes a bit moot since Free MC Boot is originally meant for systems with dead lasers. What's a ps2 going to do in the sony browser with a dead laser? Not too much.

I'm thinking that it could be simplified a whole lot by having a hardcoded button to enter the OSDSYS and of course autoboot the standard paths. As for the OSDSYS button, I would make it the Start button. Mainly to make it similar to most mod chips' disable button.

Also, launching ESR is no difficult task through uLE. It just makes it one step longer which can be a max of 20 seconds.

[remax]

I think its set like this so that it stay "transparent" for n00b when it's installed (just having now the ability to launch elfs by pressing a button, but still working like a normal PS2 if nothing is done).

Everybody will have is own view on what the default settings should be, and a choice has to be made...

[TnA]

@Bootleg: I assume, you didn't tested the FMCB 1.4c BETA.
I think, you'll see, what I mean.

And again,... If the CNF is deleted, it uses STANDARD HARDCODED STRINGS, like in other versions.
Also with the same settings.
Seems, that Jimmi added the feature, to install the CNF from the same dir, as the Installer.
FMCB is still in it's beginning. You couldn't assume, that all works as it should but it will be MORE FLEXIBE (with CNF)/WHILE also a fixed mode is available.
So it works like any other FMCB, if there is no CNF!
So why should we remove the CNF?

Don't get me wrong Bro.

@remax: You're right.
It should be more transparent. If it will provides all features, it is good that it works the way it does.

[Bootlegninja]

Yeah. That's what I based my previous post off of. With the config as it is upon install, it is too transparent since it boots directly to the ps2 browser. I've already noticed the rash of threads asking what went wrong because of that.

At the very least, it should write the cnf file to autoboot mc?:/BOOT/BOOT.ELF or at least mass:/BOOT/BOOT.ELF to get it to a point where you can actually do something with it.

I found the current 'stock' config annoying at best.

[TnA]

So you tested the new 1.4c BETA, if I get it right.

Yes, I agree with you in this point.
BOOT.ELF should auto-installed (and a Button/Autoboot mapped to it).

Btw.:
Sorry that, but I will configure it myself, that it first boots [Mod-/Custom-]OSDSYS. But I think a standardized Button is good. Modify it to Auto-Boot is very easy.
We can also easily provide 2CNFs and the users choose, which they want (placing it to the same dir, as the installer, and it copies it to the right location).

Like I said. Jimmi seems to have implemented the support of installing a custom CNF with the Installer.
With this, it should be VERY easy, to modify the CNF to your wishes (and also install it directly).
It's getting easier and easier. Time will tell.

Btw2.: Don't know what others think about it,...
-A custom folder for FMCB-Config + Icons (like DMS3, or SMS uses).

A very easy way, to delete the CNF from PS2Browser, if it is corrupted, or doesn't work as it should.
Delete the "Savegame" and FMCB will boot with hardcoded settings again.

[qwerty159]

I found the current 'stock' config annoying at best.

I think the problem is with idiot users who don't read nfo's. When I first installed 1.4b (after using earlier versions) I couldn't figure out why it was booting to the browser instead of uLE like the older version. a whole 30seconds later I had read the readme and knew the "problem". 5seconds editing the .CNF to my liking and all is fine.

I do agree it should probably autoboot an elf file, but that is to compensate for user stupidity.

I thought the cnf file was a bad idea when it was suggested (it sounded clunky and cumbersome), but in practice it works well - at least when an app to configure it without a PC (or the awkward uLE text editor) arrives. :>

[Bootlegninja]

I think the problem is with idiot users who don't read nfo's.

You really don't want to go there.