FSUIPC Problem

[kenW]

I re-intalled fs9 on a new PC and then downloaded FSUIPC 3.65. Now fs displays an error about running programs that are not accreditd for aces to an unregistered copy of FUIPC. WHat does this mean??????

[Pete Dowson]

I re-intalled fs9 on a new PC and then downloaded FSUIPC 3.65. Now fs displays an error about running programs that are not accreditd for aces to an unregistered copy of FUIPC. WHat does this mean??????

It means your FSUIPC is not user registered and you are trying to run one or more programs, gauges or modules which are trying to use FSUIPC but which have no access permission.

If you look in the FSUIPC LOG file, which you will find in the FS Modules folder, it will contain more details of the problem. If you want any further help identifying the culprit(s) just show me that.

Regards,

Pete

[kenW]

I will try to end the log file again.. I hope you receive it thi time.

[Pete Dowson]

I will try to end the log file again.. I hope you receive it thi time.

Why not just show me here? It's only a simplw text file. If you keep the FS session short it will be a short log in any case!

Haven't you looked at it yourself? It might be obvious what the problem is.

Pete

[kenW]

Here it is. It appear to have somthing to do with the aircrat air file. Whichever aircraft that is set to the default flight appears in the log file.

********* FSUIPC, Version 3.65 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

15078 System time = 16:54:48

15078 \\KW-GAME\E\Program Files\Microsoft Games\Flight Simulator 9\

15078 System time = 16:54:48, FS2004 time = 12:00:00 (00:00Z)

15281 Client Application: "fs9" (Id=2368)

15281 E:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

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

15281 Company="Microsoft Corporation"

21953 Illegal read attempt: offset 0238, size 3 [P2368]

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

44562 ### IPC Message processed in 22609mSecs ###

104578 FLIGHTS\OTHER\FLTSIM.flt

104672 AIRCRAFT\c172\Cessna172SP.air

105500 Clear All Weather requested: external weather discarded

114047 System time = 16:56:27, FS2004 time = 16:56:20 (23:56Z)

114047 *** FSUIPC log file being closed

Memory managed: 805 Allocs, 805 Freed

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

[Pete Dowson]

Here it is. It appear to have somthing to do with the aircrat air file. Whichever aircraft that is set to the default flight appears in the log file.

FSUIPC always logs details of flights and aircraft loaded.

This part shows the problem:

15281 Client Application: "fs9" (Id=2368)

15281 E:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe

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

15281 Company="Microsoft Corporation"

21953 Illegal read attempt: offset 0238, size 3 [P2368]

The aircraft you have specified in your default flight is using a Gauge which is using FSUIPC completely wrongly. It is using an incorrect access method, which can occasionally work (by fluke) but is inherently dangerous.

The only way to reliably use such a bad gauge is to register FSUIPC as a user (i.e. pay for it), as that allows FSUIPC to bypass these access checks. However, that may not prevent later problems. If you ever have two such bad gauges, or a module doing the same sort of thing, then they will be exchanging data with FSUIPC using the same memory area and they will corrupt each other causing unpredictable results.

Even if this gauge is a freeware one it is not possible for it to use an access key as it is using an illegal access method. Furthermore, it is impossible for me to tell you which gauge it is as the access method makes it look like it is FS9 itself.

Your best bet is to run FS past that point and change to a different aircraft, then save a new default flight.

Then find the culprit aircraft, and its PANEL.CFG file, and see which gauge it may be that is using FSUIPC so wrongly. Edit the panel.CFG to get rid of it. You may have to do this first if you can't get FS past it (because the gauge in question crashes FS, perhaps -- though it doesn't look as if it does).

A more drastic alternative is to delete your FS9.CFG file and let FS build a new one, so it uses its default flights.

Regards,

Pete

[kenW]

Thank you very much for diagnosing the problem!!!

I ran fs9 using three default aircraft - C172,C182 and B737 uing the default flight (Seattle AP takeoff). Same error in all caes. They mut all be using the same default gauge. Any hints which gauge?

Ken

[Pete Dowson]

Thank you very much for diagnosing the problem!!!

I ran fs9 using three default aircraft - C172,C182 and B737 uing the default flight (Seattle AP takeoff). Same error in all caes. They mut all be using the same default gauge. Any hints which gauge?

Erthat certainly sounds very unlikely. Are you really saying that you changed the DEFAULT flight to use these different aircraft and restarted FS each time, and it failed at the start each time?

If so then it is more likely to be a DLL you have added in the Modules folder.

Very few aircraft gauges use FSUIPC -- except in the very sophisticated add-ons. The main type of FSUIPC-using gauge folks add on to the default aircraft are TCAS ones (which should be easy to identify) and, possibly, pushback or fuel control ones. But certainly you would have had to add these yourself to the default aircraft.

It sounds like either you are not changing the default flight -- the one loaded BEFORE you even get to the main menu selection where you can choose another -- or, in fact, you have some add-on DLL which is the culprit.

Pete