You are currently offline, waiting for your internet to reconnect

How To Troubleshoot WinCE Application Installations

Summary
The Windows CE SDK provides tools for installing applications to a WindowsCE device. This process involves writing a setup INF file (.inf), whichwill be used by the Application Installation tools to create cabinet (CAB)files containing the files need for the application. An Application ManagerINI (.ini) file must also be created to register the CAB files with thedesktop Windows CE Application Manager. The following addresses commonproblems encountered with the Application Installation mechanism.
More information

CAB Wizard

  • To use a percent (%) character in an INF file, use %%, as specified in the Win32 SDK documentation. However, this method will not work under the [Strings] section.
  • INF files created for Windows CE cannot be used for installing to Windows 95 or Windows NT.
  • CAB files created for Windows CE cannot be used for installing to Windows 95 or Windows NT.
  • The Windows CE SDK-included files Makecab.exe and Cabwiz.ddf must be in the same directory as Cabwiz.exe.
  • Cabwiz.exe must be called with the full path.
  • Creating a CAB file using the Windows CE SDK-included file Makecab.exe doesn't work with Windows CE. You must use Cabwiz.exe (which uses Makecab.exe) to generate the CAB files for Windows CE.
  • CAB files cannot have the read-only file attribute.
  • Verify in the INF file that string lists do not have trailing commas or unnecessary/extra spaces.
          Invalid:  CopyFiles=Files.Common,  Files.Cpu,      Valid:    CopyFiles=Files.Common,Files.Cpu						

Application Manager (AppMgr)

  • When calling Ceappmgr.exe to register an application, use the full path for the location of the AppMgr INI file(s).
  • Use the "/report" parameter in debug versions to verify that AppMgr is using the correct information for the CAB files.

Errors When Registering Applications with Application Manager

  • Verify in the AppMgr INI file that the string list in the "CabFiles" key matches the actual CAB file name and relative path.
  • Verify in the AppMgr INI file that the string value in the "Component" key exists elsewhere in the INI file.
  • Verify that the desktop setup program is calling the correct AppMgr INI file, using a full path.
  • Verify in the AppMgr INI file that the string list in the "CabFiles" key contains no unnecessary spaces.
          Invalid:   CabFiles=app.sh3.cab,  app.mips.cab      Valid:   CabFiles=app.sh3.cab,app.mips.cab						

Miscellaneous

There are various third-party desktop setup programs that do not correctlyupdate the actual file sizes when overwriting existing files. Becausethe Application Manager verifies the actual file size with the embeddedfile size of the CAB file, make sure that the installed CAB file sizes arecorrect. To ensure this happens for future upgrade scenarios, you candelete the known, existing CAB files on a reinstallation scenario.
kbwince200
Properties

Article ID: 181007 - Last Review: 06/22/2014 18:47:00 - Revision: 3.0

  • kbhowto kbtshoot KB181007
Feedback
rAutoFirePV = 1; var varClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write("