. Note that a new version of Windows Embedded Compact 2013 (vNext) is coming. Its not radically different to the exist RTM. For example, you can directly load and use existing OS projects and subprojects. Of note is talk that Nokia Phones may support Android. But with the announced new of Windows Phone (8.1) the hardware is able to support Android as well as WP 8.1 so that might be a tautology Note an update for Windows 8.1 is mooted for the Northern Spring. Adeneo have a Compact 2013 BSP for the ARM Cortex A8 (TI Sitara AM33XX) and also have developed a Shell for Compact 2013. The AM33XX is on the lower end of performance relative to the multicore A9s (and cheaper).
About Hyper-V Networking (Windows 8)
The current Hyper-V discussion is about getting a desktop VM (to support Visual Studio 2012/13 with Compact 2013 Platform Builder) up and running to support Windows Embedded Compact 2013 development, as well as running a Windows Embedded Compact 2013 Virtual CEPC for OS development..
When a Hyper-V VM runs, it networks via a Virtual Network Switch. After installing Hyper-V (see previous post) you add a Virtual Network Switch in Hyper-V manager. You add a suitable network connector to the VM hardware (there are two options) , and connect it to the Virtual Network (switch). It is recommended to have two network adapters on the host machine, one for the virtual network switch and one for normal remote communications. I use a USB Network adapter as my secondary NIC. There are three types of virtual network switches:
See the following table for the differences.
Virtual Network Switch type
External Access to/from
Access from host OS
Access other VMs
RDP from host
RDP from external
Bound to physical network adapter
Generally one uses External.
There are two types of network adapters for Hyper-V VMs:
A Network Adapter is used with desktop/server Windows OS VMs to which can be installed the Integration Services allowing better options with display, copy and paste etc.. It is installed from a virtual DVD once the VM is installed and running.
A Legacy Network Adapter is used for Windows Embedded Compact 3013 vCEPC so that it can boot a receive an OS nk.bin file from a development system over the network. (Note TFTP is used).
Prior to Windows 8, Hyper-V Virtual Networking would not work over WiFi. This has now been resolved for this version of Hyper-V. Ref http://blogs.msdn.com/b/b8/archive/2011/09/07/bringing-hyper-v-to-windows-8.aspx
Finally, there is a video about the Hyper-V Networking on Windows 8 of about 3 minutes duration at: http://media.ch9.ms/ch9/cddc/8b132177-428a-4b5d-8267-9f560134cddc/HyperV09062011_low_ch9.mp4 (Also referenced on the above link).
Hyper-V Virtual Network Switch
Just "Follow-the-bouncing-ball" Some pictures tell a thousand words. Click on VIEW SLIDE SHOW in the middle below , open the first slide, then View Slide Show (or browse manually through the slides). These slides are sourced from my Skydrive (now called OneDrive):
Hyper-V VM Network Connector
Again, just "Follow-the-bouncing-ball" Some pictures tell a thousand words. Click on VIEW SLIDE SHOW in the middle below , open the first slide, then View Slide Show (or browse manually through the slides). These slides are sourced from my Skydrive (now called OneDrive):
Test the VM Network
Trackback from David JonesHyper-V and Compact 2013 (3 articles)
Managed Code as part of the OS Build ( 3 articles) ...
Have fixed the link to the slides. Permissions weren't public.