FMCB + Chip - Incompatibilities –
I opened a new thread, cuz this isnĀ“t really related to the normal bug-reports.
IĀ“m interested, which chips produce which failures with FMCB, if theyĀ“re turned on.
Try different FW-Versions for your chip (if it is upgradeable), maybe different FMCB-Versions (thought 1.8 is enough, but all is worth a try), different chip-settings (if you can change those), or even try to force its specific modes, such as DVD-Video, or PS1-Mode.
My CC 1.0 with the extended BM from Jones23 + newest FW loops on FMCB-Logo, but functions related to this are working correctly, such as RESCUE and Auto-ELF, Fastboot, thought also Buttonlaunch.
Only the hacked OSD will not work.
My DMS3 did some patching in OSD for disc-recognition, as far as I can see.
Thus causing a crazy effect like showing the "Loading-Logo" and then the PS2-Logo (but it still loads the game).
I like to hear more from others.
THX in advance.
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux