The card is now configured to start CHDK automatically when camera starts (How do I start CHDK automatically?
• Place the card in your camera. Leave the card write protected • If everything went right, when you turn on the camera, the CHDK splash screen will blink (CHDK splash screen) or (Later style Splash Screen) Other notes: The methods presented above require cards to be formatted using the FAT16 file system, which is limited to a maximum of 4 GB. Some cameras support the new SDHC (SD High Capacity) flash cards, which can go over 4 GB. If you have a card larger than 4 GB, the solution is to create two partitions on your card: a small FAT16 partition, and a larger FAT32 partition. (The FAT16 partition can be very small, like 2 MB, and must be the first partition on the card.) You would then install the CHDK boot files (DISKBOOT.BIN and possibly PS.FIR) on the FAT16 partition, and everything else on the FAT32 one. When using this system, CHDK will start from the FAT16 part of the card. It will then automatically detect the larger FAT32 partition, and “switch over” to use that one. All images
• Remove the card from your card reader and place it in your camera. Leave the card write protected • If everything went right, when you turn on the camera, the CHDK splash screen will blink (CHDK splash screen) Predefinição:Notice Other notes: The methods presented above require cards to be formatted using the FAT16 file system, which is limited to a maximum of 4 GB. Some cameras support the new SDHC (SD High Capacity) flash cards, which can go over 4 GB. If you have a card larger than 4 GB, the solution is to create two partitions on your card: a small FAT16 partition, and a larger FAT32 partition. (The FAT16 partition can be very small, like 2 MB, and must be the first partition on the card.) You would then install the CHDK boot files (DISKBOOT.BIN and possibly PS.FIR) on the FAT16 partition, and everything else on the FAT32 one. When using this system, CHDK will start from the FAT16 part of the card. It will then automatically detect the larger FAT32 partition, and “switch over” to
