Vassal-3.2.10 wont start

Just spotted this, and tried 3.2.11 on my Surface Pro 2 (which of course, comes with Win 8.1). Vassal does not start. No errors, nothing.

Thus spake Rindis:

Just spotted this, and tried 3.2.11 on my Surface Pro 2 (which of
course, comes with Win 8.1). Vassal does not start. No errors, nothing.

We need more details. Post the errorLog first.


J.

The rest of the Command line will tell us what is remaining open. Once I know that, I can make you a diagnostic build that will tell us what the process is doing. Awaiting your reply.

Took a bit to figure out where it was hiding:

2014-02-19 19:32:50,780 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - OS Windows 8 6.2
2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_45
2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.8
2014-02-19 19:32:50,960 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-02-19 19:34:45,389 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

That’s it.

Thus spake Rindis:

“uckelman” wrote:

Thus spake Rindis:

Just spotted this, and tried 3.2.11 on my Surface Pro 2 (which of
course, comes with Win 8.1). Vassal does not start. No errors,
nothing.

We need more details. Post the errorLog first.


J.

Took a bit to figure out where it was hiding:

2014-02-19 19:32:50,780 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - OS
Windows 8 6.2
2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - Java
version 1.6.0_45
2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - VASSAL
version 3.2.8
2014-02-19 19:32:50,960 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManager - Manager
2014-02-19 19:34:45,389 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManagerWindow - Exiting

That’s it.

Will any earlier version start?


J.

“2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.8”

Why would the error log of Vassal 3.2.11 show a line where the version is 3.2.8?

Your’re stretching the computer knowledge of a mere Classicist past its limits, but here is what you want I think:

“Command line:C:\Program Files \java\jre6\bin\javaw.exe” -classpath “lib\Vengine.jar” VASSAL.launch.ModuleManager

James, you might be running into the same thing another user hit just recently. Check the properties of the shortcut you’re using to launch VASSAL and find its target–it seems to be pointing to an older version you still have (partially?) installed. VASSAL 3.2.8 and earlier all installed by default to C:\Program Files (x86) (i.e., where 32 bit programs go).

For VASSAL 3.2.9 and newer, the install location became C:\Program Files (i.e., where 64 bit programs go). Try finding the VASSAL folder in there and running the executable, and/or update your existing shortcut to point to this one, which should be 3.2.11 like you expect.

Thus spake Hamster:

“2014-02-19 19:32:50,799 [0-main] INFO VASSAL.launch.StartUp - VASSAL
version 3.2.8”

Why would the error log of Vassal 3.2.11 show a line where the version
is 3.2.8?

It would not. That’s an errroLog from 3.2.8, not 3.2.11.


J.

Thus spake BSkene:

Your’re stretching the computer knowledge of a mere Classicist past its
limits, but here is what you want I think:

“Command line:C:\Program Files \java\jre6\bin\javaw.exe” -classpath
“lib\Vengine.jar” VASSAL.launch.ModuleManager

Thanks. This demonstrates that the problem you’re having is that the
Module Manager from your first run is not exiting completely.

I’ll produce a diagnostic build for you to try sometime in the next few
days which will give us some idea of why this happens.


J.

Ah, ha. Yep, that was the problem. I’ll note that the entry in the App menu (which is the Win 8 Start Menu with a different layout) has the problem.

I’ll also note that my main desktop machine (Win 7) has not had this problem, but all the file extension associations went away when I upgraded to 3.2.11 (was fine with 3.2.10).

Thus spake Rindis:

Ah, ha. Yep, that was the problem. I’ll note that the entry in the App
menu (which is the Win 8 Start Menu with a different layout) has the
problem.

I don’t follow—has what problem? Are you saying that the entry in
the App menu has a bad path? If so, what is the bad path?

I’ll also note that my main desktop machine (Win 7) has not had this
problem, but all the file extension associations went away when I
upgraded to 3.2.11 (was fine with 3.2.10).

Can you be more specific about this? Did this happen with a custom
install? With a regular install?


J.

The install of 3.2.11 left the shortcut for Vassal pointed at the old (Progam Files (x86)) path instead of updating to the 64-bit Program Files path.

Uninstalling and reinstalling generated a correct shortcut.

Custom install. I still have 3.1.20 installed as well as the latest 3.2.x (and of course, I occasionally have testing versions installed), so I always go custom to manage which versions are on the machine. This has never had a problem (or at least, not this problem), but this last time, the extension associations went away.

Here is the situation: Vassal 3.2.11 will start the first time. Then, it will not start again. However, if I go into Task Manager and close the “Java ™ Platform SE Binary” under the “Processes” tab, it starts again fine without the need to restart the PC. I hope that provides information that will help to update the Vassal file so that this extra step isn’t necessary…thanks for your help!

Thus spake sithstalker:

Here is the situation: Vassal 3.2.11 will start the first time. Then, it
will not start again. However, if I go into Task Manager and close the
“Java ™ Platform SE Binary” under the “Processes” tab, it starts
again fine without the need to restart the PC. I hope that provides
information that will help to update the Vassal file so that this extra
step isn’t necessary…thanks for your help!

I will create a diagnostic build for you and BSkene later today so we
can see why the Module Manager does not exit.


J.

BSkene, sithstalker: After you’ve run of the Module Manager successfully and closed it, do you have a line like this at the end of your errorLog? (From “INFO” onward, it should match exactly.)

2014-02-13 11:35:00,565 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

BSkene, sithstalker: I believe the temp file cleanup which happens when the Module Manager is closed was getting stuck for you in 3.2.11. Please try 3.2.12-svn9018.

It never rains but it pours.

I figures I should uninstall 3.2.11 before running the new exe. But that generated an error (I was able to uninstall a different program I wanted to get rid of anyway). So I went ahead and ran the exe. There was no difference. 1 start up, then nothing on the 2nd attempt.

Thanks for all the work you’re doing on this by the way.

Thus spake BSkene:

“uckelman” wrote:

BSkene, sithstalker: I believe the temp file cleanup which happens
when the Module Manager is closed was getting stuck for you in 3.2.11.
Please try 3.2.12-svn9018[1].

It never rains but it pours.

I figures I should uninstall 3.2.11 before running the new exe. But that
generated an error (I was able to uninstall a different program I wanted
to get rid of anyway).

What error? We can’t troubleshoot problems for which we don’t have any
details.

So I went ahead and ran the exe. There was no
difference. 1 start up, then nothing on the 2nd attempt.

Would you answer my question about the errorLog, please?


J.

Thus spake Rindis:

“uckelman” wrote:

Thus spake Rindis:

Ah, ha. Yep, that was the problem. I’ll note that the entry in the
App
menu (which is the Win 8 Start Menu with a different layout) has the
problem.

I don’t follow—has what problem? Are you saying that the entry in
the App menu has a bad path? If so, what is the bad path?

The install of 3.2.11 left the shortcut for Vassal pointed at the old
(Progam Files (x86)) path instead of updating to the 64-bit Program
Files path.

Did you check the box telling the installer to create a desktop shortcut
for this install?

I’ll also note that my main desktop machine (Win 7) has not had this
problem, but all the file extension associations went away when I
upgraded to 3.2.11 (was fine with 3.2.10).

Can you be more specific about this? Did this happen with a custom
install? With a regular install?


J.

Custom install. I still have 3.1.20 installed as well as the latest
3.2.x (and of course, I occasionally have testing versions installed),
so I always go custom to manage which versions are on the machine. This
has never had a problem (or at least, not this problem), but this last
time, the extension associations went away.

We’ve never had file associations for module extensions (.vext). Or is
this not what you’re saying?


J.