Whenever I get this problem with PODS (and it's rather often), so fat it has always meant that a crashed version of the Emulator or the Simulator is still running. It's worse with the Simulator, because as a result of the previous crash, it could be that one of its DLLs is still in memory - even though the program itself is not.
In order to fix it, I start the Task Manager of Windows (or the equivalent of your OS) and kill the processes Emulator.exe or PalmSim.exe. If I had debugged on the Simulator, I also use the ListDLLs program from SysInternals http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml to produce a list of the DLLs that are in memory and search that list for the path(s) of the folder where the Simulator resides. I also exit PODS, although I'm not sure that it is necessary. The above procedure has always worked so far - i.e., after it I was able to launch the Emulator or the Simulator and to debug on it. Yes, it is an annoying problem, but given how PODS works, I doubt very much that it can be fixed. Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
