I would like to see an option to have CHDK only start if a certain button is held during bootup. Implementation of the feature as I envision it could be quite a challenge and would require creative thinking:
I use a large SD card in my S5 IS, so I use the 2 partition method: 1st partition is small FAT16 with DISKBOOT.BIN, 2nd partition is large FAT32 with all my photos and CHDK settings. When CHDK boots, it switches the camera over to the 2nd partition.
The effect of this is to create a hidden space with all my photos, since Windows cannot see the 2nd partition. Also, if the card is booted unlocked, only photos that I put in the 1st partition will be visible.
This strikes me as potentially very valuable in situations where authorities overstep their power and demand to see the photographs, or even take the camera from me. This may occur when documenting police brutality or other ill behavior, when going through customs and border security, or when legally photographing sensitive subjects.
If there could be a way to prevent CHDK from loading if a certain button is not pressed during load, I would be able to protect any sensitive photographs.
The problem: This is not desirable for most users, and the settings would reside on the *second* partition. Could the settings be read *before* switching? Can CHDK be made to not inject itself, or maybe go into an "invisible" state?