Hi everyone,

We have some problems with the wceload program to install CAB files on our
platform.

We use the Windows CE 4.2 OS for our ARMV4I platform using the pxa255 CPU.

We can't install cab files meant for the armv4i platform, Wceload simple
rejects them. And when we use the x86 CAB files he installs them, but off
course these can't work since we have an ARM processor.

How is it possible that the wceload program thinks he is running on a x86
platform? In the Platform builder help files I found that wceload uses the
GetSystemInfo() API to determine which platform it is running from but this
API returns the ARMV4I platform??? Then why doesn't wceload accepts these
ARMV4I CAB files?

Does anyone have a clue? Or what steps to follow to make this work?

Thanks in advance,
Peter.

Re: WceLoad problems by Steve

Steve
Tue Feb 10 06:13:02 CST 2004

You'll need to verify that the CAB files themselves are created properly. It
sounds like the "x86" CAB file is reporting itself as ARMV4I so WCELOAD will
install it just fine, but of course the app won't run.

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com



Re: WceLoad problems by mikethom

mikethom
Wed Mar 03 14:47:48 CST 2004

The other thing to note is the at GetSystemInfo API that is used on the
device side pulls the CPU information from the CPU unless you override it.
For example on all PPC (not sure about the recent ones) overide the OAL to
always report SA-1100 as the CPU type. This way 1 ID can be used to
install on all devices regardless of the actual CPU ID ( which always
changes).


Mike Thomson

Program Manager, Windows CE
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.