FSX WideFS

[dickneuf]

Hello I have FSX and WideFS when i try to connect FSCommander i got the message Unable to connect to Flightsimulator Msg #2, WideFs configuration is ok because FSX see the client.

Both log files seems to be ok

Offcourse all are registered

Thanks for the help

[Pete Dowson]

Hello I have FSX and WideFS when i try to connect FSCommander i got the message Unable to connect to Flightsimulator Msg #2, WideFs configuration is ok because FSX see the client.

Both log files seems to be ok

Offcourse all are registered

I don't know what FSCommander's message "Unable to connect to Flightsimulator Msg #2" means -- you'll need to go to FSCommander support for help on that. But I would like to see both FSUIPC and WideServer logs please. Make sure they are complete -- close FSX down completely before getting the log files. If they are short enough show them here, else ZIP them to petedowson@btconnect.com.

Regards

Pete

[Pete Dowson]

Replying to message sent privately:

I solve the problem

It was my virus scanner NOD32 he also controlled my internet connections.

Its good for you to know because so you can help other people.

Anyway everything’s works fine now and I am a happy man.

Thanks again for your quick reactions, have a nice day.

Thanks for letting us know. I've not heard of NOD32, but it sounds like it is one of those whose hooks disagreee with the way SimConnect works. There seem to be some programs which cause these problems and others which don't. AVG and Norton seem okay for example (I use Norton). Maybe some of these problems will be fixed in the forthcoming SP1 update for FSX. I don't know, but let's hope so. Otherwise I think Microsoft may need to publish a list of incompatible security programs.

Regards

Pete

[quantumleap]

I've not heard of NOD32

It is an anti-virus solution developed by ESET (http://www.eset.com) and performance is far better and system overhead is considerably less than others like Norton.

Note that it is not really a firewall solution and just does things like memory resident and on demand file scanning, in/out email from Outlook via MAPI, Microsoft Office document scanning, and Winsock scanning of HTTP and POP3 traffic.

Now this last element may impact how FSCommander operates, but saying that ...

it sounds like it is one of those whose hooks disagreee with the way SimConnect works.

I use it with no issues on both my Vista 64-bit system running FSX with FSUIPC and WideFS enabled, and on my WideClient connected Win XP system running my own custom applications and things like ActiveSky (I do not run FSCommander though).

Jeff

[Pete Dowson]

Note that it is not really a firewall solution and just does things like memory resident and on demand file scanning, in/out email from Outlook via MAPI, Microsoft Office document scanning, and Winsock scanning of HTTP and POP3 traffic.

I realise that as a virus scanner it is not deliberately blocking TCP/IP communications. But as a virus scanner it is hooking into the TCP/IP stacks in Windows. It seems that SimConnect is very sensitive to how these hooks are placed, or maybe what they do exactly.

Now this last element may impact how FSCommander operates, but saying that ...

No, no. From the logs that were supplied it looked like the main problem was SimConnect being blocked, which affected the TCP/IP stacks and thence WideServer, which never managed to send anything to the Client. FSCommander would have been an innocent bystander. It wouldn't have been anywhere near any of that.

I use it with no issues on both my Vista 64-bit system running FSX with FSUIPC and WideFS enabled, and on my WideClient connected Win XP system running my own custom applications and things like ActiveSky (I do not run FSCommander though).

There must have been something about the way it was set up on dickneuf's system, then, because it seems it definitely clobbered both SimConnect and WideServer (from the logs he supplied by email). I couldn't diagnose what was causing it, but he solved it via NOD32, whether by disabling it or changing some settings I don't know.

Regards

Pete