TCP server always inactive

[GoogleCodeExporter]

Must fix this, something happened in revision 1.5.2 that caused this to occur.  
luckily it is only a text fault and not anything else.

I will look into it:

[ code ]

*************************
*Module version Beta 1.5*
*Standby for imports....*
*************************

Welcome back Commander Byrne
You are running on Windows 7 with kernel version 6.1

The current time is 11:59:22

Would you like to start both the TCP client and Joystick? (y/n): n
Would you like to enable TCP client for this sesson? (y/n): y
Would you like to enable the Joystick Controller? (y/n): n
Manual input method will now be activated!

******************************************************************
*[ALERT]Stand by for TCP connection on 192.168.12.40:9999 [ALERT]*
******************************************************************
Unable to connect to 192.168.12.40, please check your connection!
Connected to  192.168.12.40 9999
Do you want to enter debug mode? (y/n): 

[ /code ]

See the line: 
" Unable to connect to 192.168.12.40, please check your connection! "

This should not occur if it is then successful.

Maybe I might add a wait command before it prints such.

@wallarug

Original issue reported on code.google.com by cian.by...@sydstu.catholic.edu.au on 11 Nov 2012 at 1:01

[GoogleCodeExporter]

It seems the "finally: " command is not in its right place there...

any suggestions?

Original comment by cian.by...@sydstu.catholic.edu.au on 11 Nov 2012 at 1:06

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Problem seems to be fixed with the "except:" function instead of the "finally:" 
function.

Will report back here if problem re-appears.

Original comment by cian.by...@sydstu.catholic.edu.au on 11 Nov 2012 at 1:08

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Fixed! :D

Original comment by cian.by...@sydstu.catholic.edu.au on 11 Nov 2012 at 1:54

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****