Problems with Mobile 5.0...process viewer?
Thomas Magma
We just tried our application with the new Mobile 5.0, and here is a
surprise, it doesn't work! The app involves PCMCIA drivers for the
CompactFlash port of a Axim. Now Mobile 5.0 won't recognize our OEM
Compactflash++ card. Now I have to try to troubleshoot where the problem
might be. Except the remote tools in the Embedded Visual C++ 4.0 application
doesn't appear to talk to Mobile 5.0. So what do I do now? We just ordered
the Windows Mobile 5.0 Development Kit from MS which is said to have remote
tools for Mobile 5.0, but a ten day delivery could really hurt us.
I feel as though I just broke my paddle and there is a bad stink in the air.
Does anyone have any suggestions?
Thomas
Chris Scott
however not all of them function properly. I can at least tell you that the
Remote Process Viewer does work with my 2005 device.
If you have MSDN you can download the beta and get access to the tools
today.
The PocketTV Team
news:eq7fhhC...@TK2MSFTNGP15.phx.gbl...
> Visual Studio 2005 Beta 2 does provide some Remote Tools for WM2005
> devices, however not all of them function properly. I can at least tell
> you that the Remote Process Viewer does work with my 2005 device.
i was not able to make any of those tools work with the emulator.
can you use them with emulator, or only with a real device?
Thomas Magma
having problems getting to the link that allows me to download the Visual
Studio. It is no problem to download Mobile 5.0 SDK, but when it comes to
Visual Studio 2005 Beta 2 all it allow me to do is have the DVD mailed to
me. Is it possible that they have removed the download feature of Visual
Studio 2005? Or am I just blind as a bat?
Thanks,
Thomas
"Chris Scott" <donotATmailDOTcom> wrote in message
news:eq7fhhC...@TK2MSFTNGP15.phx.gbl...
Chris Scott
I never use the emulators. Due to the type of work I do, the emulators were
never able to properly reproduce the environment of an actual device. They
actually caused other issues since they had bugs that the device did not
have so you could put in a workaround for a nonexistent bug that caused
other problems on an actual device.
It is possible they have gotten better over time, but a real device is
always best for debugging. I'll try and figure out how to run it and test
them for you though.
"The PocketTV Team" <sup...@pockettv.com> wrote in message
news:e9HRYhD0...@TK2MSFTNGP09.phx.gbl...
Chris Scott
it is still available online.
"Thomas Magma" <some...@overtherainbow.com> wrote in message
news:ufCjmoD0...@TK2MSFTNGP15.phx.gbl...
Thomas Magma
Any idea if Remote Kernel Tracker works?
Thomas
"Chris Scott" <donotATmailDOTcom> wrote in message
news:eq7fhhC...@TK2MSFTNGP15.phx.gbl...
Chris Scott
"Thomas Magma" <some...@overtherainbow.com> wrote in message
news:e$vmhXR0F...@TK2MSFTNGP10.phx.gbl...
Chris Scott
seem to work just fine with the exception of the Remote Spy tool.
I was able to see the registry on the Emulator and used Remote Zoomin to
take a screenshot as well. I'm not sure why they are not working on your
end but I would guess it's a configuration issue of some kind.
On all the PC's I'm using to test WM5 I have the following:
eVC 3
eVC 4 (SP3 I think, I know I'm not on SP4)
VS .NET 2003
VS .NET 2005 Beta 2
Thomas Magma
CE Remote Kernel Tracker. It's giving me the error "Remote kernel tracker is
unable to connect to the device because it is not CELOG enabled." It looks
like it is a known issue but I can't seem to find the fix anywhere. Has
anyone heard of this bug and knows a fix?
I'm using EVC++4.0 SP4
Thomas
"Chris Scott" <donotATmailDOTcom> wrote in message
news:u38gnUy...@TK2MSFTNGP12.phx.gbl...
The PocketTV Team
When you get them to connect, is the emulator craddled, or un-craddled ?
"Chris Scott" <donotATmailDOTcom> wrote in message
news:u38gnUy...@TK2MSFTNGP12.phx.gbl...
Chris Scott
thing up and connected and it worked. Today I tried again both cradled and
uncradled and it worked for both.
"The PocketTV Team" <sup...@pockettv.com> wrote in message
news:%23eV7%238D1F...@tk2msftngp13.phx.gbl...
The PocketTV Team
> Both. I had no idea you could even do that. Initially I just started the
> thing up and connected and it worked. Today I tried again both cradled
> and uncradled and it worked for both.
The connection error given by Remote Spy++ is either:
<<No connection could be made because the target machine actively refused
it.>>
or:
<<The specified service does not exist as an installed service.>> (after a
brief windows displays: "connected to device" for a fraction of a sec)
or:
<< The process cannot access the file because it is being used by another
process.>>
The CE Device selected for the connection is "Windows Mobile 5.0 Pocket PC
Emulator", which is the emulator that is currently running (i can
cradled/uncradle it with the Device Emulator Manager).
No idea why it does not work for me, and I find that ennoying. I use an
up-to-date XP Pro SP2 with all the security patches installed.
Chris Scott
the Remote Spy application. That application does not work on the emulator
or on an actual device. I didn't need the full Spy functionality so I just
wrote a small app to give me what I needed and moved on. Hopefully they get
that one working for release though.
"The PocketTV Team" <sup...@pockettv.com> wrote in message
news:upfRZ3U1...@TK2MSFTNGP12.phx.gbl...
The PocketTV Team
I guess I'm not as lucky as you...
"Chris Scott" <donotATmailDOTcom> wrote in message
news:%236qxDPY...@TK2MSFTNGP15.phx.gbl...