Standard install goes fine, and the menu shortcut now points at the
standard (64-bit) directory, and will launch Vassal fine. However, the
Java problem causing it to not be able to launch twice in a row (as
above) persists.
Now it looks like you’re having the same problem as BsKene and
sithstalker.
I tend to suspect that something odd (and likely inexplicable) just
happened when I installed 3.2.11 on my main machine. But the fact that
the installer can’t see the previous version is interesting.
Check in the registry under HKLM\Software\vassalengine.org\VASSAL.
What do you see there?
Okay, error log after first (successful) launch on Win 8:
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - OS Windows 8 6.2
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_45
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.12-svn9019
2014-02-24 08:41:30,994 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-02-24 08:41:46,813 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting
And it doesn’t start on the second go, and the Error Log is not updated.
I’ll try to remember to test svn9016 on my Win7 desktop tonight.
Rindis, if VASSAL now won’t start for you on subsequent attempts,
please post the errorLog you’re getting from the first attempt.
Okay, error log after first (successful) launch on Win 8:
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - OS
Windows 8 6.2
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - Java
version 1.6.0_45
2014-02-24 08:41:30,807 [0-main] INFO VASSAL.launch.StartUp - VASSAL
version 3.2.12-svn9019
2014-02-24 08:41:30,994 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManager - Manager
2014-02-24 08:41:46,813 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManagerWindow - Exiting
And it doesn’t start on the second go, and the Error Log is not updated.
I’ll try to remember to test svn9016 on my Win7 desktop tonight.
Please also try to determine the latest version which does not have
the startup problem for you.
I… can’t seem to find one that doesn’t have the problem. I’ve gone all the way back to 3.1.17 (earliest version I had to hand), and they all showed the same behavior on my Win 8 machine.
If there’s any particular version you want me to try, just tell me.
I… can’t seem to find one that doesn’t have the problem. I’ve gone
all the way back to 3.1.17 (earliest version I had to hand), and they
all showed the same behavior on my Win 8 machine.
This is exactly what I expected would happen. I think the problem
is with your install of Java, not with VASSAL. Try uninstalling and
reinstalling Java.
Hmm… two versions of Java present: 6 Update 27 and 6 Update 45 (64-bit)…
Uninstalled both, went to java.com, and it installed 6 Update 51. Reinstalled Vassal 3.2.11, and it seems to work now.
Now, I hadn’t fiddled with Java on my machine. (I think the second copy is from Vassal 3.1.20 installing.) So, I would think that it was still the original configuration from Microsoft when they put together the Surface Pro 2…
I… can’t seem to find one that doesn’t have the problem. I’ve
gone
all the way back to 3.1.17 (earliest version I had to hand), and
they
all showed the same behavior on my Win 8 machine.
This is exactly what I expected would happen. I think the problem
is with your install of Java, not with VASSAL. Try uninstalling and
reinstalling Java.
–
J.
Hmm… two versions of Java present: 6 Update 27 and 6 Update 45
(64-bit)…
Oh, yes. Having more than one version of Java installed tends to
cause neither to work properly, in my experience. I should have asked
about that.
Rindis, I believe I know why your file associations disappeared: The uninstaller was unconditionally removing VASSAL file associations if they existed—which is incorrect if those file associations were put there by a different version of VASSAL. This causes a problem only when you run the uninstaller manually. When the uninstaller is launched from a later version of the installer, new file associations are established by the (new) installer after the (old) uninstaller removes them, which is why most people would never see the problem.
Sorry I didn’t respond for so long after you’ve been so helpful. but I was distracted by work and other issues. I uninstalled and reisntalled java (there were two versions), then installed the new Vassal version posted just above (3.2.12-svn9021) and was just now able to repeatedly open and close vassal, so it seems as if you’ve solved it, thanks.
Sorry I didn’t respond for so long after you’ve been so helpful. but I
was distracted by work and other issues. I uninstalled and reisntalled
java (there were two versions), then installed the new Vassal version
posted just above (3.2.12-svn9021) and was just now able to repeatedly
open and close vassal, so it seems as if you’ve solved it, thanks.
I’m glad it workd for you now.
Incidentally, what game does your icon come from?
That icon is from the Cyberboard gamebox for AH’s The Longest Day.
The 3.2.12-svn9021 version didn’t solve this for me, so I just stayed with 3.2.11; however, I need to use Task Manager to end task on Java, and then can restart Vassal, and it works fine after the restart. Thanks for your effort!
The 3.2.12-svn9021 version didn’t solve this for me, so I just stayed
with 3.2.11; however, I need to use Task Manager to end task on Java,
and then can restart Vassal, and it works fine after the restart. Thanks
for your effort!
Did you check whether you have more than one version of Java installed?