In my latest project I have been working with Windows Embedded 8 Handheld, idea was to create an App for a American Retailer with functionalities like scanning, printing, signature capture etc. If you are a .NET developer with some WPF back ground, things will go in ease with you because Windows Embedded handheld applications are built in XAML and C#. Hopefully by following this post you will be able to start your first project with ease.
Tools and SDKs
Make sure you have the below configurations and tools installed
1. Windows 8/8.1 as Operating System
2. Visual Studio 2012 Professional or Higher
3. Windows Phone 8 SDK
4. Windows Handheld SDK
Lets start
1. Lets go to Visual Studio File -> New project, If you have installed everything correctly then you will see under templates Windows Phone appearing. Select that template and in main list select Windows Phone App (as shown in the picture), I have named my project as MyFirstHandHeld.
2. You will be prompted for the target version select Windows 8.0 as target there.
3. Then you will land up in the project window along with with solution explorer. Now to check whether your handheld SDK was successfully installed you can click on the dropdown arrow in Emulator options in upper task bar. If you see the emulator options with ‘H’ suffix in their name like “WE8H Emulator WVGA” etc…it means that handheld SDK was correctly installed.
4. Now if you run your application by targeting a WE8H emulator it will run perfectly but you will not be able to use native features like Scanner, MSR etc. To take advantage of the Native features you have to include postnativeutils library which you are supposed to find in “c:\Program Files (x86)\Microsoft SDKs\Windows Embedded Handheld\v8.0\Libraries\x86\POSTestNativeUtils.winmd”. So now to add this library
a. go to References in your solution explorer and right click it and select “Add Reference”
Note: You will see few options like “Add Reference”, “Add Service Reference” etc
b. go to browse and browse the path of POSTestNativeUtils we mentioned before.
After including and clicking ok, your app is ready to use scanner and other native utils.. So Congratulations you have created your first native windows handheld app. Now you can go ahead and use the Native libraries of Scanner/ Printer/ Card Reader etc..
Troubleshoot
Now there’s one catch after you add your libraries. Before going ahead remember if the Native peripheral devices runs on 32 bit architecture you might want to select X86 as the target platform. Right click on your solution and select configuration manager. There you will be able to select the Target Platform as X86, follow the below screenshot for reference.
Moving Forward
Now we can go ahead and use our native features like Scanning/ MSR card reading etc. That is a different sort of discussion I will create few more posts for that.
The os on device is [windows(r) embedded handheld 6. 5 clasic] i checked manual i got Windows Embedded Handheld 6.5 Sdk Visual Studio this supported development tools 1 visual studio 2005 (8. 0) (. net framework 2. 0) or higher 2 visual c++, visual c 3 visual basic. net (scanner only) activesync development platform requirements. It currently has windows embedded handheld 6. 5 as the os. we use c. net in visual studio 2015 for all our development and i don’t see any way to develop an app for this os. from what i’m seeing online, you must develop apps in vs 2005 or 2008.
I’am an application s/w programmer, was working on classic vb&asp(with limited knowledge of. net and c),now Windows Embedded Handheld 6.5 Sdk Visual Studio working on ssrs reports, tasked with designing a two-form application to be deployed on intermec cn70 device (os-microsoft windows embedded. I am trying to connect a handheld device with a usb cable: windows embedded handheld 6. 5 professional (trimble tsc3 or ranger 3) to. windows 10 64 bit; in windows 10 the windows mobile device center is not connecting to the handheld device. under windows 7, in the device manger i can find the handheld device under «portable devices». The documentation has been tested on windows 7 (32 and 64 bit) with visual studio 2008. install windows ce 5. 0 sdk make sure vs2008 is up to date and close it before starting the installation.
Automatic code formatting with a product like visual studio you get what you pay for. when you start coding a method and go to enter the “{“ brackets, the code inside those brackets will. Windows mobile 6. x, windows embedded handheld 6. 5 and; windows ce 5; windows ce 6. in visual studio the term ‘smart device’ is used for windows ce/mobile programming target. ‘visual studio express’ does not support smart device development. Windowsembeddedhandheld6. 5 용 앱을 개발해야합니다. «시작하기»에 대한 자습서 나 설명서를 찾기 시작합니다. 결국 나는 주된 사실을 가지고 있다고 생각하지만, 여전히 나에 대해 궁금한 점이 있습니다. 어디서나 sdk 또는 dtk를 찾았지만 아무 것도 발견되지 않았습니다. Does anyone know if there are any ways to allow windows mobile / embedded handheld 6. 5. 3 / ce development in visual studio 2015? seems only windows phone (windows 10) dev is supported? i am unable to find a copy of vs 2008 anywhere. cheers.
• follow the instructions for installing visual studio 2013 update 2 or higher • Windows Embedded Handheld 6.5 Sdk Visual Studio install the windows embedded handheld 8. 1 sdk • click the download button for the we8h_sdk-8. 1 file. follow the instructions to install the sdk download the release notes which are in a separate file in the download link for the sdk. Visual studio versions beyond visual studio 2008 no longer supports the windows ce, windows mobile or windows embedded handheld platforms. visual studio 2008 or earlier versions need to be used to develop applications for for these platforms.
Programming For Windows Embedded 6 5mobile 6 5 In Visual
In visual studio 2015: windows mobile 6. 5; windows embedded handheld 6. 5; can i develop applications for sdks? the key here is that i can not delete 2015. but i can use plugins etc. thanks to for your help. Combining intelligent architecture with intuitive visual workflow and extensive user-defined automation capabilities.
C windows mobile 6. 5 대 windows embedded handheld 6. 5.
How To Developed App For Windows Embedded Handheld 6 5
Windows embedded handheld 6. 5 and windows ce 5 windows ce 6. in visual studio the term ‘smart device’ is used for windows ce/mobile programming target. Weh 6. 5 is essentially windows mobile 6. 5, which means using vs2005 or vs2008. i would recommend vs2008 plus sp1. in addition you will need an sdk for that platform (presumably that would be obtained from motorola or whoever sold you the device).
Description: Windows Embedded Handheld 6.5 Sdk Visual Studio 6. 5″ vga lcd panel with led backlight for 20% power saving and environmental protection 0° c ~ +50° c range operating temperature 4-wire resistive touchscreen solution or 3mm tempered smudge resistant protected glass usb touch interface dual. Windows embeddedhandheld6. 5 and windows mobile 6. 5 also share the same application development environment, with support for native and managed code (winforms) applications. this provides developers familiar tools like visual studio 2008 and the. net compact framework 3. 5, so they can leverage their existing knowledge and skills to speed. Defined by msft a choice of visual studio 2005 and visual studio 2008. developing with these would pose challenges for next generation enterprise class os is released whether it’s windows phone 8. 1 or windows embedded 8. 1 handheld, or whatever msft marketing things of.
Thank you prabu, that helped me a lot. also recommended, is the installation of windows mobile device center. for windows 7, use the x64 version. still, it’s very much a pity that in the year 2015, although weh 6. 5 is still the standard and windows 7 is wide in use (and not without reason), ms does not adapt the sdk and tdk to work with visual studio 2013. The “windows mobile 6. 5 developer tool kit” (dtk) is compatible with microsoft visual studio 2008. windows mobile 6. 5 developer tool kit microsoft. I know visual studio 2017 does not support windows embedded handheld 6. 5, and visual studio 2005 or 2008 is required. however recently got new hardware still running this mobile os but do not have access to visual studio 2008. and not really keen to purchase it for one off project for a platform i never want to develop for again.
Windows embedded handheld6. 5. built on windows mobile 6. 5 to power line-of-business applications in field mobility, transportation, retail and more. application compatibility with windows mobile 6. 5, and a consistent sdk and set of apis. so i think you just should use windows mobile 6. 5 sdk. Follow the instructions to install the sdk download the release notes which are in a separate file in the download link for the sdk. using the windows embedded 8. 1 handheld sdk • the windows handheld 8. 1 sdk will install everything you need into your existing windows phone 8. 1 development environment. after installing, start visual studio as.
Windows embedded handheld 6. 5 development available in visual.
C windows mobile 6. 5 vs windows embedded handheld 6. 5. the windows mobile 6. 5. 3 dtk provides documentation, sample code, header and library files, emulator images, and tools to visual studio that let you build applications for windows mobile 6. 5 and 6. 5. 3. dragonboard 410c android hello world (setup) david jones. Elecard aac audio decoder/encoder and mpeg audio decoder/encoder components that deliver outstanding audio quality have been updated and now support microsoft® windows sdk g4 1. 3. 2 base classes and sample applications support microsoft® visual studio. More good news for virgin tv customers virgin media has announced 22 new channels coming to your t…. I’ve spent all morning searching to see what i needed to develop for this device and found that windows embedded handheld 6. 5 classic is based on windows mobile 6. 5. and from here i enter the murky world of overlapping definitions, sdks, visual studio versions supported or not etc.
Open visual studio 2008 and create a new project for smart device click ok. select device application on the main window with the icons and change the target platform to windows mobile 6 standard sdk. click ok. right click on the the project name in the solution explorer and select change target platform and choose windows mobile 6. 5. 3.
First thing you have to know about writing applications with Windows Embedded, is the version that you are going to use of it.
In this article, I’m going to show you how to create applications for Windows Embedded 8.1 Handheld, that is the version that is running on most of the mobile POS devices (like for example the BM180 Pidion from Bluebird).
To develop for this version of WEH you just need two things:
– Visual Studio 2013 Update 2 RC or higher (any version, but recommended Ultimate if you want to have quality testing)
– Windows Embedded 8.1 Handheld SDK RC (http://www.microsoft.com/en-us/download/details.aspx?id=42538)
So just download and install the SDK in your computer before start working with it.
During the installation process you will be warned that is not only the SDK with the documentation and the APIs the one to be installed but also the Emulators in case you don’t have an Embedded device.
Once is done, let’s see how to create an app.
Go to Visual Studio
1. Create a new Windows Phone Project, let’s call it BarCodeScaner, normal Windows Phone 8.1 Silverlight project
So the first thing you will notice is that we have new emulators installed:
2. Add the following statements to the top of your class file:
using Windows.Devices.PointOfService; // The Windows RT point of service APIs
3. Add the following variables inside your class:
private BarcodeScanner scanner; private ClaimedBarcodeScanner claimedScanner;
scanner stores the instance of the default scanner object.
claimedScanner stores the instance of the barcode scanner object that is reserved for exclusive use by your application.
4. Generate the next method in your main class:
private async void ClaimBarcodeScanner() { scanner = await BarcodeScanner.GetDefaultAsync(); // get the default instance of the scanner //fakeScanner = new FakeScanner(scanner.DeviceId); claimedScanner = await scanner.ClaimScannerAsync();//Attempts to get an exclusive access to the scanner. claimedScanner.DataReceived += claimedScanner_DataReceived; await claimedScanner.EnableAsync(); //Gets the barcode scanner into a ready state. claimedScanner.IsDecodeDataEnabled = true; // provide decoded label data }
5. Now that we have the ClaimBarcodeScanner method created, we are ready to start getting data from the barcode scanner, just let’s read the information captured on the claimedScanner_DataReceived event:
async void claimedScanner_DataReceived(ClaimedBarcodeScanner sender, BarcodeScannerDataReceivedEventArgs args) { string label, data; //Label and data are de values returned by the scanner UInt32 symbology = args.Report.ScanDataType; // the symbology of the scanned data using (var datareader = Windows.Storage.Streams.DataReader.FromBuffer(args.Report.ScanDataLabel)) { label = datareader.ReadString(args.Report.ScanDataLabel.Length); } using (var datareader = Windows.Storage.Streams.DataReader.FromBuffer(args.Report.ScanData)) { data = datareader.ReadString(args.Report.ScanData.Length); } await this.Dispatcher.RunAsync(Windows.UI.Core.CoreDispatcherPriority.Normal, () => { tbData.Text = data; //Send the data to the UI through the dispatcher. tbData is a textbox in the UI tbLabel.Text = label; //Send the data to the UI through the dispatcher. tbLabel is a textbox in the UI }); }
6. Just to finish it, you can call the new method from your constructor to execute it once you start the application.
That’s all! Just deploy the application into your device and play
Now you can scan any kind of barcode you have at home or in your warehouse.
If you want to check with symbologies are recognized, check this website out, as the list is very long! But think on any kind of barcode.
Just for extra information, the following most common barcodes are supported by the decoder:
UPC-A, UPC-E, EAN-8, EAN-13, Code 39, Code 93, Code 128, ITF, Codabar, MSI, RSS-14 (all variants), QR Code, Data Matrix, Aztec and PDF-417.
And if you are wondering how can you get a barcode using the camera instead the scanner, here you have a library that can do it: https://zxingnet.codeplex.com/ but this is a topic for another article 🙂
– May the code be with you –
References:
WEH 8.1 MSDN : http://msdn.microsoft.com/en-us/library/dn715922.aspx
WEH 8.1 SDK: http://www.microsoft.com/en-us/download/details.aspx?id=42538
Windows IoT, short for Windows Internet of Things and formerly known as Windows Embedded, is a family of operating systems from Microsoft designed for use in embedded systems. Microsoft has three different subfamilies of operating systems for embedded devices targeting a wide market, ranging from small-footprint, real-time devices to point of sale (POS) devices like kiosks. Windows Embedded operating systems are available to original equipment manufacturers (OEMs), who make it available to end users preloaded with their hardware, in addition to volume license customers in some cases.
Windows IoT
Windows Embedded 8 showing «Hotel Systems» panel, Metro-style app |
|
Developer | Microsoft |
---|---|
OS family | Microsoft Windows |
Source model |
|
Kernel type | Hybrid kernel |
License | Commercial proprietary software |
Official website | developer |
Support status | |
IoT: Mainstream support until January 12, 2027 and extended support until January 13, 2032[1] Embedded: All editions out of extended support.[2] |
In April 2018, Microsoft released Azure Sphere, another operating system designed for IoT applications running on the Linux kernel.
Microsoft rebranded «Windows Embedded» to «Windows IoT» starting with the release of embedded editions of Windows 10.
Windows IoT Enterprise is a binary equivalent version of Windows 10 and 11 Enterprise designed for use in embedded applications. It replaces both Embedded Industry and Embedded Standard, as well as Embedded FES (known simply as «Windows Embedded» since Windows 8/8.1). It functions exactly the same, even including all of its components and features, but is licensed exclusively for use in embedded devices.[3] Plain unlabeled, Retail/Thin Client, Tablet, and Small Tablet SKUs are available, again differing only in licensing.
While remaining identical to their non-IoT counterparts, the later versions added a minor change that allows the use of smaller storage devices, with the possibility of more changes being made in the future.[4][5] In addition, starting with the LTSC edition of version 21H2, Windows 10 IoT Enterprise LTSC will gain an extra five years of support compared to Windows 10 Enterprise LTSC.[6]
Windows 10 IoT Mobile, also known as Windows 10 IoT Mobile Enterprise, is a binary equivalent of Windows 10 Mobile Enterprise that functions exactly the same, except that it is licensed for IoT applications. It is unsupported as of January 14, 2020.[7][8]
Windows 10 IoT Core is a cut-down version of Windows 10 that is considered by some to be the successor to Windows Embedded Compact, however it maintains very little compatibility with it. Optimized for smaller and lower-cost industry devices, it is also provided free of charge for use in devices like the Raspberry Pi for hobbyist use.
Windows 10 IoT Core Pro provides the ability to defer and control updates and is licensed only via distributors; it is otherwise identical to the normal IoT Core edition.
Windows Server IoT 2019 is a full, binary equivalent version[9] of Windows Server 2019, intended to aggregate data from many ‘things’.[10] Like the IoT Enterprise variants, it remains identical in behavior to its regularly licensed counterpart, but differs only in licensing terms. It also is offered in both LTSC and SAC options.
Windows Embedded Compact (previously known as Windows Embedded CE or Windows CE)[11] is the variant of Windows Embedded for very small computers and embedded systems, including consumer electronics devices like set-top boxes and video game consoles. Windows Embedded Compact is a modular real-time operating system with a specialized kernel that can run in under 1 MB of memory. It comes with the Platform Builder tool that can be used to add modules to the installation image to create a custom installation, depending on the device used. Windows Embedded Compact is available for ARM, MIPS, SuperH and x86 processor architectures.[12]
Microsoft made available a specialized variant of Windows Embedded Compact, known as Windows Mobile, for use in mobile phones. It is a customized image of Windows Embedded Compact along with specialized modules for use in Mobile phones. Windows Mobile was available in four editions: Windows Mobile Classic (for Pocket PC), Windows Mobile Standard (for smartphones) and Windows Mobile Professional (for PDA/Pocket PC Phone Edition) and Windows Mobile for Automotive (for communication/entertainment/information systems used in automobiles). Modified variants of Windows Mobile were used for Portable Media Centers. In 2010, Windows Mobile was replaced by Windows Phone 7, which was also based on Windows Embedded Compact, but was not compatible with any previous products.
Windows Embedded Compact 2013[13] is a real-time operating system which runs on ARM, x86, SH, and derivatives of those architectures. It included .NET Framework, UI framework, and various open source drivers and services as ‘modules’.[14]
Windows Embedded Standard is the brand of Windows Embedded operating systems designed to provide enterprises and device manufacturers the freedom to choose which capabilities will be part of their industry devices and intelligent system solutions,[buzzword] intended to build ATMs and devices for the healthcare and manufacturing industries, creating industry-specific devices. This brand consists of Windows NT 4.0 Embedded, Windows 2000 Embedded, Windows XP Embedded, Windows Embedded Standard 2009 (WES09), Windows Embedded Standard 7 (WES7, known as Windows Embedded Standard 2011 prior to release), and Windows Embedded 8 Standard. It provides the full Win32 API.[12] Windows Embedded Standard 2009 includes Silverlight, .NET Framework 3.5, Internet Explorer 7, Windows Media Player 11, RDP 6.1, Network Access Protection, Microsoft Baseline Security Analyzer and support for being managed by Windows Server Update Services and System Center Configuration Manager.[15]
Windows Embedded Standard 7 is based on Windows 7 and was previously codenamed Windows Embedded ‘Quebec’.[16] Windows Embedded Standard 7 includes Windows Vista and Windows 7 features[17] such as Aero, SuperFetch, ReadyBoost, Windows Firewall, Windows Defender, address space layout randomization, Windows Presentation Foundation, Silverlight 2, Windows Media Center among several other packages. It is available in IA-32 and x64 variants and was released in 2010. It has a larger minimum footprint (~300 MB) compared to 40 MB of XPe and also requires product activation.[17] Windows Embedded Standard 7 was released on April 27, 2010.[18] Windows Embedded 8 Standard was released on March 20, 2013.[19][20] IE11 for this edition of Windows 8 was released in April 2019, with support for IE10 ending on January 31, 2020.[21][22][23][24]
For Embedded Systems (FES)
edit
Windows For Embedded Systems is a brand of Windows Embedded that consists of binary identical variants of the editions as are available in retail and function exactly the same as their regular counterparts, but licensed exclusively for use in embedded devices.[25] This brand consists of binary equivalent versions of Windows for Workgroups 3.11, Windows 95, 98, Windows NT 4.0 Workstation, Windows 2000 Professional, Windows Me, Windows XP Professional, Windows Vista Business and Ultimate, Windows 7 Professional and Ultimate, Windows 8 Pro and Enterprise, and Windows 8.1 Pro and Enterprise.
Originally, these editions simply had Embedded tacked onto the end of the SKU name until sometime around the release of Windows XP when the naming scheme changed to For Embedded Systems (FES). Examples of this former approach include Windows for Workgroups 3.11 Embedded, Windows NT 4.0 Workstation Embedded, Windows 2000 Professional Embedded and Windows Me Embedded. Microsoft changed the moniker for FES products again starting with some Windows 8/8.1 based SKUs, simply labeling them as Windows Embedded before the Windows version and edition. Two examples of this are Windows Embedded 8 Pro and Windows Embedded 8.1 Enterprise.[3]
Windows Embedded Server FES products are binary identical to that of regular Windows Server versions but licensed for embedded use, similar to Windows Embedded FES. This subseries include Windows Server, Windows Home Server, SQL Server, Storage Server, DPM Server, ISA Server, UAG Server, TMG Server, Unified Data Storage Server, etc. of various years, including Windows 2000 Server, Server 2003, Server 2003 R2, Servers 2004, 2005, 2006 and 2007, Server 2008, Server 2008 R2, Server 2012, Server 2012 R2, etc.
Windows Embedded Industry is the brand of Windows Embedded operating systems for industry devices and once only for point of sale systems. This brand was originally limited to the Windows Embedded for Point of Service operating system released in 2006, which is based on Windows XP with SP2.[11] Since, Microsoft has released an updated version of Windows Embedded for Point of Service named Windows Embedded POSReady 2009, this time based on Windows XP with SP3. In 2011 Windows Embedded 7 POSReady based on Windows 7 SP1 was released, which succeeded POSReady 2009. Microsoft has since changed the name of this product from «Windows Embedded POSReady» to «Windows Embedded Industry». Microsoft released Windows Embedded 8 Industry in April 2013, followed by 8.1 Industry in October 2013.
Windows Embedded NAVReady, also known as Navigation Ready, is a plug-in component for Windows CE 5.0. It is intended to be useful for building portable handheld navigation devices.
Windows Embedded Automotive, formerly Microsoft Auto, Windows CE for Automotive, Windows Automotive, and Windows Mobile for Automotive, is an embedded operating system based on Windows CE for use on computer systems in automobiles. The latest release, Windows Embedded Automotive 7 was announced on October 19, 2010.[26][27]
On January 10, 2011, Microsoft announced Windows Embedded Handheld 6.5. The operating system has compatibility with Windows Mobile 6.5 and is presented as an enterprise handheld device, targeting retailers, delivery companies, and other companies that rely on handheld computing. Windows Embedded Handheld retains backward compatibility with legacy Windows Mobile applications.[28] Windows Embedded 8.1 Handheld was released for manufacturing on April 23, 2014.[29] Known simply as Windows Embedded 8 Handheld (WE8H)[20] prior to release, it was designed as the next generation of Windows Embedded Handheld for line-of-business handheld devices and built on Windows Phone 8.1, which it also has compatibility with. Five Windows Embedded 8.1 Handheld devices have been released; Manufactured by Bluebird, Honeywell and Panasonic as listed below.[30]
Product | Release Date | CPU | RAM | Storage | Display | Camera(s) | NFC | MicroSD | |
---|---|---|---|---|---|---|---|---|---|
Back | Front | ||||||||
Bluebird BM180 (BP30) | January 2014 | 1.5 GHz Dual-core |
1 GB 2 GB |
8 GB 16 GB |
5” 720 × 1280 px 1080 × 1920 px |
8 MP | 1.3 MP | Yes | Yes |
Bluebird EF500 (EF500R) | September 2015 | Yes | Yes | ||||||
Honeywell Dolphin 75e | April 2015 | 2.26 GHz Dual-core |
2 GB | 16 GB | 4.3” 480 × 800 px |
Yes | Yes | ||
Honeywell Dolphin CT50 | April 2015 | 4.7” 720 × 1280 px |
Yes | Yes | |||||
Panasonic Toughpad FZ-E1 | August 2014 | 2.3 GHz Quad-core |
32 GB | 5” 720 × 1280 px |
1.3 MP | Yes | Yes |
- Eclipse ThreadX (previously Microsoft’s Azure ThreadX, now donated as open source to the Eclipse Foundation)
- ^ Microsoft. «Windows IoT lifecycle». Retrieved August 4, 2017.
- ^ Microsoft. «Extended Security Updates». Retrieved August 21, 2020.
- ^ a b «Windows Embedded Version Overview» (PDF). PROXIS. Retrieved August 29, 2020.
- ^ «IoT Enterprise FAQ». Microsoft. Retrieved July 2, 2021.
- ^ «IoT Enterprise Features by Release». Microsoft. Retrieved July 2, 2021.
- ^ «The next Windows 10 Long Term Servicing Channel (LTSC) release». Microsoft. February 18, 2021. Retrieved July 2, 2021.
- ^ «Windows 10 on Thin Clients: Deliver Best Results with Scout Agents (Part 1 of 2)». Fujitsu. Archived from the original on January 23, 2021. Retrieved August 25, 2020.
- ^ «Supported operating systems and browsers in Intune». Microsoft. Retrieved August 25, 2020.
- ^ «What is Windows Server IoT 2019». February 7, 2019. Retrieved December 9, 2020.
- ^ «Windows for IoT Datasheet» (PDF). Archived from the original (PDF) on March 13, 2020. Retrieved December 9, 2020.
- ^ a b «Microsoft Charts Its Road Map for Windows Embedded Business». News Center. Microsoft. April 15, 2008. Retrieved January 19, 2012.
- ^ a b «Which Windows Embedded Product is Right for Me?». Windows Embedded portal. Microsoft. Retrieved January 19, 2012.
- ^ «Microsoft announces general availability of Windows Embedded Compact 2013». Microsoft News Center. Microsoft. Retrieved July 14, 2013.
- ^ «Windows Embedded». msdn.microsoft.com. June 30, 2016. Retrieved January 30, 2017.
- ^ «Microsoft Brings Rich User Experiences to Smart, Connected, Service-Oriented Enterprise Devices With Windows Embedded Standard 2009». News Center. Microsoft. June 4, 2008. Retrieved January 19, 2013.
- ^ «Microsoft Announces the Next Version of Windows Embedded Standard to Be Built on Windows 7». News Center. Microsoft. October 28, 2008. Retrieved January 19, 2013.
- ^ a b Foley, Mary Jo (June 6, 2008). «Windows Embedded ‘Quebec’ due in 2010». ZDNet. CBS Interactive. Archived from the original on November 19, 2010. Retrieved January 19, 2013.
- ^ «Microsoft Delivers Windows 7 Technologies to Device Manufacturers With Release of Windows Embedded Standard 7». News Center. Microsoft. April 27, 2010. Retrieved January 19, 2013.
- ^ «Windows Embedded 8 Generally Available | News Center». news.microsoft.com. March 20, 2013. Retrieved May 3, 2016.
- ^ a b Foley, Mary Jo. «Microsoft makes first of its Windows Embedded 8 releases generally available». ZDNet. Retrieved May 3, 2016.
- ^ Tung, Liam. «Microsoft makes final push to rid world of Internet Explorer 10». ZDNet. Retrieved March 13, 2019.
- ^ Keizer, Gregg (December 1, 2015). «Nearly 370M IE users have just 6 weeks to upgrade». Computerworld. Retrieved May 17, 2020.
- ^ GitHub-Name. «Lifecycle FAQ – Internet Explorer and Edge – Microsoft Lifecycle». docs.microsoft.com. Retrieved May 17, 2020.
- ^ «Internet Explorer Support Lifecycle Policy FAQ». Archived from the original on November 6, 2015. Retrieved May 13, 2016.
- ^ «Windows Embedded Server». Windows Embedded portal. Microsoft. Retrieved January 19, 2013.
- ^ «Microsoft Drives the Future of In-Vehicle Infotainment | News Center». news.microsoft.com. October 19, 2010. Retrieved May 3, 2016.
- ^ Foley, Mary Jo. «Microsoft delivers Windows Embedded Automotive 7». ZDNet. Retrieved May 3, 2016.
- ^ «Windows Embedded Handheld 6.5 Key Features». Windows Embedded portal. Microsoft. Retrieved January 19, 2013.
- ^ «Windows Embedded 8.1 Handheld has been released to manufacturing; SDK is now generally available». Windows Embedded Blog. April 23, 2014. Retrieved April 25, 2016.
- ^ «Windows Embedded 8.1 Handheld». Microsoft. Retrieved January 30, 2017.
- Kan, Michael (November 14, 2012). «Microsoft updates roadmap for Windows Embedded, more releases to come». PC World. IDG. Retrieved January 12, 2015.
- Foley, Mary Jo (March 20, 2013). «Windows Embedded 8 releases generally available». ZDNet. Retrieved January 19, 2015.
- Valazco, Chris (February 25, 2014). «Panasonic’s latest Toughpad has the strength, thickness of 10 smartphones (hands-on)». Engadget. Retrieved January 19, 2015.
- Official website
· Hot!
Microsoft released the developer version of Windows Phone 8.1 last week to the masses and now the enterprise version of the OS has been finished as well. Microsoft announced this week that Windows Embedded 8.1 Handheld has reached RTM status and is now available for hardware partners to install on their devices.
Windows Embedded 8.1 Handheld has a number of security enhancements that Windows Phone 8.1 does not have, along with features that would only be used in a business or enterprise setting. In a blog post, Microsoft says that some of the new additions in the OS, compared to previous versions, include bulk provisioning of devices so businesses can quickly deploy those products.
Panasonic’s FZ-E1 can support Windows Embedded 8.1 Handheld.
It also has API support for devices that have integrated peripherals like barcode scanners and magnetic stripe readers. Finally, Windows Embedded 8.1 Handheld supports Wi-Fi only devices, USB Host and hardware keyboards for the first time.
Bluebird has two 5-inch devices that already support the OS and Panasonic’s rugged FZ-E1, announced in February, can also use Windows Embedded 8.1 Handheld; developers can download the SDK here.
Source: Microsoft via WinBeta | Image via Engadget