However, we also have received some suggestions. The biggest issue is that MPSDK.zip is too complicated to build up development environment, coz it contains all the stuff for all the platforms that we support. We recognized this problem too, so we decided to split our MPSDK.zip into different packages or installers for different platforms eventually. Basically, we have installers for windows xp/vista/tablet pc, windows CE platform and Linux. We wish this is gonna help.

The first installer we launch is available for windows xp/vista/tablet pc platforms. By this installer, you can have all the binary files you need to develop your own code. It also contains the sample code for your reference. The bandwidth GUI and InforBrowser could be your daily software tools, they are very helpful. Anyway, I wish you will enjoy this new installer.

Your comments or questions are always welcome.

Unfortunately, beside the pretty downloading figure, we haven't got a customer yet, neither a bug, so I have been thinking what is the root of this problem. After building a sample code out of MPSDK package by myself, I found the proceed of setting runtime and development environment is a bit the inconvenient for customer and maybe it is not crystal for our customer to use this big package, so I have drafted a tutorial for how to build up runtime environment for MPSDK for customer's convenience.

This tutorial will guide you through the whole process of building development environment

Note: please use this tutorial with "Quick Start Guide", this tutorial is for CLR only

1. Build Framework.

$(MPSDKROOT)\ Projects\Win32\VS2003\Framework

Open VS2003 working interface and set up VC++ Directories.

Please note that:

$(PLATFORMSDKROOT)\Include

$(DDKROOT)\inc\wxp

$(DDKROOT)\inc\ddk\wxp

$(JDKROOT)\include

$(JDKROOT)\include\win32

These paths need to be put at the bottom of the list, otherwise you might encounter building errors.

2. Building other projects

After successfully building Framework, you can build bandwidth, provider, CLR binding and CLR samples by the same way. After all solutions have been built successfully, service can be registered and started now

Note: when you are building CLR sample solution, you need to run Samples\Win32\CLR\bin\copy_dll.bat before building the solution.

3. Set up runtime environment for the whole system

Starting service.

After sevice has been started successfully, you can start developing your code with our SDK smoothly.

Follow above steps, you should be able to set up runtime environment successfully. If you still have issues, please let me know.

At the meanwhile, we are thinking about to build installers for both of runtime and SDK for customer's convenience, thus the customers can put more efforts on development. I wish the installers could be ready very soon.

Here are URLs for iMPSDK resources:

• Project site on ISN: www.intel.com/software/mpsdk/; http://ossmpsdk.intel.com/
• Project on Sourceforge: http://sourceforge.net/projects/mpsdk
• An overview of iMPSDK 1.2: http://softwarecommunity.intel.com/articles/eng/1331.htm
• Software download: http://ossmpsdk.intel.com/download.php
• tech discussion forum: http://ossmpsdk.intel.com/forums.php

In the past few months, our engineering team restructured the entire software and made it to be an Open Source project. During this procedure, we learned a lot of experience from our earlier work. Because we had to remove some commercial parts from old package, we found some problems that we didn't mention before. Those experience will help us to improve the quality of the product in the future.

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.2.
• 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.

We added RFID function into 1.2 Open Source version, which was not existing in 1.1. However we only provide some basic APIs, no providers are supported.

Based on 1.2 SDK, we developed a Demo, which can help you to manage network connections automatically. Users can pre-define some policies to adapt his device's environment, such as your Notebook or handheld. Those policies could be "cost", "Bandwidth" or "PowerConsumption". To see this Demo, please go to http://softwarecommunity.intel.com/videos/home.aspx?fn=100032 With this tool, you can easily adapt to multi-networking environment and switch the connections (such as cable connection, wireless, GPRS, etc) seamlessly. This is just one example, we will more demos available later on. For more information, please pay attention on our official website: www.intel.com/software/mpsdk/

Hello, I'm Joe (Zhiheng) Zhao, a technical consulting engineer from the Intel SSG Group. My responsibility is to provide professional technical support for the IMPSDK, which soon will be released as an open source project. If you are interested in mobile software development, I will be very happy to talk with you.

We believe the IMPSDK is a fantastic chance for you to experience the fun of mobile software development. We have found the best, cost-effective solutions for mobile users, especially mobile software developers, to adapt into the mobile business rapidly, efficiently, and seamlessly. The IMPSDK contains all of our collected efforts and creative ideas. Version 1.0 was released in March 2005 and version 1.1 in April 2006, which soon will be updated by the version 1.2 open source project. Our products have already gained positive feedback and a good reputation, but we want to hear more from you to improve our product.

I'll answer your IMPSDK questions on my Blog and respond to your comments and suggestions.