Jordan

Dear Pete, Thanks for the quick reply... I included the log and .ini files of both WideServer and Wideclient, I hope you will find something in here. Thanks for helping me out, Jordan The Hague, The Netherlands =============================================== ********* WideClient.DLL Log [version 6.101] Class=FS98MAIN ********* Date (dmy): 27/10/03, Time 23:18:48.187: Client name is SIMULATOR-B 62 Attempting to connect now 2640 Reception maximum achieved: 0 frames/sec, 0 bytes/sec 2640 Max receive buffer = 0, Max send depth = 0 2640 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* =============================================== WideClient.ini =============================================== [Config] Port=8002 UseTCPIP=Yes Window=63,389,886,589 Visible=Yes ServerName=SIMULATOR-A ServerIPAddr=192.168.123.25 ; ----------------------------------------------- [user] Log=Errors+ =============================================== =============================================== ********* WideServer.DLL Log [version 6.10] ********* Using blocksize guide of 4096 bytes Date (dmy): 27/10/03, Time 23:06:55.875: Server name is SIMULATOR-A 52438 Initialising server socket now 82516 Restarting service due to total lack of use =============================================== WideServer.ini =============================================== [Config] Port=8002 UseTCPIP=Yes ServerName=SIMULATOR-A ServerIPAddr=192.168.123.25 ; ----------------------------------------------- [user] Log=Errors+ ===============================================

Hello Everybody... :) I am probably overlooking something obvious, but since I am more or less new to using WideFS and FSUIPC (and paying for them...) I would really like some help trying to get them working together with FS2004. I installed all files concerned into the folders specified in their manuals : FSUIPC.dll (v3.1.0) , WideServer.dll and WideServer.ini (v6.1.0) into FS2004/modules ; WideClient.exe and WideClient.ini into Project Magenta folders on several networked pc's. All Pc's used have fixed IP adresses (FS2004 PC : 192.168.123.25) and are connected via a Broadband/LAN Router. (network workes fine) All harddrives used are fully shared. The registration codes for FSUIPC and WideFS were succesfully entered in FS2004. The WideServer.ini and WideClient.ini file were then modified as follows: =============================================== [Config] Port=8002 UseTCPIP=Yes Window=189,195,886,589 (only wideclient) Visible=Yes (only wideclient) ServerName=SIMULATOR-A ServerIPAddr=192.168.123.25 =============================================== After starting FS2004 (sim mode, not setup screen) and running WideClient on the network pc's, the status of WideClient remains "waiting for connection" for reasons unknown to me... Running the very helpfull PMFileCheck tool on the network pc's(comes with Project Magenta) results in the following report: (example: PC with Project Magenta PFD/ND "Simulator-B") =============================================== Standing by (Press button on the right) Opening Connections Local Path: E:\Program Files\PFD ND Checking Computer and User Name Local Computer Name: SIMULATOR-B Local User Name: Jordan C. Tuinman FSUIPC/WideFS found! FSUIPC Version 0 FAIL - FMC Not Detected (CDU or MCDU) FAIL - A/P NOT Detected (MCP or FCU) Checking FS Path FAIL - No FS Path reported Checking PMNETDIR Path (FMC Generated Path) Looking for INI files Closing Everything =================================== Since both FSUIPC and WideFS are found by PMFileCheck I think the network settings are OK up to the misterious "FS Path" wich is missing. Non of the manuals I have read refers to a "FS Path" setting in the .ini files or anywere else. Please help me out !!?? Regards in advance, Jordan Tuinman The Netherlands