Configuring Pocket PC 2003 Emulator to use Virtual Switch prior to

Hi

I am trying to get my Pocket PC 2003 Emulator set up to work with
ActiveSync.
As far as I can tell, I need to follow the instructions that accompany
the Pocket PC SDK, that tells me to configure the emulator to use
Virtual Switch, and then run the emulascfg command to set up the
necessary parterships so that ActiveSync can work.

Well, I fail at the first hurdle - getting VirtualSwitch configured
using emvedded VC++ 4. I can get the correct dialogue boxes up - but
after I set the ethernet connectivity to Virtual Switch, and then try
and test the connection, it never completes. The emulator is started
successfully, and I see messages about copying various files across to
the device, but the connection is never made to the device.

I have checked in the event log, and see regular 10 sec timeouts
appearing in the WinCE section (source beign tltcpip) but after 101
attempts the cemgr app gives up trying.

What have i done wrong?

Everything was installed from scratch onto a win 2k server machine,
service pack 4.

I downloaded the embedded vc4++, pocket pc sdk, and active sync stuff
from new (no prior install). I installed .NET framework after all these
were installed.

Is there some diagnostics or or mechanism I can use to find out what
is causing this failure?

Do I need to completely reinstall and start again?

Is there some basic config issue I need to complete?



Thanks for any pointers anyone might have for me here

- chris

Chris
Sun Feb 08 00:12:02 CST 2004

Hi,
My understanding is that the virtual ethernet requires a physical ethernet
in the desktop which it virtualizes to the Pocket PC Emulator. Do you have
one installed?


--
Chris De Herrera
http://www.cewindows.net
http://www.tabletpctalk.com

"Chris Jobson" <jobson@sybase.com> wrote in message
news:e1axnvL7DHA.2760@TK2MSFTNGP09.phx.gbl...
> Hi
>
> I am trying to get my Pocket PC 2003 Emulator set up to work with
> ActiveSync.
> As far as I can tell, I need to follow the instructions that accompany
> the Pocket PC SDK, that tells me to configure the emulator to use
> Virtual Switch, and then run the emulascfg command to set up the
> necessary parterships so that ActiveSync can work.
>
> Well, I fail at the first hurdle - getting VirtualSwitch configured
> using emvedded VC++ 4. I can get the correct dialogue boxes up - but
> after I set the ethernet connectivity to Virtual Switch, and then try
> and test the connection, it never completes. The emulator is started
> successfully, and I see messages about copying various files across to
> the device, but the connection is never made to the device.
>
> I have checked in the event log, and see regular 10 sec timeouts
> appearing in the WinCE section (source beign tltcpip) but after 101
> attempts the cemgr app gives up trying.
>
> What have i done wrong?
>
> Everything was installed from scratch onto a win 2k server machine,
> service pack 4.
>
> I downloaded the embedded vc4++, pocket pc sdk, and active sync stuff
> from new (no prior install). I installed .NET framework after all these
> were installed.
>
> Is there some diagnostics or or mechanism I can use to find out what
> is causing this failure?
>
> Do I need to completely reinstall and start again?
>
> Is there some basic config issue I need to complete?
>
>
>
> Thanks for any pointers anyone might have for me here
>
> - chris
>

Chris
Mon Feb 09 06:55:46 CST 2004

Chris De Herrera wrote:
> Hi,
> My understanding is that the virtual ethernet requires a physical ethernet
> in the desktop which it virtualizes to the Pocket PC Emulator. Do you have
> one installed?
>
>

When you say 'physical ethernet in the desktop' what do you mean by that?

I have an ethernet card (for LAN connectivity) - so I assume that counts
as physical ethernet.

Do you need to install and use the loopback adapter? Or is that onlt
when there is no physical ethernet (presumably, I guess, when you
connect to the outside world by USB modem or whatever).

I would be interested in hearing from anyone who has actually made this
work. I completely reinstalled everything last Friday - but it still
didn't work. I just wonder if there is some fundamental mistake I am
making - probably really simple but dumb on my part.

thanks for getting back on this

- chris