OpenNETCF CAB Question

[Keith]

Maybe a post better suited for the OpenNETCF website - but
I know people here use OpenNETCF in some of their
applications - so I thought it would be an appropriate
post.

Obviously if they application uses OpenNETCF controls -
then it needs the OpenNETCF CAB/program file installed -
and WHICH one is required is based on processor of the
device. I was wondering if someone could offer some
clarification to some of the versions of the OpenNETCF.
Specifically:

OpenNETCF.SDF.PPC.ARMV4.CAB vs.
OpenNETCF.SDF.SMP.ARMV4.CAB vs.
OpenNETCF.SDF.WCE4.ARMV4.cab

Also - what are the differnces in these versions:
OpenNETCF.SDF.WCE4.MIPSII.CAB vs.
OpenNETCF.SDF.WCE4.MIPSIV.CAB
(I thought there was only one MIPS version)

Finally:
OpenNETCF.SDF.WCE4.SH3.CAB vs.
OpenNETCF.SDF.WCE4.SH4.CAB
(again - I thought there was only one SH version)

thank you.

 

[Alex Feinman [MVP]]

OpenNETCF.SDF.PPC.ARMV4.CAB - PPC2000/2002 (Win CE 3.0)
OpenNETCF.SDF.SMP.ARMV4.CAB - Smartphone 2003 (WinCE.NET 4.2)
OpenNETCF.SDF.WCE4.ARMV4.cab - WM2003 (WinCE.NET 4.2)

OpenNETCF.SDF.WCE4.MIPSII.CAB and OpenNETCF.SDF.WCE4.MIPSIV.CAB are
technically two slightly different versions of MIPS CPU (more follows)

OpenNETCF.SDF.WCE4.SH3.CAB and OpenNETCF.SDF.WCE4.SH4.CAB are two different
SuperH (Hitachi) CPUs. I am not 100% sure as for exact command set
difference but Windows CE development tools support compilation for these
two as separate platforms

Internally all PPC distributions are identical since NETCF IL code is
CPU-invariant. The difference is in a sdf_setup.dll shipped inside the cab
that must be CPU-specific, since it is unmanaged code.

 

[Neil Cowburn [MVP]]

Alex is exactly right with his response. The only reason there is so many
CAB variations is native setup DLL which is executed during the CAB
installation.

--Neil

 

[Keith]

Thank you both. Alex - that post was great - thank you
for the detail.

And the OpenNETCF.SDF.PPC.ARMV4.CAB - Also includes the
PPC 2003 - correct? What about the non V4 version
(OpenNETCF.SDF.PPC.ARM.CAB)? What does that cover?


How does a user go about doing determining CPU-type?
Given I understand that different PDAs require different
CABs based on their CPU - what is a good rule of thumb to
tell a novice user to determine his/her own CPU (so he/she
can load the appropriate CAB).

thank you.

 

[Alex Feinman [MVP]]

Actually it's rather simple. Every PPC2000-2003 and every smartphone on the
market (at least that I know of) is an ARM device.
The devices that use different hardware are non-PPC (Windows CE.NET)
devices, many of those custom built with PB. For those devices the user
typically would know what he is doing and what kind of hardware there is.
Then again, the correct cab will be deployed automatically depending on the
platform by both VStudio and CeAppMgr launched from the installer

 

[Peter Foot [MVP]]

The only exceptions are a few Pocket PC 2000 devices which were MIPS or SH3
based.

Peter

 

[Keith]

I hear you about the installer knowing the version that it
should install. Unfortunately - my user base cannot use
the MSI deployment method - at this time.

So most devices are ARM - so what is the difference
between ARM and ARMV4?
Is ARMV4 better?
Is it backward compatible with older devices?

thank you.