Win8 64-bit under MyEclipse 10.x custom JVM could not be started by workaround

The recent period of time in Win8 64 began to popularize, and other reasons, many children's shoes are beginning to use WIN8;

My machine is a brand of notebook, because of the so-called genuine, it has been used win8, but also slowly accustomed to, but found a good strange problem.

The problem is that MyEclipse 10.x under the Win8 64 bit, if the boot parameters (Myeclipse.ini) custom Set the JVM, that is, do not use the MyEclipse comes with the JVM, from a custom-VM or according to the environment variable JVM, will not start, whether the choice of 64 , 32myeclipse installation is the case,

Of course, the JVM here and Myeclipse64, 32 is also corresponding.

Report the following error:

Navigate to the log file:

Basically, I can't find the jar bag of myeclips.

However, if you do not use a custom JVM, you can use the MyEclipse default JVM to start successfully , and if you do not set it after installation, you use the MyEclipse default JVM. Very strange.

Never understood how this custom JVM differs from its myeclipse, and has not found the answer in Google for half a day.

• With administrator rights,
• It is useless to reduce the custom JVM version and bring it to the same.

Finally, directly in the win 7 64 test both,

1. JDK Myeclpise 32,
2. JDK Myeclpise 64,

1 and 2 are successful, the replacement JVM can be started.

A whim; can be run directly with Windows using Win7 compatibility, and finally solve the problem:

Now my environment is win 8 x64 +java 1.7 + MyEclipse 32 + custom JVM, use compatibility normal use, because I always love the 32-bit JVM, save memory. Hey..

As for this problem, only blame Myeclpise 10.X and win 8 compatibility.

Summary: Sometimes, the compatibility of Windows can solve a lot of unexpected problems.

Win8 64-bit under MyEclipse 10.x custom JVM could not be started by workaround