1. Wince 5.0 Download
2. Microsoft Windows Ce Version 5.00 Build 1400
3. Windows Ce 5.0 Support
4. Microsoft Windows Ce 5.0 Device Emulator
5. Platform Builder For Microsoft Windows Ce 5.0
6. Microsoft Windows Ce 5.0 Emulator Interrupted

ActiveSync and Windows Mobile Device Center do not work with Windows Embedded CE 4.2 or 5.0, Pocket PC 2002, or Smartphone 2002 devices. To determine which Windows Mobile operating system you’re using if your phone doesn’t have a touch screen, click Start, click Settings, and then click About. The Device Emulator contains the emulator technologies featured in Windows CE 5.0. By using the Device Emulator, you can run emulated-based images created by Windows CE 5.0 without installing Platform Builder, its platform development tool. The old CE 5.0 emulator is an x86 emulator and must run on a 32-bit target. If you need to run on a 64-bit machine, use Device Emulator 3.0 (which is what Studio 2008 is using). Of course that also means you have the generate an OS image for it using the proper BSP.

Portable GPS navigator - 5' LCD display - Microsoft Windows CE.NET 5.0 Core operating system - CPU: Media Tek MT3351 - Internal memory: 64MB - Audio forma.

This function specifies an event object to be associated with the supplied set of FD_XXX network events.

Parameters

• s
  [in] Descriptor identifying the socket.
• hEventObject
  [in] Handle identifying the event object to be associated with the supplied set of FD_XXX network events.
• lNetworkEvents
  [in] Bitmask that specifies the combination of FD_XXX network events in which the application has interest.

Return Values

The return value is zero if the application's specification of the network events and the associated event object was successful. If an error occurs, the value SOCKET_ERROR is returned, and a specific error number can be retrieved by calling the WSAGetLastError function.

As in the case of the select function, WSAEventSelect will frequently be used to determine when a data transfer operation (send or receive) can be issued with the expectation of immediate success. Nevertheless, a robust application must be prepared for the possibility that the event object is set and it issues a Windows Sockets call that returns WSAEWOULDBLOCK immediately. For example, the following sequence of operations is possible:

1. Data arrives on socket s; Windows Sockets sets the WSAEventSelect event object.
2. The application does some other processing.
3. While processing, the application issues an ioctlsocket and notices that there is data ready to be read.
4. The application issues a recv to read the data.
5. The application waits on the event object specified in WSAEventSelect, which returns immediately indicating that data is ready to read.
6. The application issues recv which fails with the error WSAEWOULDBLOCK.

The occurrence of the network event is recorded, the corresponding bit is set in the internal network event record, and the associated event object is signalled. No further action is taken for the network event until the application makes the function call that implicitly re-enables the setting of the event and signals the associated event object.

Any call to the re-enabling routine, even one that fails, results in re-enabling of recording and signaling for the relevant network event and event object.

For FD_READ, FD_OOB, and FD_ACCEPT network events, network event recording and event object signaling are level-triggered. This means that if the re-enabling routine is called and the relevant network condition is still valid after the call, the network event is recorded and the associated event object is set. This allows an application to be event-driven and not be concerned with the amount of data that arrives at any one time. Consider the following sequence:

1. A transport provider receives 100 bytes of data on socket s and causes ws2.dll to record the FD_READ network event and set the associated event object.
2. The application issues recv(s, buffptr, 50, 0) to read 50 bytes.
3. The transport provider causes ws2.dll to record the FD_READ network event and sets the associated event object again because there is still data to be read.

With these semantics, an application need not read all available data in response to an FD_READ network event — a single recv in response to each FD_READ network event is appropriate.

Wince 5.0 Download

The FD_ROUTING_INTERFACE_CHANGE and FD_ADDRESS_LIST_CHANGE events are considered edge-triggered as well. A message will be posted exactly once when a change occurs after the application has requested the notification by issuing WSAIoctl with SIO_ROUTING_INTERFACE_CHANGE or SIO_ADDRESS_LIST_CHANGE correspondingly. Other messages will not be forthcoming until the application re-issues the IOCTL and another change is detected since the IOCTL has been issued.

If a network event has already happened when the application calls WSAEventSelect or when the re-enabling function is called, a network event is recorded and the associated event object is set as appropriate. For example, consider the following sequence:

1. An application calls listen.
2. A connect request is received but not yet accepted.
3. The application calls WSAEventSelect specifying that it is interested in the FD_ACCEPT network event for the socket. Due to the persistence of network events, Windows Sockets records the FD_ACCEPT network event and sets the associated event object immediately.

The FD_WRITE network event is handled slightly differently. An FD_WRITE network event is recorded when a socket is first connected with connect/WSAConnect or accepted with accept/WSAAccept, and then after a send fails with WSAEWOULDBLOCK and buffer space becomes available. Therefore, an application can assume that sends are possible starting from the first FD_WRITE network event setting and lasting until a send returns WSAEWOULDBLOCK. After such a failure, the application will find out that sends are again possible when an FD_WRITE network event is recorded and the associated event object is set.

The FD_OOB network event is used only when a socket is configured to receive out of band (OOB) data separately. If the socket is configured to receive OOB data inline, the OOB (expedited) data is treated as usual data and the application should register an interest in, and will get an FD_READ network event, not an FD_OOB network event. An application can set or inspect the way in which OOB data is to be handled by using setsockopt (Windows Sockets) or getsockopt (Windows Sockets) for the SO_OOBINLINE option.

The error code in an FD_CLOSE network event indicates whether the socket close was graceful or abortive. If the error code is zero, then the close was graceful; if the error code is WSAECONNRESET, then the socket's virtual circuit was reset. This only applies to connection-oriented sockets such as SOCK_STREAM.

Matlab 2016a download. You can now also Download Matlab R2016a Mathworks for windows with a single tap. Matlab R2016a Mathworks Features:– High enhanced technical calculations communication.– The most useful software in universities classes.– Invent live scripts also with enhanced output.– Powerful toolboxes.– Enhanced Language and Programming Tools implemented.– Moving Mathematics statistics functions.– Logic arrays created.– Enhanced Graph classes.– Enhanced Digraph classes.– Add legend objects and titles.– Use latest drivers to avoid instabilities with older NVIDIA Windows drivers.– Use Matlab Coder to generate C-code.– Performance graphics display and also discover much more features. Install the software on your windows device and have fun. How to download Matlab R2016a Mathworks:– First of all, click on the direct download link below.– Then, download the full zip file that contains Matlab full cracked software.– Also, Install the program on your windows computer. Please follow the installation instruction on the file instructions.– Also, use the crack to crack the setup.– Then, open the software.

The FD_CLOSE network event is recorded when a close indication is received for the virtual circuit corresponding to the socket. In TCP terms, this means that the FD_CLOSE is recorded when the connection goes into the TIME WAIT or CLOSE WAIT states. This results from the remote end performing a shutdown on the send side or a closesocket. The FD_CLOSE network event is posted after all data is read from a socket. An application should check for remaining data on receipt of FD_CLOSE to avoid any possibility of losing data.

Windows Sockets will record only an FD_CLOSE network event to indicate closure of a virtual circuit. It will not record an FD_READ network event to indicate this condition.

The FD_ROUTING_INTERFACE_CHANGE network event is recorded when the local interface that should be used to reach the destination specified in WSAIoctl with SIO_ROUTING_INTERFACE_CHANGE changes after such IOCTL has been issued.

The FD_ADDRESS_LIST_CHANGE network event is recorded when the list of addresses of the protocol family for the socket to which the application can bind changes after WSAIoctl with SIO_ADDRESS_LIST_CHANGE has been issued.

The following table shows a list of possible error codes.

Microsoft Windows Ce Version 5.00 Build 1400

Remarks

This function is used to specify an event object, hEventObject, to be associated with the selected FD_XXX network events, lNetworkEvents. The socket for which an event object is specified is identified by the parameter s. The event object is set when any of the nominated network events occur.

This function sets the associated event object and records the occurrence of this event in an internal network event record. An application can use WSAEnumNetworkEvents to retrieve the contents of the internal network event record and thus determine which of the nominated network events have occurred.

WSAEventSelect is the only function that causes network activity and errors to be recorded and retrievable through WSAEnumNetworkEvents. See the description of select to find out how that function reports network activity and errors.

The WSAEventSelect function automatically sets socket s to nonblocking mode, regardless of the value of lNetworkEvents. See ioctlsocket and WSAIoctl for how to set the socket back to blocking mode.

The lNetworkEvents parameter is constructed by using the bitwise OR operator with any of the values specified in the following table.

Issuing a WSAEventSelect call for a socket cancels any previous WSAEventSelect calls for the same socket and clears the internal network event record. For example, to associate an event object with both reading and writing network events, the application must call WSAEventSelect with both FD_READ and FD_WRITE as the following code sample shows.

It is not possible to specify different event objects for different network events. The following code will not work because the second call will cancel the effects of the first, and only the FD_WRITE network event will be associated with hEventObject2.

To cancel the association and selection of network events on a socket, lNetworkEvents should be set to zero, in which case the hEventObject parameter will be ignored.

Closing a socket with the closesocket function also cancels the association and selection of network events specified in WSAEventSelect for the socket. The application, however, still must call WSACloseEvent to explicitly close the event object and free any resources.

The socket created when the accept function is called has the same properties as the listening socket used to accept it. Any WSAEventSelect association and network events selection set for the listening socket apply to the accepted socket. For example, if a listening socket has a WSAEventSelect association of hEventOject with FD_ACCEPT, FD_READ, and FD_WRITE, then any socket accepted on that listening socket will also have FD_ACCEPT, FD_READ, and FD_WRITE network events associated with the same hEventObject. If a different hEventObject or network event is desired, the application should call WSAEventSelect, passing the accepted socket and the desired new information.

Requirements

OS Versions: Windows CE .NET 4.0 and later.
Header: Winsock2.h.
Link Library: Ws2.lib.

See Also

accept (Windows Sockets) closesocket getsockopt (Windows Sockets) ioctlsocket listen recv recvfrom select send sendto setsockopt (Windows Sockets) shutdown WSAAccept WSACloseEvent WSACreateEvent WSAEnumNetworkEvents WSAGetLastError WSAIoctl WSARecv WSARecvFrom WSASend WSASendTo WSAStartup

Send Feedback on this topic to the authors

Windows Embedded Compact,^[6] formerly Windows Embedded CE and Windows CE, is an operating system subfamily developed by Microsoft as part of its Windows Embedded family of products.

Unlike Windows Embedded Standard, which is based on Windows NT, Windows Embedded Compact uses a different hybrid kernel.^[7] Microsoft licenses Windows CE to original equipment manufacturers (OEMs), who can modify and create their own user interfaces and experiences, with Windows CE providing the technical foundation to do so.

The current version of Windows Embedded Compact supports x86 and ARM processors with board support package (BSP) directly.^[8] The MIPS and SHx architectures had support prior to version 7.0. 7.0 still works on MIPSII architecture.

Windows Ce 5.0 Support

• 3Development tools

Features[edit]

Windows CE is optimized for devices that have minimal memory; a Windows CE kernel may run with one megabyte of memory.^[9] Devices are often configured without disk storage, and may be configured as a 'closed' system that does not allow for end-user extension (for instance, it can be burned into ROM). Windows CE conforms to the definition of a real-time operating system, with a deterministic interrupt latency. From Version 3 and onward, the system supports 256 priority levels^[10] and uses priority inheritance for dealing with priority inversion. The fundamental unit of execution is the thread. This helps to simplify the interface and improve execution time.

The first version – known during development under the code name 'Pegasus' – featured a Windows-like GUI and a number of Microsoft's popular apps, all trimmed down for smaller storage, memory, and speed of the palmtops of the day. Since then, Windows CE has evolved into a component-based, embedded, real-time operating system. It is no longer targeted solely at hand-held computers.^[11] Many platforms have been based on the core Windows CE operating system, including Microsoft's AutoPC, Pocket PC 2000, Pocket PC 2002, Windows Mobile 2003, Windows Mobile 2003 SE, Windows Mobile 5, Windows Mobile 6, Smartphone 2002, Smartphone 2003, Portable Media Center, Zune, Windows Phone and many industrial devices and embedded systems. Windows CE even powered select games for the Dreamcast, was the operating system of the Gizmondo handheld, and can partially run on modified Xbox game consoles.

A distinctive feature of Windows CE compared to other Microsoft operating systems is that large parts of it are offered in source code form. First, source code was offered to several vendors, so they could adjust it to their hardware. Then products like Platform Builder (an integrated environment for Windows CE OS image creation and integration, or customized operating system designs based on CE) offered several components in source code form to the general public. However, a number of core components that do not need adaptation to specific hardware environments (other than the CPU family) are still distributed in binary only form.

History[edit]

Windows Embedded Compact was formerly known as Windows CE. According to Microsoft, 'CE' is not an explicit acronym for anything, although it implies a number of notions that Windows developers had in mind, such as 'compact', 'connectable', 'compatible', 'companion' and 'efficient'.^[12][13] The name changed once in 2006, with the release of Windows Embedded CE 6.0, and again in 2011, with the release of Windows Embedded Compact 7.

Windows CE was originally announced by Microsoft at the COMDEX expo in 1996 and was demonstrated on stage by Bill Gates and John McGill. Microsoft had been testing Pegasus in early 1995 and released a strict reference platform to several hardware partners. The devices had to have the following minimum hardware specifications:

• SH3, MIPS 3000 or MIPS 4000 CPU
• Minimum of 4 MB of ROM
• Minimum of 2 MB of RAM with a back up power source, such as a CR2032 coin cell battery
• Powered by two AA batteries
• Weigh less than 1lbs
• A physical QWERTY keyboard including Ctrl, Alt and Shift keys
• An LCD display of 480×240 pixels with four shades of gray and two bits per pixel with touchscreen that could be operated by either stylus or finger nail
• An Infrared transceiver
• Serial port
• PC Card slot
• Built in speaker

Devices of the time mainly had 480×240 pixel displays with the exception of the Hewlett-Packard 'Palmtop PC' which had a 640×240 display. Each window took over the full display. Navigation was done by tapping or double tapping on an item. A contextual menu was also available by the user pressing the ALT key and tapping on the screen. Windows CE 1.0 did not include a cascading Start menu unlike Windows 95 and Windows NT 4.0 did. Microsoft released the Windows CE 1.0 Power Toys that included a cascading menu icon that appeared in the system tray. Also bundled were several other utilities, most notable were a sound applet for the system tray, enabling the user to quickly mute or unmute their device or adjust the volume and a 'pocket' version of Paint.

The release of Windows CE 2.0 was well received. Microsoft learned its lessons from consumer feedback of Windows CE 1.0 and made many improvements to the operating system. The Start menu was a cascading menu, identical to those found on Windows 95 and Windows NT 4.0. Color screens were also supported and manufacturers raced to release the first color H/PC. The first to market however, was Hewlett Packard with the HP 620LX. Windows CE 2.0 also supported a broader range of CPU architectures. Programs could be also installed directly in the OS by double clicking on CAB files. Due to the nature of the ROMs that contained the operating system, users were not able to flash their devices with the newer operating system. Instead manufacturers released upgrade ROMs that users had to physically install in their devices, after removing the previous version. This would usually wipe the data on the device and present the user with the setup wizard upon first boot.

Development tools[edit]

Visual Studio[edit]

Microsoft Visual Studio 2012, 2013, and 2015 support apps and Platform Builder development for Windows Embedded Compact 2013.^[14]

Warhammer 40k RPG PDF's From DriveThruRPG I love owning the physical books, but they are far less efficient when it comes to pulling up information quickly. Furthermore it's often very useful to be able to easily copy text and images from the books into your own documents/maps or to send to players. Game Information. 40k RPG Master Bestiary. Warhammer 40k pdf. Jun 17, 2017  Games Workshop is keeping with their promise that you will have access to the rules for free. Come take a look at the Battle Primer! The release of 8th edition has been one of the most anticipated things to happen for 40k, and Games Workshop made a lot of promises with this new edition. Warhammer 40K - 8th Edition - Codex.pdf - Free download Ebook, Handbook, Textbook, User Guide PDF files on the internet quickly and easily.

Microsoft Visual Studio 2008 and earlier support projects for older releases of Windows CE/Windows Mobile, producing executable programs and platform images either as an emulator or attached by cable to an actual mobile device. A mobile device is not necessary to develop a CE program. The .NET Compact Framework supports a subset of the .NET Framework with projects in C#, and Visual Basic .NET, but not Managed C++. 'Managed' apps employing the .NET Compact Framework also require devices with significantly larger memories (8 MB or more) while unmanaged apps can still run successfully on smaller devices. In Visual Studio 2010, the Windows Phone Developer Tools are used as an extension, allowing Windows Phone 7 apps to be designed and tested within Visual Studio.

Free Pascal and Lazarus[edit]

Free Pascal introduced the Windows CE port in Version 2.2.0, targeting ARM and x86 architectures. Later, the Windows CE header files were translated for use with Lazarus, a rapid application development (RAD) software package based on Free Pascal. Windows CE apps are designed and coded in the Lazarus integrated development environment (IDE) and compiled with an appropriate cross compiler.^[15]

Platform Builder[edit]

This programming tool is used for building the platform (BSP + Kernel), device drivers (shared source or custom made) and also the apps. This is a one stop environment to get the system up and running. One can also use Platform Builder to export an SDK (software development kit) for the target microprocessor (SuperH, x86, MIPS, ARM etc.) to be used with another associated tool set named below.

Others[edit]

The EmbeddedVisual C++ (eVC) – a tool for development of embedded apps for Windows CE. It can be used standalone using the SDK exported from Platform Builder or using the Platform Builder's Platform Manager connectivity setup.

CodeGearDelphi Prism – runs in Visual Studio, also supports the .NET Compact Framework and thus can be used to develop mobile apps. It employs the Oxygene compiler created by RemObjects Software, which targets .NET, the .NET Compact Framework, and Mono. Its command-line compiler is available free of charge.

Basic4ppc – a programming language similar to Visual Basic – targets the .NET Compact Framework and supports Windows CE and Windows Mobile devices.

GLBasic – a very easy to learn and use BASIC dialect that compiles for many platforms, including Windows CE and Windows Mobile. It can be extended by writing inline C/C++ code.

LabVIEW – a graphical programming language, supporting many platforms, including Windows CE.

AutoHotkey – a port of the open source macro-creation and automation software utility available for Windows CE. It allows the construction of macros and simple GUI apps developed by systems analyst Jonathan Maxian Timkang.^[16]

Relationship to Windows Mobile, Pocket PC, and SmartPhone[edit]

Often Windows CE, Windows Mobile, and Pocket PC are used interchangeably, in part due to their common origin. This practice is not entirely accurate. Windows CE is a modular/componentized operating system that serves as the foundation of several classes of devices. Some of these modules provide subsets of other components' features (e.g. varying levels of windowing support; DCOM vs COM), others which are separate (bitmap or TrueType font support), and others which add additional features to another component. One can buy a kit (the Platform Builder) which contains all these components and the tools with which to develop a custom platform. Apps such as Excel Mobile (formerly Pocket Excel) are not part of this kit. The older Handheld PC version of Pocket Word and several other older apps are included as samples, however.

Windows Mobile is best described as a subset of platforms based on a Windows CE underpinning. Currently, Pocket PC (now called Windows Mobile Classic), SmartPhone (Windows Mobile Standard), and Pocket PC Phone Edition (Windows Mobile Professional) are the three main platforms under the Windows Mobile umbrella. Each platform uses different components of Windows CE, plus supplemental features and apps suited for their respective devices.

Microsoft Windows Ce 5.0 Device Emulator

Pocket PC and Windows Mobile are Microsoft-defined custom platforms for general PDA use, consisting of a Microsoft-defined set of minimum profiles (Professional Edition, Premium Edition) of software and hardware that is supported. The rules for manufacturing a Pocket PC device are stricter than those for producing a custom Windows CE-based platform. The defining characteristics of the Pocket PC are the touchscreen as the primary human interface device and its extremely portable size.

CE v3.0 is the basis for Pocket PC 2002. A successor to CE v3.0 is CE.net.^[17] 'PocketPC [is] a separate layer of code on top of the core Windows CE OS.. Pocket PC is based on Windows CE, but it's a different offering.' And licensees of Pocket PC are forbidden to modify the WinCE part.^[18]

Platform Builder For Microsoft Windows Ce 5.0

The SmartPhone platform is a feature-rich OS and interface for cellular phone handsets. SmartPhone offers productivity features to business users, such as email, and multimedia abilities for consumers. The SmartPhone interface relies heavily on joystick navigation and PhonePad input. Devices running SmartPhone do not include a touchscreen interface. SmartPhone devices generally resemble other cellular handset form factors, whereas most Phone Edition devices use a PDA form factor with a larger display.

Releases[edit]

See also[edit]

Microsoft Windows Ce 5.0 Emulator Interrupted

References[edit]

1. ^'Special Report: Windows CE 6 arrives with 100% kernel source'. windowsfordevices.com. November 1, 2006. Archived from the original on August 20, 2012. Retrieved July 20, 2011.
2. ^'Microsoft opens full Windows CE kernel source'. Linux Devices. November 1, 2006. Archived from the original on February 16, 2009.
3. ^'Microsoft announces general availability of Windows Embedded Compact 2013'. Microsoft News Center. Microsoft. Retrieved July 14, 2013.
4. ^'Windows CE overview'. Archived from the original on May 28, 2010.
5. ^'Windows Embedded CE'. Microsoft. Microsoft. Archived from the original on July 17, 2015. Retrieved February 6, 2015.
6. ^'Windows Embedded Homepage'. Microsoft.com. Retrieved November 14, 2010.
7. ^'How does Windows Embedded CE 6.0 Start?'. Windows CE Base Team Blog. Microsoft. December 18, 2007. Retrieved November 14, 2010.^{[dead link]}
8. ^'Board Support Package (Compact 2013)'. MSDN. Microsoft. Retrieved July 15, 2013.
9. ^'Create or Modify a BSP (Compact 2013)'. Microsoft Developer Network. Microsoft. Retrieved June 11, 2014.
10. ^'Priority Levels'. Msdn.microsoft.com. Retrieved November 14, 2010.
11. ^'Embedded Platform Integrated Development Environment (IDE) Windows CE'. Microsoft.com. Retrieved November 14, 2010.
12. ^'The Meaning of 'CE' in Windows CE launch date'. support.microsoft.com. February 14, 2015. Retrieved February 14, 2015.
13. ^'Microsoft renames Windows CE, sets CE 6.0 launch date'. windowsfordevices.com. September 22, 2006. Archived from the original on January 4, 2009. Retrieved July 20, 2011.
14. ^'What's New (Compact 2013)'. MSDN. Microsoft. Retrieved January 24, 2016.
15. ^WinCE port - Lazarus wiki
16. ^Autohotkey build for CE devices
17. ^ ^abcdefghijPöhls, Henrich C. (September 5, 2003), 'Risk Analysis of Mobile Devices with Special Concern of Malware Contamination'(PDF), Diploma Thesis, University of Hamburg, p. 27, retrieved October 24, 2009
18. ^Smith, Tony (April 16, 2003). 'Why Pocket PC isn't WinCE'. The Register. Retrieved October 24, 2009.
19. ^'Microsoft Announces Broad Availability of Handheld PCs With Windows CE'. Microsoft News Center. November 18, 1996. Retrieved June 20, 2011.
20. ^ ^abcdefgHall, Mike (September 19, 2006). 'Windows Embedded Blog: CE 6.0 - why the codename 'Yamazaki' ?'. MSDNBlogs. Retrieved October 24, 2009.
21. ^'Microsoft Announces Release of Windows CE 2.0'. Microsoft News Center. September 29, 1997. Retrieved July 27, 2015.
22. ^'Microsoft Announces Availability of Windows CE 3.0'. Microsoft News Center. June 15, 2000. Retrieved June 20, 2011.
23. ^'Microsoft Launches Windows CE .NET'. Microsoft News Center. January 7, 2002. Retrieved June 20, 2011.
24. ^Walker, Geoff (January 7, 2002). 'Windows CE .Net: Microsoft's successor to Windows CE 3.0'. Pen Computing Magazine. Retrieved October 24, 2009.
25. ^ ^abcSmith, Tony (March 29, 2004). 'MS readies WinCE 5.0 preview'. The Register. Retrieved October 24, 2009.
26. ^'The History of the PDA'(DOC). 090517 seditaville.com
27. ^'Windows Embedded CE 6.0 Advanced Memory Management'. Retrieved May 25, 2011
28. ^Leckie, Andrew (March 25, 2008). 'Introduction to Microsoft embedded technologies - Session 1'. New Zealand: Embedded .NET User Group. Archived from the original(PPT, 10 MB) on July 24, 2011.
29. ^Babu, K. Ashok (November 22, 2006). 'Differences between Windows CE 5.0 and Windows CE 6.0'. WindowsForDevices.com. Archived from the original on July 16, 2012. Retrieved October 24, 2009.
30. ^Veerabahu, Maharajan (December 24, 2010). 'Comparison between Windows Embedded Compact 7 (WEC7) and Windows CE 6'. e-consystems.com. Retrieved December 24, 2010. The new kernel also supports ARMv7, but as a tradeoff, ARMv4 support is dropped by WEC 7
31. ^ ^abcdef'What's New (Compact 2013)'. MSDN. Microsoft. Retrieved July 15, 2013.

External links[edit]

• A Brief History of Windows CE, by HPC:Factor with screenshots of the various versions
• 'Site hosted by Windows CE'. Archived from the original on March 11, 2005. Retrieved July 23, 2006.CS1 maint: BOT: original-url status unknown (link) , Website hosted by Handheld PC. Unfortunately offline now; only this archived version exists