Hi, looks like an excellent application, I've been looking for something like this for a while!

I'm trying to build an installation that supports both MIPS and ARM platforms and I can't quite work out how this is done. I've added the 2 target platforms, then created 2 copy files sections, 1 for each target and called them 'Platform_MIPS' and 'Platform_ARM'. Then I assume to assign these 2 each platform I select the 'Installation details for MIPS target' and then tick the file section for that, and then do likewise for the ARM platform.

But if I then click the MIPS installation details the copy files section for it is no longer ticked? And the project will not build?

Am I doing something wrong or is there a bug here?

Thanks!

Oh yes, another bug is discovered

Redownload the program:
http://www.aperitto.com/content/view/14/28/

The procedure is
1. Create the target platforms.
2. Add sources for the specified sources into the Desktop Side Dialog.
3. Add Copy Files Sections for specified sources into the Pocket PC Side.
4. Check them ( bug was here ... )
5. Build it ...

Thanks for using PPCIC and pointing out this bug.

PS:
Can you give me feedback for working setups with different platforms?

Regards,
Nick Protopapas.

Hi Nick, that's fantastic, worked perfectly!

Well, almost... After working out how to properly configure the files for the different platforms I managed to build the cab files and the single exe installer. But the installer failed - ActiveSync (v4.5) threw an error saying that the installation failed 'due to an error in the setup file'.

Did some diagnosis on the cause of this problem, examined the files that the installer put on the PC side. Found that there was an error in setup.ini - the Cabfiles= line was incorrect, the 2 cab files (one for each platform) was missing a comma in between them - was something like:

Cabfiles = application.MIPS.CABapplication.ARM.CAB

Changed it to:

Cabfiles = application.MIPS.CAB,application.ARM.CAB

And manually pointed CEAPPMGR at the edited version and it installed perfectly.

So just a small bug there I think?

One other thing - is it possible to control where on the PC the files in the executable end up? I see they go to "program files\application name", I would like them to go to "program files\activesync directory\application name" as this is where most PPC programs normally end up on the PC.

The reason I want this is that I also have a PC/WIN32 build of my application (packaged using the great Inno Setup!) and if a user has both the PC and PPC versions installed then it could be confusing as the default directory name for that app is close to the one generated by your program.

Thanks again for your help!

Another bug...

Download it again
Sorry for making you download again and again 15mb's

And yes, and the other feature you requested is implemented
In the builder tab, click 'Advanced Options' and there are some options, like the DefaultDirName and also the appearance options of Inno, like WizardImage, WizardSmallImage etc etc...

If everything is working ok, i'll check the other bug mentioned for the SQL installation into 2003 and i release the 1.8 version.

Regards,
Nick Protopapas

Great, worked!

Was able to install on both the platforms I have to support (MIPS/CE2.01+ and ARM/CE2.11+).

Re the feature to define the PC installation location - thanks for that! Just one thing, is it possible to use the % defined items here - eg %installdir%? And would it be possible to detect the MS Activesync dir in case it isn't in the default location - maybe create a %MSASYNC_DIR% defined item? I realise this may be a bit of work though so no worries if you can't do it - in 99% of cases I expect that ActiveSync will be in the default location!

Finally, one other little thing I noticed - to uninstall the app completely you have to do 2 things - use the 'Remove' button in the ActiveSync Add-Remove programs dialog, as well as use the PC Add-Remove programs function from Control Panel. If you don't do both these things then files or reg entries get left behind.

I believe that the ActiveSync Add-Remove programs function can invoke an uninstaller on the PC - but did a quick search on how this works and couldn't figure it out. I see there is a reg key that gets set in HKLM--Software--Microsoft--Windows CE Services--AppMgr--Apps--[app name]--Uninstall that looks like it has something to do with this process, but not sure how it works? (Note -- = slash, your forum sw doesn't seem to display back or forward slashes?)

Not a major for me, can just advise my users about the need for the 2 step unistallation process - so just a suggestion for the future!

Ok, the first feature is added. The variable for the active sync directory is {async}. In the left help window are listed all the available options. Additional to the Inno's variables I have added support and for the %xxxx% constants. For example you can combine them:

DefaultDestDir = {async}\%AppName% or
DefaultDestDir = {async}\%Provider%\%AppName% or
DefaultDestDir = {pf}\%Provider%\%AppName% and so on...

Download the executable and replace it into the PPCIC installation:
www.aperitto.com/media/downloads/ppcic_bin.rar

As for the second, i can't find out how it can be done. As I understood you want when the user uninstalls the program via activesync, then the uninstaller of the desktop pc to be launched ??

Regards,
Nick Protopapas.