Free McBoot not working!

[TehJawknee]

Disable the chip and try to load it on the modded console that way.

[Babyface]

Just did that an it does the same thing as before: Free McBoot logo appears and disappears over and over again...

[JNABK]

since you did use the Noobie package, try holding one of the buttons while FMCB logo is showing, see if it at least boots into one of the apps.

uLaunchELF ( R1)
ESR ( R2)
HDLOADER ( L1)
SMS ( L2)
FMCB Configurator ( START)

One of my modchips also dont work with FMCB, but holding a button allows it to run those apps assigned to FMCB.

If you can get into uLaunchELF, check to see what files got installed to the MC by looking in each folder.

[Babyface]

It does actually launch the apps if I hold one of the buttons... So my problem is it does not boot into OSDSYS. In the slim one it doesn't even show me the logo so it's useless to press any buttons (I tried it tough,but no luck).

EDIT:I checked the files and everything seems to be ok except in the BAEXEC-SYSTEM folder,where all .ELF files are .elf ,I tried launching OSDSYS.elf and it said it is not an elf file. I will try to rename all .elf to .ELF and see if it makes a difference...

EDIT2:How do I rename those files? When I bring up the R1 menu in uLaunchELF the rename command is all greyd out,among other commands.

[TehJawknee]

EDIT2:How do I rename those files? When I bring up the R1 menu in uLaunchELF the rename command is all greyd out,among other commands.

They're greyed out because those files are write protected. Those aren't supposed to be messed with.

Instead, try running the FMCB configurator. Go to your SYS-CONF folder and run FMCB_CFG.ELF and if you have a little bit of knowledge on how the OSDSYS works, you should be able to configure it and make sure it's running okay. There should be in-depth explanation in the FMCB tutorial page you used to install it in the first place.

Another question I forgot to ask. Is there anything in the DVD drive when you try to start up your console? If the console is trying to read something off the DVD, it could be interfering with the boot process... I could be wrong, since it usually tries to boot from the memory card first and the DVD second.

[Gnom]

Unless I misunderstood something, you should not rename those files on a multi-installed FMCB, because they're not written according to normal mc format. What the console sees are merely pointers for one only file, so messing with it could cause problems to the memory card. Not to mention the program would probably not find the files it's looking for (I think uppercase makes a difference). Please correct me I'd I'm wrong.

Edit : shorted

[JNABK]

It does actually launch the apps if I hold one of the buttons... So my problem is it does not boot into OSDSYS. In the slim one it doesn't even show me the logo so it's useless to press any buttons (I tried it tough,but no luck).

If the apps launched ok, then the FMCB install is good, thats mainly what i was trying to find out.

EDIT:I checked the files and everything seems to be ok except in the BAEXEC-SYSTEM folder,where all .ELF files are .elf ,I tried launching OSDSYS.elf and it said it is not an elf file. I will try to rename all .elf to .ELF and see if it makes a difference...

EDIT2:How do I rename those files? When I bring up the R1 menu in uLaunchELF the rename command is all greyd out,among other commands.

You definitely DONT want to mess with those files or you will wind up corrupting them. Those files are signed and encrypted and only one is a real ELF files, the others are merely "links" that point to that one real ELF.

I only wanted you to look to see they were all installed for the BAEXEC-SYSTEM and SYS-CONF folders. But it seems from your post all is in good working order as for the FMCB install, its just your Slim that has a problem. its normal to not see the OSD menu from a modded console, as both the modchip and FMCB sometimes use the same addresses and of course the modchip being hardwired is going to boot over the FMCB software.

On the Slim ps2, have you tried both MC slots to see if it works?
Have you tried any other another MC too, to make sure the MC ports are ok? Any problems with games saving/loading from the Slim?

[Babyface]

Well,first of I tried it with the drive empty on both consoles so that's not the problem.Second,I already ran the FMCB config and it's set up right,I even tried a few modifications but it's exactly the same situation.So if I'm not supposed to rename these files (as far as I know they should be uppercase .ELF,and they are not!),I have no frickin' ideea what to do... God this is frustrating!

EDIT:Yes,I've tried with both memory cards and both memory card slots (also formatted both before installing).

EDIT2:I'm going to try and make another .iso and burn it but this time without the noobie package (I can't see why that would make a difference but it's worth a try) and add the apps myself,too bad the phat one does not read cd-rw(that would save me alot of cd's).

[JNABK]

(as far as I know they should be uppercase .ELF,and they are not!),I have no frickin' ideea what to do... God this is frustrating!

Only those apps in the BOOT folder must be all in caps, as those are optional apps that are added, but any system folders/files installed by the installer are already correct and should not be changed. But that is only for the default install, as it is pre-coded to use those names in all caps, but you can use small letters when configuring FMCB yourself with the FMCB Configurator or manually editing the CNF. They just have to match the actual filenames.

I can only assume its your Slim line thats causing you the problems, as you already confirmed the install works fine when you booted an app from a button press.

The only thing i can think of is the Multi-Install isnt installing the correct BIOS version for your Slim's bios version. Each one of those .elfs in the BAEXEC-SYSTEM folder are meant for the console to read its specific bios version for that console, so thats why they are all added with a Mutli-install.

Edit
i just re-read your first post and it might also be your modded ps2 causing the problem, as you say it says a different SCPH number on the case than whats displayed in the screen. Maybe your ps2 has 'mixed' parts put in by the modder and that might be the cause of the install not working on the slim if the modder used parts from an out of region console.

[Babyface]

Well then I'll try to install FMCB from another modded console,but I can't do that only in the weekend when I go home. I'll report back,until then thanks for all your help. Looking forward to report success