Hi, all. I've got a collection of very old versions of Windows, Tomcat, and Java. My working configuration is Windows 2000 Professional, Tomcat 4.1.30, and Java SDK 1.3.1_09.
When I install a newer version of Java and remove 1.3.1, the three instances of Tomcat that I use will no longer run as a service. When Windows starts up, or when I attempt to start the services manually, I get the following error messages in the NT event viewer: "Could not load the Java Virtual Machine. " "The LoadLibrary function failed for the following reason: The specified module could not be found." Combing over the documentation, this seems to be caused by an incorrect configuration of my environment variables. So, I checked (and double-checked) that they're correct. When Tomcat works, I have a JAVA_HOME of c:\jdk1.3.1_09 and a PATH entry of c:\jdk1.3.1_09\bin. When it doesn't work, the JAVA_HOME and PATH entries point to where I've installed whatever new version of Java I'm trying (1.4x, 5.x, or 6.x), which is just off of the root directory of c. Now, when I attempt to start Tomcat using the startup.bat, it works just fine. So, here's my two-part question: Is there something else that I need to do to my environment variables in order to get this to work? Furthermore, is there a setting in any of the xml properties documents that I can adjust to "force" Tomcat to look for a jdk/j2sdk in the location of my choosing? I do have plans to update all of this stuff to much newer versions of both the OS and the Java components, but right now, I can only update Java; I have to stick with the current version of Tomcat. Thank you for the assistance! Eric B
