| SPECIAL REPORT: Microsoft launches first "Shared Platforms" program |
Jun. 02, 2003
[Updated 9:00am PDT] -- Microsoft today launched a further expansion of its Shared Source initiative: a "Shared Platforms" initiative which allows, for the first time, the "non-commercial" sharing of Windows CE .NET "platforms" and "runtimes." Previously, only CE .NET sources could be shared. The earlier sharing program, via the Shared Source License for Microsoft Windows CE .NET, does not permit the sharing of binary (executable) image files. In contrast, the new Shared Platforms program allows complete, executable modified OS images to be shared.
The new program was actually unveiled by Bill Gates last month as part of his WinHEC keynote; but at that time it was upstaged by the much heralded announcement of $3 pricing for Windows CE .NET "core" licensing.
Defining terms
We spoke with a member of Microsoft's embedded group to clarify a few key terms used in the description of the company's new Shared Platforms initiative.
"Platform" (also referred to as "device platform"), our source explained, refers to "the collection of files that are combined to create the binary runtime image," while "runtime" (also referred to as "device runtime") is "the binary file that is deployed on the device" (i.e., the OS image). Another key term, "non-commercial", will be clarified below.
Export wizard
In order to facilitate the creation of shareable CE .NET "platforms" and "runtimes", Microsoft has created a special tool, called the "Windows CE .NET Platform Export Tool" (CEPET), which is offered as a free download, we were told. The tool includes a wizard that wraps all of the platform files and associated licenses together into a single Shared Platform file. The device platforms and runtimes can then be used on any target device, including both actual device hardware and the Windows CE .NET Device Emulator (which runs on x86 PCs).
On the receiving end, those wanting to use the shared platform can use any version of Microsoft's CE .NET "Platform Builder" development platform -- including, if desired, a freely downloadable non-commercial version -- to create the actual executable binary code images, and write them into Flash memory on the target device.
Binary vs. source
The CEPET tool also provides an option to include Shared Source along with the platform being shared. "If the Shared Platform developer includes Shared Source in the platform that is being shared, then it will be included with the Shared Platform file," in which case "the recipient can modify the Shared Source code and redistribute it to other developers," we were told.
This brings out the interesting point that under the Shared Platforms program, sharing of source is an option. That is, the creator of the shared platform can choose to include -- or not include -- source in the distributed file, as desired. This contrasts notably with licenses such as the GNU General Public License which requires source to be made available to those who receive binaries that request the source to those binaries.
There's another major difference between the Shared Platforms and Shared Source programs, which has to do with the amount of source that is available for sharing. Although the Shared Source program provides access to a large subset of the CE .NET code which can be modified and shared for non-commercial purposes, it is not possible to share an entire system image via source. Therefore, using Shared Source, developers wanting to share modified code must provide the modified source along with instructions on how to rebuild the full system image. On the other hand, with Shared Platforms the full image can be shared, making the sharing process much more straightforward -- and preventing the source itself from being shared, if that is desired.
The meaning of "non-commercial"
The end user license agreement (EULA) that goes with the CEPET tool restricts the sharing Windows CE .NET Platform images to non-commercial purposes, only. Just what does this mean?
Microsoft says the CEPET enables . . . - Hobbyists to share and modify device platforms developed by the community. An example might be "to convert an old PC into any number of Windows CE .NET-based devices, such as a digital audio receiver," our source suggested.
- Professors to distribute a Shared Platform to students for a Windows CE .NET-based class assignment.
- OEMs to use the Windows CE .NET Platform Export Tool to enable developers within a company to collaborate on a new device platform.
- OEMs and systems integrators to collaborate on Windows CE .NET device platforms.
Although Microsoft calls these "non-commercial" uses, clearly some of them have business-related benefits -- for example OEMs using the tool to enable internal development or to work with system integrators to develop desired implementations for customers.
Apparently, the platform images can be shared freely provided either: (1) they are not sold by themselves; or (2) they are not distributed within products that are sold. However, those "non-commercial" shared platforms can later be converted into "commercial" images by licensing the OS from Microsoft, we learned. "If a commercial interest [wants] to sell devices using a shared platform, they [can then] obtain licenses from Microsoft to do so," our source said.
No costs for participation
Microsoft said there is no cost to participate in the Windows CE .NET Shared Platforms Program, or to share non-commercial Windows CE .NET Shared Platforms, and a collection of community Shared Platforms will be available for download from the User Samples section of Microsoft's www.gotdotnet.com website.
Although Microsoft is hosting an area where developers can share their Shared Platforms, developers can share the images without going through a Microsoft upload/download area, as long as they use the CEPET to do so. According to Microsoft, the steps required are . . . - Developer A uses the CEPET to create the shared platform file (.msi file) to be shared.
- Developer A makes the shared platform file available to other developers.
- Developer B receives the shared platform file and accepts the Shared Platforms EULA upon receipt. The EULA explains that the shared platform is for "non-commercial uses" only.
As mentioned previously, the Platform Builder developer tool is used to create shareable device platforms, or to install shared platforms on devices. However, the situation is slightly different at the two ends of the sharing process . . . - Creating shared platforms: a free "Emulation Edition" version of Platform Builder, which is limited to creating device platforms that run on a device emulator that executes on an x86 PC, is currently available for download from Microsoft's download center. However, to create OS images that run on actual hardware, developers must either use the "full version" of Platform Builder, which sells for $995, or they can order a "free" 120-day "Evaluation Edition" of Platform Builder.
- Receiving and using shared platforms: any version of Platform Builder -- "full version", Evaluation Edition ("free" 120-day version), or Emulation Edition (free download) -- can be used for receiving and installing shared platforms on all devices, whether for use on actual hardware or on the device emulator (on x86 PCs).
Further details about ordering the 120-day evaluation version of Platform Builder are available here (shipping and handling charges apply).
Related stories:
(Click here for further information)
|
|
|
7 Advantages of D2D Backup
For decades, tape has been the backup medium of choice. But, now, disk-to-disk (D2D) backup is gaining in favor. Learn why you should make the move in this whitepaper.
4 Legal Reasons to Control Internet Access
The Internet is obviously a valuable resource for many organizations. However, many are exposed to legal liability concerns because they fail to control Internet access. Learn if you're safe in this white paper.
Rapidly Resolve J2EE Application Problems
Whether you are in the process of building J2EE applications or have J2EE applications already running in production, you must ensure that they deliver the expected ROI. Learn how in this white paper.
Load Testing 2.0 for Web 2.0
There are many unknowns in stress testing Web 2.0 applications. Find out how to test the performance of Web 2.0 in this white paper.
Build Better Games Online
For the game infrastructure providers, life is complex. Making money from games has become more complicated. Why? Find out in this white paper.
Building a Virtual Infrastructure from Servers to Storage
This white paper discusses the virtual storage solutions that reduce cost, increase storage utilization, and address the challenges of backing up and restoring Server environments.
Gaining Faster Wireless Connections with WiMAX
Welcome to what is quickly becoming the hyperconnected world where anything that would benefit from being connected to the network will be connected. Learn more in this white paper.
Is Your Desktop a Security Threat?
The new wave of sophisticated crimeware not only targets specific companies, but also targets desktops and laptops as backdoor entryways into those business’ operations and resources. Learn how to stay safe in this white paper.
Increasing SAN Reliability by 100 Percent
Storage area networks (SAN) are a strong part of storage plans. Learn how to increase your reliability and uptime by 100 percent in this case study.
|
|
|
|
|
Use of this site is governed by our Terms of
Service and Privacy Policy.
Except where otherwise specified, the contents of this site are copyright © 1999-2008
Ziff Davis Enterprise Holdings Inc. All Rights Reserved.
Reproduction in whole or in part in any form or medium without express written permission of Ziff Davis Enterprise is
prohibited. Windows is a trademark or registered trademark of Microsoft Corporation in the United States and/or other countries and is used by WindowsForDevices under license from owner. All other marks are the property of their respective owners. WindowsForDevices is an independent publication not affiliated with Microsoft Corporation.
news feed