Thus spake kroen1987:
From Vassal:
[1]
Also, what happens if you run:
javaw -client -cp Vengine.jar VASSAL.launch.ModuleManager
from C:\Program Files\VASSAL\lib?
–
J.
Thus spake kroen1987:
From Vassal:
[1]
Also, what happens if you run:
javaw -client -cp Vengine.jar VASSAL.launch.ModuleManager
from C:\Program Files\VASSAL\lib?
–
J.
Thus spake kroen1987:
- The error dialog does not appear in the first one.
- When I run javaw -client -cp Vengine.jar VASSAL.launch.ModuleManager
from lib Vassal opens for a split second and immediately closes.
After doing #2 again, please look for a file called errorLog, which should
exist in the VASSAL directory in your user directory. Post the contents of
that here. It should show us what’s going wrong.
–
J.
09 Mar 2011 17:51:10.841 0 – Starting
09 Mar 2011 17:51:10.843 0 – OS Windows 7
09 Mar 2011 17:51:10.843 0 – Java version 1.6.0_24
09 Mar 2011 17:51:10.843 0 – VASSAL version 3.1.15
09 Mar 2011 17:51:10.902 0 – Manager
09 Mar 2011 17:51:12.350 0 VASSAL: Problem with socket on port 50644
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 java.net.ConnectException: Connection refused: connect
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.PlainSocketImpl.socketConnect(Native Method)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.PlainSocketImpl.doConnect(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.PlainSocketImpl.connect(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.SocksSocketImpl.connect(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.Socket.connect(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.Socket.connect(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.Socket.(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at java.net.Socket.(Unknown Source)
09 Mar 2011 17:51:12.350 0
09 Mar 2011 17:51:12.350 0 at VASSAL.launch.ModuleManager.main(ModuleManager.java:202)
09 Mar 2011 17:51:12.350 0
Thus spake kroen1987:
09 Mar 2011 17:51:10.841 0 – Starting
09 Mar 2011 17:51:10.843 0 – OS Windows 7
09 Mar 2011 17:51:10.843 0 – Java version 1.6.0_24
09 Mar 2011 17:51:10.843 0 – VASSAL version 3.1.15
09 Mar 2011 17:51:10.902 0 – Manager
09 Mar 2011 17:51:12.350 0 VASSAL: Problem with socket on port 50644
09 Mar 2011 17:51:12.350 0
The immediate problem you’re having is that the Module Manager is unable
to connect to the socket it has set up on your computer’s loopback
interface (127.0.0.1).
Do you have some piece of firewall software which is blocking connections
over 127.0.0.1?
–
J.
how do I check for that?
Thus spake kroen1987:
how do I check for that?
Hmm. That’s where my expertise ends. I don’t have a copy of Windows 7
for reference. There’s probably a built-in firewall which is configured
from Control Panel or something like that—at least there was in XP.
Does anyone else know where to find these settings in Windows 7?
Another possibility is that you have some anti-virus software which is
blocking access to this port. You might also look there.
–
J.
From what I’ve googled Windows 7 handles localhost in the DNS itself, which means that if the DNS got misconfigured it could change the localhost record (which should never happen under normal circumstances). Or it’s simply a firewall misbehaving. If it’s a firewall, turn off all network security software on the computer (disconnect from all networks first if you want to be secure), and see if it still does not work. If it still doesn’t, and all firewall/security software is definitely disabled, then it’s going to be difficult to troubleshoot this.
turned the firewall off and all anti-viruses off and it still behaves the same =[
does anyone have windows 7 and it works for him? maybe it’s just not optimized for windows 7?
It works fine on my Windows 7, it is a problem particular to your installation.
I have found an idea that you could try, it wouldn’t fix your computer (which sounds to me like there is something seriously wrong with), but might fix VASSAL opening. At your own risk (you might want to make a restore point/backup):
In start menu search for “notepad”, right-click notepad, open as Administrator. Confirm the choice if dialog pops up.
File > Open. Go to: C:\windows\System32\Drivers\etc
Open file “hosts” (no extension)
The file should look like this:
[code]# Copyright (c) 1993-2009 Microsoft Corp.
The line with “# 127.0.0.1 localhost”, remove the leading "# " part, so it looks like this:
[code]# Copyright (c) 1993-2009 Microsoft Corp.
127.0.0.1 localhost
Restart the computer. If it still starts up, VASSAL might work now.
Did you install Apache by any chance? Or are you running IIS?
It shouldn’t ruin your computer (any more). Some software depends on local loopback functioning correctly. Maybe you do something wrong with my instructions. I just don’t want you to blame me if it does.
and if i do your instruction 100% correctly, is it 100% safe?
Thus spake kroen1987:
and if i do your instruction 100% correctly, is it 100% safe?
The ‘#’ you’re being asked to remove is something you can always
put back if you don’t like the results.
–
J.
I had the exact same problem. I deleted Vassal and reinstalled it. Presto! Works perfectly.
Thus spake Joel Uckelman:
Thus spake kroen1987:
how do I check for that?
Hmm. That’s where my expertise ends. I don’t have a copy of Windows 7
for reference. There’s probably a built-in firewall which is configured
from Control Panel or something like that—at least there was in XP.Does anyone else know where to find these settings in Windows 7?
Another possibility is that you have some anti-virus software which is
blocking access to this port. You might also look there.
I think we’ve found the cause of this problem:
vassalengine.org/tracker/sho … gi?id=3730
It turns out that it’s not a connection problem, but rather that Java
doesn’t correcly pick up the path to the user’s home directory in
Windows 7. There will be a workaround for this in the next release.