I run FSX (SP2) on a very fast, two month old Windows 7 Home Premium (32 bit) machine. The FSX SDK SP2 is also installed on it.I used to run ActiveSky X over my home LAN on a Compaq notebook SimConnect client which ran with Windows XP (home edition), without any problems. That notebook died just over a week ago :( . It's been replaced with a new Compaq notebook that came with Windows 7 Home Premium 64 bit installed. On that new Compaq, I installed SimConnect as a client, in accordance with the instructions in the ASX documentation. Then I installed ASX and all service packs. But now whenever I try to load ASX, I'm getting the dreaded "Simconnect SP1 managed version was not found to be correctly installed on this system..." message during startup.The weird thing about this is that on my old XP Compaq notebook as SimConnect client, ASX worked flawlessly over the LAN. In addition, today I installed SimConnect as per instructions, followed by ASX and all service packs, on my wife's PC which runs Vista Home Premium (32 bit) - and from this SimConnect client ASX connected immediately to my FSX over the LAN ! This has got me beat :( Another thing that happened when I installed ASX on the new notebook, is that when I specified the location of the FSX and AppData folders (which are found on the network on the server PC, of course) on first running ASX, I was asked for a username and password. Just typed in my username and hit Enter and the connection was made. But this did not happen when I installed ASX on my wife's PC. I did not put any passwords on the FSX PC anyway.It must be something to do with my new notebook. Are there any known issues when running SimConnect client under Windows 7 Home Premium 64 bit ? Or is there anything else I could try on my new notebook ? Would the username/password request have something to do with it ? Any help much appreciated.Thanks,Emile.

I may be wrong, but SimConnect is installed on your computer when you install FSX. Each 'patch' of FSX installs a new WinSxS version of the SimConnect DLL. This is a 32-bit unmanaged file that connects other apps to FSX.Why is the ASX app looking for the managed Simconnect DLL file from the SDK SP1? Those are only useful for creating a .NET application, not for running one.The Owl's Nest Downloads site has the ADE9X environment checker program:ADE9X Environment Checker SetupRunning that would indicate if you are set for Simconnect properly.Dick

I may be wrong, but SimConnect is installed on your computer when you install FSX. Each 'patch' of FSX installs a new WinSxS version of the SimConnect DLL. This is a 32-bit unmanaged file that connects other apps to FSX.

Yes that's correct AFAIK. For example, FSInn communicates with FSX through SimConnect and I didn't need to do anything with SimConnect to get FSInn to work (runs on the same PC as FSX). I take it from there that SimConnect is installed with FSX.

Why is the ASX app looking for the managed Simconnect DLL file from the SDK SP1? Those are only useful for creating a .NET application, not for running one.

Your guess is as good as mine :( . I'm not a programmer. But I AM trying to run ASX on a notebook over the LAN, NOT on the PC that FSX is installed on, maybe that's why. The ASX documentation has clearly defined steps to follow on the FSX "server" as well as the client PC in order to get ASX to communicate with FSX on the other PC. This includes running a file called simconnect.msi on each client PC. Now, this file is found in one of the installed SDK subfolders and copied to the client PC where it is then run to install SimConnect on the client. After running it on my 64 bit notebook, SimConnect Client does appear in the list of installed programs. Yet ASX still gives me a warning. But it DOES/DID run on two other client PCs set up in EXACTLY the same way, that's what gets me. Why not on the notebook - because it has a 64 bit OS ?

The Owl's Nest Downloads site has the ADE9X environment checker program:ADE9X Environment Checker SetupRunning that would indicate if you are set for Simconnect properly.

Got that, installed it, and it all looks OK (see attached screen capture from the FSX PC). Am I supposed to run this from the client notebook as well ?Thanks,Emile.

Hi Emile.Ok, I do understand now.I would try to run the owl's nest app on the notebook, and see what it does... hopefully it will tell you that SimConnect is installed.Dick

I would try to run the owl's nest app on the notebook, and see what it does... hopefully it will tell you that SimConnect is installed.

Hi Dick,I installed and ran ADE Environment Checker on both my wife's PC (where ASX works fine via SimConnect) and on my new notebook (where ASX doesn't want to know). The check results were different alright. On my wife's PC (named KERRYS), I could locate FSX OK over the LAN and the checker output shows the path correctly. On my new notebook (named FLIGHTDECK2), I could locate FSX over the LAN but once done, the checker did not seem to be able to store the path - version and install path boxes remained red. No wonder then, I guess, that ASX is confused !I attach screen captures of ADE Environment Checker from both computers. Hopefully you can make some sense out of it.Oh and BTW, I just installed Pete Dowson's WideClient on the new notebook, and that DOES work - at least one thing to smile about :( Cheers,Emile.

I take it, then, that no-one here has an idea what could cause the problem I posted ?Ah well, worth a try.Perhaps I'd be better to post it on the Active Sky forums.Thanks anyway, Dick - I appreciate your replies.I'm curious as to the background of your rather unique handle ?

Simconnect SP1 managed version was not found to be correctly installed on this system...

And the ADE Checker shows that SP2/Acc version is on that computer... but not SP1 of SimConnect, nor the RTM Simconnect. So you may have followed the instructions, but used SP2 rather than SP1.Dick