Pete Dowson

Phew! Thank goodness for that! Thanks for letting me know! Regards Pete

FSUIPC is not a "process" so it cannot know anything about FSUIPC. What is crashing is SimConnect, which is loading and talking to FSUIPC via TCP/IP. All this is part of FSX -- the process is called FSX.EXE, nothing to do with FSUIPC. There is no way FSUIPC needs any "permission". It doesn't use anything which needs permission, and in any case it is not running because your "Panda" program is preventing FSX from running it! Please do read things more carefully. I'm sure you are continuing to misunderstand this. Pete

What exactly says "non-aircraft"? My code does check for and accept SIMCONNECT_SIMOBJECT_TYPE_AIRCRAFT and SIMCONNECT_SIMOBJECT_TYPE_HELICOPTER so if they aren't getting through to me with those checks they must somehow be provided as something else. The only other types listed are: SIMCONNECT_SIMOBJECT_TYPE_BOAT SIMCONNECT_SIMOBJECT_TYPE_GROUND and I eliminate those for obvious reasons. It'll be the user object ID. I've no idea what is going on there -- I've made no changes at all. Maybe MS have included a new bug -- or they've added some sort of "autotrim" mechanism? I'll have a look when I can, but it'll be in about two weeks' time -- I've got a load on here then I'm off for a week. I have made a note to check into it. Meanwhile if you can collect any more specific data it may be useful. Regards Pete

When you right-click on any program icon or short cut the menu should certainly include a "Run as administrator" option -- unless perhaps you are not even an administrator when you logged on? I don't know about that case, but on WinXP you had to log off and log back on again using the admin account. Obviously if your Vista is not the English language version it will say something dfferent. There's a lot of things you are prevented from doing on Vista unless you can be an administrator on occasion! Regards Pete

There is no minimum for WideClient. As long as the machine supports Windows 98 or later and is networking okay. The need for any power, memory, and so on is for whatever programs you want to run on top. Regards Pete

I've not heard of that one. but I do know that FSX (Simconnect in particular) doesn't get on very well with several virus and firewall programs. Even when they don't actually crash it they slow it down or make it fail in some other way. I use Norton. its antivirus seems okay, and both its firewall and the default Windows XP firewall are okay. But Norton isn't cheap and it is a bit on the 'heavy' side (lots of it). You are forgetting, FSUIPC4 isn't even getting to run! The problem you have is actually stopping SimConnect from running properly -- it is SimConnect which is crashing. SimConnect is part of FSX, so the actual program you need to give full permissions to is FSX.EXE. Please, send a full report of your problems, including the full name and version of the "Panada" program, to Microsoft at tell_fs@microsoft.com, so they can add it to their list of security programs to either deal with or warn folks about. Then, if you want to carry on, if you cannot find a way around it I can only suggest not using that program, at least not when you want to use FSX. Regards Pete

Well, if you are starting completely from scratch I would say the correct order would be: FSX SDK from DVD which brings you to original release state, then SP1 SDK SP1A update which brings you up to date. FSUIPC4 install would come last, as for any other add-ons. Like all add-ons, at the end. But maybe before FSUIPC4, so that the DLL.XML file will be fixed by that. Also bear in mind that the TrafficExplorer.DLL supplied with the original MyTrafficX is the old one. You'd be better off enabling the newer one, installed by the SDK SP1A update -- but for that you'll need to edit the DLL.XML file to enable it, and to check that it has the correct path. Regards Pete

Is that version of FSInn and FSCopilot specifically designed for FSX with the SP1 update? If not I suggest you wait until a suitable version is available. It sounds like something it is doing is wrecking something. If you are using versions updated for SP1, could you try getting a SimConnect log file please (see the FSX Help announcement). I'd like to see how the PFCFSX.DLL manages to load and run without a menu when it is FSUIPC4 which loads and runs it and adds the menu. I'm wondering if we've discovered another, or a new, SimConnect bug. Regards Pete

That one is not relevant. It is not used. That is the one FSX will use. This shows that you have installed the SDK from the FSX DVDs. You do need to update that -- download and install the SP1A update to the SDK. You have made the mistake of only partially updating FSX to SP1. If you install both FSX and its SDK you should update both when you update either. Regards Pete

Ah, that's a standard error message window. Error 2 is simply file not found. Though why FSX should close I've no idea. I'll check that here. Are you absolutely sure that file is there, in that folder? Regards Pete

Okay, that all looks fine. I take it this log is from an occasion where FSX was not "prevented from opening"? Can you expand upon what you actually mean by this The term "error tablet" isn't one I'm familiar with, and I don't really know how FSX is not "opening". What actually happens? Have you an FSUIPC4.LOG from such an event? Oh, also, can I see the FSUIPC4.INI file please? Regards Pete

What version of FSUIPC4? Any Log files to show? Pete

Ah. At last some useful information! In that case FSUIPC4 is not even loading. It cannot possibly crash FSX. Something else is crashing FSX. Find this file DLL.XML in C:\Documents and Settings\Miguel\Datos de programa\Microsoft\FSX and show that to me. It must exist because it is trying to load your (incorrect version) TrafficToolbox.dll. Pete

Okaylooking more closely at the message: that DLL wasn't loaded in any case. But the fact that it says 60905 is a "mismatch" indicates that the original SimConnect is not correctly installed. It should try to load it as both the original Simconnect and the new SP1 one should both be there. Can you please look again at the SimConnect log file -- if it even TRIES to load FSUIPC there will be a message there. If there isn't, then it isn't even getting that far. Have you got FSX Deluxe? If so, did you install the SDK? If so, did you remember to update that with the SP1A update after you installed SP1? If not then it is probably one of the other DLLs used by FSX. Please also see these points I mentioned beforte, but you appear to be ignoring still: 2. If not, then it sounds as if SimConnect is corrupted on your system. In that case, please see the Announcement entitled " FSX HELP: Logging or Re-installing SimConnect", and try re-installing Simconnect. 3a. First, I need to know if there is actually an FSUIPC4.LOG file in your FSX modules folder. If so, show it to me please. It is coming to the point that I shall have to ask you to contact Microsoft Technical Support instead of dealing with me, as I evidently cannot help you despite trying very hard. Your FSX installation, especially the SimConnect part, is in disarray. If you cannot follow the instructions I try to give to help, I think you will have to start again or get Microsoft to sort it out for you. Regards Pete

Aha! This is why your FSX is crashing. It is nothing whatsoever to do with FSUIPC at all! It is because you have previously installed MyTraffic and its "TrafficToolBox" which I think is from the original Microsoft SDK -- if so I don't think it is compatible with SP1. You will need to go to your "MyTraffic" folder and delete the traffictoolbox.dll. Or go to MyTraffic support and get help there. There was a new DLL included with the SDK SP1A update, but you need FSX Deluxe for that. Regards Pete

You are too quick for me! I edited the message after you read it. Please check this part and let me know, please: ============================= Actually, I also thought that this local had to be changed to global for a remote connection? Do you find your remote application works with that set to "local" still? If you had set it to "Global" then installing FSUIPC4 (using my installer) would have actually fixed your XML file for you, as it looks for a "local" section and if it isn't present it adds one for you. If keeping "local" in works for remote clients, then it seems I'll have to make even more checks in the InstallerPlease let me know! Regards Pete

If it was going completely to sleep it could cause FSUIPC to timeout and re-connect, so it can't be, really. At least not completely. Is this some other code, not using FSUIPC? If so, possibly it is using the non-MP ID of the User Aircraft to read the data. I think the ID is 1 normally, but it could be anything, apparently, when MP mode is started. This is what caused the problem in FSUIPC 4.102 that I got you to try earlier. I always actually asked SimConnect for the ID, and used the one which was returned. Before SP1, because enterring MP mode cut off SimConnect data and FSUIPC4 re-copnnected, it asked for the ID again, so, once reconnected, it worked okay. With the fix in SP1 it wasn't reconnecting initially, so used the wrong ID. There's a note about this in the SDK which isn't terribly prominent: Please do check that FSUIPC4 is getting the aircraft location in MP first, just to be sure. Run TrafficLook, for example -- the User aircraft position is in the first line listed. Regards Pete

The only modifications I made to this file are the 192.168.0.3 500 Any advice you can offer would be much appreciated. Easy. The XML file stops SimConnect service altogether on the FSX PC, and only supports remote PCs. You need to retain the XML file exactly as supplied and ADD a new section for your remote connection. The part from to <\SimConnect.Comm> needs to be intact, as it was. Add another copy to modify for your remote use. Actually, I also thought that this local had to be changed to global for a remote connection? Do you find your remote application works with that set to "local" still? If you had set it to "Global" then installing FSUIPC4 (using my installer) would have actually fixed your XML file for you, as it looks for a "local" section and if it isn't present it adds one for you. If keeping "local" in works for remote clients, then it seems I'll have to make even more checks in the InstallerPlease let me know! Regards Pete

No! That is the Install Log, from the installer. The FSUIPC log is called FSUIPC4.LOG, as I said: And that was step 3a. What happened to steps 1 and 2? You are not reading what I write, again! :-( Pete

Okay. Good. In that case the original SimConnect (not the SP1 version) was broken, and you fixed it. It shouldn't, according to other wise folks who have told me that it won't undo the new additions, only replace missing parts or any looking older than they should. But do get back and tell me if you find anything wrong. If so I'll need to get advice on how to repair things safely with SP1 installed. At least the newer (SP1) version of SimConnect is still okay, and working, as these lines in the Log show: Regards Pete

Sorry, I thought I was just explaining it clearly, not boxing any ears. :-( Pete

I assume, because you haven't supplied it, that you aren't getting an FSUIPC4.LOG file produced in the FSX Modules folder? If you are, then that's the first place to check. It may indicate a firewall or other similar problem, or a problem only with the SP1 install of Simconnect. If you aren't getting a Log, then FSUIPC4 simply is not being loaded. In this case it looks very much like the "usual" problem -- SimConnect just hasn't installed correctly. I say "usual", but in actual fact, although it seems to be the commonest SimConnect problem, it doesn't seem to affect a very significant proportion of folks. This is probably why it still isn't fixed -- I have never been able to reproduce it on any of 4 different systems, and neither has MS. The steps you can take are: 1. First get a SimConnect log, as described in the FSX help announcement. 2. Then try repairing SimConnect, also as described in the FSX help announcement. Note that the latter only repairs the original SimConnect, but this is the one used to load FSUIPC4 and run it. If the SP1 version of SimConnect is broken, that may allow FSUIPC4 to load, but then fail -- the FSUIPC4.LOG would show that. At present I am not sure how you would go about repairing an SP1 installation. Just uninstalling it and re-installing it doesn't help with the Windows Side-by-Side installs. I suspect you'd need to delete the second SimConnect WinSxS folder as well as the one mentioned in FSX Help. I'm awaiting advice on this from MS. Regards Pete

Okayit is a SimConnect bug. Please follow my other suggestions. I am repeating myself here as you seem not to be reading everything I'm telling you: 1. Please read the Announcement above entitled "Important FSUIPC4 Installation Notes". Does this describe what you see? If so, please try to do what it says. 2. If not, then it sounds as if SimConnect is corrupted on your system. In that case, please see the Announcement entitled " FSX HELP: Logging or Re-installing SimConnect", and try re-installing Simconnect. 3. I can help get the proper Microsoft help to sort your problems out, but I need more information. 3a. First, I need to know if there is actually an FSUIPC4.LOG file in your FSX modules folder. If so, show it to me please. 3b. Second, you need to make SimConnect produce a log, so we can see what is going wrong during the load sequence. How to do this is also explained in the Announcement " FSX HELP: Logging or Re-installing SimConnect". Pete

Please read the section in the WideFS documentation entitled "What’s this about UDP?". It is exactly this question that I address there. Regards Pete

What does that mean? You haven't got a problem or you don't care about it? Sorry, but nothing is making any sense yet. Don't you care to explain anything? Pete