Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

My CAB file installed fine on Windows Mobile 2003 Second Edition. Why doesn it work on Windows Mobile 5.0?

April 26, 2017CAB edition file Fine installed mobile Windows

0

Posted

My CAB file installed fine on Windows Mobile 2003 Second Edition. Why doesn it work on Windows Mobile 5.0?

1 Answer

0

Posted

Starting with Windows Mobile 5.0, the installers for Pocket PC and Smartphone were merged for consistency purposes. As a result, the install behavior across both platforms is now more uniform, and a common set of command line options is supported. Command line options for wceload.exe are fully documented in the platform SDKs. On Windows Mobile 5.0, any attempt to reinstall an application will prompt the user to remove the existing installation first. This prompt is a change from previous versions of Pocket PC that left the existing installation intact during reinstallation. If you build a .cab file to patch or upgrade an application, be sure to package a .cab file that maintains its own unique install information (for example, unique AppName) to avoid removing the existing program components. INF files that list anything other than DLLs (such as EXEs) in the CESelfRegister section fails on Windows Mobile 5.0. INF files that set registry values to numbers outside of the range of signed