Intel® Mobile Platform SDK for Windows* Release Notes

• Download now!
• Overview
• Product Contents 
• Provider Development Kit (PDK) 
• What's New 
• System Requirements 
• How To Instructions 
• Known Issues and Limitations 
• License Information
  

Intel® Mobile Platform Software Development Kit 1.3 (Intel® Mobile Platform SDK) simplifies the task of adapting an application for use in a mobile environment. It provides a set of libraries and runtime components, along with a programming interface that is common across supported platforms and runtimes. Intel® Mobile Platform SDK 1.3 enables developers to quickly and efficiently deliver applications with mobility features while maximizing code reuse. 

When Intel® Mobile Platform SDK version 1.3 is installed, a number of directories and files are created under the product install directory. 

//Note: Uninstall all previous versions of Intel® Mobile Platform SDK from your system.

//Note: $INSTALL_PATH is the root directory where Intel® Mobile Platform SDK is installed. If you un-zip the package in the root driver, it is C:MPSDK

//Note: The following directory information is correct for Windows XP* SP2 Platform, Windows Vista* Business/Ultimate Edition, Windows Tablet PC* 2005, Windows Mobile* 5.0 PocketPC Edition, Windows Mobile* 5.0 Smartphone Edition, Windows Mobile* 2003 PocketPC Edition and Windows Mobile* 2003 Smartphone Edition.

Directory Information Summary

Intel® Mobile Platform Provider Development Kit (Intel® Mobile Platform PDK) provides you with a set of tools for writing DLL plug-ins, called providers, for Intel® Mobile Platform SDK runtime. Using Intel® Mobile Platform PDK, you can write providers that enhance the information provided by the default providers in Intel® Mobile Platform SDK runtime.

Directory Information of Intel® Mobile Platform PDK (available for Windows XP* SP2, Windows Vista* Business/Ultimate Edition, and Windows TabletPC* 2005)

Intel® Mobile Platform SDK 1.3 contains a set of APIs for mobile software development and several GUI tools that can be used to view and manage resources on mobile platforms. The following devices and capabilities are supported by Intel® Mobile Platform SDK:

Updates since Intel® Mobile Platform SDK 1.1

The following changes have been made since Intel® Mobile Platform SDK 1.1 version:

• Rfid/Gprs/Cdma only have the binding interface, no corresponding providers are supported in Intel® Mobile Platform SDK 1.3.
• Additional development environment are supported, including Microsoft Visual Studio* 2005, and .NET Framework 2.0.
• The package includes Intel® Mobile Platform Provider Development Kit, which enables you to develop plug-in modules for your own devices.
• Improved the performance by avoiding the multiple mobile servers co-existing in the system
• Supports linkage with different C runtime libraries, not only the dynamically loadable libraries (/MD and /MDd compiler options), but also the static libraries (/MT and /MTd compiler options).
• Detection of Intel® Virtualization Technology is supported.
• Detection of Intel® Centrino® processor technology is supported.

For more details, please refer to the Quick Start Guide.

For the Processor device, the following properties have not been implemented:

• MinFrequency
• MinVoltage
• MaxVoltage
• Multiplier
• MinMultiplier
• MaxMultiplier
• Temperature

The Network device has limitations for the following objects:

For DisplayAdapter device

• The get operation for the ScreenState property has not been implemented.
• The event Blanked & Unblanked has not been implemented.
• The Brightness property is not implemented.
• The Orientation is only supported on Windows* Tablet PC Edition 2005.

• At times, the runtime process may reach 100 percent of CPU utilization.  This is expected to only happen for a short period of time.
• If an observer is defined at the global scope, the system may throw an unhandled exception
• Some network applications may crash if certain bandwidth limiting applications are installed before Intel® Mobile Bandwidth Module component is installed.
• For Java* applications developed on top of Intel® Mobile Platform SDK, every call to  AddObserver() should have a corresponding call to  RemoveObserver().
• Intel® Mobile Bandwidth Module supports TCP/IP based applications. It may not be effective for applications based on other proprietary protocols.
• The Battery Removed event is not triggered on Compaq* Evo* N1015v models.
• Some battery information (such as temperature, circle count etc.) depend on OEMs. Users of our Intel® Mobile Platform SDK may not be able to get some information or may get incorrect information depending on the platform it is run on.
• Bluetooth* provider works on Windows* XP SP2. It supports only Microsoft* Bluetooth* stack.
• Intel® Mobile Platform SDK version 1.3 contains a specific 802.11 provider for Intel® PROSet/Wireless Software, which is superior to the default network provider implementation both in terms of information/events quality and quantity.

To set the PATH variable:

1. Find the location of MurocAPI.dll. It is usually installed in the C:Program FilesIntelWirelessBin folder.
2. Open Control Panel>System
3. Click the Advanced tab.
4. Click Environment Variable.
5. Find the PATH in the System Variables list.
6. Add the folder containing MurocAPI.dll to the PATH variable.

This new feature will not take effect if users install Intel® PROSet/Wireless Software after installing Intel® Mobile Platform SDK version 1.3 components unless the user manually includes Intel® PROSet/Wireless Software installation folder to the system searching path.

The following properties and events are only supported on platforms with Intel® PROSet/Wireless Software 9.0 installed:

• RadioAdapterInstance.HardwareRadioDisabled event
• RadioAdapterInstance.HardwareRadioEnabled event
• RadioAdapterInstance.SoftwareRadioDisabled event
• RadioAdapterInstance.SoftwareRadioEnabled event
• Protocol802_11Instance.StatisticsReset event
• Proto col802_11Instance.AuthenticationMode property
• Protocol802_11Instance.EncryptionModes property
• Protocol802_11Instance.EncryptionMode property
• Protocol802_11Instance.AssociationState property
• Protocol802_11Instance.SecurityModes property
• Protocol802_11Instance.Qos property
• Protocol802_11Instance.DataTxPackets property
• Protocol802_11Instance.DataRxPackets property
• Protocol802_11Instance.DataTxBytes property
• Protocol802_11Instance.DataRxBytes property
• Protocol802_11Instance. ResetStatistics ()

• Installing the 1.1 version of Intel® Mobile Platform SDK on a system running version 1.3 may leave both inoperable.
• Under some conditions the percent-based limits on an application or process will not be enforced by the bandwidth limiting component.
• The implementation of ConnectivityInstance.IsReachable() method has these limitations:
  • The method doesn't support proxy servers for TCP and ICMP protocols.
  • For HTTP protocol, the method IsReachable (Destination,ProxyUrl,UserName,Password,…) will return TRUE if the proxy returns an error page.
  • For FTP protocol, the method IsReachable(Destination,ProxyUrl,UserName,Password,…) supports USER user@site type proxy only
• The Java* SDK will load native library using the same class loader of the calling class.
  • Whenever the archive is already loaded by a class with another class loader, the loading will fail with an UnsatisfiedLinkError. 
  • Avoid using multiple class loaders to load Intel® Mobile Platform SDK library in the same Java* Virtual Machine.
• When using Intel® Mobile Platform SDK in a multithreaded application and dynamically loading Intel® Mobile Platform SDK libraries, initialize the xClass objects before starting the threads.
• For the first time, calling to ConnectivityInstance.IsReachable with a bad or unreachable Proxy URI, it returns false. Within 30 seconds, when the same Proxy URI becomes reachable, and then   call ConnectivityInstance.IsReachable again with the same Proxy URI. It returns false again even the destination URI is reachable through the proxy. This is a known limitation of Windows* XP. See the Microsoft website for more information. 
• In some situations, the transfer rate of system can exceed the real bandwidth limitation in Intel® Mobile Platform Bandwidth GUI.
• The C++ sample shipped with Intel® Mobile Platform SDK version 1.3 is in Microsoft* Visual C++* 2003. If using Visual Studio* 2005 to open the sample projects, after converting the project with Visual Studio* 2005, change project settings as follows: c/c++ > Language > Treat wchart as Built-in Type, set it as No.
• Running this version of Intel® Mobile Platform SDK version 1.3 on Windows Vista* Business/Ultimate Edition has the following limitations:
  • Only support Windows Vista* Business/Ultimate Edition. 
  • If UAC is turned on, Intel® Mobile Platform SDK applications (such as ToolsWin32InfoBrowserCLRIntelMobileBrowser.exe etc) need to run with administrator privileges. To run it with administrator privileges, right-click the application execute file and select Run as administrator from the popup menu (if the extension is .bat, please run the Command Prompt as administrator , then run the bat file), otherwise some information such as Network/Linkprotocol will not be retrieved
• To use those methods in BandwidthInstance which accepts a Socket parameter, the input socket should be associated with a local address first, which could be achieved by either calling connect (for TCP) or bind (for TCP and UDP).
• ProviderTester.exe only supports property/event validation. No method test is supported.
• ProviderTestGUI.exe only supports method test. No property/event is supported.
•  In this release, instance provider of the following devices can not be a "Scannable” instance provider.
  • DisplayAdapter
  • StorageAdapter
• “Platform” instance provider interface is not supported in this release.

Intel® Mobile Platform Software Development Kit 1.3 (Intel® Mobile Platform SDK) is licensed under the BSD License

http://www.opensource.org/licenses/bsd-license.php

Disclaimer and Legal Information

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.

UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.

Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.

The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.

Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or b y visiting Intel's Web Site.

Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See http://www.intel.com/products/processor_number for details.

BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino logo, Core Inside, FlashFile, i960, InstantIP, Intel, Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel Core, Intel Inside, Intel Inside logo, Intel. Leap ahead., Intel. Leap ahead. logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel Viiv, Intel vPro, Intel XScale, IPLink, Itanium, Itanium Inside, MCS, MMX, Oplus, OverDrive, PDCharm, Pentium, Pentium Inside, skoool, Sound Mark, The Journey Inside, VTune, Xeon, and Xeon Inside are trademarks of Intel Corporation in the U.S. and other countries.

* Other names and brands may be claimed as the property of others.

Copyright (C) 2004–2008, Intel Corporation. All rights reserved.

For more complete information about compiler optimizations, see our Optimization Notice.

Comments (1)

August 7, 2010 6:56 AM PDT richard

will try

Trackbacks (0)

Leave a comment