Hi, I have been following : http://www.buzztouch.com/resources/Setting_Up_Your_Android_Development_Environment_v1.3.pdf and got to "Step 5. Install Eclipse" when I encountered my first problem. I installed everything as detailed in the above link, including Java but I get a Java Virtual machine Launcher error that states : --------------------------- Eclipse --------------------------- Java was started but returned exit code=1 C:WindowsSYSTEM32javaw.exe -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx512m -XX:MaxPermSize=256m -jar D:Android App softwareEclipseeclipseplugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -os win32 -ws win32 -arch x86_64 -showsplash -launcher D:Android App softwareEclipseeclipseeclipse.exe -name Eclipse --launcher.library D:Android App softwareEclipseeclipseplugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502eclipse_1406.dll -startup D:Android App softwareEclipseeclipseplugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.overrideVmargs -exitdata 1838_60 -product org.eclipse.epp.package.jee.product -vm C:WindowsSYSTEM32javaw.exe -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx512m -XX:MaxPermSize=256m -jar D:Android App softwareEclipseeclipseplugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --------------------------- OK --------------------------- I appreciate any help offered. Linda

Just an update, I have uninstalled and re-installed Java, and get the same error. I have also gone to MySkylla's blog and used the link in "Got Milk? Is Eclipse Setup? Correctly? Got SDK, ADT, Platform Tools? " which tests if you have Java. The result of running it says Java is working. Linda

Are you 32 bit or 64 bit ? Fred

Looks like you have the 64-bit version of Eclipse installed. I personally use the 32-bit version, even on my 64-bit laptop. Also..you have a JDK, and not a JRE, installed, correct? Mark

Hi Fred and Mark, Thank you both and sorry for the slow response (time differences and work). Yes my PC is 64-bit and I installed JDK-7u5-windows-x64.exe . Should I change the Eclipse to 32-bit? Linda

That's a good question. I'm not sure if the answers is yes or not . I have seen that some do so and the issue is resolved. It won't be much of a limitation so I would recommend it. Fred

Do you suggest the Eclipse Classic 3.7.2? Linda

I just installed the Eclipse for 32-bit and it now successfully opens!! Just thought I should let you know that I just realised that I had inadvertently installed the Eclipse IDE for Java EE Developers 64-bit (not the Classic). Thank you both for your help with this. My learning curve can now continue! Linda

The reason I qualify my answer is that in various YouTube videos 64 bit is apparently used with out a problem. In my guide to installing Eclipse I recommend against the 64 bit version. I think I'll emphasis that even more. Fred

If you're not going to be making 64-bit apps, which we don't with buzztouch, than there's no need to use the 64-bit version. That version does provide better memory management on 64-bit machines but, again, not that big an issue for most people. Mark

Thanks Mark, I didn't know the difference between them. It is all so new.

Different cause, same problem. No VM found error when attempting to launch eclipse. Uninstalled, reinstalled, updated, right version, classic, jre, sdk, etc. Once eclipse and java where installed directly into c:\folder they worked fine. Letting the installer place them in "Program Files" or "Documents and Settings" paths did not result in success. C:\eclipseV1\eclipse\eclipse -vm :\javaV1\jre\bin\java If EVERYONE else knew this already, free laugh on me. If you don't know this yet, install directly to c:\ path folder. One readme file indicated java occasionally has trouble interpreting $PATH$ info correctly, which clued me into this possible solution. Rock-N-Roll

Interesting! When I did the install on my systems, I let the Java installer put it where it wanted, which was in Program Files. For Eclipse, I unzipped it into c:\eclipse, like you did. It seems to work just fine this way for me. Pathing stuff for Windows seems to be problematic from time to time. Thanks for the report! Mark

@ShadowHound, I appreciate your feedback and will note the issue for future reference, but I found the letting the installer do it's work is best. Perhaps in your new install something innocuous was the difference. Perhaps not. Either way welcome and hope the rest of the process goes more smoothly. Fred