I've had a go installing SkyDemon Plan and InFlight 1.01. Plan went well, and the enhancements look good, but upgrading InFlight was a bit more problematic, so I'm putting my comments in the InFlight bit of the forum.



The first problem (installing on a Loox 560, no previous problems using ActiveSync) was that the installer told me it couldn't find the .NET framework. It's there, and fortunately the installer allowed me to carry on so that wasn't a problem.



I then chose to install via ActiveSync, but since there was no option to choose where I wanted the program installed (main memory or SD card) problems ensued when it tried to install in main memory - and there isn't enough of that so in due course the installation failed.



I then removed the SD card and installed direct to that. This worked fine, but it seems to mean that the shortcuts to start SkyDemon from the Start menu and buttons on the device don't work anymore. I have to find the program using file explorer and start from there. It looks like the system doesn't know the program exists.



So, once started the program works fine - although I had to do some juggling to get all the old data files in the new folders - and there are some nice improvements. However, it would be good to install via ActiveSync with a choice as to where the installation happens, as this seems like the best way to get a 'proper' install that allows use of menu and button shortcuts.

The installer allows you to specify exactly where SkyDemon will be installed, whether you're installing via ActiveSync or to an SD card.

Tried again and got there in the end. I hadn't realised that I'm supposed to type in the location I want. This isn't the way my ActiveSync does it (it forces you to choose between device and SD card) and wasn't obvious. I think you could provide clearer guidance for this step.



The shortcut in the Start menu only worked after I'd used Add/Remove programs in ActiveSync to remove SkyDemon/SkyAngel. This could have been a hangover from the number of installations there've been, or the change in installation procedure. Possibly for the same reasons I had to manually copy the license and other user files.



I still get the message telling me it can't find .NET.