Hi Everybody

Could anyone help me about that. I have to change my motherboard and after reinstall my licenced PATC2, could not anymore activate.

I mailed with all information to the [email protected], but until yet no sense  (since 27.12.2018)

Thanks for info about that.

9 minutes ago, gsm350 said:

Hi Everybody

Could anyone help me about that. I have to change my motherboard and after reinstall my licenced PATC2, could not anymore activate.

I mailed with all information to the [email protected], but until yet no sense  (since 27.12.2018)

Thanks for info about that.

If you change a processor or motherboard, the DRM software will see your computer as a different computer.  You'll have to contact the developer via a support ticket to resolve.

Best wishes.

EDIT: The way around this is to deactive the license first, and then reactive it after you've made the hardware changes.

 

Edited January 5, 20197 yr by DaveCT2003

Unfortunately pilot2atc is very “strict” with hardware changes. I upgraded from 16 to 32GB ram and that was sufficient to disable the product. A recent health scare for the developer makes me wonder about what contingency plans developers in general make to guard against this issue if they are a one man band.

David.

Just did the same thing...upgraded motherboard and CPU and GPU before Christmas and just getting everything finally set back up.  I did not deactivate my license...original motherboard failed so that wasn't an option.  Anyway I emailed support and have not heard back yet.  I would hope with the cost of P2ATC it would not be a problem to get my license reactivated.  I also provided my new Hardware ID from the installer.  Here's to hoping we both get our licenses back!

I am also waiting for a license re-activation. This is a very cumbersome procedure! In my case, I did not change anything, but merely formatted my machine. No other add-on that I have needs this manual re-activation process!

 

Edited January 6, 20197 yr by GCBraun

I have the same problem because I upgraded to 32 Gb RAM. I hope a positive solution to solve this problem

I think if you send an email with your license information to [email protected] Dave may be able to get this issue resolved.

He is recovering  and is not on the forum but does seem to get to the registration problems when up to it.

FYI.In the tutorial video, this can be prevented if you uninstall pilot2atc before your hardware change or re-install windows.  Planning any significant change doesn't hurt to uninstall/install as a precaution.  I don't know about anyone else but flying without pilot2atc is downright boring.

 

25 minutes ago, tori63 said:

I have the same problem because I upgraded to 32 Gb RAM. I hope a positive solution to solve this problem

What problem?

If one changes hardware, or even overclock the processor, the DRM software will see this as a new computer.  Dev documentation almost always covers this and in the case of PMDG it certainly does and it instructs us to deactivate the license before making such the changes. This way you don't have to involve the developer at all, just reactivate the license after the hardware changes.  As such, there really is not resolution to this.  As stated previously, if you have made hardware changes without first deactivating the license, then you have to go through support to get the license issue resolved.

My very best wishes!

 

I have uninstalled before formatting, but it did not help. In any case, I just got the e-mail confirming that my license was resetted.

Great.  Have a great flight.

3 hours ago, DaveCT2003 said:

What problem?

If one changes hardware, or even overclock the processor, the DRM software will see this as a new computer.  Dev documentation almost always covers this and in the case of PMDG it certainly does and it instructs us to deactivate the license before making such the changes. This way you don't have to involve the developer at all, just reactivate the license after the hardware changes.  As such, there really is not resolution to this.  As stated previously, if you have made hardware changes without first deactivating the license, then you have to go through support to get the license issue resolved. 

My very best wishes!

 

Agreed. But P2A has no deactivation function. An uninstall prior to the change does not work either. It's too strict. If the developer had been laid up for several weeks/months then those users (customers) who needed to reinstall would be unable to do so. There has to be a better way to protect software without customers being inconvenienced or at worse loosing access totally. My PMDG products continue to work after several changes without ever deactivating but I'm guessing this is more a function of the Flexnet product they install to keep their software secure.

Cheers.

40 minutes ago, howevr said:

Agreed. But P2A has no deactivation function. An uninstall prior to the change does not work either. It's too strict. If the developer had been laid up for several weeks/months then those users (customers) who needed to reinstall would be unable to do so. There has to be a better way to protect software without customers being inconvenienced or at worse loosing access totally. My PMDG products continue to work after several changes without ever deactivating but I'm guessing this is more a function of the Flexnet product they install to keep their software secure.

Cheers.

 

Ah-ha!  I wasn't aware of that brother!   Understand, you're right, that needs to be resolved.

Best wishes friends!