Cannot open Vassal any more ...

Thus spake crozzelle:

The command prompt is C:\Users\cjroz

This time I typed: java -classpath Program
Files/Vassal-3.2.17/lib/Vengine.jar

The response was: Error: Could not find or load main class
Files.Vassal-3.2.17.lib.Vengine.jar

Is Vengine.jar in C:\Users\cjroz\Program Files\Vassal-3.2.17\lib?


J.

Vengine.jar is found in C:\Program Files\Vassal-3.2.17\lib

Do I need to change my command prompt to C:\ before entering the command? If so, how do I do that?

Thus spake crozzelle:

Vengine.jar is found in C:\Program Files\Vassal-3.2.17\lib

This is the path you need for the argument to “-classpath”. The
full command should be:’

java -classpath C:\Program Files\Vassal-3.2.17\lib VASSAL.launch.ModuleManager
You might need double quotes around the path, as it contains spaces.

Do I need to change my command prompt to C:\ before entering the
command? If so, how do I do that?

No, but the way to change directory is with “cd”.


J.

Thanks for your patience with me on this problem. I’ve decided to do a fresh install of Windows 7 to see if that fixes it. If not, I will be back.

Thus spake crozzelle:

Thanks for your patience with me on this problem. I’ve decided to do a
fresh install of Windows 7 to see if that fixes it. If not, I will be
back.

That’s a huge waste of time. If you try what I suggested last, we’ll
see what’s wrong.


J.

IT support was not supportive so my laptop did not get Windows re-installed after all. Below is a screen capture of what you requested…

[attachment=1]JavaError.JPG[/attachment]

Below is the part that wouldn’t fit in the window on my screen.

[attachment=0]JavaError2.JPG[/attachment]

Thus spake crozzelle:

IT support was not supportive so my laptop did not get Windows
re-installed after all. Below is a screen capture of what you
requested…

JavaError.JPG

This didn’t work because the closing quote is in the wrong place. Try
again with this:

java -classpath “C:\Program Files\Vassal-3.2.17\lib” VASSAL.launch.ModuleManager

and post the result.


J.

Here it is …

[attachment=0]JavaError3.JPG[/attachment]

Thus spake crozzelle:

Here it is …

I’m sorry. My fault this time. I left off the name of the JAR file.
What it should be is this:

java -classpath “C:\Program Files\Vassal-3.2.17\lib\Vengine.jar” VASSAL.launch.ModuleManager


J.

And now for something completely different …

[attachment=0]JavaError4.JPG[/attachment]

Thus spake crozzelle:

And now for something completely different …

Right, this is what I was wanting to see from the start. The problem
you’re having is that one of the files VASSAL checks when it opens
has the wrong permissions.

It’s safe to delete C:\Users\cjroz\AppData\Roaming\VASSAL\lock, as
it’s recreated when VASSAL starts. After that, I expect VASSAL to work
for you again.


J.

No such luck. I found the lock file by revealing hidden files in that folder, then I deleted it. Vassal still did not open so I looked in that folder again to find a brand new lock file, created at the date/time I’d just tried to open Vassal. I suppose that the “wrong permissions” haven’t gone away. Also, there is an error log file in there dated from approximately the time this problem arose…

it creates a new lock file every time I delete one then try to open Vassal. Opening the lock file (0KB) with Notepad I find nothing – no characters at all.

Thus spake crozzelle:

it creates a new lock file every time I delete one then try to open
Vassal. Opening the lock file (0KB) with Notepad I find nothing – no
characters at all.

This is all as expected. The lock file is supposed to be created when
you open the Module Manager and should be empty.


J.

Thus spake crozzelle:

No such luck. I found the lock file by revealing hidden files in that
folder, then I deleted it. Vassal still did not open so I looked in
that folder again to find a brand new lock file, created at the
date/time I’d just tried to open Vassal. I suppose that the “wrong
permissions” haven’t gone away. Also, there is an error log file in
there dated from approximately the time this problem arose…

Delete the lock file. Then run VASSAL from the command line and
post the result here and the contents of the errorLog.


J.

I ran it from the Cmd line several times:

[attachment=0]JavaError5.JPG[/attachment]

As you can see, still no response, no error message, … nothing. It created another blank lock file and the error log was not modified. Below is a copy/paste of the last portion of the error log (last modified on 4/23/17).

2017-04-23 09:38:11,167 [3-AWT-EventQueue-0] INFO VASSAL.build.GameModule - Exiting
2017-04-23 09:38:11,587 [0-IPC receiver for 87924608] ERROR VASSAL.tools.ipc.IPCMessageReceiver -
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source) ~[na:1.6.0_45]
at java.net.SocketInputStream.read(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream.readObject0(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream.readObject(Unknown Source) ~[na:1.6.0_45]
at VASSAL.tools.ipc.IPCMessageReceiver.run(IPCMessageReceiver.java:34) ~[Vengine.jar:na]
at java.lang.Thread.run(Unknown Source) [na:1.6.0_45]
2017-04-23 09:40:10,828 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

Thus spake crozzelle:

I ran it from the Cmd line several times:

What I meant for you to do was to run VASSAL via Java manually, as
we had been doing, after deleting the lock file:

java -classpath “C:\Program Files\Vassal-3.2.17\lib\Vengine.jar” VASSAL.launch.ModuleManager

The purpose of this is so we may see what the error message is.

As you can see, still no response, no error message, … nothing. It
created another blank lock file and the error log was not modified.
Below is a copy/paste of the last portion of the error log (last
modified on 4/23/17).

Manually creating a lock file will guarantee that you won’t be able
to start VASSAL. Don’t do that.


J.

Sorry, it should be clear to you by now that I don’t know what I’m doing in the Cmd.exe window. I have not created any lock files manually. A new one appears each time I try to open Vassal.

Anyway, here’s the error message (finally):

[attachment=0]JavaError6.JPG[/attachment]

It created another new lock file, too.

Thus spake crozzelle:

Sorry, it should be clear to you by now that I don’t know what I’m doing
in the Cmd.exe window. I have not created any lock files manually. A
new one appears each time I try to open Vassal.

Anyway, here’s the error message (finally):

Ok. I can see what your problem is now. You have several files in
C:\Users\cjroz\AppData\Roaming\VASSAL which you don’t have permission
to modify with the account you’re using. A likely explanation for this
is that you ran VASSAL with admin privileges at some point, which
could have changed the file permissions.

What you need to do is reset the permissions for that directory and
everything under it so that your normal user account can write to those
files. I’m not a Windows user, so I can’t tell you excactly how to do
that.

This might have something useful in it:

technet.microsoft.com/en-us/lib … 44(v=ws.11.aspx

If you can’t figure it out from that, hopefully someone else here
who uses Windows can suggest how to do it.


J.

Permission granted. Vassal opens again. Thank you … both your assistance and for your patience with me!