Fs commander error msg #14

[pabulas]

I've net worked my desktop running vista with my laptop running XP.

Both pc's are on the same workgroup.

I can share files between the the two pc's.

I have Fsuipc ver 3.93 installed on the vista machine and wide client v 6.78 on the XP machine, Flightsim FS9 installed on desktop. Both Fsuipc and wide client are registered.

I run FS9 then wide client, FS9 displays that wide client has connected. I then run FS commader v8.5 (registered) when I try to connect to FS9 I get the following message (error msg#14).

Log files:-

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 06/11/09, Time 19:24:16.640: Server name is VISTA

57890 Initialising TCP/IP server

57922 Initialising IPX/SPX server

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

57922 Failed to start IPX/SPX Server

57922 Initialising UDP/IP server

58859 Broadcasting service every 1000 mSecs

69078 Restarting service due to total lack of use

69078 Failed to start IPX/SPX Server

140609 Incoming connection Accepted ok (skt=2644) TCP

140719 Connected to computer "ACER" running WideClient version 6.780 (skt=2644) TCP

156859 Error 10053: client socket disconnected at Client: removing (skt=2644) TCP

161390 Close signalled to clients

162500 Closing down now ...

Memory managed: Offset records: 23 alloc, 23 free

Read buffer usage: 8 alloc, 8 free, max in session: 1

Write buffer usage: 207 alloc, 207 free, max in session: 1

Throughput maximum achieved: 12 frames/sec, 778 bytes/sec

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

Average receive rate from "ACER": 0 frames/sec, 13 bytes/sec

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

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

Date (dmy): 06/11/09, Time 19:26:36.015: Client name is ACER

1203 Attempting to connect now

1859 Server = VISTA

1875 Trying TCP/IP host "VISTA" port 8002 ...

1875Okay, IP Address = 192.168.0.2

1875 Connection made okay!

18078 ****** End of session performance summary ******

18078 Total time connected = 14 seconds

18078 Reception maximum: 12 frames/sec, 737 bytes/sec

18078 Reception average whilst connected: 10 frames/sec, 655 bytes/sec

18078 Transmission maximum: 0 frames/sec, 20 bytes/sec

18078 Transmission average whilst connected: 0 frames/sec, 32 bytes/sec

18078 Max receive buffer = 739, Max send depth = 1, Send frames lost = 0

18078 ********* Log file closed (Buffers: MaxUsed 2, Alloc 165 Freed 165 Refused 0) *********

Wideclient config

[Config]

server=vista

protocol=TCP

Port=8002

Window=43,44,886,589

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

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

[user]

Log=Errors+

Wideserver config

[Config]

AdvertiseService=1

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port=8002

Port2=9002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

[ClientNames]

1=TOSHIBA

2=ACER

I've read all related posts but could not find the answer to resolve and I'm no expert . I would really appreciate your help with this.

Regards,

Paul.

[Pete Dowson]

I run FS9 then wide client, FS9 displays that wide client has connected. I then run FS commader v8.5 (registered) when I try to connect to FS9 I get the following message (error msg#14).

Where's the erorr message -- or is that it "error msg#14"? Does it in any way attribute anything to FSUIPC? If not why do you think it is anything to do with WideFS or FSUIPC? I'm pretty sure FSCommander needs data access to FS files aside from its connection via FSUIPC -- from ther posts here that seems to be folks usual problem. Have you asked FSC support?

The logs only show that you connected the client for 16 seconds, and it ran okay, before you terminated the FS session and also WideClient. Was 16 seconds long enough even for FSC to fully initialise and get itself ready?

I've read all related posts but could not find the answer to resolve and I'm no expert .

I think that is because you are in the wrong place. Try FSC support, as I don't know it (I don't have it and have never seen it). Your WideFS connection is fine, though you could consider running FS for a bit longer than 16 seconds after connection.

Regards,

Pete