Jump to content

Widefs and fs9


 Share

Recommended Posts

Hi,

I have a problem to connect fs9 with the moving map installed on mij laptop, I have a registrated fsuipc and wide fs and I have fs9 and fsx installed on the same drive I installed fsuipc and wide fs according the instructions but the strange thing is that fsx connects to the moving map and works perfect but fs9 will not connect it is still waiting for a connection,please let me now how to solve this problem regards martin.

Link to comment
Share on other sites

I have a problem to connect fs9 with the moving map installed on mij laptop, I have a registrated fsuipc and wide fs and I have fs9 and fsx installed on the same drive I installed fsuipc and wide fs according the instructions but the strange thing is that fsx connects to the moving map and works perfect but fs9 will not connect it is still waiting for a connection,please let me now how to solve this problem regards martin.

More information would help. For instance:

What "moving Map" is that -- is it a WideFS client directly, or does it use GPSout?

What version of FSUIPC and WideFS are you using for the FS9 connection?

What do the logs show (WideServer.LOG in the FS9 Modules folder, WideClient.LOG on the Client PC)?

Have you edited INI files at all, if so show me those.

Pete

Link to comment
Share on other sites

Hi pete,

here some more information,the moving map that I use is from John Hnidec.

For fs9 I used the widefs 6.71 and fsuipc 3.71.

The ini file that I used is the ini file inside wide fs 6.71.

This is the log from the laptop Where moving map is installed.

********* WideClient Log [version 6.71] Class=FS98MAIN *********

Date (dmy): 19/12/06, Time 13:50:53.968: Client name is ACER-8805ECFF1B

2485 Attempting to connect now

3141 Server = MARTIE

3141 Trying TCP/IP host "MARTIE" port 8002 ...

3141Okay, IP Address = 192.168.2.2

19360 ****** End of session performance summary ******

19360 Total time connected = 0 seconds

19360 Reception maximum: 0 frames/sec, 0 bytes/sec

19360 Transmission maximum: 0 frames/sec, 0 bytes/sec

19360 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

19360 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

This is the log from the fs2004 pc.

********* WideServer.DLL Log [version 6.71] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 19/12/06, Time 13:49:30.781: Server name is MARTIE

71234 Initialising TCP/IP server

71234 Initialising IPX/SPX server

71234 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

71234 Failed to start IPX/SPX Server

71234 Initialising UDP/IP server

72531 Broadcasting service every 1000 mSecs

82359 Restarting service due to total lack of use

82375 Failed to start IPX/SPX Server

120437 Closing down now ...

Memory managed: Offset records: 0 alloc, 0 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

********* Log file closed *********

I hope this is the information jou ask for regards martin.

Link to comment
Share on other sites

here some more information,the moving map that I use is from John Hnidec.

For fs9 I used the widefs 6.71 and fsuipc 3.71.

The ini file that I used is the ini file inside wide fs 6.71.

Can I assume that the Wideclient & Moving Map installation and files are identical (i.e. you run the same program from the same shortcut, or whatever) for both FSX and FS9? I hope so -- there is no need for any difference there.

In this log:

This is the log from the laptop Where moving map is installed.

********* WideClient Log [version 6.71] Class=FS98MAIN *********

Date (dmy): 19/12/06, Time 13:50:53.968: Client name is ACER-8805ECFF1B

2485 Attempting to connect now

3141 Server = MARTIE

3141 Trying TCP/IP host "MARTIE" port 8002 ...

3141Okay, IP Address = 192.168.2.2

19360 ****** End of session performance summary ******

19360 Total time connected = 0 seconds

19360 Reception maximum: 0 frames/sec, 0 bytes/sec

19360 Transmission maximum: 0 frames/sec, 0 bytes/sec

19360 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

19360 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

is the gap between the line of time 3141 and the line of 19360 really in the file, or have you added that to show something has been deleted? In other words, are there lines I cannot see because you removed them?

Here you allowed 16 seconds only. The retry period in WideServer is something like 20 seconds, so the logs are missing any information about whether anything was detected and/or retried.

I hope this is the information jou ask for regards martin.

Well, it is if you are using default INI files -- i.e. you have not edited them? If you have edited them I would need to see them of course.

As WideClient can detect the Server, but the Server never sees the Client, it looks exactly like a firewall issue. You would need to allow FS9 and/or WideServer to receive data from your client. I suspect this has already been done for FSX, hence the difference in behaviour.

The actual code driving the Network in WideServer.DLL and in FSUIPC4.DLL is the same, so the differences can only be in configuration (the INI files if you've edited them) or the Server PC's settings, and the Firewall settings are the only ones I can think would create this problem.

Regards

Pete

Link to comment
Share on other sites

Yes I run the same program from the same shortcut for fs9 and fsx

The log is a exact copy so the cap between line 3141 and 19360 is realy there.

I am using the default ini files and I have not edited them.

For your info on the computer where the moving map is installad I am able go into all directories of fs9 of the server pc so I think there is no firewall blocking but the strange thing is it works for almost 2 years in the same conficuration but now togheter whit fsx there is a problem.

Regards martin.

Link to comment
Share on other sites

The log is a exact copy so the cap between line 3141 and 19360 is realy there.

That is still only 16 seconds, not enough time for an auto-reconnection retry.

For your info on the computer where the moving map is installad I am able go into all directories of fs9 of the server pc so I think there is no firewall blocking

What has Explorer access to explicitly shared directories got to do with firewall protection against other programs? I really cannot see any other possibility as the WideServer network code is identical in both FSX and FS9, and you just said that there's no change in the Client end. You tell me what else it could possibly be? Have you even checked yet? :-(

but the strange thing is it works for almost 2 years in the same conficuration but now togheter whit fsx there is a problem.

When you are running FS9, FSX does not come into the picture at all. It is totally irrelevant.

But if in that 2 years you never updated Windows then I don't think FSX would install. One of the updates to Windows automatically enables the WinXP firewall. It might be a good idea to check, don't you think?

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.