baw150

How do you mean? If you change aircraft it all springs to life? Well, not really, but with the default aircraft there are no problems. Then when I load the Level D, during the loading process itself, the computer becomes slower and slower until it eventually freezes. What sort of "general crash"? And we don't know that it's a Client problem. If there's only a problem when using the LDS 767, maybe it is taking too much of the FS processor and not letting WideServer run -- though I've never heard of such a thing before. What processor is it? What is your FS frame rate limiter set to? What are your frame rates? This was my initial reaction. My frame rates are limited to 22, I have a 1.8GHz processor with plenty of memory. I've used Level D fine with WideFS in the recent past. It is a printer connected to the main computer, but also installed on the other computer as a network printer. I will try de-installing the network printer, and see what happens. Is this a known problem? What do you think it might be? Thankyou very much for your help. Best wishes, Tom

Hi Pete, I've had a look at the Client Log and it's full of: 113663 Attempting to connect now 113663 Connection made okay! 131719 Timed out response: connection assumed lost! 131729 Ready to try connection again 131770 Timed out response: connection assumed lost! 131780 Attempting to connect now 131780 Connection made okay! 149886 Timed out response: connection assumed lost! 149896 Ready to try connection again 149936 Timed out response: connection assumed lost! 149946 Attempting to connect now 149956 Connection made okay! 168002 Timed out response: connection assumed lost! ...which I guess is what you were thinking of. So are you saying that there's something in the server which is stopping the messages from the Client getting through? It only seems to be happening with the Level-D 767... very strange. Could it be that the WideClient 'problem' I'm having is just a symptom of a general crash, and not a cause? Everything else is working fine on the network. Thanks again for your help? Tom

Dear Pete, I've been using your software for ages without a problem, so I don't think your programme is causing this problem, but without having done very much since last time (I installed a printer, but that's it), my FS9 is getting strangled by WideFS, with up to 15 connections. I don't know what the process is that's behind it, but I seem to be able to have multiple connections to FS9, even though only one computer is connected to it. Here's the log. I would really appreciate your help on this. ********* WideServer.DLL Log [version 6.47] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 27/06/05, Time 11:47:08.984: Server name is ONE 115766 Initialising TCP/IP server 115937 Initialising IPX/SPX server 115953 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 115953 Failed to start IPX/SPX Server 116844 Incoming connection Accepted ok (skt=2940) 116922 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2940) 127797 Incoming connection Accepted ok (skt=3012) 127875 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=3012) 138703 Incoming connection Accepted ok (skt=2996) 138781 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2996) 146172 Incoming connection Accepted ok (skt=2980) 146172 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2980) 150094 Incoming connection Accepted ok (skt=2964) 150094 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2964) 374719 Incoming connection Accepted ok (skt=3036) 374797 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=3036) What I don't understand, is why these multiple connections from the same computer are being accepted.... this didn't happen before, I'm sure! Best wishes, Tom