So far, the major roadblock for most users who find trouble installing 400plus seems to be the process of preparing the card (which is similar to the process of preparing a card for CHDK or ML, by the way); if we could have just a tool capable of preparing the cards, we would have won an important battle.
Thank you for your interest.
Thank you, too!
No uninstaller:
I can see why this hasn't been a priority so far. However, now that a user may get the hack running on their camera in a couple of mouse clicks (without reading any of the warnings, of course), I believe the change has to be reversible.
Enabling a camera to use 400plus is the same as enabling a camera to use ML; and as far as I know, it is also a permanent change on ML, too (see
http://wiki.magiclantern.fm/faq#does_ml_do_any_persistent_changes_to_my_camera). We know how to revert that change, but it is considered a dangerous procedure.
Package structure:
- 400plus-testfir-1.bin.zip contains testfir.fir under 400plus-testfir-1\bin, which must be copied to A\, while
- 400plus-20160404-07.bin.zip (version-dependent) contains
- AUTOEXEC.BIN under 400plus-20160404-07\bin (version-dependent), which must also be copied to A\, and
- languages.ini under 400plus-20160404-07\bin (version-dependent), which must be copied to A\400PLUS.
I can deal with multiple downloads and even with non-root source directories (thanks to SDM), but could you at least place languages.ini under 400PLUS please?[/li][/list]
Yes, I think we can do that; we could also maintain an "auto-installer" ZIP file with the latest version, and a structure carved to the needs of your software.
Missing license.
I believe at least some portion of the code was taken from Magic Lantern, so it has to be GPLv2 or later (not recommended). However, I'm not sure about the copyright notice.
Yes, there is code grabbed from ML in 400plus (and there is code in ML grabbed from 400plus!). Code is licensed as GPL v2, but I am surprised to realize that I cannot find any mention to license of copyright in the site... will have a look at that issue later and fix it.
Difficult detection.
CHIMP uses string matching to gather detailed version data from CHDK, ML and (most of) SDM binaries. The latest 400plus AUTOEXEC.BIN contains little more than a standalone
Please consider adding metadata in future releases.
Looks reasonable, too.