Replying here.The easiest 'fix' would be to extend the directory name check to allow '_' (underscore) too. Would that be correct? (AFAIK date based dir names always have an underscore as 4th char).(I'm asking other devs, not necessarily @oneaty).
From stick，I knew the firmware version of my camera is 100a. When everything is done，I can open the camera with chdk successfully. However，the build info shows FW Vers：100b ！ Could someone confirm this problem？What's the problem if I continues to use 100b？
Quote from: rick on 02 / January / 2015, 06:30:10From stick，I knew the firmware version of my camera is 100a. When everything is done，I can open the camera with chdk successfully. However，the build info shows FW Vers：100b ！ Could someone confirm this problem？What's the problem if I continues to use 100b？Some version of Canon firmware are essentially identical (at least from a CHDK port requirement). When that happens, we only make one actual version of CHDK and then rename it so it will match the available firmware versions. In the case of the A1200, the 100a and 100b versions are done that way. So you will see 100b as the firmware version even though your camera has 100a. It will work fine that way.
Just a note. It was mentioned in the German forum that the CHDK file browser has problems on exFAT cards: it's not possible to return from a subdirectory. My guess is that this happens because exFAT doesn't have .. (and .) directory entries. Can somebody with an appropriate card confirm this?
gui.c:(.text+0x106e): undefined reference to `gui_reset_alt_helper'
compilation with OPT_EXPIRE_TEST is broken for touchscreen cameras in trunkedit:... and 1.3Code: [Select]gui.c:(.text+0x106e): undefined reference to `gui_reset_alt_helper'
Started by Barney Fife AllBest's Builds
Started by obsidian General Discussion and Assistance
Started by nirschi « 1 2 » General Discussion and Assistance
Started by Kenith Olson General Help and Assistance on using CHDK stable releases
Started by srsa_4c CHDK Releases
