Device Emulator 1.0 standalone with Windows Mobile 5.0 MSFP
Hello Everyone,
Device Emulator 1.0 (yes, the same one that released with Visual Studio 2005), is now available as astandalone download from:http://www.microsoft.com/downloads/details.aspx?FamilyId=C62D54A5-183A-4A1E-A7E2-CC500ED1F19A&displaylang=en
This release comes along with theOS Image for Windows Mobile 5.0 w/ Messaging and Security Feature Pack (MSFP).Using this OS image with the emulator will allow you to demonstrate and play with technologies like Direct Push. Better still, you can now include the emulator and OS images in your online training materials
Thanks,
Anand for the Device Emulator Team
I can't get it to browse the internet either. I've tried everything, loopback adapter, NE2000 config, connection settings changes and nothing. At best, I can generate an IP address conflict between the NE2000 NIC on my computer and the one used by the emmulator but, even then, there is no connectivity.
Very frustrating. Get it right people - it shouldn't be this difficult to install/configure/use.
For Internet connectivity, you will need to have installed the Virtual Switch (VMNet) Driver. This is best obtained by installing Virtual PC software:
-- Virtual PC 2004 is available from www.microsoft.com/downloads and Virtual PC 2007 Beta is available by registering via the Microsoft Connect program (http://connect.microsoft.com).
Once you have installed the Virtual Machine network driver (you can check under "My network Places->Properties"), then enable the NE2000 checkbox on the emulator's config dialog. this should help the emulator get an IP address. You can ping the IP address to make sure you have connectivity.
-- Device Emulator Team
In most intranet networks, your intranet sites will have IPSec enabled. For older versions of CE and Windows Mobile, there was no way to connect to corpnet machines short of requesting a boundary machine exception from your IT folks.
Please check into this matter.
-- Device Emulator Team
Installing Virtual PC 2004 or 2007 automatically installs the VMNet driver.
FYI: This was the preferred way to get the virtual machine network driver even when the standalone VMNet installer was still out there, as the VMNet installer was *old*