ModelFlyer

Hi Peter, You must be a genius. The workgroup names were different. I must admit that I hate networks. The computers were connecting before, for file sharing, so I assumed that part of it was OK. Thanks for your help. I can now do some serious flying. Regards Don

Hi Peter, I have pasted the 3 files below. Regards, Don Riley FSUIPC$.log ********* FSUIPC4, Version 4.152 by Pete Dowson ********* User Name="Don Riley" User Addr="donriley@lisp.com.au" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX (SimConnect SP1 May07) Module base=069F0000 DebugStatus=255 141 System time = 20:06:48 157 FLT UNC path = "\\ASUS\Data (D)\My Documents\Flight Simulator X Files\" 157 FS UNC path = "\\ASUS\Program Files\" 1828 LogOptions=00000001 1828 SimConnect_Open succeeded: waiting to check version okay 6688 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 6688 Initialising SimConnect data requests now 6688 FSUIPC Menu entry added 6907 F:\Program Files\FLIGHTS\OTHER\FLTSIM.FLT 6907 F:\Program Files\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 65953 System time = 20:07:54, FSX time = 20:06:56 (03:06Z) 66157 Aircraft="Aircreation582SL red" 66813 Advanced Weather Interface Enabled 447297 System time = 20:14:16, FSX time = 20:08:53 (03:08Z) 447297 *** FSUIPC log file being closed Memory managed: 178 Allocs, 178 Freed ********* FSUIPC Log file closed *********** WideClient.log ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 20/08/07, Time 20:28:57.265: Client name is TOSHIBA-BDC772C 296 C:\Program Files\Aerosoft\FSC 296 C:\Program Files\Aerosoft\FSC\FSC.exe 328 Attempting to connect now 1328 Trying to locate server: Need details from Server Broadcast 1328 Failed to connect: waiting to try again 3328 Attempting to connect now 67546 Trying to locate server: Need details from Server Broadcast 70953 New Client Application: "FSC" (Id=2876) 193921 Trying to locate server: Need details from Server Broadcast 245125 ****** End of session performance summary ****** 245125 Total time connected = 0 seconds 245125 Reception maximum: 0 frames/sec, 0 bytes/sec 245125 Transmission maximum: 0 frames/sec, 0 bytes/sec 245125 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 245125 **************** Individual client application activity **************** 245125 Client 2876 requests: 5 (Ave 5/sec), Data: 270 bytes (270/sec), Average 54 bytes/Process 245125 ********* Log file closed (Buffers: MaxUsed 1, Alloc 5 Freed 5 Refused 0) ********* WideServer.log ********* WideServer.DLL Log [version 7.152] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 20/08/07, Time 20:07:54.468: Server name is ASUS 15188 Initialising TCP/IP server 15188 Initialising IPX/SPX server 15204 ServerNode=0.0.4352.57135.22456 15204 Initialising UDP/IP server 16063 Broadcasting service every 1000 mSecs 379657 Closing down now ... Memory managed: Offset records: 178 alloc, 177 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed *********

I thought that I included the files with my last post, but I have attached them with this one.

Since posting my problem, I found that FSUIPC4 was working. Being fairly new to FSX, I was expecting the add-on menu to appear in the opening screen of FSX, and my flying had been done in full-screen mode, which does not show menus. Having passed this hurdle, and registering FSUIPC4 and WideFS, I still have the problem with WideFS on the client PC. When I start FlightSim Commander 8.1 and try to connect to FSX on the GPS menu, I get the message "Unable to connect to Flight Simulator Msg #11". The WideClient FS98 Eliminator window says "Waiting for a connection".

I have been trying to get FS Commander to work on a second PC, using WideFS 6.7.5.0 and FSUIPC4.152, but FSX fails to display the add-ons menu. Both PC's use Windows XP, the FSX computer used Norton360 initially, and the FS Commander computer uses Trend PC-Cillin 2007. Following the first failure I disabled the protection features of Norton360. This made no difference, so I then uninstalled Norton360, but this also had no effect. I then reinstalled FSX and FSUIPC4. This too made no difference. I am logged on as an administrator on both machines. On the FS Commander PC, WideFS starts with a window headed "Waiting for a connection" then loads FS Commander. I presume that the connection fails because FSUIPC4 is not working.