deployment

Hot Topic

Copy protection?
Application Manager - Device Not Connected
Cannot Connect dialog balloon
Get Device ID from Desktop
what is MMI?
Creating a Virtual COM port for an application to connect to.
GPS sample and Windows Mobile 2005
DataGridTableStyle MappingName for Details BindingSource
Handling events in a multi-form application
Data inconsistent

Smart Device

Microsoft.WindowsMobile.PocketOutlook in PPC 2003 se
Windows Mobile 2005 - Can you reset/clear Database (EDB) sync flags/count to avoid sync with ActiveSync? Serious Bug in WM2005!!
Print a bitmap using sockets or httpwebrequest
Problem in Emulator
Method in searching record in 40 thousand records in Pocket PC
add control problem with multiple framework
Signature encryption and storing
Any ideas for VC code rewrite to evc 4.0
[SOLVED] xmldocument.load - Anyway to get bytes loaded?
Once again Problems with SerialPort class

deployment

Hi there.

I am using cabwizsp (VS.NET 2003) to deploy project cab file for SPV's (ARM devices)

I have noticed that not all the cab files will install/run on any MDA/PDA device because of the proc.

Currently by default it works for ARM procs (v4).

I noticed that there is a switch to specify what CPU type you wish to deploy the files to -

I need to create a cab file for the t-mobile MDA platforms. I think it is an intel XScaler proc. How would I deploy it for that type of device using the cpu-type switch

any guidance is much appreciated!

Thanks!




Answer this question

deployment

  • silverballz

    Ilya - signing the CAB file - what is this and how can I do it Or is this one of those things where the operator has to sign it or something Or are these 2 things different

  • Fradam

    ah - wow :) thanks alot! so where do I obtain cabwiz I have .NET Framework 1.1 installed and smartphone SDK... I am guessing I need PPC sdk

  • World

    No, the problem is not because of processor. XScale is an ARM CPU.
    In fact, starting from PocketPC 2002 _all_ Pocket PC and SmartPhone devices are ARM based.

    The problem here is what CAB format is different for SmartPhone and PPC, so CAB file created by cabwizsp (SP) won't install on PPC. Same is true for CAB file created for PPC- it won't install on SP.

    To solve this problem you need 2 different CABs - one created for PPC and another one for SmartPhone - one created by cabwizsp, another one by cabwiz from same INF.

    Note: Windows Mobile 5.0 can use unified CABs.

  • jmasramon

    Absolutely, we shipped NETCF V2 CAB for WM 5.0 this way. You need to use compressed CAB format in order to use it on SP. WM 5.0 PPC can handle both compressed and uncompressed (legacy) CABs, WM 5.0 SP can only handle compressed ones. So, compressed CAB would work on both. Also don't forget to properly sign CAB and it content or SP would reject it.



  • skilled_desinger

    Ilya Tumanov wrote:

    Note: Windows Mobile 5.0 can use unified CABs.

    Is this for sure I have the same problem, even if deploying on WM 5.0. The cabs created by cabwiz can not be used on wm5.0 smartphone edition.



  • Aqib

    Correct. I believe it also included with VS 2003.



  • deployment
Answer this question