FSUIPC and WideServer/client & windows xp.

[Guest Gregg]

Recently I upgraded one of my (3) computers used for MSFS2002, the new computer is the FS2002 base computer with the other two acting as clients and all three running Windows XP.

I have no problem getting the client computers recognising the server computer but I cannot get any of the computers to recognise FSUIPC (ver 2.974) which is housed in the MODULES directory. The programs being loaded on the client computer is Flight Tracker (V7.0.1) and FS Meteo (ver 5.2).

I have searched all computers and cannot find other copies of the ini files so I am a bit at loss as to where to turn next.

The client log file is as follows.

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

Date (dmy): 04/06/03, Time 21:21:24.323: Client name is GK

140 Trying TCP/IP host "ewa" ...

140Okay, IP Address = 10.0.0.2

9312 New Client Application: "fs_meteo" (Id=3776)

88062 New Client Application: "FlightTracker" (Id=3088)

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

120218 Reception average achieved whilst connected: 0 frames/sec, 0 bytes/sec

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

120218 ********* Log file closed (Buffers: MaxUsed 1, Alloc 89 Freed 89 Refused 0) *********

It would seem that I am not looking in the right place.

Does anyone have any ideas?

By the way before the upgrade, everything was working fine.

Would appreciate any comments.

Regards

Gregg

[Pete Dowson]

I have no problem getting the client computers recognising the server computer but I cannot get any of the computers to recognise FSUIPC (ver 2.974) which is housed in the MODULES directory[\quote]

Apart from the insignificant thing that the current FSUIPC version is 2.975, there's no such thing in WideFS as "computers recognising FSUIPC". If WideClient is running then it "pretends" to be Flight Sim with FSUIPC includes, so that any applications will connect to it.

Some programs will only operate then they are getting valid data through from FS. The thing to do with them is simply start them AFTER FS is running and WideFS is communicating. This will be when FS is actually ready to fly and not before. You can use the "RunReady" parameters to get WideClient to load such programs only when the interface can supply their needs. Check the WideFS documentation for details.

The programs being loaded on the client computer is Flight Tracker (V7.0.1) and FS Meteo (ver 5.2).

Well I don't know Flight Tracker (though I have it here someplace), but I use FSMeteo every day and I know it loads okay with "RunReady".

I have searched all computers and cannot find other copies of the ini files so I am a bit at loss as to where to turn next.

Sorry, what "other copies" of what "ini" files do you need?

The client log file is as follows.

That looks fine, except there are apparently no exchanges with the Server. Was FS running? Where's the WideServer log? That might show something, don't you think?

Pete

[Guest Gregg]

Peter, thanks for your response and to clarifysome of the points as follows.

1. FS is running before I start WideClient on the second computer.

2. The top toolbar in FS (when activated) shows that WideServer is running and between 2 -4 connects. That is suprising as with only one other computer active I would not have thought that it would show 4 connections.

3. The error message in Flight Trakker is as follows:-

"Error Source: ucACARS.ACARS_ON()

Error Number: 1

Eror Description: Maybe running WideClient, but FS not running on server, or wrong FSUIPC."

4. In FS_METEO V.2 after clicking "start" the status line shows "Waiting for FSUIPC...."

THe WideClient log reads as follows ....

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

Using blocksize guide of 2048 bytes

111516 Client socket unused for too long: removing (skt=2532)

136516 Client socket unused for too long: removing (skt=2196)

136516 Client socket unused for too long: removing (skt=2628)

161516 Client socket unused for too long: removing (skt=2404)

186516 Client socket unused for too long: removing (skt=2516)

211516 Client socket unused for too long: removing (skt=2636)

236531 Client socket unused for too long: removing (skt=2720)

236531 Client socket unused for too long: removing (skt=2704)

261516 Client socket unused for too long: removing (skt=2612)

286516 Client socket unused for too long: removing (skt=2840)

311516 Client socket unused for too long: removing (skt=2772)

336516 Client socket unused for too long: removing (skt=2616)

336516 Client socket unused for too long: removing (skt=2556)

361516 Client socket unused for too long: removing (skt=2608)

386563 Client socket unused for too long: removing (skt=2316)

411578 Client socket unused for too long: removing (skt=2376)

436563 Client socket unused for too long: removing (skt=2384)

436563 Client socket unused for too long: removing (skt=2288)

461906 Client socket unused for too long: removing (skt=2388)

5. The reference to additional .ini files was copies of the WideClient and WideServer.ini files which may have been on the computer(s) and may have caused a conflict, that was all.

I have had no problems in the past setting up these programs and have enjoyed and appreciate their application. Hence I am just a little concerned as to why I cannot lay my finger on this problem. Maybe it is staring me in the face and I cannot see it, hence the call for assistance....Gregg

[Pete Dowson]

The top toolbar in FS (when activated) shows that WideServer is running and between 2 -4 connects. That is suprising as with only one other computer active I would not have thought that it would show 4 connections.

This is actually explained in the documentation. The Server is timing out and disconnecting those clients which don't send it messages and the clients are re-connecting when they time out and don't see messages from the Server. The server timeout is deliberately longer than the Clients, so these events overlap and produce what you see.

The error message in Flight Trakker is as follows:-

"Error Source: ucACARS.ACARS_ON()

Error Number: 1

Eror Description: Maybe running WideClient, but FS not running on server, or wrong FSUIPC."

4. In FS_METEO V.2 after clicking "start" the status line shows "Waiting for FSUIPC...."

Yes, these both simply mean the client is not getting responses from the Server.

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

Please upgrade to Version 5.50. I cannot support old versions. Let me know how you get on when you are up to date.

Pete