Eclipse not working on windows 7

You can download the x64 edition of Java 1. As of right now, you can download only x32 editions from the Eclipse main website. DLL requires a x32 system. The site with the latest releases, including x64 systems, can be found here. The latest stable edition of Eclipse is 3. Microsoft goes open source It looks like Microsoft is finally going open-source. Windows Azure, an open-source system optimnized for cloud computing will receive some cool tools for PHP and Java development.

Windows 7 release date in ? He is interested in finding new ways to break Windows, find common errors and help others to fix them. Aside from that, he loves to fully customize systems with Rainmeter and Dreamscene, find out more about ancient civilizations like the Chachapoya, sharpen his digital photography skills and create software with a small group of selected developers.

Breadcrumbs Home Projects Forums. Eclipse Community Forums Forum Search:. Search Help Register Login Home. NullPointerException at org.

Powered by FUDForum. Page generated in 0. Sign up to our Newsletter A fresh new issue delivered monthly. Eclipse Community Forums. Forum Search:. Tue, 29 May Vincenzo Caselli Messages: Registered: January Hi, maybe the problem is only due to the undergoing work on the Photon Eclipse Train, but just in case I would like to make it known. I am testing WB 1. I first tried with 3. I have the latest JDK installed as well, which is 6 update This is a 32 bit machine.

Any ideas? Here is the log file that Eclipse is generating:. The sun. If I have the equinox jar in a path with a percent sign in it, equinox won't start. For example:. Eclipse requires a JVM to run and does not include one in the download. You need to grab a VM yourself; the Eclipse downloads page has pointers to where you can get one. You may have a VM, but Eclipse cannot find it.

To avoid possible conflicts, always specify the VM you are using with the -vm command-line argument. Eclipse 3. As of Eclipse 3. If you are using a home-grown or experimental JVM and encounter problems, you may not be able to get help from other Eclipse users. Use a reputable VM. If you run into trouble, always try a VM from a major distributor and see whether the problem goes away. Eclipse also may not start if there is a mismatch in the JVM's architecture and the particular Eclipse build you are using.

If you are on a bit system but are using a bit JVM, then you should download the bit version of Eclipse. Likewise, if you are using a bit JVM, then you should get the bit version of Eclipse. Eclipse will not run on Windows 95 or Commodore 64, for example. If your machine does not match one of the configurations described in the readme, it may still run, but you are on your own!

Believe it or not, about once a month, a user reports start-up failure: The user has unzipped Eclipse without selecting the use folder names option. Make sure that the result of unzipping is an install tree with an eclipse directory at its root. The Ark unzip utility in KDE is known to mangle Eclipse zips, so use a different unzip program to install there.

The built-in unzip utility in Windows has also been known to have problems, particularly when installing into paths with relatively long names. Do not do this. Either install Eclipse in a brand new directory or use the Eclipse Update Manager to upgrade an older Eclipse.

You can still keep your old workspace. Look in the Eclipse readme file for more details. It is not always user error. Some integration builds, and even the odd stable build, will have start-up problems under certain configurations that were not well tested.

For example, build 3. For more advanced users willing to accept less stable builds, consult Bugzilla to see if your particular start-up problem has already been reported. Prior to Eclipse 3. This should not be a problem with Eclipse 3. See FAQ for more details.