Jump to content

v4-07 No Addon Visible - Despite Firewall /Anti-Virus Unin.


 Share

Recommended Posts

I have read and acted on the various bits of information in readme files and on the web but... my problem still exists in that I do not see the 'Addon' in FSX menu.

I have taken following actions after the installation reports that the installation of FSUIPC v4.07 (latest) was OK...

1) placed FSX as a trusted item in the Norton Firewall settings (no difference)

2) reinstalled FSUIPC (no change)

3) uninstalled Symantec Firewall (no change)

4) Uninstalled Symantec Anti-virus (no change)

5) uninstalled all Symantec software [systemworks 2006] (no change)

6) disabled Windows firewall (no change)

Here is the readout from the FSUIPC log file

********* FSUIPC4, Version 4.070 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC Key is provided

WideFS Key is provided

Running inside FSX

Module base=61000000

LogOptions=00000001

DebugStatus=255

60 System time = 09:32:17

60 FLT UNC path = "C:\Documents and Settings\Dave\My Documents\Flight Simulator X Files\"

60 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

1783 SimConnect_Open succeeded: proceeding to initialise interface!

73085 Failed on SimConnect_CallDispatch for Message, return = 0xC000020D

134444 **** No SimConnect events or states being received! Re-connecting now****

134444 SimConnect_Open succeeded: proceeding to initialise interface!

139992 Failed on SimConnect_CallDispatch for Message, return = 0xC000020D

145640 System time = 09:34:43

145640 *** FSUIPC log file being closed

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

FSUIPC is a trusted item within the FSX and is enabled in the dll.xml - here is the readout for this file:-

***************************************

Launch

dll.xml

False

False

Object Placement Tool

True

False

..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll

Traffic Toolbox

True

False

..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll

Visual Effects Tool

True

False

..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll

Traffic Toolbox

False

False

MyTraffic\traffictoolbox.dll

FSUIPC 4

False

Modules\FSUIPC4.dll

*************************************

Your assistance appreciated as I can't run any map, weather external programs that need FSUIPC (oh I have the registered version).

Operating system is WinXP Pro.

Many thanks.

Link to comment
Share on other sites

1) placed FSX as a trusted item in the Norton Firewall settings (no difference)

2) reinstalled FSUIPC (no change)

3) uninstalled Symantec Firewall (no change)

4) Uninstalled Symantec Anti-virus (no change)

5) uninstalled all Symantec software [systemworks 2006] (no change)

6) disabled Windows firewall (no change)

Good grief! You had three Firewalls set up? You are very worried about invasion? ;-).

Or is "Symantec Firewall" the same as "Norton Firewall"?

Here is the readout from the FSUIPC log file

...

1783 SimConnect_Open succeeded: proceeding to initialise interface!

73085 Failed on SimConnect_CallDispatch for Message, return = 0xC000020D

134444 **** No SimConnect events or states being received! Re-connecting now****

134444 SimConnect_Open succeeded: proceeding to initialise interface!

139992 Failed on SimConnect_CallDispatch for Message, return = 0xC000020D

I've not seen this error before, but I am sure Microsoft will be interested. If you check the "FSX Help" Announcement above, it tells you how to get a Simconnect Log file. If you can do that, please, then send your error report (exactly as you have said here) along with both the FSUIPC4.LOG and the SimConnect LOG to tell_fs@microsoft.com , that will be the best way to get this fixed. I just hope it is in time to allow them to find and fix it before the expected FSX update.

Also, try re-installing SimConnect, as suggested in the FSX Help Announcement.

I'm afraid there is nothing I can do to fix SimConnect problems -- if re-installing doesn't work we are wholly dependent upon Microsoft I'm afraid.

Regards

Pete

Link to comment
Share on other sites

Thanks Peter - I have sent the information to the microsoft guru's as requested today. for what it may be worth here is the Simconnect log file printout:-

QUOTE

0.00000 SimConnect version 0x00000002

0.30325 DLL Loaded: Path="MyTraffic\traffictoolbox.dll" Version="10.0.60905.0"

0.33720 Panels data export found and set to 20A41990

2.10512 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.0.7.0"

74.31744 [63] Inactive!

140.06149 [63] Inactive!

170.14046 [63] Inactive!

UNQUOTE

Yes Symantec = Norton, I'm security minded but not quite that crazy :)

Thanks again will try a reinstall of Simconnect later and revert...

Link to comment
Share on other sites

Hi Jim,

Nice to hear from you again. The tip appreciated but I had taken the rather unusual step of uninstalling the AV and all FW's before attempting to reinstall SC - I regard my simulator as more important!.

Actually I'm sat out in West Africa on my lap-top and not connected to the outside world on that machine so the AV is not so important (at the moment).

The good news is that I tried the sim again today and hey-presto! the addon menu is there!. I just hope it continues that way.

Take care - and I'll be back amongst the real weather on my main machine when I get back to the UK - thanks to Peter Dowson and Active Sky.

Thanks again and keep in touch.

Capt. Dave D.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.