I've also experienced this "Can't connect to target environment" problem, both on XP Home and XP Pro. Both machines have a GB of memory. Instead of agonizing over it (although I did write a note to this list about it a month or two ago) I just set up the debugger and the emulator/simulator as tools in the tools menu and launch them that way. No big deal. You can start them from the Windows start menu, too, as mentioned below.
As one who doesn't derive a wage from coding for the Palm (yes, I'm a hobbyist...) I've found PODS to be a nice way to get things built and debugged without spending $$$ on Codewarrior (which I'm sure is a fine tool) or (gasp) using the command line. As an aside, before PODS I was using MS Visual C++ as my IDE for Palm development. VC++ allows you to create a "makefile" project--basically, it runs a makefile that you specify whenever you want to do a build. Obviously, you can't use the built-in debugger, but you can define menu items to run the Palm debugger and emulator and simulator, just like PODS (except that PODS will maintain the makefile for you). Incidentally, Microsoft is offering free Express versions of Visual C++, Visual Basic, and some of its other development environments. You can download them at Microsoft's web site (at least, you could a couple of months ago...). Dave Ek -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jay Ts Sent: Monday, May 15, 2006 7:54 PM To: Palm Developer Forum Subject: Re: PODS ERROR one last time Jim McConnell wrote: > I have been watching and reading these posts with interest because I am > having the same problem. I have attempted all the 'proposed possible fixes' > with no luck. Wow, that's a real bummer. I've been getting a lot out of this discussion, because it's helped me understand the workings of the PODS IDE much better. It seems that the "Can't connect to target environment" error message happens when the IDE attempts to start up a simulator task, and then open a communications connection to it through networking. If the simulator fails to start, or the network connection fails, that same error message comes up. What I suggest to anyone who's still suffering from the problem is to think of the overall system, and see if there's some way to more perfectly isolate the exact source of the failure. If you can do that, then I'm willing to believe that there's probably a way to solve, or at least work around, the problem. As I've said before, I don't rely on the PODS IDE for debugging AT ALL! On the rare occasions I even use it, I'm much happier starting up the debugger from the Windows Start Menu, and I have a folder containing shortcuts to each simulator executable, so I can pick the one I want. Once you get the hang of it, it's really easy, just not as automatic. > What makes this even weirder for me is that I have two situations with > different results. I have a laptop that has Windows XP Professional and a > desktop with Windows XP Home. Both of them have the same version of PODS > installed and both installations have the same settings. > > However, the laptop runs PODS without any hitches at all and the desktop > generates the error. One of the very few differences between the Home and Pro versions of XP has to do with networking support. The difference I'm aware of has to do with ability to join a domain, and that wouldn't or "shouldn't" have any effect on the operation of PODS on a single system. (But then, who knows?) > I find it quite odd that noone is able to give a > definitive answer for this, especially since PODS is the "premier" > application to be used. Cough. :) PODS is "free as in beer", and sometimes maybe "free and worth it". It's been around a couple of years, is only at version 1.2, is in serious need of bug-fixing and further development, and PalmSource hasn't delivered an update in a very long time. I'm starting to wonder if anyone at Access/Palmsource is still working to further develop PODS at all. After reading about the tribulations of others I feel very fortunate to say that PODS is _very_much_ working for me, and I get along with it very well. But, I'm definitely keeping my eyes open with respect to switching to CodeWarrior at some point. All I need is a compelling reason to do so. (Or, maybe I'll just keep using PODS as I have been, and in a couple of years shift to developing native Palm Linux apps.) Jay Ts -- There is no path to happiness. Happiness is the path. -- The Buddha -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
