[Jon Nelson]

As I mentioned, there were keys for both HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Development Kit1.7 and HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Development Kit1.7.0_03.  I'm not sure where the 1.7 key came from.  The JavaHome for that key was C:Program FilesJavajdk1.7, which does not exists on my system.  I changed that value to C:Program FilesJavajdk1.7.0_03 to match the one I do have on my system, but that does not seem to have made a difference.  I don't know if a reboot is required, but I have not done that yet.

Since I am not currently building a Java application to control XMetaL Author, please do not spend any more time on this unless others are having the same problem.  If I do need to build a Java application to control XMetaL Author at some point in the future, I will reopen this discussion.

Thanks.

Reply

[Jon Nelson]

Derek,  thanks for the quick reply.

In my case, I have both HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Development Kit and HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Runtime Environment in the registry.  For some reason, there is both a 1.7 and 1.7.0_03 folder under each.  The CurrentVersion was set to 1.7 and looked there for the JavaHome.  The 1.7 folder had an incorrect JavaHome path, so I changed that JavaHome path to point to the 1.7.0_03 installed folder.

Everything now matches the rules you listed.  However, I am still getting the same error.

When you say it checks a value, what exactly does that mean?  Is there a log somewhere that might have more information about why I am still getting that error?

Reply

[Author]

Posts