Jump to content
The simFlight Network Forums

FS9 + WideFS + FSMap


Recommended Posts

Hello to all,

i would need some help.

I´m suing fs9 and fsmap. now i would like to run the fsmap on my laptop and the simulator on my pc. I have already bought and used the licenses for both the FSUIPC and the WideFS tool. I´ve installed the FSUIPC version 3.9 and the WideFS version 6.78.

I have also copied the WideServer.dll and the wideserver.ini into the FS9 Moduls folder. On the other hand i´ve also copied the Wideclient.exe and WideClient.ini file into a seperate folder called WIDECLIENT on my laptop

However, when i try to connect my laptop via the wideclient.exe file, connecting process doesn´t finish.

The log files of both the wideclient and wideserver look like this:

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

Date (dmy): 12/06/09, Time 13:14:59.921: Client name is PC2

641 Attempting to connect now

1641 Trying to locate server: Need details from Server Broadcast

1641 Failed to connect: waiting to try again

3688 Attempting to connect now

21063 ****** End of session performance summary ******

21063 Total time connected = 0 seconds

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

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

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

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

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 12/06/09, Time 12:41:52.828: Server name is PC1

30574 Initialising TCP/IP server

30574 Initialising IPX/SPX server

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

30574 Failed to start IPX/SPX Server

30574 Initialising UDP/IP server

32116 Broadcasting service every 1000 mSecs

42020 Restarting service due to total lack of use

42020 Failed to start IPX/SPX Server

86814 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 *********

It would be nice if anyone of you could support me in this instance.

Many thanks

sw

Link to comment
Share on other sites

i would need some help.

I just caught this before leaving for my holiday.

The salient entry in the client log is this:

1641 Trying to locate server: Need details from Server Broadcast

In the Server log:

Date (dmy): 12/06/09, Time 12:41:52.828: Server name is PC1

...

32116 Broadcasting service every 1000 mSecs

42020 Restarting service due to total lack of use

So, the Server is broadcasting, but the client cannot see the broadcasts. There are only two possible reasons for this:

1. The Client is running Windows 98 or ME or possibly even NT. Certainly not XP or Vista, or

2. The two computers are not in the same workgroup. Broadcasts don't span workgroups. You can change the workgroup name in the same place as you set your Computer name, in the My computer properties. Note that, if you've not set the workgroup name, Vista and XP default to DIFFERENT names.

An alternative to allowing WideClient to automatically connect when it sees the Server broadcasts is to tell it explicitly what the server is -- as documented in the WideFS documentation. In your case you'd do this by adding

ServerName=PC1

Protocol=TCP

to the first section of the client INI file.

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
×
×
  • 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.