Hello again,
Sorry for the bother
To my surprise I found 2 folders for
C:\Programs\Vassal which apparently were created within two days from one to another.
The C:\Programs\Vassal File
has an uninstallation icon next to a Vassal program icon (which does not open when I click on it)
plus a folder named C:\Programs\Vassal2
C:\Programs\Vassal2 has 2 folders, named doc and lib
The folder named doc contains a ReadMe HTML document, 2 tour documents, and a version history document in addition to 3 folders
These 3 folders are the Images folder, the Reference manual folder, and the User guide folder.
The images folder has 6 images : Splash, Take the tour, Step Forward, Console Window, connect and Library Window
The Reference Manual Folder has approximately 100 image in the HTML file format
plus an images folder with a comparable number of images in the Portable Network Graphics Image format.
The User Guide folder contains a Word Doc plus a pdf file
On the other hand the Lib file has a License folder containing 12 different folders, plus approx 20 Executable Jar files.
including the Vengine file which amounts to 3476 Ko
I hope this will help you
Cheers
Thus spake Coryphodon:
Hello again,
Sorry for the bother
To my surprise I found 2 folders for
C:\Programs\Vassal which apparently were created within two days from
one to another.
The C:\Programs\Vassal File
has an uninstallation icon next to a Vassal program icon (which does not
open when I click on it)
plus a folder named C:\Programs\Vassal2
C:\Programs\Vassal2 has 2 folders, named doc and lib
The folder named doc contains a ReadMe HTML document, 2 tour documents,
and a version history document in addition to 3 folders
These 3 folders are the Images folder, the Reference manual folder, and
the User guide folder.
The images folder has 6 images : Splash, Take the tour, Step Forward,
Console Window, connect and Library Window
The Reference Manual Folder has approximately 100 image in the HTML file
format
plus an images folder with a comparable number of images in the Portable
Network Graphics Image format.
The User Guide folder contains a Word Doc plus a pdf file
On the other hand the Lib file has a License folder containing 12
different folders, plus approx 20 Executable Jar files.
including the Vengine file which amounts to 3476 Ko
I hope this will help you
Cheers
The immediate problem is that the shortcut you’re tyring to use
points to C:\Program Files\Vassal\VASSAL.exe, but
C:\Program Files\Vassal doesn’t contain a lib direcory with all of the
libraries VASSAL uses.
I recommend uninstalling whatever versions of VASSAL “Add/Remove
Programs” gives you the option of uninstalling, deleting any such
directories associated with VASSAL which are left C:\Program Files, and
then doing a fresh install.
–
J.
Sorry Uckelman for
bothering again,
After unistalling and deleting all Vassal files on my machine,
I performed several new installations of the application but I keep receiving the same error message:
“The socket over which the Module Manager communicates has had a fault Please restart Vassal”
a more detailed message says :
java.net. Socket. exception: Socket closed
at java.net Plain Socketlmpl.socketAccept (Native Method)
at java.net Plain Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at Vassallaunch Command Server.run (Command ServerJava 62)
atjavalang.Thread run (Unknown Source)"
after which the program fails to launch any downloaded module
Cheers
Thus spake Coryphodon:
Sorry Uckelman for
bothering again,
After unistalling and deleting all Vassal files on my machine,
I performed several new installations of the application but I keep
receiving the same error message:
“The socket over which the Module Manager communicates has had a fault
Please restart Vassal”
a more detailed message says :
java.net. Socket. exception: Socket closed
at java.net Plain Socketlmpl.socketAccept (Native Method)
at java.net Plain Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at Vassallaunch Command Server.run (Command ServerJava 62)
atjavalang.Thread run (Unknown Source)"
after which the program fails to launch any downloaded module
What files are in %APPDATA%\VASSAL now?
–
J.
Hello Uckelman
I found in the Application Data Folder a Vassal folder which
contains 4 files:
error lock (1 ko)
key (1 ko)
lock (empty as before)
Preferences (1 ko)
Cheers
Thus spake Coryphodon:
Hello Uckelman
I found in the Application Data Folder a Vassal folder which
contains 4 files:
error lock (1 ko)
key (1 ko)
lock (empty as before)
Preferences (1 ko)
With VASSAL not running, delete key and lock.
–
J.
Hello again,
I deleted those files but I encounter the same problem whenever I try to open a module
Thus spake Coryphodon:
Hello again,
I deleted those files but I encounter the same problem whenever I try to
open a module
Post the complete contents of the errorLog.
–
J.
Hello Uckelman
Sorry,
I keep receiving the original error message when
I try to open a module
As posted previously, the message is the following:
“The socket over which the Module Manager communicates has had a fault Please restart Vassal”
Details :
java.net. Socket. exception: Socket closed
at java.net Plain Socketlmpl.socketAccept (Native Method)
at java.net Plain Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at Vassallaunch Command Server.run (Command ServerJava 62)
atjavalang.Thread run (Unknown Source) "
All the best
Thus spake Coryphodon:
Hello Uckelman
Sorry,
I keep receiving the original error message when
I try to open a module
As posted previously, the message is the following:
“The socket over which the Module Manager communicates has had a fault
Please restart Vassal”
Details :
java.net. Socket. exception: Socket closed
at java.net Plain Socketlmpl.socketAccept (Native Method)
at java.net Plain Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at Vassallaunch Command Server.run (Command ServerJava 62)
atjavalang.Thread run (Unknown Source) "
Please post the entire contents of the errorLog file, not just the
stack trace. We need to see all of it.
–
J.
Sorry Uckelman, but
where should I look for the error Log file?
All the best
Thus spake Coryphodon:
Sorry Uckelman, but
where should I look for the error Log file?
It’s in %APPDATA%\VASSAL, the same place as the lock file.
–
J.
Hello Uckelman
I just got back from vacations,
OK, I looked at the App Data Folder and to my suprise the key and the lock files have reappeared despite the fact that I remember having suppressed them.
I examined the error Log file and it presently has 266 octets and was created on Saturday the 16th and
for some reason unknown to me it was modified a minute ago (I believe when I checked its properties).
The attributes of the error Log File are marked AN
All the best
Thus spake Coryphodon:
Hello Uckelman
I just got back from vacations,
OK, I looked at the App Data Folder and to my suprise the key and the
lock files have reappeared despite the fact that I remember having
suppressed them.
This is normal. The key and lock files will be recreated each time you
start VASSAL.
I examined the error Log file and it presently has 266 octets and was
created on Saturday the 16th and
for some reason unknown to me it was modified a minute ago (I believe
when I checked its properties).
The attributes of the error Log File are marked AN
Sorry, maybe I wasn’t clear: We need to see the contents of the
errorLog, not the file properties. Attach the errorLog to a post here.
–
J.