I have Windows 64 bit. Java is up to date, 64 bit. For every Vassal version after 3.4.3 (I have tried them all), Vassal will not open. It works fine for 3.4.3 and earlier versions. Error logs are empty. What should I do?
Thus spake Monkatronic:
I have Windows 64 bit. Java is up to date, 64 bit. For every Vassal
version after 3.4.3 (I have tried them all), Vassal will not open. It
works fine for 3.4.3 and earlier versions. Error logs are empty. What
should I do?
Check in the directory jre/bin where you have VASSAL installed. Are
java.exe and javaw.exe there?
–
J.
Yes, both. They are there for 3.4.3 (which works), and in the 3.4.11 folder (which does not work).
Thus spake Monkatronic:
Yes, both. They are there for 3.4.3 (which works), and in the 3.4.11
folder (which does not work).
If you try running VASSAL.exe from 3.4.11 from the command line, what
happens? Is there output in the terminal?
–
J.
I’m not quite sure what that means. I opened a command prompt, changed to the Vassal directory, and tried to run vassal.exe from that. No error message, no anything.
In your terminal, cd to the directory where 3.4.11 is installed. Then run:
jre\bin\java.exe -version
Does that give you any output?
Yes:
openjdk version “15” 2020-9-15
openjdk Runtime Environment AdoptOpenJDK (build 15+36)
openjdk 64-bit Server VM AdoptOpenJDK (build 15+36, mixed mode)
Ok. That’s good. It demonstrates that the bundled Java works.
In your terminal, cd to the directory where 3.4.11 is installed. Then run:
jre\bin\java.exe -cp lib\Vengine.jar VASSAL.launch.ModuleManager
Does that give you any output? Does the Module Manager open? Is anything written to the errorLog?
Output is “VASSAL: C:\users\Emper\AppData\Roaming\Vassal”
Nothing opened. I can’t find any error log.
Your errorlog would be located in C:\Users<username>\AppData\Roaming\VASSAL
It would be called errorlog-3.4.11 or something like that.
There is no error log (only error logs from previous installs).
Please try this test build:
vassalengine.org/~uckelman/t … ows-64.exe
Launch it the same way as previously, running
jre\bin\java.exe -cp lib\Vengine.jar VASSAL.launch.ModuleManager
on the command line from the directory where the test build is installed. There should be additional output beyond “VASSAL: C:\users\Emper\AppData\Roaming\Vassal”. Please paste that here.
Output is again “VASSAL: C:\users\Emper\AppData\Roaming\Vassal”. Only that.
Thank you for your help, much appreciated.
Are you certain you were running from the directory where the test build is installed?
I’m using 64bit Windows, and I am also having trouble running 3.4.11. When I try to open my computer thinks for a moment and then nothing happens. However, if I log in to the Administrator profile, it will run just fine. It’s not a permissions setting that I can find. My named profile has full administrative access.
After reading other comments, I do have an errorLog. When I open it, it reads:
2020-12-15 06:26:50,674 [0-main] INFO VASSAL.launch.StartUp - Starting
2020-12-15 06:26:50,680 [0-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2020-12-15 06:26:50,680 [0-main] INFO VASSAL.launch.StartUp - Java version 15
2020-12-15 06:26:50,680 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.4.11
2020-12-15 06:26:50,805 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
Yes, it’s the same directory as the test build.
Ok. In that case I think the Module Manager is exiting through the other path, a bit further on from the one I modified in the test build to dump a stack trace. I’ve created another build which should produce a stack trace for you this time, VASSAL-3.4.12-SNAPSHOT-e592996db, which you can get here:
vassalengine.org/~uckelman/tmp/
Please try running this build as before and post the output.
That build is not available at that link.
Test builds usually get removed after a few weeks.
You can try the same thing you would have had with that test build by running the 3.4.12 release:
github.com/vassalengine/vassal/ … ows-64.exe
If you’re not able to run 3.4.12 normally, please try running it on the command line as noted earlier in this thread. There should be some output in the terminal; please post that here.