The application probably requires that security be lowered. So to be able to run it, the device needs to have security lowered at least to the level at which the user is asked for permission when he/she is running an unsigned executable. In the context of Windows Mobile security, it means that the device's security configuration needs to be set to Two-Tier-Prompt
, One-Tier-Prompt
or Security-Off
(see MSDN for more details).
Changing of the security configuration might require device manufacturer's or operator's assistance.
In some cases it can be done by the user. Some of them are listed below:
If the user has a registry editor application which can run on
the device and can change the device registry (such application
needs to be signed by a certificate which is trusted by the device
though, or the same issue will repeat itself.)
The device has installed Microsoft Windows Mobile development
certificates.
The device allows the user to install the Microsoft Windows
Mobile development certificates.
Of the above, 2 and 3 are more than likely be the case; if so then try the following:
Install Windows Mobile SDK (Here)
Install <WM SDK>/Tools/Security/SDK Development
Certificates/Certs.cab
on the device.
Go to <WM SDK>/Tools/PocketPC/Security/Security Configuration
and
use one of the cpf
file to change the device's security
configuration (see the Readme File located at <WM
SDK>/Tools/PocketPC/Security/Security Configuration/ReadMe.txt
)
Hope this helps someone, even-though I'm a year or so late...