Ropipo

Papaalfazero (Detleff), What did you do with the firewall ? Roger

Walouigi, What was your firewall problem ? Roger

Pete, Since the last post I have no more problem. So for the time being I consider the problem solved. I think the source of the problem was the different definitions of the workgroup in both PCs. If the problem comes back I will check as you suggested. Roger

Pete, I assume it as no message appears above the menu bar of FSX when I am in window mode. No message saying it is waiting or is connected. On the client side the WideFS says it is waiting for a communication. Roger

Pete, Thank you for your answer. For the moment I have no problem but I am also less flying the usual flights. I am following the Missions and therefore not needing the client PC. But I will check what you suggest and will report as soon I find something or have a log. To answer you first question >> Ropipo wrote: But I still have one intermitent problem: WideFS for the server doens't start.>> < FSUIPC is active but no WideFS for the server starts. I will sent you a log as soon I get the problem again. Roger

Pete, I have fixed 95 % of the problem. I think it was a definition problem in the network groups. But I still have one intermitent problem: WideFS for the server doens't start. I use Windows 7 on the server. From time to time a random application will not respond to the W7. To overcome that problem I must reboot the server. I think it is the same problem with WideFS for the server. When there is no message in the server bar I believe FSX/FSUIPC are waiting for WideFS. Maybe it is there but if there is no dialog to establish a connection between FSX and WideFS for server we can just wait for centuries. To overcome the problem I must reboot the server. Stoping and restarting FSX will not solve the problem. Conclusion: this must be a W7 problem. Checking with Google I find several sites where people are complaining for the same problem with W7 but nobody has yet found an answer. The problem is annoying but as I get it sometimes far a part I can live with it. But I would be happy if somebody could help or point to me to the correct site where I can find help. Roger

Pete, May or may not means that sometimes the warning that FSX waits for WideFS connection is posted above FSX screen and other times it does not mention any waiting (or if the client is on line). But MAYBE I found the reason for this intermitent problem. Reviewing every parameter I realized that the server was connected to WORKGOUP and the client to FSNETWORK. It took me some time to figure out how to correct this. Now it is O.K. I just need to wait and see it the connection is successful each time or again sometimes yes, sometimes no. I do not have the time to check more in detail your message. I will examine it tomorrow morning. I hope you had a good holiday ! More in the next few days. Roger

Follow up: I added an Ethernet card. This solved many communication problems. But not the WAITING FOR FSUIPC on the client PC. Now what I may or may not have is that FSUIPC doesn't show any message, waiting for client or having a connection. And of course there is no communication with WideFS. I must then stop FSX AND the PC then restart the PC. Roger

Andy, Yes I missed that. But I don't think Peter can really help me. Just his opinion is needed. Today FSUIPC and WideFS are communicating !!!!!. It seems that the failures occur when it is warmer summer days. I still need to check that. Today my tests are conducted in the morning when it is still cool. I am suspecting the Ethernet is too sensible to heat. Then I also have some slow down going over the internet. As I said I need to check this with other warm days. If this is the case I will need extra fans in the case or buy a dedicated Ethernet card instead of using the Mobo Ethernet. But Peter's opinion will be interresting.

Peter, Now the ini files: FSUIPC.INI PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=Yes ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=Yes BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=No LogWrites=Yes LogReads=Yes LogLua=Yes [JoyNames] AutoAssignLetters=No 0=CH PRO PEDALS USB 0.GUID={98CDD9C0-46FA-11DF-8006-444553540000} 1=CH FLIGHT SIM YOKE USB 1.GUID={98CDD9C0-46FA-11DF-8007-444553540000} [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [buttons] ButtonRepeat=20,10 [AutoSave] AutoSaveEnabled=Yes Interval=750 Files=10 SaveOnGround=Yes Next=7 1=Sat 160845 2=Sun 120256 3=Sun 121525 4=Sun 122755 5=Sun 124024 6=Thu 103230 7=Thu 163707 8=Thu 185149 9=Sat 133030 10=Sat 155615 [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port= Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [ClientNames] 1=ROGER-POTIE-NB [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 LeftBrake=-7232,0 RightBrake=-7200,-32 ------------------------------------------------------------------------------------------------------------------------------ WideFSClient.INI ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=-32000,-32000,160,25 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 ServerName=RogerP Protocol=TCP ; ----------------------------------------------- [user] Log=Errors+ ; ===============================================

Peter, I am posting the two log files. ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 26/06/10, Time 12:20:43.802: Client name is ROGER-POTIE-NB 468 Attempting to connect now 500 Trying TCP/IP host "192.168.0.2" port 8002 ... 500Okay, IP Address = 192.168.0.2 21497 Error on client pre-Connection Select() [Error=10060] Connection timed out 21497 Ready to try connection again 22527 Attempting to connect now 66582 Trying TCP/IP host "192.168.0.2" port 8002 ... 66582Okay, IP Address = 192.168.0.2 132710 Trying TCP/IP host "192.168.0.2" port 8002 ... 132710Okay, IP Address = 192.168.0.2 198808 Trying TCP/IP host "192.168.0.2" port 8002 ... 198808Okay, IP Address = 192.168.0.2 264953 Trying TCP/IP host "192.168.0.2" port 8002 ... 264953Okay, IP Address = 192.168.0.2 331019 Trying TCP/IP host "192.168.0.2" port 8002 ... 331019Okay, IP Address = 192.168.0.2 397179 Trying TCP/IP host "192.168.0.2" port 8002 ... 397179Okay, IP Address = 192.168.0.2 463277 Trying TCP/IP host "192.168.0.2" port 8002 ... 463277Okay, IP Address = 192.168.0.2 529405 Trying TCP/IP host "192.168.0.2" port 8002 ... 529405Okay, IP Address = 192.168.0.2 595565 Trying TCP/IP host "192.168.0.2" port 8002 ... 595565Okay, IP Address = 192.168.0.2 646999 ****** End of session performance summary ****** 646999 Total time connected = 0 seconds 646999 Reception maximum: 0 frames/sec, 0 bytes/sec 646999 Transmission maximum: 0 frames/sec, 0 bytes/sec 646999 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 646999 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* and ********* WideServer.DLL Log [version 7.60a] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 26/06/10, Time 12:20:56.038: Server name is ROGERP 15257 Initialising TCP/IP server 15257 Initialising IPX/SPX server 15257 IPX/SPX socket() failed [Error=10044] Socket type not supported 15257 Failed to start IPX/SPX Server 15257 Initialising UDP/IP server 16130 Broadcasting service every 1000 mSecs 635127 Closing down now ... Memory managed: Offset records: 470 alloc, 468 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 checked the IP address: O.K. Both PC are in same workgroup (I can read shared files between them). Roger

Peter, I have once in a while a problem connecting FSUIPC and WideFS. (more less than often) FSX PC in Windows 7 64 bits, the client in Vista 32 bits. FSUIPC version 4.60a; WideFS 6.78 The FS saying waiting for client. The client WideFS saying WideClient FS98 Eliminator - Waiting for a connection. No dialog between them. FScommander failes when turning on GPS. On the other had ActiveSky ASE has the connection: so Simconnect is O.K. What troubles me is the title WideClient FS98 ! Do you have an idea what I should do ? Roger

Yes, one more proof that regular back-ups is not wasted time and money. Roger

Peter, First may I thank you. You did enlighten me a bit with SimConnect. I thought SimConnect was a product installed with SDK. There is some relation betweeen the products (SimConnect.msi). I also needed to execute ConfigSDK.exe and I think it helped me to have SimConnect working. I never gave a thought to how FSX basic worked with FSUIPC or ASA. Now Acronis save me a day (or weeks) of work. The system restore was not good enough but the full restore helped me. I just did some extra BUP (pictures and My Document) to save some work done after the last BUP. Now FSUIPC4 and ASA work perfectly. I will now start my tests with RC4. Roger

Peter, >>You will have to "bite the bullet".<< I just did it. I replaced the mobo and processor. Then I installed Windows 7. And after that FSX with its load of add-ons and tuning based on NickN suggestions. 3 weeks I am busy with that. BUT... I do have Acronis back-ups (Total files BUP and System BUP). So I could restore to the last known good picture before I messed up with SimConnect (Last Friday a week ago). Will the restore help me to avoid a total reinstallation ? Roger

Peter, One more thing. Here is the content of DLL.XML found in Users\Roger\AppData\Roaming\Microsoft\FSX " <?xml version="1.0" encoding="Windows-1252"?> Launch dll.xml False False AFXModule False False C:\Program Files (x86)\AFX\AFXModuleFSX.dll Object Placement Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll Traffic Toolbox True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll Visual Effects Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll FSUIPC 4 False Modules\FSUIPC4.dll "

Peter, >> Assuming you mean "FSX" not "SDX" << I meant SDK. >> There never is a Modules tab in FSX. << I meant the last entry of the top menu bar of FSX, the option that should follow HELP option. >> SDK? What has the SDK got to do with it? << Is it not SDK that install SimConnect ? It is in the folder Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib that the file SimConnect.MSI can be found. It is after executing it that the "SimConnect build 60905 (Original)" "SimConnect build 61242 (SP1)" and "SimConnect build 61259 (Acc/SP2)" are created, is it not ? And these are the data that FSUIPC says is not correctly installed. >> Yet ASA linked okay? via SimConnect? << Yes ! >> All the FSUIPC4 installer is doing is reporting back what Windows says when it tries to connect to the SimConnect DLL. << So it need SimConnect, yes? >>If FSUIPC4 is loading there will be an FSUIPC4.LOG file. If there is on, show it to me. If not, you have a corrupted DLL.XML file. << I am not trying to load it. I am trying to reinstall it . And that is where I receive: "Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original), but this is not correctly installed! Found SimConnect build 61242 (SP1 May07), but this is not correctly installed! Found SimConnect build 61259 (Acc/SP2 Oct07), but this is not correctly installed! ... Probe Manifest fails to match a valid SimConnect needed to use FSUIPC4! " And the installation of FSUIPC stops. And I am positive that no error was mentioned with the installation of the different versions of SimConnect. Talking about loading FSUIPC4 the FSUIPC4.DLL is present in the modules folder of FSX. How can I repair/copy/reinstall DLL.XML ? So now I am even more completely confused with the relation of FSUIPC and SimConnect. Before this I would have never thaught that there was a relation between the 2 products. Here is the FSUIPC log when I started the last time FSX. Now I see that there is a loading process for FSUIPC4 taking place. I did not realized that. But there is a simconnect connection problem here. >>********* FSUIPC4, Version 4.60a by Pete Dowson ********* Reading options from "E:\Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... NOTE: SimConnect Acc/SP2 Oct07 appears to exist, but is not loadable! Trying to connect to SimConnect SP1 May07 ... NOTE: SimConnect SP1 May07 appears to exist, but is not loadable! Trying to connect to SimConnect Original ... NOTE: SimConnect Original appears to exist, but is not loadable! User Name="Roger Potie" User Addr="rogerpotie@skynet.be" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows 7 (using SimConnect Original) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=255 203 System time = 13/05/2010 22:28:52 296 FLT UNC path = "\\ROGERP\Documents\Flight Simulator X Files\" 296 FS UNC path = "\\ROGERP\Flight Simulator X\" 764 LogOptions=00000000 00000001 764 Could not link to all needed SimConnect facilities 16583Now trying to connect to another version of SimConnect ... 31606Now trying to connect to another version of SimConnect ... 46644Now trying to connect to another version of SimConnect ... 61683Now trying to connect to another version of SimConnect ... 76721Now trying to connect to another version of SimConnect ... 92368Now trying to connect to another version of SimConnect about 70 to 80 similar lines Can you help me with this ? Do you need more information ? I repeat ASA from HiFi is finding SimConnect. Is it a path problem ? I doubt but I really do not know. Roger

Peter, Here is the complete installer messages: Installer for FSUIPC4.DLL version 4.60a Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: AppPath="E:\Flight Simulator X\" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original), but this is not correctly installed! Found SimConnect build 61242 (SP1 May07), but this is not correctly installed! Found SimConnect build 61259 (Acc/SP2 Oct07), but this is not correctly installed! ... Probe Manifest fails to match a valid SimConnect needed to use FSUIPC4!

Peter, I had some problems with Simconnect. I finally uninstall SDX and Simconnect (and ALL the related files I could find in Program files, Document, Windows SXS etc.. on both computers. The FSX folder is NOT in the default Programs Files or c drive. It is on a seperate F drive. I reinstalled all three versions of SDK. I tested after each install. ASA from HiFi worked each time. I realized that the Module tab was missing from FSX. So I tried to reinstall FSUIPC version 4.60a (last version downloaded 10 minutes ago). During the install I get the message: "Your FSX installation is incorrect! The version of SimConnect installed will not run FSUIPC4. You may need to repair the installation to rectify this first." On the FSUIPC installation log I read: " Found SimConnect build 60905 (Original), but this is not correctly installed!" Same thing for build 61242 (SP1) and build 61259 (Acc/SP2) "Prode Manifest fails to match a valid SimConnect needed to use FSUIPC4! I am sure that I received no error message during the SDK installations. I did execute the ConfigSDK.exe (needed when FSX or SDK are not in the default library); the proof is that ASA works. Please do not tell me to reinstall SDK: I was really cautious and checked everything (messages, tests) during the last reinstall of SDK. Do yoy have any suggestion ? Roger

Peter, Everything seems normal again. FSUIPC and WideFS seem happy again. To get rid of the AI entries in the menu bar I let FSX recreate th cfg file. The nuissance could result of an incorrectly overclock. So now that OC isrunning without error and the cfg file is recreated, I am a happy user. Thank you for your help. Roger

Thank you Pete. 1. I will check the log next time. 2. Yes those pgm are on a networked PC 3. Well how to say it: If FSUIPC doesn't say that it is waiting a connection then there is no dialog between FSUIPC and WideFS 4. Yes the menu bar of FSX (the one called by alt) No icon but words. They appear on the right of "add-ons". They have nothing to do with FSUIPC but this phenomen appearted at the same time as the FSUIPC problem. Next time I will take a picture of the screen and send it with the log. I suspect more a corruption of FSX than a real problem with FSUIPC. FSUIPC worked for years without problem for me. I willl be back soon with the log and picture. Roger

Peter, I have a recent problem. I don't think that FSUIPC is really the cause. Until recently I had not problem with FSUIPC (in XP) and WideFS (in Vista). But now it looks like FSUIPC doesn't get started at each FSX session: sometimes yes, sometimes no. When yes the FSUIPC warning appears at the top of the screen to say there is a connected session with WideFS, when no no message appears. In this last case the FSCommander and Radar Contact cannot dialog with FSX. I need then to stop FSX and XP and then restart them in the hope that it will work. I also get something strange after the add-ons entry on the task bar above the screen, again not systematically: entries for different planes; if I click on one I get a sort of video of that plane that I cannot control. When all this started I still had an older version of FSUIPC and WideFS. Now I updated them to FSUIPC 4.57 and WideFS 6.78. But still these strange things may happen. I must also confess that I overclocked my PC and did not do a thourough checking with the last parameters and that when I did I realized that I had sometimes an error. This could have corrupted something in FSX. But as I said the strange things do not happen systematically. Any idea ? I will also post this message in AVSIM. Roger XP Pro ,and FSUIPC 4.57 for XP Pro and WideFS 6.78 with Vista.

Peter, Problem solved. I fly FSX using 2 monitors. On monitor 1 is used for FSX main window (cockpit). On monitor 2 I put the radio stack and GPS. If my last action was with a click in GPS or Radio stack, then pressing one of the keys for RC was not intercepted. If I click anywhere on monitor 1 then FSUIPC intercepts the keystroke and sends it to RC. This is what jd calls the focused window. I never experienced this with FS9. Well everything is O.K. for me now. Roger

Peter, More info: I have already noticed that when I press Alt or Alt-Enter it MAY unblock the situation. In fact what seems to unblock at each attempt is by going to View, Panel Instruments and choose a panel. In my case itis the Groundhandling. Now before anybody accuses the freeware Groundhandling, I did have the same problem before implementing this module. Not being an expert with FSUIPC or FSX, I cannot understand why moving in or out a panel on the screen can change the acceptance of a code ofrom the KB, especially that I move the panel without touching the KB. Roger

Peter, I have a problem transmitting key strokes to RCV4. This program doesn't receive some (radomly) of the key strokes. The RC log shows it. But the FSUIPC log also shows that it did not receive them. So what is happening. I execute FSX and RC in the same PC (no WideFS involved). XP Professional in English and FSX also. But the keyboard is defined as Belgium French. While the keystrokes for RC are not transmitted, other keystrokes are recognized by FSX. (such as Q for mute or shift-Z for fps display) Sometimes but not always pressing Alt or Alt-Enter will help to regain control. The problem happens as much in Full Screen or windowed screen. I used 2 KB: wireless Logitech and wired Dell. Both with same results. I have the logs if you need them. RC is version 4. FSUIPC is version 4.20 from October 23rd 2007. Can you help ? I already sent a msg to this forum (at least I tought so) but I cannot find it. So if you do have duplicate msg you know why. My PC specs Antec P182A case, OCZ GameXtreme 700W PSU, Abit AW9D-Maw mother board, Intel Core 2 E6750/2.66GHz processor, Corsair 2Gb-800 DDR2 PC-6400 Dominator memory, 2x250GB WD Caviar SATA Hard Disk (RAID 0), EVGA e-GeForce 8800 GTS 640 MB, DVD R/W NEC Sony AD7173A, Samsung 931BF 19" 2ms monitor, WD e-SATA external HD, Windows XP Professional. Roger P.S I also ave a problem with the AV NOD32. I am just mentioning it but I really don't think there is any relation between them. Tha AV crashes the FSX sometimes (at least from MS point of view).