Illegal read attempt for FS9.exe

[seanj]

Hi

I am very confused as to why I would have the following message in the loge file:

temporary flight.flt

462906 Clear All Weather requested: external weather discarded

497063 AIRCRAFT\savajs41-98-2k\SAVAJS41.air

679297 AIRCRAFT\B727-2ANG 2004\b727.air

692031 Client Application: "fs9" (Id=320)

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

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

692047 Company="Microsoft Corporation"

692063 Illegal read attempt: offset 0B78, size 4

692063Program not accredited for use with this unregistered FSUIPC

742422 ### IPC Message processed in 50421mSecs ###

I do not have a register copy.

Regards,

[Pete Dowson]

I am very confused as to why I would have the following message in the loge file:

temporary flight.flt

462906 Clear All Weather requested: external weather discarded

497063 AIRCRAFT\savajs41-98-2k\SAVAJS41.air

679297 AIRCRAFT\B727-2ANG 2004\b727.air

692031 Client Application: "fs9" (Id=320)

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

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

692047 Company="Microsoft Corporation"

692063 Illegal read attempt: offset 0B78, size 4

692063Program not accredited for use with this unregistered FSUIPC

742422 ### IPC Message processed in 50421mSecs ###

I do not have a register copy.

It looks like the aircraft you are loading (B727-2ANG 2004\b727) has a Gauge installed which accesses FSUIPC and has two things wrong with it:

1. It is accessing FSUIPC using the EXTERNAL applications interface, which is why it looks like it is FS2004 which is accessing FSUIPC (the external interface check identifies the PROCESS, which is FS of course).

This access method is wrong and always has been wrong. It is inefficient, it can cause problems with other, more legitimate, gauges and modules attempting to access FSUIPC. I provided a special internal module user library and interface over four years ago.

2. It is not an accredited program, so it hasn't got a key. Moreover, because of its incorrect access method it cannot be granted a key, even if it is FreeWare. There's no way it can be recognised correctly.

The only way you can use it as it stands would be to register FSUIPC yourself. This wouldn't avoid the possibility that its access method won't clash with other add-ins, but it would allow it to work correctly, assuming it is really FS2004-compatible, which looks a little unlikely to be honest.

Oh, there is one other course of action if you prefer. It may only be one gauge in the aircraft which is responsible. If you found it (in the PANEL.CFG file) and stopped it loading, then the rest would probably run okay. As the first access it is making is to the Central Fuel Tank (0B78) I suspect it will be either a fuel gauge or some re-filling or warning system.

Regards,

Pete