I have created a setup program based on the following MS Article:
http://msdn.microsoft.com/library/de...deployment.asp

Everything is working great with one major exception. When CEAppMgr is
executed it copies the incorrect CAB file to the Pocket PC device. For
example it tries to install the X86 CAB on my iPaq ARM based Pocket PC.
What it is doing is copying the first CAB file listed in the setup.ini file
that is passed to the CEAppMgr. If I change the order of the CAB files
listed in the setup.ini file to list the ARMV4 CAB file first then
everything works.

What might I have missed. I don't want to have to distribute a different
setup for every processor type I need to support.

Thanks
Hank

you haven't missed anything - an MS rep mentioned this a few weeks ago and
the fact that not all of the .NET CF cab files
have valid versions and processors specified (MIPS are a particular
problem) - most people use RAPI to do the .NET CF files

even MS do when they released the SP1 and the aborted SP2 (now back in beta)

"HankC" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I have created a setup program based on the following MS Article:
>
http://msdn.microsoft.com/library/de...deployment.asp
>
> Everything is working great with one major exception. When CEAppMgr is
> executed it copies the incorrect CAB file to the Pocket PC device. For
> example it tries to install the X86 CAB on my iPaq ARM based Pocket PC.
> What it is doing is copying the first CAB file listed in the setup.ini
file
> that is passed to the CEAppMgr. If I change the order of the CAB files
> listed in the setup.ini file to list the ARMV4 CAB file first then
> everything works.
>
> What might I have missed. I don't want to have to distribute a different
> setup for every processor type I need to support.
>
> Thanks
> Hank
>
>
>