Later, this product became the Windows Embedded Component Designer in the released product
Bill Luan, Program Manager, who was in charge of the design of the first internal tool iCat, which enabled all the Windows team engineers to "componentize" their features in Windows.Mike Cherry, Program Manager, who was leading the infrastructural process work.Tim Hill, Group Program Manager who was in charge of the PM team, and served as the overall architect.
MICROSOFT WINDOWS 10 IOT ENTERPRISE FULL
On August 26, 2001, Beta 2 of Windows XP Embedded was released, with a full release planned for later that year. The initial team consisted of: Tools were also added to make it easier to start with a blank slab of hardware and to deploy an embedded OS on it quickly and easily. The feature set of the embedded tools was enriched to include things like basic version control, component scripting, and expandability.
The component count has risen from 250 to over 10,000-most of them device-driver components. Plans were drawn up, the team was expanded, and work started on Whistler Embedded, codenamed Mantis. A decision was made to stop development of Windows 2000 Embedded, and start work on a Windows XP Embedded product (then called Whistler). The team set their sights on this next version. He served as the Product Unit Manager (PUM) of the first Windows Embedded – and started recruiting engineers within Microsoft. A new Windows Embedded team was formed, under the leadership of Bruce Beachman. Shortly after release, in early 2000, Microsoft decided that it was best to take that architecture and make a new product leveraging the new Windows code. Minimum run-time images were as small as 9 MB for a system featuring the full Win32 API. The tools allowed OEMs and embedded developers to create components encapsulating their binaries, and to add them seamlessly into Windows NT Embedded runtimes containing limited functionality and devices. This project, known within Microsoft as Impala, was released in 1999 as Windows NT Embedded 4.0-a set of tools and a database of approximately 250 components that allowed developers to put together small Windows NT 4.0 run-time images for embedded devices. In mid-1998, Microsoft worked with VenturCom, for their Windows NT Embedded product. Windows NT Embedded 4.0 got its start in 1998 with a small team of developers at Microsoft.
0 kommentar(er)
