FSUIPC 3.911 "too old"

[Luke Kolin]

I have been receiving reports from users that have installed FSUIPC 3.911 that the PMDG MD-11 for FS9 is reporting this version as "too old", and advising them to use 3.81 or above. I've also heard this about the iFly 747 panel.

I don't own the PMDG, but I'm going to test this with the iFly later today. Has anyone else heard about this, or has the latest FSUIPC interim release working with these aircraft?

Cheers!

Luke

[Andydigital]

The MD-11 works fine for me in FSX and FS9 with the registered version of FSUIPC.

[Luke Kolin]

Just to confirm, that's with 3.911? If so, that's great to hear. I loaded the iFLY just now without issues so that's good to hear.

Also makes the mystery more interesting to fix. :)

Cheers!

Luke

[Pete Dowson]

I have been receiving reports from users that have installed FSUIPC 3.911 that the PMDG MD-11 for FS9 is reporting this version as "too old", and advising them to use 3.81 or above. I've also heard this about the iFly 747 panel.

Such reports only occur when users are either using invalid (pirated) registration keys, or ones sold AFTER today's date according to their computer's clock.

Regards

Pete

[Andydigital]

I always use the latest interim versions as posted at the top of this forum.

[Luke Kolin]

Such reports only occur when users are either using invalid (pirated) registration keys, or ones sold AFTER today's date according to their computer's clock.

Thanks, that's helpful to know. Is there any way that this error message can be triggered if no registration key is supplied, and the clock is merely set incorrectly?

Cheers!

Luke

[Pete Dowson]

Is there any way that this error message can be triggered if no registration key is supplied, and the clock is merely set incorrectly?

Not merely from the clock/date being wrong, no. That only matters for Key validity. However, if the code signature on the DLL module is incorrect -- e.g. because the module has been tampered with or infected by a virus -- then it is possible the same problem could occur. A code signature failure will be reported in the FSUIPC LOG, and the user can check by looking at the file properties too.

Otherwise, since it isn't my program reporting the message there's no way I can answer it 100%. It may have an error in its code which compares something against "3911" and decides it is too low for some erroneous reason. But it sounds most unlikely.

Pete