Illegal read attempt: offset 0238, size 3 [p1432]

[RetepB]

I have just connected two GoFlight Modules, GF-46 & GF-166 to use in FS2004. I have FSUIPC version 3.60. When FS2004 program loads I get an onscreen message re "one or more programs not accredited for access" One line of the FSUIPC log reads : "Illegal read attempt: offset 0238, size 3 [p1432]" I am told that GoFlight Modules should work with unregistered copy of FSUIPC. Can you advise/help please. I will register my copy of FSUIPC if necessary. Thanks

[Pete Dowson]

I have just connected two GoFlight Modules, GF-46 & GF-166 to use in FS2004. I have FSUIPC version 3.60. When FS2004 program loads I get an onscreen message re "one or more programs not accredited for access" One line of the FSUIPC log reads : "Illegal read attempt: offset 0238, size 3 [p1432]" I am told that GoFlight Modules should work with unregistered copy of FSUIPC.

The GoFlight modules don't use FSUIPC at all as far as I know.

"offset 0238 size 3" is the FS local time (hours, minutes, seconds).

In the FSUIPC log the "P1432" is a reference to a Process which will have been logged shortly before that line -- 1432 is the process "ID". See if that tells you. If it says it is "FS9.exe" then it is a gauge or DLL using FSUIPC incorrectly.

Regards,

Pete

[RetepB]

Thanks very much for your quick respose and info Pete. I did check the log as you suggested and it stated "client application: "fs9" (Id=1432)"

Not sure what that means, but as your respose said FSUIPC should not be involved anyway and as the problem started after downloading and installing the latest GoFlight software to configure the modules, I decided to reinstal using an older version on disk they had also supplied with the modules. ( I had been advised to use their latest download version !) All was OK then, so I will have to download and check out the latest version again.

Thanks once again for your time - PeterB

[Pete Dowson]

TI did check the log as you suggested and it stated "client application: "fs9" (Id=1432)"

Not sure what that means, but as your respose said FSUIPC should not be involved anyway and as the problem started after downloading and installing the latest GoFlight software to configure the modules, I decided to reinstal using an older version on disk they had also supplied with the modules. ( I had been advised to use their latest download version !) All was OK then

Ouch! That does indeed imply that Goflight are using FSUIPC for something.

They haven't approached me about this, so there's no access key issued for their modules. Even if they were to get a key it wouldn't work because they are using an incorrect method to access FSUIPC in the first place -- one which will certainly cause problems with other modules or gauges in due course in any case.

If you were to pay for and register FSUIPC then those modules may work, but if you ever have any other gauge or module using the same incorrect access method they could easily corrupt each other's data (as they would be forced to share the data interchange memory space), probably causing odd problems or even FS crashes.

Please, when you've verified this, do report it to GoFlight support.

Regards,

Pete