Jump to content
The simFlight Network Forums

Connection Probs with WideFS and SB3


Recommended Posts

Hello everyone :)

I have following probs:

I´m running FS2004 on one PC, SB3 on another PC.

SB3 has been setup with the client and server option.

Wide FS is also correctly installed.

FSUIPC and WideFS are the latest versions an registred.

When I start my FS and the WideClient, WideServer and WideClient are obvisualy connected, because in the FS frame it says: "[...] with WideServer: 1 connected". And so it says in the WideClient frame.

When sarting SB 3 (it is started by wideClient) it says:

wide1.jpg

I click on "Start anyway, for FS 2004" and the Multiplayer session is hosted on the client PC. Once hosted, i can even join it on my FS2004 server PC.

Now I create my FP in order to connect to VATSIM server.

When I click on the SB3 "connect-button" this message pops up:

wide2.jpg

Well, nothing I do seems to be the sollution :(

See attached the client log:

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

Date (dmy): 15/09/05, Time 03:32:04.250: Client name is LAPTOP

375 C:\Programme\SquawkBox3\squawkbox.exe

391 Attempting to connect now

1219 Server = HEIMPC

1219 Trying TCP/IP host "HEIMPC" port 8002 ...

1219Okay, IP Address = ***.***.***.*** (intentionaly left blank :wink: )

1219 Connection made okay!

1219 New Client Application: "squawkbox" (Id=4076)

And here the server log:

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 15/09/05, Time 03:31:13.531: Server name is HEIMPC

64719 Initialising TCP/IP server

65797 Initialising IPX/SPX server

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

65813 Failed to start IPX/SPX Server

65938 Broadcasting service every 1 mSecs

76406 Restarting service due to total lack of use

76406 Failed to start IPX/SPX Server

83547 Incoming connection Accepted ok (skt=344)

83641 Connected to computer "LAPTOP" running WideClient version 6.500 (skt=344)

And to make it complete, here the Client.ini:

PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=43,44,886,589

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

PollInterval=2000

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

UseTCPIP=Yes

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

; -----------------------------------------------

[user]

Log=Errors+

Run1=C:\Programme\SquawkBox3\squawkbox.exe

; ===============================================

And here the Server.ini:
PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

AdvertiseService=Yes

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

RestartTime=10

SendTimeout=15

TCPcoalesce=No

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[ClientNames]

1=LAPTOP

Perhaps someone can help me?

Thanks in advance,

Link to comment
Share on other sites

And to make it complete, here the Client.ini:

Actually, for completeness, it is the FSUIPC Log which is needed. Start everything up, get the problem, close FS down, then let me see the FSUIPC Log file.

Also the WideClient and WideServer log files are much more useful after FS and WideClient has been closed, as they both place performance summaries at the end of the Logs showing how many blocks have been exchanged and how much data.

This looks more like some sort of data dependency in SB3 -- it isn't seing something it wants to see. The connection looks fine.

Regards,

Pete

Link to comment
Share on other sites

Hi Pete :D

for completeness
That was the word i was looking for yesterday night :wink: , thanks *lol*

Back to the Problem:

Did it like You said.

Here the FSUIPC.log:

********* FSUIPC, Version 3.50 by Pete Dowson *********

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Ingmar Bail"

User Addr="*********" (intentionally left blank :wink: )

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

16062 System time = 16:21:36

16078 \\HEIMPC\FS 2004\

16078 System time = 16:21:36, FS2004 time = 12:00:00 (00:00Z)

35859 FLIGHTS\OTHER\FLTSIM.flt

36000 AIRCRAFT\c172\Cessna172SP.air

36281 Aircraft="Cessna Skyhawk 172SP"

42844 Module [M1] identified = "sbmpjoin9.dll"

42859 Module [M2] identified = "sbtrans9.dll"

47828 C:\Dokumente und Einstellungen\Ingmar\Eigene Dateien\Flight Simulator-Dateien\Von der Benutzeroberfläche erzeugter Flug.flt

48172 Clear All Weather requested: external weather discarded

56219 Advanced Weather Interface Enabled

347015 System time = 16:27:07, FS2004 time = 16:25:58 (23:25Z)

347015 *** FSUIPC log file being closed

Memory managed: 2 Allocs, 3040 Freed

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

The Server log:

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 15/09/05, Time 16:21:40.609: Server name is HEIMPC

65375 Initialising TCP/IP server

69000 Initialising IPX/SPX server

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

69015 Failed to start IPX/SPX Server

69015 Broadcasting service every 1 mSecs

70390 Incoming connection Accepted ok (skt=2800)

70453 Connected to computer "LAPTOP" running WideClient version 6.500 (skt=2800)

330203 Closing down now ...

Memory managed: Offset records: 237 alloc, 237 free

Throughput maximum achieved: 18 frames/sec, 8779 bytes/sec

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

Average receive rate from "LAPTOP": 0 frames/sec, 32 bytes/sec

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

And the Client.log:

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

Date (dmy): 15/09/05, Time 16:22:16.890: Client name is LAPTOP

375 C:\Programme\SquawkBox3\squawkbox.exe

391 Attempting to connect now

391 Connection made okay!

1094 New Client Application: "squawkbox" (Id=2444)

260250 Connection closed by server!

260250 Ready to try connection again

260297 Attempting to connect now

261344 Error on client pre-Connection Select() [Error=10061] Connection refused

261344 Ready to try connection again

261360 Attempting to connect now

524063 ****** End of session performance summary ******

524063 Total time connected = 260 seconds

524063 Reception maximum: 18 frames/sec, 8409 bytes/sec

524063 Reception average whilst connected: 8 frames/sec, 3247 bytes/sec

524063 Transmission maximum: 6 frames/sec, 273 bytes/sec

524063 Transmission average whilst connected: 0 frames/sec, 33 bytes/sec

524063 Max receive buffer = 941, Max send depth = 13, Send frames lost = 0

524063 **************** Individual client application activity ****************

524063 Client 2444 requests: 505 (Ave 1/sec), Data: 21614 bytes (83/sec), Average 42 bytes/Process

524063 ********* Log file closed (Buffers: MaxUsed 13, Alloc 2901 Freed 2901 Refused 0) *********

I hope this is enough information, or do You need more info?

Thanks for Your help! :D

Best regards,

Link to comment
Share on other sites

I hope this is enough information, or do You need more info?

It is enough to indicate that there is something wrong with your Keys, either the FSUIPC one or the WideFS one, or both. Can you tell me where you purchased them, please? There are some illegal key generators around and they can produce exactly the results you are getting.

I can see an Ingmar Bail listed as purchasing an FSUIPC key back in April 2004, but I have no record of any WideFS purchase at all. However, my records aren't complete and are only from one reseller.

Please ZIP up your FSUIPC.KEY file from the FS Modules folder (do not send it without Zipping please) and send it to me at petedowson@btconnect.com, and I will confirm this or otherwise investigate the problem.

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.