Jump to content

Wide Client


Recommended Posts

Using four computers for FS2002 and Project Magenta.

The server is programmed for Fs2002 and the client computers - 1 has PFD\MCP\CDU for Boeing B744 and the other two have PFD, one being used for EICAS and the other for First Officer. Using WideFS5.50 and FSUIPC2.975. Everything works well except for the First Officers computer which comes up with the message "Wide Client failed to start. " We have checked that the EICAS and First Officers .INI files are exactly the same. The following is the Wide Client.Dll log for the errant computer.

********* WideClient.DLL Log [version 5.41] *********

Date (dmy): 28/05/03, Time 11:31:30.380: Client name is PC2

239 Attempting to connect now

359 Client socket() failed [Error=10047] Address family not supported by protocol family

11023 WRITESTATEDATA received with bad data size!

11023 0 ReadLocal: Offset=10000, Size=0000

17942 Failed to start Client!

23122 Reception maximum achieved: 0 frames/sec, 0 bytes/sec

23122 Max receive buffer = 0, Max send depth = 0

23122 ********* Log file closed (Buffers: MaxUsed 1, Alloc 15 Freed 15 Refused 0) *********

Anyone have any suggestions?

Barry :

Link to comment
Share on other sites

Using WideFS5.50 and FSUIPC2.975. Everything works well except for the First Officers computer which comes up with the message "Wide Client failed to start. " ...

You say you are using WideFS 5.50, but the WideClient LOG shows otherwise:

********* WideClient.DLL Log [version 5.41] *********

359 Client socket() failed [Error=10047] Address family not supported by protocol family

You should use the matching WideClient which was inlcuded in the WideFS 5.50 package. The above error message most certainly shows that WideClient is trying to use a protocol you've not installed. You do not show your WideClient.ini file, but the default protocol bfore version 5.50 was IPX/SPX, so that could be the reason.

For TCP/IP you will also need to provide the ServerName in the Client INI files, of course.

Pete

Link to comment
Share on other sites

Hullo Peter,

Sorry, sent the wrong information. Have reinstalled WideFS5.50 in the First Officer's Client computer and still received the same fault message. Here is the Log file and the .INI file for this computer:-

********* WideClient.DLL Log [version 5.50] *********

Date (dmy): 31/05/03, Time 13:10:05.970: Client name is PC2

297 Attempting to connect now

297 Client socket() failed [Error=10044] Socket type not supported

7736 New Client Application: "PFD" (Id=-852145)

8770 WRITESTATEDATA received with bad data size!

8770 0 ReadLocal: Offset=10000, Size=0000

18527 Failed to start Client!

18920 Reception maximum achieved: 0 frames/sec, 0 bytes/sec

18920 Max receive buffer = 0, Max send depth = 0

18920 ********* Log file closed (Buffers: MaxUsed 1, Alloc 30 Freed 30 Refused 0) *********

; PLEASE SEE WideFS documentation for parameter details

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

[Config]

UseTCPIP=Yes

ServerName=PC4

Port=8002

Window=43,44,886,589

Visible=Yes

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

[user]

Run1=c:\PFD\PFD.exe

Log=Errors+

Here are the same two files for the adjacent EICAS client computer:-

********* WideClient.DLL Log [version 5.50] *********

Date (dmy): 31/05/03, Time 12:07:41.970: Client name is PC1

693 Attempting to connect now

12163 New Client Application: "PFD" (Id=-868275)

17858 WRITESTATEDATA received with bad data size!

17858 0 ReadLocal: Offset=10000, Size=0000

; PLEASE SEE WideFS documentation for parameter details

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

[Config]

UseTCPIP=Yes

ServerName=PC4

Port=8002

Window=43,44,886,589

Visible=Yes

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

[user]

Run1=c:\PFD\PFD.exe

Log=Errors+

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

Does this help you,

Reagrds,

Barry :roll: :roll:

Link to comment
Share on other sites

Have reinstalled WideFS5.50 in the First Officer's Client computer and still received the same fault message. Here is the Log file and the .INI file for this computer:-

********* WideClient.DLL Log [version 5.50] *********

Date (dmy): 31/05/03, Time 13:10:05.970: Client name is PC2

297 Attempting to connect now

297 Client socket() failed [Error=10044] Socket type not supported

Hmmm. Very strange. Everything else looks right now. so now I've really no idea what Windows can mean by "Socket type not supported". Windows documentation says

"The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. "

The "socket type" I am asking for in WideFS is SOCK_SEQPACKET. Now this was new to Winsock Version 2, but Winsock 2 was most definitely introduced with Windows 98 (and possibly 95 SR2, but I cannot remember -- it wasn't part of the original Windows 95, I know).

So the only conclusion I can draw is that your Win98SE installation is in error, possibly corrupted or changed by something else that's been installed. Try running the System File Checker (SFC, accessible through System Information I think). Maybe re-installing Win98SE over the top will recover it.

But first of all, in case it is down to your NIC driver, try re-installing the NIC itself -- delete it from the Windows System-Device Manager list, then re-booting and re-installing its driver(s).

I really can't think of anything else. sorry.

Pete

Link to comment
Share on other sites

  • 4 weeks later...

Hi Peter,

Sorry haven't replied earlier. I reformated the computer and all hell broke loose. Replaced the hard drive and reloaded everything and bingo, we returned it to the network and everything works fine.

Regards,

Barry

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.