I've given the code for STICK to several people - the main reason for not making it public is its messy nature, lack of useful comments and general untidiness.
I guess that would work, but I'm hoping for a (supposedly) more reliable method of deducing it from the CHDK repo.
I'm hoping checking drive sizes could be avoided. I believe that if someone really wants to format or corrupt their hard drive, they will find a way.
2. the ALT button. I found CAM_ALT_BUTTON_NAMES and CAM_ALT_BUTTON_OPTIONS in platform_camera.h, but what if CAM_ADJUSTABLE_ALT_BUTTON is undefined (as in ixus870_sd880)?
Is the SD Card tool a module? I'm hoping to remove it whenever possible (i.e., for a bootable single partition).
3. the autoboot flag. N and N Facebook use the microSD door, which is indicated by KBD_SKIP_READONLY_BIT and SD_DOOR_OVERRIDE in platform_kbd.h. Any other models/flags?
There is not, I would say using the PID as zeno describes would be the best option. The ability to boot from FAT32 is purely a product of the Canon firmware, so isn't explicitly defined in the CHDK source. CHDK usually supports multi-partition on cameras that don't support FAT32 booting, but there could be exceptions in either direction.
Then it's KEY_PRINT, but this may or may not be an actual "print" button. For example, on cameras without a print button, the play button might defined as print for CHDK purposes. In some cases there might be another key defined with the same bits (e.g. KEY_PRINT and KEY_PLAYBACK defined with the same bit values kbd.c) and others might not. Unfortunately this isn't defined in any coherent way, and is very hard to fix without having all the cameras.
in any case I would strongly urge you to install the full, unmodified CHDK package no matter what.
nothing in here yet.
First of all, there are two "full" CHDK packages, which will appear as Installation Type options. However, I was thinking about adding at least one other option - a "Minimal" install, which would exclude all the extras, i.e. games and Eye-Fi. I believe CHDK could do just fine without those (I wish the Games menu item could be removable as well). And how about Module Explorer, CPU info, Benchmark etc.?
PS.FI2 - can be removed unless absolutely necessary (or convenient, as could be the case with the N model)vers.req - no use if installed via GUIchangelog.txt - outdatedreadme.txt - little use if installed via GUI
Quotenothing in here yet./quote]Maybe it's just my OCD, but I suggest removing those.Yeah, they aren't helping much and should either have content or be removed.
nothing in here yet./quote]Maybe it's just my OCD, but I suggest removing those.
Note the minimal package is not intended an option for new installs. It's a leftover to allow people who already had an install to update only the binary files. These days the difference between a 300k and 700k download isn't significant, but changing the autobuild is complicated and potentially breaks things that scrape the page, so we've left them.
If you start leaving things out, the wiki pages etc will refer to stuff that isn't there and cause headaches.
There goes the Installation Type step. The less the merrier I suppose Speaking of updates, is there any reliable way of gleaning the build number from the binaries?
Well, the whole point of this utility is for people to not need the wiki.
Once they are installed? Not that I can think of. For all modern cameras, binaries are encoded (see dancingbits and packfi2 in the source tools directory) so you can't trivially read the version from the executable.
Having the version identified on the SD card seems like it could be useful, suggestions are welcome.
Started by andyroo General Help and Assistance on using CHDK stable releases
Started by morel « 1 2 » General Help and Assistance on using CHDK stable releases
Started by francoisrabelais « 1 2 3 4 » General Discussion and Assistance
Started by genosmm General Help and Assistance on using CHDK stable releases
Started by dmitrys General Discussion and Assistance
