From: Robert Scott on
Signed CAB files cannot be installed on older devices if ActiveSync is older
than version 4, right? So here is what I would like to do about that.

I am using an old version of the Wise installer to build my installation
program. The Wise installer follows a scripting language that provides the
ability to query the registry to find the path to CEAppMgr.exe. Furthermore, it
provides a means to query the FileVersion resource in any file such as
CEAppMgr.exe. When I do this I get "4.1.4841.0". I have ActiveSync 4.1.0 (build
4841) on my computer, so it seems to make sense. The Wise installer scripting
language also provides string processing to take the first character of the
Version string ("4" in this case) and compare it with a fixed string. Finally,
I can select one of two CAB files (signed or unsigned) to install on the host
computer base on the first character of the Version resource of CEAppMgr.exe.

So my question is am I right to assume that any version of CEAppMgr that starts
with 1, 2, or 3 is to be given the unsigned CAB and all others are to be given
the signed CAB?

We also distribute our application as a CAB file. For that option I will just
leave it up to the customer to decide which file he should use. But the
majority of our customers use the Windows installation program which uses
CEAppMgr. For those customers I would like to make the issue of signed vs.
unsigned CAB files transparent to them.

Robert Scott
Ypsilanti, Michigan