@Taucher
EDIT: Also tested with PocketPC 2003 SDK - works fine too - example exe (hello world - no additional benefit) is attached.
<IMG of Hello World App>
You search a nice new menu feature?
Save a short video sequence on a E4 as I am discriped here
//set file name
rset .image.services.rtrecord.filename \FlashIFS\001.seq
//activate recording to memmory
rset .image.services.rtrecord.active true
//wait a moment while rcording
//now save video to flash
rset .image.services.rtrecord.store true
or write a fast sequence of images (while the trigger button is pressed) with this (repeated) command
store -j \FlashIFS\myfolder\0####.jpg
this needs no RAM as buffer memory and you can write about 10.000 frames until the Flash is full
Matter of fact: I've already put that one on my TODO list and my current menu has those commands even in the comments so I don't lose them... but believe it or not - I hadn't a spare hour to hack around for weeks...
... unfortunately also unknown yet: any method how to launch the exe from within the menu itself - of cause it could be added to the startup script... what's already possible is to show a menu with panorama, video etc... but those modes are still non-functioning as the multimedia engine (MediaServer.exe) from the Exx simply crashes when started on the E4 (yes, I've checked DLL deps and brought MP4.dll over, too).
Maybe let's add a brief explanation how the menu system works: It's a frontend to the registry - that's it

.
See also (very close match): Model-View-Controller (MVC) programming concept... IMHO Flir did a really nice job in respect to a multitasking data backbone with this registry.

Well, you'll might ask how the functions switch then etc... that's done by subsystems which run in the background and which can either poll or subscribe to certain registry entries. It's going even so far, that even the image data is stored in a registry key (data-blob)

Now as everybody knows such things like video just scream "compress my data or I'll eat up all your free space" - that's what the MediaServer.exe with it's nice little MP4 dll comes into play... unless it's crashing on startup.
A "dirty" hack could be to write an app to watch for "video" mode, then display itself on the GUI and allow to capture output by setting up the image capture sequence (or simply replace the mediaserver by consuming the frames itself and piping them to some ffmpeg routines or similar code)

Heh, while writing this I think about if there are menu-keys projected over the registry... like the main trigger switch...
... ah, but there's that other thing again - no C/C++ includes for the registry yet ... good news is - the DLLs export a sh***load of classes and similar goodies... but OTOH my time is quite constrained right now - so I'd be really glad for some co-op work here.