Somehow, since a month ago or so, I can't debug or use any util on Win
Mobile 2003 (both iPaqs and Dells) when WiFi is turned on!
I know that you can't start debugging and use Wifi successfully, but I could
always break into a running process in PPC 2003 to debug.

This is pretty weird. I tried re-installing eVC++, Platform Manager and the
2003 SDK in different order. I even reinstalled Windows in my desktop, but I
keep having these problems. Has anybody experienced the same thing? could it
be that some of the latest Windows Update patches is generating this poblem?

Thanks in advance for any hint on this.
--
Raul Santelices Ahués, M.Sc.
Edunova / Tecnlogía Portátil en la Sala de Clases
Pontificia Universidad Católica de Chile

Re: platform manager (debugger, etc.) fails when WiFi is on! by David

David
Thu Apr 07 14:47:18 CDT 2005

Yes, I've seen this problem before. How the debugger connects when there are
multiple IP addresses is apparently undefined. So I have no ideas on how to
configure things to work. Sometimes it does, often it does not. The most
reliable solution is disable WiFi on your desktop while debugging.

If your Pocket PC has Wifi as well, you might try connecting the Pocket PC
via ethernet instead of via ActiveSync (see eVC help for instructions).

Hopefully others here will have some ideas.

David
------
This posting is provided "AS IS" with no warranties, and confers no rights.

"Raul Santelices" <no spam rasantel@ no spam ing.puc.cl> wrote in message
news:eQ2Is4gOFHA.4000@TK2MSFTNGP15.phx.gbl...
> Somehow, since a month ago or so, I can't debug or use any util on Win
> Mobile 2003 (both iPaqs and Dells) when WiFi is turned on!
> I know that you can't start debugging and use Wifi successfully, but I
> could always break into a running process in PPC 2003 to debug.
>
> This is pretty weird. I tried re-installing eVC++, Platform Manager and
> the 2003 SDK in different order. I even reinstalled Windows in my desktop,
> but I keep having these problems. Has anybody experienced the same thing?
> could it be that some of the latest Windows Update patches is generating
> this poblem?
>
> Thanks in advance for any hint on this.