Pss777

[Jim Harnes]

Am getting FS crashes to a black screen and system lock up with the new Pss777 release candidate and registered copy of FSUPIC. Following is from FSUPIC log:

40704 Module [M7] identified = "PSS-B777.GAU"

40704 Module [M7] "PSS-777.gau" access registration is invalid

Pss state the gauge is registered for FSUPIC access. Please advise if that is correct. If the gauge is not registered for FSUPIC access, could this cause the FS and system crashes?

Thanks for your help.

Jim Harnes

[Pete Dowson]

Am getting FS crashes to a black screen and system lock up with the new Pss777 release candidate and registered copy of FSUPIC. Following is from FSUPIC log:

40704 Module [M7] identified = "PSS-B777.GAU"

40704 Module [M7] "PSS-777.gau" access registration is invalid

Pss state the gauge is registered for FSUPIC access. Please advise if that is correct.

Look again at that pair of messages. The Module is called "PSS-B777.gau" but it is attempting to register itself as "PSS-777.gau". Do you see that the "B" is missing? PSS have not requested registration for a PSS-777 gauge at all, and in any case the name in the access request MUST match the name of the Gauge.

You need to report this to them. Haven't they tested such small matters before Release Candidate stage?

If the gauge is not registered for FSUPIC access, could this cause the FS and system crashes?s

That is entirely dependent upon the code in PSS's gauge. Certainly there is nothing in FSUIPC which would do that.

However, you also say that your FSUIPC is user registered? If so then it makes no difference whatsoever whether the gauge is registered for access of not. Your subscription for FSUIPC covers access for everything. Although FSUIPC will log the details, to aid in development and debugging, it will not prevent full access to a user-registered install.

Seems you need to report this to PSS and get the 777 fixed before user release! ;-)

Regards,

Pete

[Jim Harnes]

Thanks! Attention to detail . . . :)

Jim Harnes