clipper747pa

I will wrap the information up and send to MS regards Wolfgang

Dear Pete, to cut a long story short, FSUIPC works now very well, it shows up in the add on menu and I finally could register it!! :D :D :D How? I did the manual installation of SimConnect from the DVD as told, but still no success. Anyway, it was a good hint to check the installation date in the WIN SxS. I don't know if it had someting to do with my problems, but at least I could be sure simconnect is properly installed. But even then I never got the simconnect.ini working. The startimmediately=yes command in FSUIPC didn't help either. No simconnect.log and no change in the FSUIPC.log as previously sent to you. So this was it for me. I completely deinstalled Mc Affee Security Suite and subsequentely FSUIPC (just to produce a new and clean FSUIPC installation afterwards). I then bought the complete antivirus software of a provider with a "N " in its brand name. Installed that software, installed FSUIPC 4.04 and here we go. :P Solution summary (for my PC): Simconnect works in the Geman version of FSX. FSUIPC works well with the German version of FSX It was just a problem with the antivirus program, not with the windows firewall software. Even though I told my previous antivirus software (via the trusted entry) that FSUIPC ist indeed to be trusted, it did not help. So..., now its time to take off again ! Thanks again Pete!! Wolfgang

This morning I told myself not to work on that problem tonight :!: , but here we go again :D Well, you're right. I just thought I should. JFI, this is the entry in the FSX.cfg: [TRUSTED] D:\Flight Simulator X\Modules\FSUIPC4.dll.tuabrchaukuzzqlruiozrltwqqwoizbietecnoet=1 I have the deluxe edition. I read in another post (by MARK T) regarding this issue, to find the SDK on DVD1, install that, then find the Simconnect.msi file which is in the SDK's "Core Utilities Kit\SimConnect SDK\lib" folder. Then run the msi file to install Simconnect. That's exactely what I did. I checked and positevely identified: Under C:\WINDOWS\WinSxS the x86_SimConnect folder, it had the simConnect.dll file in it. Under C:\WINDOWS\WinSxS\Manifest- There was a simconnect mainfest file and a security catalog file. these had the name x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_x-ww_429211e9. and x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_x-ww_429211e9.Manifest I then started the FSX, but still no logs. I will now try to play around with the manual installation hint as povided by Jason Jacobs (you wrote me that hint) One last word (...folks, forgive me for getting a bit off track): You know, what drives me crazy is, that with all that hints, your support, the time both of us spent on this, I still see no success, not a bit. I wonder if anybody else has these problems? On top I am asking myself, how those guys, who have no idea about SDK's, ini files and so on, and just want to play with this FSX software do in these cases. Regards Wolfgang

Hi Pete, ok. What I am going to do is the following: + I will delete the trusted entry of FSUIPC out of the FSX.cfg and delete all existing FSUIPC files in FSX + I will then run thru the entire installation process again with your latest version 4.04. (didn't do that in the first place, because the log never showed up anyway). + I will then add the StartImmediately=Yes to the [General] section of the FSUIPC4.INI file. + Create and save the simconnect.ini with the console=yes command "all over the place" + I will finally make sure, that FSUIPC is trusted also by McAfee (at least I will try this entry) and then see what happens. If I still get no add on entry and no Console window and no response of simconnect to my simconnect.ini., I will try a complete reinstallation (...really looking forward to that "waste of time" :? ) If all that won't help, I will send it all to Microsoft and see what they make out of it. Maybe it has something to do with the German version of FSX, we'll see. Last but not least, I now need to readjust my priorities for the next couple of days. I spent so much time working on this, my family starts asking what I am doing :lol: Pete, let me again thank you for your support. It is not your fault, we could not solve the problem, nor do I think that it is a FSUIPC problem. I will update you on my findings as soon as I have something new. Best regards from EDDK a nice sunday evening Wolfgang To all folks reading these posts: Please let us know, if you came across similar problems!!! - share your experience!!

Hi again, now I am getting a little confused as -to where to put the simconnect.ini, -where to expect the simmconnect.log after closing FS/X and finally which path to name in the simconnect.ini? a) the FSX main dirctory, subfolder Modules or b) the Own documents/Flight Simulator Files directory Yes I am continuing with the different naming and so on. Well, my first attempt to try the CONSOLE logging failed. ...I will not give up!! :D regards Wolfgang

Hi Pete, well, it seems, this thing gets more and more complex. I did as you told me (and rechecked that I copied everything in the .ini file). This is how the file looks: [simConnect] level=Verbose console=No file=D:\Flight Simulator X\Modules\SimConnect%01u.Log file_max_index=9 Well, in the German version of WIN XP this folder is called "Eigene Dateien" which translates into Own documents. I. assume that is the same folder as My Documents. It also containes the saved flights and the saved settings for the Visuals. I saved the text file as simconnect.ini in this folder I then ran FSX, closed it after a couple of minutes, but did not find any simconnect.log in the modules folder (that's at least where i thought I had to search). I then copied the simconnect.ini also into the FSX main folder and in the modules folder, tried it again, but to no avail. All in all I come to the conclusion, that the problem may derive from the following sources: - Antivirus program refuses to let FSUIPC talk to simconnect or receive messages from simconnect - Incomplete installation of simconnect (maybe also because of Mc Afee) - Not very probable though, but FSX is installed on the D: drive, while the my documents folder is on the C: drive So, the next questions are: - Maybe simconnect is not installed at all? (??? --same thing like in the posting http://forums.simflight.com/viewtopic.php?t=56831 --???), - But then again, why does MyTraffic for FSX work (I assume it must also use simconnect)? - Can I somehow make sure, or identify, that simconnect is working or installed? - Maybe the Antivirus programm did not allow the FSX to install simconnect in the first place Thanks again for your ongoing support!!! ...and I hope, we will finally find the cause Wolfgang

hi again, This time I closed the Mc Afee Security Center before installing. I then installed 4.03 and got the ok message. Launching FSX and no add on menu appeared. A little flying and then closing FSX. This is how the log file looks: ********* FSUIPC4, Version 4.03 by Pete Dowson ********* User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Running inside FSX Module base=61000000 LogOptions=00000001 DebugStatus=0 31 System time = 23:11:47 31 FLT UNC path = "C:\Dokumente und Einstellungen\Wolfgang\Eigene Dateien\Flight Simulator X-Dateien" 31 FS UNC path = "D:\Flight Simulator X" 1219 SimConnect_Open succeeded: proceeding to initialise interface! 175297 System time = 23:14:42 175297 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed *********** ...by the way, even though I don't see the light at the end of the tunnel in this matter yet, I would like to thank you for your support and your efforts!!! Best regards Wolfgang

Dear Pete, first of all, thanks for the prompt answer! - Since I have to run a business in my real life I couldn't get back earlier to answer your questions. But here we go: Well, as I am not a native speaker, I probably choose the wrong word. What I meant was, the installation of FSUIPC went fine, I got the success message, but the FSUIPC menu never showed up as an "add ons" menu. Same thing as above. In the German version of FSX there is an "EXTRA" menu which probably is the add on menu in the English version. Thats the "Extra" section showing up on top as a drop down menu, when you have add ons installed. In my case FSX MyTraffic It says: ********* FSUIPC4, Version 4.026 by Pete Dowson ********* User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Running inside FSX Module base=61000000 LogOptions=00000001 DebugStatus=0 78 System time = 21:33:08 78 FLT UNC path = "C:\Dokumente und Einstellungen\Wolfgang\Eigene Dateien\Flight Simulator X-Dateien\" 78 FS UNC path = "D:\Flight Simulator X\" 1297 SimConnect_Open succeeded: proceeding to initialise interface! Does this log file show anything unusual to you? Regards Wolfgang

Hi Pete, I am new to this forum and, frankly, I do need your help. I have two questions: 1) Using FSUIPC for years I was eager to install it on FSX. Now, I am one of those guys who cannot install FSUIPC 4.0., probably because of the Mc Afee Antivirus Program I am using. You remember, the problem you listed in your anouncement under problem type 1. I tried everything, except for the uninstallation, but to no avail. I still cannot see the FSUIPC menu in the EXTRA section of FSX. Since I also paid for the registration, I am desperately seeking a solution. You mentioned somebody with the the same Mc Afee software who got it fixed. Do you have more details on the way he did it or could you please tell me his alias or email adress so i can get in touch with him? 2) Does FSUIPC work even though it does not show up in the add on menu? Thanks for your help. Wolfgang