CC 2.0-do you NEED BM

[GeToChKn]

I'm doing a chip for a friend's little brother, who he would prefer didn't have access to the BM at all to change or mess with anything. Is there anyway I can either no install BM on the 2.0 or make it least so that BM doesn't start up by default and only with button press or something?

thanks

[CrystalChip]

Release 32(coming out tomorrow) allows you to use CC2.0 without BM. I would highly suggest using BM though as he can't really do any harm to the system except perhaps format the memory card, which is his own loss and would teach him to mess with things he's not supposed to. I would install BM, tell the kid not to touch anything and keep a bat to beat him with if he does, perhaps even giving him a couple preemptive whacks just in case!

Some time ago Jones23 made a "child-safe" version of the BM scripts but this is no longer compatible with the existing scripts. It may be that in the future we will incorporate some "child-safe" features in the official BM scripts, though this is not likely due to the fact that very few people would use such a thing and the development time is better spent on other things.

To recap, using Release 32(out tomorrow) will let you use your CC2.0 without BM but of course you will not have the majority of the features supported by CC then.

[d3xion]

Sorry, the answer is no. You must run BM to take advantage of any of the features of the Crystal Chip. If you don't like BM, go with the Matrix Infinity which uses the native Sony Browser.

Now I don't know why you wouldn't want CC BM, it's much more superior than what you are accustomed to, including removal of the "Playstation 2" logo when it boots media, speeding up the load time significantly.

[Yoc]

There is one thing you could do easily is to make a custom version of Bootmanager with two memory cards and the following modification of BMMENUS.PBT (this is theory, I didn't test it myself) :

    IF EQU "$BM.INSTALLER_MODE$" "1"
        ADDWIDGET "CALL" "$BM.TXT_INST_BM$" "$BM.TXT_HINT_INST_BM$" "$ARG0$" "MENU_INST_BM"
        ADDWIDGET "CALL" "$BM.TXT_UPG_FIRMWARE$" "$BM.TXT_HINT_UPG_FIRMWARE$" "$ARG0$" "MENU_UPG_FIRMWARE"
        ADDWIDGET "CALL" "$BM.TXT_MC_MANAGER$" "$BM.TXT_HINT_MC_MANAGER$" "$ARG0$" "MENU_MC_MANAGER"
        ADDWIDGET "CALL" "$BM.TXT_SYS_INFO$" "$BM.TXT_HINT_SYS_INFO$" "$ARG0$" "MENU_SYS_INFO"
        ADDWIDGET "CALL" "$BM.TXT_DISC_TEST$" "$BM.TXT_HINT_DISC_TEST$" "$ARG0$" "MENU_DISC_TEST"
    ELSE
        ADDWIDGET "CALL" "$BM.TXT_BOOT_MEDIA$" "$BM.TXT_HINT_BOOT_MENU$" "$ARG0$" "MENU_BOOT"
        ADDWIDGET "CALL" "$BM.TXT_APP_BROWSER$" "$BM.TXT_HINT_APP_BROWSER$" "$ARG0$" "MENU_APP_BROWSER"
        ADDWIDGET "CALL" "$BM.TXT_DEV_MANAGER$" "$BM.TXT_HINT_DEV_MANAGER$" "$ARG0$" "MENU_DEV_MANAGER"
       ADDWIDGET "CALL" "$BM.TXT_FW_MANAGER$" "$BM.TXT_HINT_FW_MANAGER$" "$ARG0$" "MENU_FW_MANAGER"
       ADDWIDGET "CALL" "$BM.TXT_MC_MANAGER$" "$BM.TXT_HINT_MC_MANAGER$" "$ARG0$" "MENU_MC_MANAGER"
        ADDWIDGET "CALL" "$BM.TXT_SYS_INFO$" "$BM.TXT_HINT_SYS_INFO$" "$ARG0$" "MENU_SYS_INFO"
        ADDWIDGET "CALL" "$BM.TXT_CONFIGURATION$" "$BM.TXT_HINT_CONFIGURATION$" "$ARG0$" "MENU_CONFIG"
    ENDIF

Just comment a few lines :

    IF EQU "$BM.INSTALLER_MODE$" "1"
        ADDWIDGET "CALL" "$BM.TXT_INST_BM$" "$BM.TXT_HINT_INST_BM$" "$ARG0$" "MENU_INST_BM"
        ADDWIDGET "CALL" "$BM.TXT_UPG_FIRMWARE$" "$BM.TXT_HINT_UPG_FIRMWARE$" "$ARG0$" "MENU_UPG_FIRMWARE"
        ADDWIDGET "CALL" "$BM.TXT_MC_MANAGER$" "$BM.TXT_HINT_MC_MANAGER$" "$ARG0$" "MENU_MC_MANAGER"
        ADDWIDGET "CALL" "$BM.TXT_SYS_INFO$" "$BM.TXT_HINT_SYS_INFO$" "$ARG0$" "MENU_SYS_INFO"
        ADDWIDGET "CALL" "$BM.TXT_DISC_TEST$" "$BM.TXT_HINT_DISC_TEST$" "$ARG0$" "MENU_DISC_TEST"
    ELSE
        ADDWIDGET "CALL" "$BM.TXT_BOOT_MEDIA$" "$BM.TXT_HINT_BOOT_MENU$" "$ARG0$" "MENU_BOOT"
#        ADDWIDGET "CALL" "$BM.TXT_APP_BROWSER$" "$BM.TXT_HINT_APP_BROWSER$" "$ARG0$" "MENU_APP_BROWSER"
#        ADDWIDGET "CALL" "$BM.TXT_DEV_MANAGER$" "$BM.TXT_HINT_DEV_MANAGER$" "$ARG0$" "MENU_DEV_MANAGER"
#        ADDWIDGET "CALL" "$BM.TXT_FW_MANAGER$" "$BM.TXT_HINT_FW_MANAGER$" "$ARG0$" "MENU_FW_MANAGER"
#        ADDWIDGET "CALL" "$BM.TXT_MC_MANAGER$" "$BM.TXT_HINT_MC_MANAGER$" "$ARG0$" "MENU_MC_MANAGER"
        ADDWIDGET "CALL" "$BM.TXT_SYS_INFO$" "$BM.TXT_HINT_SYS_INFO$" "$ARG0$" "MENU_SYS_INFO"
#        ADDWIDGET "CALL" "$BM.TXT_CONFIGURATION$" "$BM.TXT_HINT_CONFIGURATION$" "$ARG0$" "MENU_CONFIG"
    ENDIF

Burn a CD with this new version of BM, install it on a new memory card, and ask the father to keep the original memory card safe.

A much more elegant way would be to add some kind of password protection. It shouldn't be too difficult to do, but you'll have to check and perhaps remake your script modifications with each firmware upgrade...