Author Topic: GSX error befor P3Dv3 finished loading.  (Read 2676 times)

Martyjr

  • Full Member
  • ***
  • Posts: 181
GSX error befor P3Dv3 finished loading.
« on: November 16, 2015, 10:53:22 am »
Old PC failed. It had FSX, P3Dv2.5, FSDT KJFK and GSX.

Got new PC.
Installed and activated my FSTDT KJFKv2 and GSX and working in P3Dv3 for a few weeks now.

Today P3Dv3 start loading and I get message box saying :
FSDT GSX installed but not activated. Do I want to activate it now.
I clicked NO. I figured I would checkit from inside P3Dv3 FSDT menus to see if it was needing re-activation or not.
Then I get another error message eSellerate error -25007 Machine Mismatch.
Now I can only clcik OK.
Now I get another error box ...
And I am basically locked out of using P3Dv3.
At this point P3Dv3 will not continue loading (cannot be started and used e.g. without GSX).

I figured I possibly had some kind of virus.

I shut the PC OFF (power button).

Started PC.
Started P3Dv3 and all ok.

I then checked and my FSDT purchases including GSX are properly activated.

So, what is going on where eSellerate is doing this??

I did screen shots of all this for your reference.

Best Regards,
Vaughan Martell

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: GSX error befor P3Dv3 finished loading.
« Reply #1 on: November 16, 2015, 10:58:00 am »
Nothing you reported is an error or a bug or a problem with Esellarate or GSX. It's likely a problem or a bug with one of your drivers, that for some reason decided to report a new hardware ID. It can also happen when updating the BIOS, depending on the mainboard.

Quote
I clicked NO. I figured I would checkit from inside P3Dv3 FSDT menus to see if it was needing re-activation or not

You simply had to reply YES here, and confirm the activation.

Martyjr

  • Full Member
  • ***
  • Posts: 181
Re: GSX error befor P3Dv3 finished loading.
« Reply #2 on: November 16, 2015, 11:08:08 am »
Thanks for confirming all is OK and the additional information.


I figured I may have had a virus .. never seen anything like that before.

I thought pressing OK might "activate" a possible virus ....
So I tried to error on the side of caution by selecting NO .. which was a choice ...
But that put me in a loop with no way out .. could not load P3Dv3 ... which should not have happened.
That is a problem with this error box sequence.

Best Regards,
Vaughan Martell