FSUIPC error after installing 747dlx.zip file

[jonwoody]

Hi,

I downloaded a freeware update for the 747-400 from Flightsim.com called 747dlx6.zip. Now when I load FS9 and select the 747 in the aircraft menu, an FSUIPC error box appears that says:

FSUIPC access error. One or more programs you are using is not accredited for access to an unregistered copy of FSUIPC. See the FSUIPC.log for details.

You click OK and the 747 loads and flies ok. I only got this message after loading the new zip file. Previously the 747 ran ok.

I have the most recent version of FSUIPC v.3.48 April 2005.

I have attached a copy of my FSUIPC.log as I have no idea what it means.

FYI I use FSUIPC to run ASACARS - a program from a VA - Atlantic Sun Airways. I run windows XP.

Hope you can help.

Jon

[jonwoody]

I don't think the log attached, so I pasted it here:

********* FSUIPC, Version 3.48 by Pete Dowson *********

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=0000B027[0000B027]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=0

3719 System time = 15:31:06

3719 C:\Program Files\Microsoft Games\Flight Simulator 9\

3719 System time = 15:31:06, FS2004 time = 12:00:00 (00:00Z)

5032 FLIGHTS\OTHER\FLTSIM.flt

5078 AIRCRAFT\c172\Cessna172SP.air

5469 Aircraft="Cessna Skyhawk 172SP"

9578 Advanced Weather Interface Enabled

11969 C:\Documents and Settings\Owner\My Documents\Flight Simulator Files\UI generated flight.flt

12141 Clear All Weather requested: external weather discarded

26438 Traffic File #14 = "scenery\world\scenery\traffic030528"

43500 AIRCRAFT\b737_400\Boeing737-400.air

43922 Aircraft="Boeing 737-400"

105891 AIRCRAFT\b747_400\Boeing747-400.air

106313 Aircraft="Boeing 747-400"

115953 Client Application: "fs9" (Id=3852)

115953 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

115953 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

115953 Company="Microsoft Corporation"

115953 Illegal read attempt: offset 0B78, size 4 [P3852]

115953Program or module not accredited for use with this unregistered FSUIPC

157750 ### IPC Message processed in 41797mSecs ###

171094 C:\Documents and Settings\Owner\My Documents\Flight Simulator Files\UI generated flight.flt

171141 AIRCRAFT\c172\Cessna172SP.air

171547 Aircraft="Cessna Skyhawk 172SP"

172797 Clear All Weather requested: external weather discarded

[Pete Dowson]

115953 Client Application: "fs9" (Id=3852)

115953 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

115953 Product="Microsoft Flight Simulator 2004 - A Century of Flight"

115953 Company="Microsoft Corporation"

115953 Illegal read attempt: offset 0B78, size 4 [P3852]

115953Program or module not accredited for use with this unregistered FSUIPC

I'm afraid some Gauge in what you've added to the Aircraft in that update is accessing FSUIPC incorrectly -- i.e. it is badly programmed. Even if it is freeware there is no way I could make an Access key for it, because it is not using a valid interface.

The correct way for gauges to access FSUIPC was defined back in FS2000 days, years ago, and pretty much all such access implemented since then has been correct, so either this must be a very old piece of programming you've just installed, or it is simply badly written more recently.

Unfortunately, because it uses the wrong access method it is impossible for me to identify it precisly. There are two choices here:

1. You find out which Gauge it is by a process of trial and error -- i.e. examine the PANEL.CFG file, then remove each gauge in turn till the culprit is found. Then leave it out, or

2. Purchase a user key for FSUIPC, which will allow all accesses, even bad ones.

The last is slightly risky -- one of the reasons the access method being used is "bad" is that it can cause problems when two or more such internal modules (Gauges or DLLs) try to access FSUIPC in the same way. Because of the way the memory-mapping is done they could corrupt each others data.

Regards,

Pete

[ddawson]

The gauge in question is TC.FuelStatusCG.gau. It does indeed date back to the days of FS98.

While it does seem to work with a registered version of FSUIPC, it will of course not support the fuel tanks which have been defined in newer versions of FS.

Doug

[jonwoody]

I did also notice a page where you list programs and guages and noted another guage requiring a key was f16.gau. I will try Doug's suggestion and the f16.gau by removing them and re-loading. Thanks.

Jon