Re: Which cab file, arm, armv4 or armv4i?

#1

Thanks for the info!
A little confused, though. The FAQ basically says for PPC2000 or PPC2002,
use the cab file with arm extension; for PPC2003 (or Windows Mobile 2003)
and Windows CE .NET use the cab file with armv4 extension. What if I
upgraded my PPC2002 to PPC2003? Should I change the cab file from arm to
armv4 even the CPU(XScale) is the same? In other words, is it based on CPU
type or OS version? My original understanding is it is based on CPU type and
it is OS independent! Am I wrong?

"Daniel Moth" <dmoth74 (AT) hotmail (DOT) com> wrote

Quote:

See if this FAQ item helps:
http://msdn.microsoft.com/smartclient/understanding/netcf/FAQ/default.aspx#1.23

CF questions are best addressed here:
microsoft.public.dotnet.framework.compactframework

Cheers
Daniel
--
http://www.danielmoth.com/Blog/

"Robert" <rxl (AT) comcast (DOT) net> wrote in message
news:W42dnW3G67IejSHcRVn-uw (AT) comcast (DOT) com...
As you may know, when you build cab files, VB.NET generates a bounch of
cab files like the ones I mentioned on the subject line. Although CE
devices tell you what CPUs they use but they use the model number like
SA1110, PXA250..... My question is: how do you match these model numbers
to the catagories like arm, armv4, armv4i so that you can deploy the
right cab file to the device?

Any ideas?

#2

It's dependent on what the CE image was built for. The same exact processor
could support ARM, ARMv4, ARMv4I or ARMv4T

Also XScale isn't a processor, it's an Intel technology that many processors
fall into. They all have an ARM core, the xXXX stuff is basically the
instruction set used, and ARM and ARMv4 are really the same.

-Chris

"Robert" <rxl (AT) comcast (DOT) net> wrote

Quote:

Thanks for the info!
A little confused, though. The FAQ basically says for PPC2000 or PPC2002,
use the cab file with arm extension; for PPC2003 (or Windows Mobile 2003)
and Windows CE .NET use the cab file with armv4 extension. What if I
upgraded my PPC2002 to PPC2003? Should I change the cab file from arm to
armv4 even the CPU(XScale) is the same? In other words, is it based on CPU
type or OS version? My original understanding is it is based on CPU type
and it is OS independent! Am I wrong?

"Daniel Moth" <dmoth74 (AT) hotmail (DOT) com> wrote in message
news:eSfNbcE4EHA.3708 (AT) TK2MSFTNGP14 (DOT) phx.gbl...
See if this FAQ item helps:
http://msdn.microsoft.com/smartclient/understanding/netcf/FAQ/default.aspx#1.23

CF questions are best addressed here:
microsoft.public.dotnet.framework.compactframework

Cheers
Daniel
--
http://www.danielmoth.com/Blog/

"Robert" <rxl (AT) comcast (DOT) net> wrote in message
news:W42dnW3G67IejSHcRVn-uw (AT) comcast (DOT) com...
As you may know, when you build cab files, VB.NET generates a bounch of
cab files like the ones I mentioned on the subject line. Although CE
devices tell you what CPUs they use but they use the model number like
SA1110, PXA250..... My question is: how do you match these model numbers
to the catagories like arm, armv4, armv4i so that you can deploy the
right cab file to the device?

Any ideas?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Which cab file, arm, armv4 or armv4i?

Dotnet Framework (Compact Framework) microsoft.public.dotnet.framework.compactframework

Re: Which cab file, arm, armv4 or armv4i? - 12-12-2004 , 10:22 PM

Re: Which cab file, arm, armv4 or armv4i? - 12-12-2004 , 10:30 PM