Preliminary information:
System information
Model: TOSHIBA Satellite A305-S6905
OS: Windows Vista Premium 32bit (Service Pack 2)
CPU: Intel Core 2 Duo T6400
Memory: 3GB
Video Card: Mobile Intel 4 Series Express Chipset Family
VASSAL: 3.1.15
Java: Version 6 Update 26
Module: N/A
errorLog
28 Jun 2011 01:03:21.493 0 – Starting
28 Jun 2011 01:03:21.495 0 – OS Windows Vista
28 Jun 2011 01:03:21.495 0 – Java version 1.6.0_26
28 Jun 2011 01:03:21.495 0 – VASSAL version 3.1.15
28 Jun 2011 01:03:21.532 0 – Manager
28 Jun 2011 01:03:43.002 0 VASSAL: Problem with socket on port 58827
28 Jun 2011 01:03:43.002 0
28 Jun 2011 01:03:43.002 0 java.net.ConnectException: Connection timed out: connect
28 Jun 2011 01:03:43.002 0
(This is only the first 10 lines: the entire log will be posted upon request)
When I start up VASSAL, it opens in a window and everything is fine. I can open a module, in this case Summoner_Wars_(1-2), and see the hourglass on my cursor notifying me that it’s loading. However, after 20 seconds (and it is always 20 seconds) of VASSAL being opened, the program window disappears. On Task Manager, the program just disappears, telling me that VASSAL just, for lack of a better term, “kills itself.”
Things I have already tried:
Uninstalling and reinstalling VASSAL (nothing changed from above)
Uninstalling and reinstalling Java (nothing changed from above)
Restarting my computer (nothing changed from above)
The sixth line of the errorLog made me think it was a port problem, so I opened the port it was having trouble with. All this changed was that in the errorLog it found a new port to have a problem with, so after opening that one it found another one to have a problem with, leading me to believe that this is not a port problem.
What I have concluded with my limited knowledge of programming and one techie friend helping me pinpoint the above problems: this is a java problem.
If this is not a java problem, and can be solved with the use of the cmd and some special commands, then I would like if those could be made aware to me so I can use VASSAL.
If this is a java problem, I would ask those relevant to ask that this be looked into, possibly for a future patch.