Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 824409 - Last Review: March 27, 2007 - Revision: 1.5
You receive an error message when you try to install a mobile software application on a device
When you try to install Microsoft Windows Mobile 2003 software for Pocket PC
2003 or Microsoft Windows Mobile 2003 software for Smartphone 2003 on a supported device, you receive the following error
message on the desktop computer:
Unsupported Device
Type
Provider AppName does not support the connected device
type. Application Manager will make the application available for installation
when a supported device type is connected.
<OK>
Alternatively, you may receive the following error message on the device:
App
Install
Info name.CAB failed to install on your
device.
<OK>
This problem occurs only if the
CAB file was generated by using either the Cabwiz.exe tool or the Cabwizsp.exe tool and the
PlatformString
directive.
This problem occurs because the original equipment manufacturer (OEM) of the Microsoft Pocket PC device has not implemented the SPI_GETPLATFORMVERSION input/output control (IOCTL). Without this IOCTL, the Application Manager tool (CeAppMgr) and the
device Application Installer (Wceload.exe) cannot determine the platform
version of the device. This lack of information causes the Application Installer to report that the
application does not support the device.
You can restrict CAB platform support without using the
platform section. Use a setup DLL for Microsoft Windows Installer, determine the type of
connected device, and then install only the CAB file that you want. Alternatively, let the user choose the specific
package to install.
To work around this issue, follow these steps:
- Name the CAB files uniquely. This important step enables the user to choose the correct package to install either manually or by using the Add/Remove
Programs item in Control Panel.
- If you are using a Windows Installer (.msi) package setup
DLL, follow these steps:
- If a device is connected, use the Remote access API (RAPI) to obtain the version of the platform (CeVersion),
and then run the CeAppMgr tool to install only the appropriate .ini file.
Note CeVersion 4.20
corresponds to platform 3.0 of either Pocket PC or Smartphone. - Regardless of whether a device is connected, register all
packages by using the CeAppMgr /register command.
Note If the user has
multiple mobile devices, this important step enables the user to install different packages by using the ActiveSync Add/Remove Programs tool.
Microsoft is working with OEMs to make sure that all new
Windows Mobile devices implement the SPI_GETPLATFORMVERSION IOCTL.
This problem occurs in some of the early OEM releases of Windows Mobile 2003. This problem is not expected to occur on later versions of read only memory (ROM) images.
If you are experiencing this problem, contact the OEM of your Pocket PC or Smartphone device to determine whether an updated ROM image is available.
The platform section of a CAB information (.inf) file is new for Windows
Mobile 2003.
For more information about the Cabwiz.exe tool, the Cabwizsp.exe tool, and the platform
information, see the software development kit for either Pocket PC 2003 or
Smartphone 2003, or visit the following MSDN Web site:
For more information about the implementation of the SPI_GETPLATFORMVERSION IOCTL, visit the following MSDN Web site:
For information about your hardware manufacturer, visit the following Web site:
APPLIES TO
- Microsoft Windows Mobile 2003 software for Pocket PC Standard Edition
- Microsoft Windows Mobile 2003 software for Smartphone
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please