Thus spake kroen1987:
latest
Please give the version number. I don’t know what version you think the
latest version is.
–
J.
I thought the problem was java myself before posting this thread so I went to their site to check my java. it is the latest. fact, not what I think.
Thus spake kroen1987:
I thought the problem was java myself before posting this thread so I
went to their site to check my java. it is the latest. fact, not what I
think.
Is there a reason why you can’t tell me the actual version number of
what you have installed?
–
J.
sigh… version 6 update 24
Thus spake kroen1987:
sigh… version 6 update 24
Thank you. I’ve had people tell me before that they’re running the “latest”
version when they’re not; I’ve also had it happen that a new update has been
released since the last time I checked myself. Having a version number
ensures that we’re talking about the same version.
To troubleshoot this, we need to determine a few things:
Can you run Java from a terminal? Bring up a terminal window (one way is
to go to Run and type ‘cmd’). Type ‘java -version’ at the prompt and hit
enter. What you you get as output?
–
J.
java version “1.6.0_24”
Java™ SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot™ Client VM (build 19.1-b02, mixed mode, sharing)
Thus spake kroen1987:
java version “1.6.0_24”
Java™ SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot™ Client VM (build 19.1-b02, mixed mode, sharing)
This means your JVM appears to be working. That’s good.
From within the terminal, change directories to where you installed
VASSAL. The default install location is C:\Program Files\VASSAL. If
you didn’t change the install location, that’s where it will be.
So, in the terminal:
cd C:\Program Files\VASSAL
If you type ‘dir’, you should see VASSAL.exe and a directory called ‘lib’.
Now, we’re going to try running VASSAL manaully, without it’s launcher.
Type this at the prompt:
javaw -client -cp lib/Vengine.jar VASSAL.launch.ModuleManager
What happens when you do that?
–
J.
you mean type it after i’m in vassal in the terminal? if so, nothing happens.
if you meant typing it from scratch, then a java virtual machine window pops up saying “Could not find the main class: VASSAL.launch.ModuleManager. Program will exit.”
Thus spake kroen1987:
you mean type it after i’m in java in the terminal? if so, nothing
happens.
if you meant typing it from scratch, then a java virtual machine window
pops up saying “Could not find the main class:
VASSAL.launch.ModuleManager. Program will exit.”
I meant the latter.
Ok. What do you see in C:\Program Files\VASSAL? Is there a directory
called lib? Does lib contain a file called Vengine.jar?
–
J.
Yes and yes.
Thus spake kroen1987:
Yes and yes.
Just to be sure, try this from the VASSAL install directory:
javaw -client -cp lib\Vengine.jar VASSAL.launch.ModuleManager
(The difference is the backslash instead of the slash. It’s not
supposed to matter in the classpath argument…)
–
J.
same result
Thus spake kroen1987:
same result
What directory are you doing that from in the terminal? Can you post
me a screenshot of the state of the terminal after running the command?
–
J.
tried both from the vassal directory and from stratch and the results (which I already copied&pasted here) were exactly the same…
Thus spake kroen1987:
tried both from the vassal directory and from stratch and the results
(which I already copied&pasted here) were exactly the same…
Yes, I understand. I’d like to see a screenshot just to verify that
things are in the state I believe them to be; there may be something
important that I see this way which isn’t obvious now.
–
J.
From Vassal:
Thus spake kroen1987:
From Vassal:
Yes, I wouldn’t expect the latter one to work—in that case, the JAR
file containing all of VASSAL’s classes isn’t in the classpath, so it
can’t be located.
The former case is the interesting one. Am I to understand that you’re
not getting the error dialog in the first one that you have in the
second?
–
J.
Thus spake kroen1987:
From Vassal:
[1]
Also, what happens if you run:
javaw -client -cp Vengine.jar VASSAL.launch.ModuleManager
from C:\Program Files\VASSAL\lib?
–
J.
- The error dialog does not appear in the first one.
- When I run javaw -client -cp Vengine.jar VASSAL.launch.ModuleManager from lib Vassal opens for a split second and immediately closes.
Thus spake kroen1987:
- The error dialog does not appear in the first one.
- When I run javaw -client -cp Vengine.jar VASSAL.launch.ModuleManager
from lib Vassal opens for a split second and immediately closes.
After doing #2 again, please look for a file called errorLog, which should
exist in the VASSAL directory in your user directory. Post the contents of
that here. It should show us what’s going wrong.
–
J.