Problem with the Pocket PC 2003 Emulator

  • Thread starter Thread starter Carsten Marx
  • Start date Start date
C

Carsten Marx

Hello,
since today i've a huge problem with my Pocket PC 2003 Emulator.
I'm using the emulator with Visual Studio .NEt 2003 to debug a application.
When i start debugging my project is build properly, all the data is
copied via active sync 3.7 to the emulator...
the the message applcation starts appears in the output window from
visual studio but nothing happens in the emulator...
one minute later a message appears, that the application is unable to
start...

whats going on ..... i'm frustrated.

btw:
when i start the executable manually in the emulator the application
starts.. but this is not the best way to debug isn't it... :-)
 
Search the archives as the cause of this problem vary (I don't have it
myself). Apologies if you have answered some of the questions below already.
In random order here are some questions:

Does the problem occur on a device or the emulator?
On a device is toolhelp.dll included?
Can you Debug->Start Without Debugging? Can you manually run the exe on the
target?
Have you got a network connection (or loopback adaptor) when trying this?
Have you tried resetting/turningOff the unit/emulator?
Are you running on a "slow" laptop?
Does it happen with all CF apps or just a particular one? Try a simple
"hellworld" app.
Can you try another device with this PC OR another PC with this device?
Which ActiveSync version are you running?
Have you got a wireless card on the device?


Cheers
Daniel
 
the application is unable to start...

This is normally a network problem. VS has to use what it thinks is an Ethernet connection to do debugging with the emulator.

If you don't have an Ethernet board, then you have to install the Microsoft loopback adapter. Do searches at MSDN to find the instructions.

If you have another network connection that isn't Ethernet, you might have a lot of trouble getting this to work. I have one computer with a dial-up modem connection and I can't get debugging to work on the emulator because VS only finds the dial-up connection when it wants to find the loopback connection.

By the way, if you start without debugging, your application will probably run fine, even if you don't fix the problem.

Also, one easy way to make it work is to use VMWare or Virtual PC with the VS 2005 beta. The emulator with VS 2005 can work in a virtual session, and this is good because you can also have a virtual network connection that side-steps the problems.

Eric
 
Back
Top