Just for information here, so we all learn:
Originally Posted by b1gzz
1. The SCPH-75000 series probably looks for a different file from the OP's console (Probably something like mcX:\BEEXEC-SYSTEM\osdmain.elf versus mcX:\BEEXEC-SYSTEM\osd150.elf).
2. Older consoles used to look for an update to the OSD named osdXXX.elf, where XXX is the console's ROM version number rounded up to the next nearest 10 (E.g. boot ROM v1.01 will look for osd110.elf, while boot ROM v1.20 will look for osd130.elf). Only v1.00 looks for osdsys.elf, and all newer consoles (After boot ROM v1.50, I think) look for osdmain.elf.
3. The original point of the multi-install in the 'official' FMCB installers was to work around this issue here, by making all the boot files co-exist at the same time in the BEEXEC-SYSTEM folder. This is so all consoles will find update files for their own OSD programs, making FMCB work on all console models.
4. Note: The OP's console will look in mcX:\BEEXEC-SYSTEM because it's an European/PAL console.
So... just making a multi-install will most likely solve this problem, even if it's not FMCB v1.8C.
Unmodified SCPH-77006 with SM 3.6
SCPH-39006 with M-chip modchip, SCPH-10281 NA and refurb Seagate 80GB HDD
SCPH-10000 v1.00 with SCPH-10190 PCMCIA NA and SCPH-20400 HDD unit