Intel® Mobile Platform SDK 1.2 Quick Start Guide

Submit New Article

August 25, 2008 12:34 PM PDT


 

Folder Structure

Directory

Content

Bin

Intel® Mobile Platform Software Development Kit (Intel® Mobile Platform SDK) runtime binaries, separated according to platform.

Docs

Intel® Mobile Platform SDK Programmer's Guide

Intel® Mobile Platform Provider Development Kit (Intel® Mobile Platform PDK) Programmer's Guide

Intel® Mobile Platform SDK Release Notes and legal documents.

Projects

Intel® Mobile Platform SDK project files, separated according to development environment

Src

Intel® Mobile Platform SDK source code, separated into two categories:

Win32*

Windows CE*

  • Win32

Framework: source code for infrastructure

Providers: source code for providers include: Battery, Display, Network, Platform, Processor, Rfid, Storage, Microsoft* Bluetooth* and Context

Bandwidth: source code for Bandwidth Module

Binding: source code for C++, CLR and Java* binding layer

Binding11: source code for Intel® Mobile Platform SDK version 1.1 interface of C++, CLR and Java* binding layer

 

  • Windows CE*

Framework: source code for infrastructure

Providers: source code for different include: Battery, Display, Network, Platform, Processor, Storage, Microsoft* Bluetooth*, Symbol Network and Context

Bandwidth: source code for Intel® Mobile Bandwidth Module

Binding: source code for C++, CLR and Java* binding layer

Binding11: source code for Intel® Mobile Platform SDK version 1.1 interface of C++, CLR and Java* binding layer

Samples

Intel® Mobile Platform SDK samples and Intel® Mobile Platform PDK samples

Tools

Intel® Mobile Platform SDK tools include Info-Browser, BandwidthGUI and Intel® Mobile Platform PDK test Tools

 

How to Build Sources

Win32*

Software Requirement for Building Process:

  • Microsoft* Visual Studio* .NET 2003
  • Microsoft* Platform SDK for Windows XP SP2
  • Windows* Driver Development Kit 2600
  • Java* Development Kit 1.4.2 or later

Visual Studio* 2003 Environment Setting

Add the following paths to Vistual Studio* 2003 environment variables:

Tools->Options->Projects->VC++ Directories->Includes Files

$(PLATFORMSDKROOT)Include
$(DDKROOT)incwxp
$(DDKROOT)incddkwxp
$(JDKROOT)include
$(JDKROOT)includewin32
Tools->Options->Projects->VC++ Directories->Library Files
$(DDKROOT)ilibwxpi386
$(PLATFORMSDKROOT)lib

Build Process

  • Please accord to the following steps to build Intel® Mobile Platform SDK source code:
  • Build Framework  (ProjectsWin32VS2003FrameworkIntelMobileFramework.sln)
  • Build Bandwidth Module (ProjectsWin32VS2003BandwidthBandwidth.sln)
  • Build Providers (ProjectsWin32VS2003ProvidersProviders.sln)

Build Binding

  • C++ Binding (ProjectsWin32VS2003BindingC++IntelMobileCPP.sln)
  • CLR Binding (ProjectsWin32VS2003BindingCLRIntelMobile_CLR_Binding.sln)
  • Java Binding

Native Library: ProjectsWin32VS2003BindingJavaIntelMobileJNI.sln

Java: ProjectsWin32VS2003BindingJavainuild.bat

Windows Mobile* 2003

Software Requirement for Build Process

  • eMbedded Visual C++* 4.0 with Service Pack 4
  • Microsoft Windows Mobile* 2003 SDK for Pocket PC
  • Microsoft Windows Mobile* 2003 SDK for Smartphone
  • Java* 2 SDK, version 1.4.2 or later      

eMbedded Visual C++* 4.0 Environment Setting:

  • Tools->Options->Directory->Smartphone2003->Win32(WCE ARMV4)->Include files, add directory:$(PROGRAM FILES)Windows CE Toolswce420POCKET PC 2003mfcinclude
  • Tools->Options->Directory->Pocket PC 2003->Win32 (WCE ARMV4)->Include files, please add directories:$(PROGRAM FILES) J2SDK1.4.2INCLUDE$(PROGRAM FILES)J2SDK1.4.2INCLUDEWIN32

Build Process

Build the following projects in the sample compile mode, either debug or release.

  • Build framework workspace:
    ProjectsWinCEEvc4.0FrameworkIntelMobileFramework_CE.vcw
  • Build bandwidth workspace:
    ProjectsWinCEEvc4.0Bandwidthw_wince.vcw (Pocket PC2003)
    ProjectsWinCEEvc4.0Bandwidthw_smartphone.vcw (Smartphone 2003)
  • Build providers workspace.
    ProjectsWinCEEvc4.0Providerspro viders.vcw

Build Bindings

  • C++ Binding
    ProjectsWinCEEvc4.0BindingC++IntelMobileCPP.vcw
  • CLR Binding
    ProjectsWinCEEvc4.0BindingCLRIntelMobileWrapper_CE.vcw
    ProjectsWinCEEvc4.0BindingCLRIntelMobileCLR_CE.sln+ CopyDll_PPC.bat (Windows Mobile* 2003 PocketPC Edition)
    ProjectsWinCEEvc4.0BindingCLRIntelMobileCLR_Smartphone.sln + CopyDll_Smartphone.bat (Smartphone2003)
  • Java* Binding (only Pocket PC 2003)
    ProjectsWinCEEvc4.0BindingjavaIntelMobileJNI_CE.vcw
    ProjectsWinCEEvc4.0Bindingjavauild.bat

Windows Mobile* 5.0

Required Software for Build Process:

  • Microsoft* Visual Studio* 2005
  • Windows Mobile* 5.0 for Pocket PC SDK.msi
  • Windows Mobile* 5.0 for Smartphone SDK.msi
  • Java* 2 SDK, version 1.4.2 or later           

Visual Studio* 2005 Setting:

Tools->Options->Project and Solution->Windows Mobile 5.0 Pocket PC(ARMV4) ->Include files, please add directories:

$(PROGRAM FILES) J2SDK1.4.2INCLUDE
$(PROGRAM FILES)J2SDK1.4.2INCLUDEWIN32

Build Process

  • Build framework workspace:
    ProjectsWinCEVS2005FrameworkIntelMobileFramework_CE.sln
  • Build bandwidth workspace:
    ProjectsWinCEVS2005Bandwidth Bandwidth.sln
  • Build providers workspace.
    ProjectsWinCEVS2005Providersproviders.sln

Build Bindings

  • C++ Binding
    ProjectsWinCEVS2005BindingC++IntelMobileCPP.sln
  • CLR Binding
    ProjectsWinCE VS2005BindingCLR IntelMobileCLR_CE.sln
    ProjectsWinCEEvc4.0BindingCLRIntelMobileCLR_CE.sln+ CopyDll_PPC.bat (Windows Mobile* 5.0 Pocket PC)
    ProjectsWinCEEvc4.0BindingCLRIntelMobileCLR_Smartphone.sln + CopyDll_Smartphone.bat (Windows Mobile* 5.0 Smartphone)
  • Java Binding(only Windows Mobile* 5.0)
    ProjectsWinCEVS2005Bindingjava IntelMobileJNI_CE.sln
    ProjectsWinCEEvc4.0Bindingjavauild.bat

How to Setup/Clean Runtime Environment

Intel® Mobile Platform SDK version 1.2 also releases the binaries required for the runtime environment. All binaries are under the directory Bin.

Win32*

Follow these steps to setup the runtime environment:

Customer Environment Path Variables

  • $(MPSDKROOT)BinWin32Framework
  • $(MPSDKROOT)BinWin32BindingC++
  • $(MPSDKROOT)BinWin32BindingJava
  • $(MPSDKROOT)BinWin32BindingCLR
  • $(MPSDKROOT)BinWin32Binding11C++
  • $(MPSDKROOT)BinWin32Binding11Java
    • < li>$(MPSDKROOT)BinWin32Binding11CLR

Register Bandwidth LSP

Call $(MPSDKROOT)BinWin32BandwidthLSP_Install.bat
Restart your machine, or some LSP functions will not run properly.

Register Intel® Mobile Platform SDK Services


For Windows XP*: $(MPSDKROOT)BinWin32FrameworkIntelMobile_Server.exe /Service
For Windows Vista*: $(MPSDKROOT)BinWin32FrameworkIntelMobile_Server.exe /Regserver
Regsvr32 /s  $(MPSDKROOT)BinWin32FrameworkIntelMobile_d.dll
Regsvr32 /s  $(MPSDKROOT)BinWin32FrameworkIntelMobile.dll
$(MPSDKROOT)BinWin32FrameworkIMPPolicyService.exe -install

Start Intel® Mobile Platform SDK Services

net start IMPPolicyService

Network provider supports settable functions only on Windows XP* SP2. To use the setting functions, you must stop the service of "Wireless Zero Configuration" in Windows XP* SP2 ,otherwise you need to follow following steps to install a driver. This section assumes the driver target name is IMPSUNET.

  • Install Microsoft® Windows® Driver Development Kit (DDK) for Windows XP* SP2 (build number: 2600).
  • Install the sample/src component
  • Go to $WINDDK2600src etwork dis disuiosys folder
  • Open ntdisp.c and using the code 
NDIS_STRING                     protoName = NDIS_STRING_CONST ("IMPSUNET");  
Open Nuiouser.h
Replace FILE_ANY_ACCESS with FILE_READ_ACCESS | FILE_WRITE_ACCESS
Open ndisuio.rc and using the following definitions.
#define VER_INTERNALNAME_STR        "IMPSUNET.SYS"
#define VER_ORIGINALFILENAME_STR    "IMPSUNET.SYS"
Open the “sources “ file
Replace the TARGETNAME=impsunet.
  • Build and install the target driver file.

Please accord to the following steps to clean runtime environment:

  • Stop Intel® Mobile Platform SDK Services

net stop IMPPolicyService
For Windows XP* SP2 only: net stop IntelMobileService

  • Un-register Intel® Mobile Platform SDK Services

$(MPSDKROOT)BinWin32FrameworkIMPPolicyService.exe -remove
$(MPSDKROOT)BinWin32FrameworkIntelMobile_Server.exe /Unregserver
Regsvr32 /s /u  $(MPSDKROOT)BinWin32FrameworkIntelMobile_d.dll
Regsvr32 /s /u  $(MPSDKROOT)BinWin32FrameworkIntelMobile.dll

  • Un-register Bandwidth LSP

Call $(MPSDKROOT)BinWin32BandwidthLSP_Remove.bat
Restart your machine. Otherwise, some LSP functions will still work and could impact your reinstall.

Remove the following path from Path customer environment variable

  • $(MPSDKROOT)BinWin32Framework
  • $(MPSDKROOT)BinWin32BindingC++
  • $(MPSDKROOT)BinWin32BindingJava
  • $(MPSDKROOT)BinWin32BindingCLR
  • $(MPSDKROOT)BinWin32Binding11C++
  • $(MPSDKROOT)BinWin32Binding11Java
  • $(MPSDKROOT)BinWin32Binding11CLR

Remark:
Intel® Mobile Platform SDK runtime binaries are built on Visual Studio* 2003. Copy the following components of the Microsoft* C Runtime Library to %SYSTEMROOT%system32:

  • msvcp71.dll
  • msvcp71d.dll
  • msvcr71.dll
  • msvcr71d.dll

Install Microsoft* Visual Studio* .NET 2003 before setting up or cleaning the runtime environment.

Microsoft Windows CE*

Framework Core Pre-works

Follow these steps every time you run any components of Intel® Mobile Platform SDK.
Set the running environment of your mobile device:

  • Copy Bin$(Platform)Framework*.dll to Device $Windows folder
  • Copy SrcWinCEFrameworkinproviders.xml to Device $Windows folder
  • Copy SrcWinCEFrameworkin IntelMobileErrorInfo.property to Device $Windows folder
  • Copy SrcWinCEFrameworkin IntelMobileWirelessLookup.sys to Device $Windows folder
  • Copy the MFC80U.dll and msvcr80.dll to $Windows folder (Windows Mobile* 5.0 platform)
    Folder: $(Program file)Microsoft Visual Studio 8VCceDll$(ARMV4i)

Bandwidth Module Core Pre-works

This work must be done if you need a bandwidth module function, such as BandwidthPolicyGUI.exe, or Get ContextClass.Bandwidth Instance.

  • Copy Bin$(Platform)andwidth*.dll to Device $Windows folder
  • Copy Bin$(Platform)andwidth*.dll (release version) to Device $Windows folder
  • Copy Bin$(Platform)andwidth*.exe to Device Bandwidth folder
  • Copy Tools$(Platform)BandwidthGUIBW Policy.exe to Device Bandwidth folder
  • Copy Tools$(Platform)BandwidthGUIBWPolicy.htm to Device $Windows folder
  • Launch impbwi.exe and install LSP
  • Launch BwSvcInstall_CE.exe and install Bandwidth update service
  • Restart mobile device
  • Launch BW Policy.exe

How to Run C++ Infobrowser

  • Copy Bin$(Platform)BindingC++*.dll to Device $Windows folder
  • Copy Tools$(Platform)InfoBrowserC++Infobrowser.exe to Device Tools folder
  • Launch ToolsInfobrowser.exe on your device.

How to Run CLR Infobrowser

  • Copy Bin$(Platform)BindingCLR*CLR_CE12.dll to Device Tools folder
  • Copy Bin$(Platform)BindingCLR IntelMobileWrapper_CE12.dll to Device $Windows folder
  • Copy Tools$(Platform)InfoBrowserCLRInfobrowser.exe to Device Tool s folder
  • Launch ToolsInfobrowser.exe on your device.

How to Run Java* Infobrowser

  • Install IBM* J9* Java Virtual Machine on your mobile device
  • Copy Bin$(Platform)BindingJava IntelMobile12.jar to Device Folder
  • Copy Tools$(Platform)BindingJavaInfobrowser.jar to Device folder
  • Copy Bin$(Platform)BindingJavaIntelMobileJNI_CE12.dll to Device $Windows folder
  • Write a shortcut file , which context is “
    123#"Program FilesJ9FOUN10inj9" -Djava.library.path=Windows -cp "Infobrowser.jar;IntelMobile12.jar" ConsoleTest
  • Copy the short cut file to your device, and run it.

 

Help Script
  • CopyBinaries.bat copies all the binaries you build from upper build process to Bin directory. All binaries are released with release format, so do not call this bat after a debug build.
  • SetRuntimeEnv.bat sets up the runtime environment for Windows XP*. SetRuntimeEnv_Vista.bat sets up the runtime environment for Windows Vista* systems. If UAC is turned on, run SetRuntimeEnv_Vista.bat with administrator privileges. To run it with administrator privileges, right-click SetRuntimeEnv_Vista.bat and select Run as administrator from the popup menu.
  • ClearRuntimeEnv.bat will help to clean runtime environment for Windows XP*. ClearRuntimeEnv_Vista.bat cleans the runtime environment for Windows Vista* systems. If UAC is turned on, run ClearRuntimeEnv_Vista.bat with administrator privileges. To run it with administrator privileges, right-click ClearRuntimeEnv_Vista.bat and select Run as administrator from the popup menu.
  • Remark:
    Call SetRuntimeEnv(_Vista).bat and ClearRuntimeEnv(_Vista).bat orderly and in pairs. Wrong calling sequence may cause some unpredictable errors, but can be ignored.

Samples

Win32*

After successfully building all source code and setting up Intel® Mobile Platform SDK runtime environment, you can start to build and run samples.

Build Samples

Under Samples directory, open the following solution or bat to build Intel® Mobile Platform SDK and Intel® Mobile Platform PDK samples

  • C++ (SamplesWin32C++Samples.sln)
  • CLR (SamplesWin32CLRSamplesCLR.sln)
    Need to run SamplesWin32CLRincopy_dll.bat before building the solution
  • Java* (SamplesWin32JavauildSample.bat)
  • Intel® Mobile Platform PDK (SamplesWin32PDKSamples.sln)

Run Samples
  • C++: all sample application will be copied to SamplesWin32C++in directory, you can run them directly
  • CLR: all sample application will be copied to SamplesWin32CLRin directory, you can run them directly
  • Java*: all sample application will be copied to SamplesWin32Javain directory, using runSamples.bat to run the samples
  • Intel® Mobile Platform PDK: using Intel® Mobile Platform PDK tools under ToolsWin32PDK to test the sample providers you built

Windows Mobile* 2003

Build Sample code

  • Pocket PC2003
    C++
            SamplesPPC2003C++SamplesSamples_CE.vcw
  • CLR
             CopyDll.bat
             SamplesPPC2003CLRSamples_CE SamplesCLR_CE.sln
  • Java*
             SamplesPPC2003JavaSamples_CEuildSamples.bat
  • Smartphone 2003

C++
        SamplesSmartphone2003C++SamplesSamples_CE.vcw

  • CLR
            CopyDll_Smartphone.bat
            SamplesSmartphone2003CLRSamples_CE SamplesCLR_Smartphone.sln

Run Sample code

  •       Please refer to the section of "Run Sample Code" in Windows Mobile* 2005

Windows Mobile* 2005

Build Sample code

  • C++
            SamplesWM5.0C++Samples Samples.sln
  • CLR
            CopyDll.bat+SamplesWM5.0CLRSamples_CE SamplesCLR_CE.sln (Windows Mobile* 5.0 Pocket PC)
            CopyDll_Smartphone.bat+ SamplesWM5.0CLRSamples_SmartphoneSamplesCLR_Smartphone.sln (Windows Mobile* 5.0 Smartphone)
  • Java*
            SamplesWM5.0JavaSamples_CEuildSamples.bat

Run Sample code

How to run C++ Sample code

  • Copy Bin$(Platform)BindingC++*.dll to Device $Windows folder
  • Copy your C++ Sample**.exe to Device Samples folder
  • Copy the C++ UIHelper.dll to Device $Windows
  • Copy the MFC Debug dlls into Device $Windows folder if you run a debug version sample code.
  • mfcce300d.dll,oldce300d.dll (Windows Mobile* 2003 PocketPC Edition)
  • Folder $(Program file)Windows CE Toolswce420POCKET PC 2003MfcLibarmv4
  • MFC80UD.DLL, msvcr80d.dll,atl80.dll (Windows Mobile* 5.0)
  • Folder: $(Program file)Microsoft Visual Studio 8VCceDll$(ARMV4i)
  • Launch Sample**.exe on your device

How to run CLR Sample code

  • Copy Bin$(Platform)BindingCLR*CLR_CE12.dll to Device Samples Folder
  • Copy Bin$(Platform)BindingCLR IntelMobileWrapper_CE12.dll to Device $Windows folder
  • Copy your CLR Sample**.exe to Device Samples folder
  • Copy the CLR UIHelper.dll to Device Samples folder
  • Launch Sample**.exe on your device

How to run Java* Sample code

  • Install IBM* J9* Java Virtual Machine on your mobile device
  • Copy Bin$(Platform)BindingJava IntelMobile12.jar to Device Folder
  • Copy Bin$(Platform)Binding JavaIntelMobileJNI_CE12.dll to Device $Windows folder
  • Copy your Java* Sample*.jar to Device folder
  • Copy the Sample run short cut to Device folder
  • Launch Sample shortcut on your device

How to Develop

Win32*

Set up the C++ Development Environment

  • Click on Tools > Options - Projects > VC++ Directories > Include Files.
  • Add the following to the Include path:
    $(MPSDKROOT)BinWin32BindingC++include
  • Click on Project >Properties.
  • Click on Configuration Properties > C/C++ > Language.
  • Locate the variable "Treat wchar_t as Built-in Type".

If the value of the variable is Yes (/Zc:wchar_t), set it to No

  • Click on Configuration Properties>Linker>General
    Add the following to the Additional Library Directories path: $(MPSDKROOT)BinWin32BindingC++lib
  • Use IntelMobileCPP12.lib as the link library.

If the application use any device/context information, it also needs to use the library of the corresponding device or context, such as BatteryCPP12.lib, ContextCPP12.lib as the link library

Set the CLR Development Environment

  • Add $(MPSDKROOT)ProjectsWin32VS2003Binding CLRBinIntelMobileCLR12.dll and the corresponding device/contexts' assembly (e.g. BatteryCLR12.dll, ContextCLR12.dll, etc) into the project references

Set the Java* Development Environment

  • Add $(MPSDKROOT)ProjectsWin32VS2003Binding JavaBinIntelMobile12.jar and the corresponding device/contexts' jar files (e.g. IMBattery12.jar, IMContext12.jar, etc) into the environment variable CLASSPATH

Windows CE*
  • $Windows = Windows (Windows Mobile* 2003 PocketPC Edition.Windows Mobile* 5.0)
           $Windows = StorageWindows (Smartphone2003)
  • Some Windows Mobile* 5.0 devices include the MFC dll (MFC80U.dll and Msvcrt80.dll), often stored in $Windows and $WindowsOEM. If you can not run the Infobrowser and Sample code, you need replace them with the one in $(Program file)Microsoft Visual Studio 8VCceDll$(ARMV4i) folder.
    To run Intel® Mobile Platform SDK code on the Smartphone, you should sign it.  See the Microsoft website for information about the signature of the Smartphone.

How to work with the Intel® Mobile Platform PDK

Intel® Mobile Platform PDK enables you to develop/validate/deploy providers for Intel® Mobile Platform SDK runtime.

  • To develop a provider, please reference to Intel® Mobile Platform PDK Programmer’s Guide, chapter “Developing a provider”
  • To validate a provider, please reference to Intel® Mobile Platform PDK Programmer’s Guide, chapter “Validating a Provider”
  • To deploy a provider, please reference to Intel® Mobile Platform PDK Programmer’s Guide, chapter “Registering and installing a provider”

References

&bul l; An Overview of Intel® Mobile Platform SDK 1.2
• Intel® Mobile Platform SDK 1.2 Release Notes
• FAQ - Intel® Mobile Platform SDK v1.2 Open Source Project 
 

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 by 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 pr operty of others.

Copyright © 2004–2007, Intel Corporation. All rights reserved.