مشكلة في تشغيل برنامج ال Blue J

BlueJ asks for the JDK location on every startup - how can I fix this?

The situation is usually this: on a multi-user installation, the system administrator installs and starts BlueJ, including the selection of the Java version (JDK/J2SDK). BlueJ runs fine. But when other users start BlueJ, they are prompted every time for the JDK location.

The reason are write restrictions to the Windows registry. On Windows, BlueJ remembers the selected JDK version by writing an entry into the user space of the registry. If the registry is write protected, or if it is restored to its original state on every login, this information is lost, and the user will be asked again.

There are two solutions available.

The first is to give users write access to the Windows registry.

If this is not practical (for example in some lab environments) then BlueJ can be explicitly configured to use a specific JDK, using a property in bluej.defs (see Tip 4 in the tips archive for general info about configuring BlueJ).

Set the 'bluej.windows.vm' property in bluej.defs to the path of the JDK you want to use. This property is commented out by default. If it is set, BlueJ will not check the registry, not ask the user, but just use this Java version and start.

اقتباس

Error: "Bluej was unable to create a virtual machine(VM) to execute projects".

• As the full message text states, this problem is normally caused by firewall software interfering with BlueJ's operation. More information on how to deal with this issue is available

here.
Another possible cause of this problem is that characters in the path to your project (including the project name) are not representable in the system character set (which an option available from the Control Panel). You can either change the system setting, or rename/move your projects to a location without the troublesome characters. This problem is actually due to a Java bug.
If you cannot resolve the problem, you will need to contact the BlueJ support team.