Hi Al,Inspiration! (on your part)When you said "Whey would you install the simconnect-client (simconnect*.msi) files on you FSX PC? They only need to be installed on the client-PC to talk over the network to your FSX installation." and "Remember, FSX has its own internal simconnect functionality local to that PC. You are installing that functionality remotely on a client-PC with these msi files. It does not matter where you install the SDK. The point is to get at the simconnect.msi installation file (each version) to save and rename them for installation on the client-PC. The SDK is nothing more than a collection of docs, files, and executables. It does not installing anything functional to the FSX environment, so you can install it anywhere to get at the msi files."you made it all so clear.I now have ASX SP2 working with SimConnect SP1a. I shall now try to upgrade to ASX SP3 (thanks a lot, Damian & Carl) and SimConnect SP2. Then I should be in good shape to install SB4 (wait, wait!).To Damian.I think that I would like to make 2 points:1. I would like ASX documentation to have an overview added explaining the installation process in somw words similar to Al's.2. Your ASX SP3 announcement posting in this forum would be greatly improved if you would always fully qualify terms such as 'SP3' so that it is really clear that, in your case, you are referring to ASX SP3. (It's a little late to expect MS to change their product name to 'SimConnect Client for MSFS'). Our environment is now quite confusing, with SPs for everything!Thanks to all for all the help given,Regards, Richard

>Hi Al,>Inspiration! (on your part)>I now have ASX SP2 working with SimConnect SP1a.Very good Richard, glad it works and I could help. I love it when a plan comes together! Sometimes us long-time users need to step-back and remember, not all forum posts are by folks who have have a long history with FS and need some clarification.Regards,

Al,It did help me. I found this post and following the instructions I managed to get things working.

>I just went through this myself last night, after attempting>to reinstall my simconnect facilities on my wide-client PC. >From what I can determine, ASXsp2 needs the exact version of>Simconnect.msi that came with the FSX SDK, SP1(a). What you>must understand is the simconnect.msi that we copy out of the>SDK folder change versions with each SDK update; and I think>ASX is version checking the simconnect facilities installed. >Simconnect installation are cumulative, like .NET Framework>entries, in your Add/Remove Programs table. You need to>install all simconnect.msi versions as you patch forward the>SDK.>> (Very specific order)>Uninstall all SDKs.>Uninstall all simconnect entries from Add/Remove Programs.>Install the SDK from FSX Deluxe DVD.>Copy the simconnect file to safe location and rename>"simconnect_RTM.msi">Install SDK SP1a patch>Copy the simconnect file to a safe location and rename>"simconnect_SP1a.msi"> (If you have FSX-SP2) Install SDK SP2 patch> (If you have FSX-SP2) Copy the simconnect file to a safe>location and rename "simconnect_SP2.msi".>>Now, on the wide-client PC, install all the different version>simconnect files you just saved away, in-order, without>un-installing any of them.>Install simconnect_RTM.msi>Install simconnect_SP1a.msi> (If you have FSX-SP2) Install simconnect_SP2.msi>>You should now have two or three simconnect entries in your>Add/Remove Programs List.>>FWIW, I have not had to change any of the ini/cfg files,>locations, or versions, as described in the ASX Networking>instructions. Once you have had simconnect working over the>network, it seems all the other simconnect configuration files>work over the various versions of the msi file without having>to be changed or patched-foward.>>Hope this helps.Give that man an orange and at the same time pin this thread. This works like a dream. Thanks Al - I really appreciate the work you have put into this.