Splodge

Peter All sorted - it turns out it was indeed a firewall issue! I had blocked FSX from both the trusted and internet zones when it initially asked me what to do (I'm on a bandwidth limited connection, and didn't want it downloading things and using up my allocation!). I have now allowed it in both zones, and the addons menu now appears. Quite why it works like that is probably best left to MS! Thanks again for your help. Martin

Well, that's short and sweet! It definitely shows SimConnect loading the DLL, but it doesn't then actually call the entry point to start FSUIPC4 off. It is supposed to call a routine called "DLLstart" in FSUIPC4 -- everything kicks off from there. Is there an FSUIPC4.LOG or INI file in the Modules folder at all? It doesn't look likely, but if there is can you show it to me please? I recall one (and only one) instance like this in the FSX Beta test group, several weeks ago. The SimConnect author in Microsoft was looking into it. I'm not sure whether it was ever resolved, I've a feeling it wasn't. I'm going to try searching for it now. Regards, Pete There is an INI file, containing: [General] History=9JO9IXS6W04UDAE5ZQK54 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No WeatherReadSeconds=1 [WideServer] WideFSenabled=Yes and a log: ********* FSUIPC4, Version 4.01 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 109 System time = 12:51:21 109 FLT UNC path = "C:\Documents and Settings\Martin Hodgson\My Documents\Flight Simulator X Files" 109 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X" 3875750 System time = 13:55:56 3875750 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed ***********

Hi Pete, thanks for the quick response! Is there a Modules folder in your FSX installation, with FSUIPC4.DLL included? If so, please right-click on it, select Properties, and check that it is Version 4.01 and has my Signature attached. What Windows version are you using? Yes to the Modules folder and FSUIPC.DLL, and it is signed by yourself. I am running XP home SP2, with all the latest updates. Hmmmnot sure. Maybe you accidentally told it NEVER to run programs by me instead? I'm not sure how to find out or how to reverse it if so --- those checks are imposed by Windows following calls to check the modules by FSX's SimConnect. However, I think it should be possible via Internet Explorer (for some reason IE is what Windows uses to manage these things). Do this: 1. Load IE, select Tools - Internet Options - Content. 2. Click the "Publishers" button. 3. You should now see tabs for "Trusted" and "untrusted" publishers. See which one I'm in. 4. If I'm not in either then your choice wasn't logged, so you SHOULD get the warning next time you run FSX. If I'm in the Untrusted list, Remove me from there. If I'm in the Trusted list, then, wellwe need to look further. You are indeed on the trusted list. Though in order to test this, I deleted the entry - and didn't get the message next time I started FSX - doh! Presumably because I had checked 'always accept...' etc. It is present, and contains the following: FSUIPC 4 False Modules\FSUIPC4.dll They were both installed on the same username, there is only one on this PC. You will have mail shortly... Yes. Always best to install, check, then pay, really. We'll sort it out though. Sorry it's so complicated. This is all imposed by Microsoft, it isn't my design. And I am informed it gets worse with Vista. More red tape than the tax man! Regards, Pete Ah well, the support is good anyway!

After installing FSUIPC 4.0 (and later 4.1) yesterday, I still cannot see it in the menu - the 'Addons' option is simply non-existant. I have read the various threads regarding installation, and how it is affected by installation location, but they don't apply to me - I installed FSX (deluxe) with all the default installation options, and when installing FSUIPC get the 'Installation Successful' (or equivalent) message, this with both versions of the module. One slightly interesting thing is that I got an 'alert' when starting FSX after the initial installation about the external program, so it was clearly detected, however I'm sure I told it to run the program, and to ALWAYS run programs signed by 'Peter L. Dowson'. Is there any way to check this? I have also checked my simconnect module, which is the correct version and is in the expected place. Any ideas what is going on? This is all the more annoying as I paid to upgrade to 'registered' status yesterday!