Mike,
This problem was brought to my attention and I had a few suggestions I’d like you to try before we give up.
My first thought on this problem is that your path for Tomcat is too long. Let me explain the “too long” part… in NetBeans when you launch Tomcat, the Tomcat launcher builds out the classpath by finding and FULLY qualifying all of the JARs that Tomcat needs to run. The problem here is that if you install Tomcat to some long path (like you have) the actual command line that attempts to be run by the launcher is so long, that the operating system concatonates the command which makes it invalid and the whole operation dies.
I’m not sure how the Tomcat launcher in ME works, but I can’t imagine its much different. So, Tip #1
Try and reinstall your version of Tomcat to C:\Tomcat for testing reasons. If that works, then maybe you can find a good balance on your own system between too long of a path and good organized directory.
If this doesn’t work and doesn’t change anything, then Tip #2 is to:
Install Tomcat 5.0.16 into C:\Tomcat5 and give it a try to see if that works. Don’t forget to change the application launcher and update your deployment settings.
If this doesn’t help, I would wonder if its a JDK issue, so to help avoid downloading a new JDK, try Tip #3:
I noticed in your screenshots you have the preview of 1.5 installed, switch your JDK to that for Tomcat to use and see if it works now (try Tomcat 4 and 5 if 4 doesn’t work).
Now if THAT doesn’t work, I would definately do Tip #4:
Download stable release of both pieces of software: Eclipse 2.1.2 and MyEclipse 2.7RC2 and try that.
If THIS doesn’t work, well then I’m all out of ideas. We would have to probably have to start digging into what plugins you have installed. A majority of the time you get weird errors with ME is due to conflict with another plugin. So fresh installs of the software (IDEs) I mentioned above are good to try.
Let me know if any of that helped.