Vassal-3.2.10 wont start

BSkene · February 19, 2014, 2:34pm

uckelman:

Thus spake BSkene:

Ok, I usually start it from the desktop icon–IIRC whenever I tried to
start it form the apps page (or whatever microsoft calls it) it wouldn’t
start at all.

Hold on to that second problem. I’d like to investigate that once we
solve the present one.

Here is a screenshot of the processes tab relevant to Java (the whole
thing is much larger than a single screen I looked over the whole list
and I did did not see a line for java.exe):

There appears to be a context menu available from the column headers in
the Processes tab which lets you determine which columns are displayed.
Please turn on “PID”, “Command line”, and “Process name” and tell me what
those columns say for the “Java™ Platform SE binary” entry between
a successful and a failed run of VASSAL.

–
J.

Ok. but I was only to figure out what you meant by “context menu” through blind luck.
PID: 1480
Process name" javaw.exe
“Command line:C:\Program Files \java\jre6\bin\javaw.exe”-…

I bet what you want to know is hidden by that ellipsis but I could not figure out how to expand it But I did manage to go to the details tab which confirms that java.exe is running

uckelman · February 19, 2014, 2:44pm

Thus spake BSkene:

Ok. but I was only to figure out what you meant by “context menu”
through blind luck.

“Context menu” is the standard name for menus you can bring up by
right-clicking on GUI elements.

PID: 1480
Process name" javaw.exe
“Command line:C:\Program Files \java\jre6\bin\javaw.exe”-…

I bet what you want to know is hidden by that ellipsis but I could not
figure out how to expand it

In fact, that’s precisely the thing I need. If this table is like others
typically found in Windows, then you can widen the Command line column by
dragging the boundaries between the column names. You might need to get
more space in the table by making the task manager dialog larger. It’s
also possible that you can see the complete value of that cell in a
tooltip if you hover over it.

–
J.

Rindis · February 20, 2014, 3:37am

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.

uckelman · February 20, 2014, 8:34am

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.

uckelman · February 20, 2014, 8:49am

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.

Rindis · February 21, 2014, 4:23am

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.

uckelman · February 21, 2014, 8:48am

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.

Hamster · February 21, 2014, 1:52pm

“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?

BSkene · February 21, 2014, 2:03pm

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

JoelCFC25 · February 21, 2014, 3:09pm

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.

uckelman · February 21, 2014, 3:22pm

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.

uckelman · February 21, 2014, 3:25pm

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.

Rindis · February 21, 2014, 4:16pm

JoelCFC25:

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?

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.

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).

uckelman · February 21, 2014, 5:50pm

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.

Rindis · February 21, 2014, 7:07pm

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.

sithstalker · February 22, 2014, 6:15am

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!

uckelman · February 22, 2014, 9:06am

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.

uckelman · February 22, 2014, 1:39pm

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

uckelman · February 22, 2014, 11:04pm

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.

BSkene · February 23, 2014, 12:35am

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.