Ok, I have installed onto Win2K
Seemed to install ok although I noted that the installer didn't ask which
JVM I wanted to use and stuck the comm.jar file into the JVM under
C:\JBuilder4\jvm Maybe there is a way/option to let the user choose which
JVM to put the comm stuff into
I had to modify the DecoderPro Menu Shortcut and specify a value for the
"Start In" directory to:
"C:\Program Files\JMRI"
I also had to modify the DecoderPro.bat file and change the classpath
definition from:
java -Djava.class.path=".;jmri.jar;lib\collections.jar;lib\log4j.jar;lib\jdo
m-jdk11.jar;lib\crimson.jar;lib\comm.jar;$VFS" apps.DecoderPro.DecoderPro
to
javaw -classpath
".;jmri.jar;lib\collections.jar;lib\log4j.jar;lib\jdom-jdk11.jar;lib\crimson
.jar;lib\comm.jar;$VFS" apps.DecoderPro.DecoderPro
as it was complaining about not finding the main class. Must be a MacOS /
Windows thing...
We have just got JBuilder7 at work and it has the ability to build a native
executable wrapper to lauch Java applications and it is supposed to be able
to setup specific classpath and which JVM to use etc - haven't played with
it yet but maybe I should...
Cheers
Alex
