Name: chT40241 Date: 05/06/99


After installing the Java Plug-in 1.1.2_001, execution of the jre command from the system directory on Windows NT/95/98 fails with the following message: "Cound not locate Java runtime". Investigation shows that the cause of the problem is related to how the Java Plug-in install writes the Java Runtime Environment keys and a defect in the jre command's processing of the version string.

The Java Plug-in 1.1.2_001 install writes the following Java Runtime Environment keys to the registry under HKEY_LOCAL_MACHINE:

    Software\JavaSoft\Java Runtime Environment
        1.1.7B_003
            JavaHome <location of Plug-in install>
            MicroVersion "7"

However, these values do not match the registry keys expected by the jre command. The correct keys to write would have been:

    Software\JavaSoft\Java Runtime Environment
        1.1
            JavaHome <location of Plug-in install>
            MicroVersion 7B_003

However, even if these correct key values were written to the registry by the Plug-in install, there is a defect in the jre command that prevents it from parsing a MicroVersion string that contains an underscore. In the JRE_ParseVersion method in jre.c, the sscanf command needs to be updated to accept an underscore as part of the micro version string. Here is the corrected sscanf call:

sscanf(ver, "%*[0-9]%n.%*[0-9]%n.%*[0-9a-zA-Z_]%n", &n1, &n2, &n3);

Note that execution of the jre command from a typical Java runtime install directory still works since it can overcome the registry key problems by using GetModuleFileName to determine its path and then work from there to find javai.dll and the JAR files for the classpath.

(Review ID: 57907)

======================================================================