We just recently switched my Residential Gateway project to Windows CE 4.2
(from 4.1) to pick up the new features for gateways and found an issue we
can find no documentation on. We are using the "residential gateway"
configuration for our project (ARMV4I). When we enable KITL, do a debug
build and run it on our device, we are no longer able to PING the device or
HTTP out to it. The device is also not able to PING the PC it is connected
to. Since the device only has one Ethernet port we use VMINI to share that
port between KITL and the Networking stack. This worked perfectly in WinCE
4.1 and it works perfectly if we do a retail build with KITL and VMINI
disabled. What do we need to change between 4.1 and 4.2 in our VMINI network
configuration to get this to work?
Mark Moeller
Qualnetics Corporation