Thus spake Justin Morgan:
> There are two java.exe excutables on my machine. Both have the same version.
>
> I tried this variety of paths:
>
> c:\Users\Justin\Desktop\VassalWindows\jre\bin\java.exe -Xms1024M -Xmx1024M -c
> lasspath "C:\Users\Justin\VASSAL\lib\*" VASSAL.launch.Main
> Exception in thread "main" java.lang.NoClassDefFoundError: C:\Users\Justin\VA
> SSAL\lib\cryptix32/jar
>
> c:\Users\Justin\Desktop\VassalWindows\jre\bin\java.exe -Xms1024M -Xmx1024M -c
> lasspath "C:\Users\Justin\VASSAL\lib" VASSAL.launch.Main
> Exception in thread "main" java.lang.NoClassDefFoundError: VASSAL/launch/Main
>
> C:\Users\Justin\VASSAL\jre\bin\java.exe -Xms1024M -Xmx1024M -classpath "C:\Us
> ers\Justin\VASSAL\lib\*" VASSAL.launch.Main
> Exception in thread "main" java.lang.NoClassDefFoundError: C:\Users\Justin\VA
> SSAL\lib\cryptix32/jar
>
> C:\Users\Justin\VASSAL\jre\bin\java.exe -Xms1024M -Xmx1024M -classpath "C:\Us
> ers\Justin\VASSAL\lib" VASSAL.launch.Main
> Exception in thread "main" java.lang.NoClassDefFoundError: VASSAL/launch/Main
>
> java.exe -showversion output:
>
> java version "1.5.0_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
> Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode)
>
> I still cannot launch vassal from the command line. I'm running command as a
> n administrator to bypass UAC problems if they play a part.
>
> Ideas?
Thanks for checking your version of Java. Java 1.6 (a.k.a. Java 6) is the
first version which supports wildcards ('*') in the classpath. Since you're
running 1.5 (Java 5), the VM doesn't know how to interpret
"C:\Users\Justin\VASSAL\lib\*"
when it sees it.
Try this, as one command:
C:\Users\Justin\VASSAL\jre\bin\java.exe -Xms1024M -Xmx1024M -classpath "foo"
VASSAL.launch.Main
but replace "foo" with a ;-separated list of all of the JARs in VASSAL\lib.
For example:
C:\Users\Justin\VASSAL\lib\Vengine.jar;C:\Users\Justin\VASSAL\lib\cryptix32.jar;...
and so on. I realize this will be rather tedious to type out, but I think
this will be sufficient to get you running.
Also: Do you really want to force the VM to allocate 1GB of RAM at start-up?
You must have a *lot* of memory if you want to give VASSAL 1GB regardless of
whether it asks for it. Maybe set -Xms to something smaller? (-Xms sets
memory allocated at start; -Xmx sets maximum memory.)
Let me know whether this works for you.
--
J.
