The infamous Cacko crash is not really a crash of the OS, but rather a crash of Qtopia which is then restarted. This is due to flaws in Sharp's Qtopia libraries that shipped with the unit. There is no source available for the libraries which makes it next to impossible to fix. The draw back is that without these libraries there is no video accleration for the ATI Imageon100 chip in the C series devices. Some folks have hacked up a header file to take advantage of this accleration (pdaxrom, kino2, etc.), but it is still based on the same binaries. Many of the developers in this forum have solicited ATI and Sharp for documentation or source for this chip so that the problem could be fixed, but there has been no response. So, there is the story on the Cacko Qt mystery crashing.