This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n2:

rdfs:label

CHDK 1.1.0 User Manual

rdfs:comment

Before downloading and using the CHDK software, careful consideration should be given to the following: Usually the first question is: Can CHDK damage your camera? The short answer: It is unlikely, but theoretically possible. CHDK is created by reverse engineering an undocumented system that directly controls the hardware. Because of this, it is impossible to be certain that it is completely safe. One more thing: There are thousands, if not tens of thousands of satisfied users all around the world enjoying the benefits of CHDK. See also GPL license information below.

dcterms:subject

n10: n11:

n3:wikiPageUsesTemplate

n4: n5: n7: n12:

n8:abstract

Before downloading and using the CHDK software, careful consideration should be given to the following: Usually the first question is: Can CHDK damage your camera? The short answer: It is unlikely, but theoretically possible. CHDK is created by reverse engineering an undocumented system that directly controls the hardware. Because of this, it is impossible to be certain that it is completely safe. The long answer: It is very unlikely that CHDK will permanently harm your camera. There have been no confirmed reports of CHDK damaging a camera, and both the original firmware and the CHDK developers use safeguards to prevent situations where this could happen. There are at least two ways in which CHDK could theoretically do damage: 1) By commanding physical hardware to do something it was not designed to do. For example, it is possible to command the lens hardware to move when the lens is closed. It is also possible to move lens hardware beyond limits allowed by Canon's firmware, using scripts, or overrides. See Talk:UBASIC/Scripts#Tele-Super-Macro_Mode_Comments; 2) By overwriting the internal flash ROM where the Canon firmware is kept, rendering the camera un-bootable. Since CHDK is never intended to write directly to internal flash, it would take an extremely unlikely sequence of events for this to happen. It is worth noting that neither of these cases has resulted in actual damage, and both would require direct input from the user. If you are concerned about this, the risk can be minimized by avoiding untested developmental builds (such as test builds posted on the forum) and being selective about what scripts you run. One more thing: There are thousands, if not tens of thousands of satisfied users all around the world enjoying the benefits of CHDK. See also GPL license information below.