I have also run into the disk corruption, but I'm not sure what the cause is. I know Booboo says he thinks he has resolved the issue with dingux corrupting the SD card, but I am finding it hard to believe. There is nothing that is done in Dmenu that is outside the normal realm of a standard C program. The only addition to dmenu 0.6 was adding fsync'ing to the file writes, which may ultimately be the culprit. Again, calling fsync on file writes is a common/encouraged practice, but I think there is still something wrong Dingux. I have a ticket in the project to enable read only mode via the dmenu.ini file. The code is in place, I just need to read that config file. Plus with a new startup/shutdown sequence the need for writing to the filesystem decreases. I very well may try to remove the fsync today and see if that makes any difference in the time between usefulness to disk corruption. If you have any other information on what you are doing before corruption, let me know, otherwise I will just try it myself.