| How to keep license in wine |
Feb 17, 2021 07:43 PM
by boskar
by boskar
Hello,
I'm a Linux/wine Radiant user (that's my primary radiant host).
I own a single license and I try to keep using it there, although I always tried to keep the wineprefix as clean as possible - therefore before any Radiant installation I purged the old one, including old registration data. Moreover, as I try to contribute (occasionaly) to wine appdb/bugzilla, clean wineprefix (preferably created after each wine update) is a must.
I assume some registry keys should be exported and imported to new wine prefix to keep the activation, on the other hand I don't know what other PC properties Radiant rely on, they might be different in new, clean wineprefix.
What do You recommend, apart from using Radiant licensed Radiant in a stable, not updated wineprefix, and keeping experiments, debugging and research in a different sandbox?
I'm a Linux/wine Radiant user (that's my primary radiant host).
I own a single license and I try to keep using it there, although I always tried to keep the wineprefix as clean as possible - therefore before any Radiant installation I purged the old one, including old registration data. Moreover, as I try to contribute (occasionaly) to wine appdb/bugzilla, clean wineprefix (preferably created after each wine update) is a must.
I assume some registry keys should be exported and imported to new wine prefix to keep the activation, on the other hand I don't know what other PC properties Radiant rely on, they might be different in new, clean wineprefix.
What do You recommend, apart from using Radiant licensed Radiant in a stable, not updated wineprefix, and keeping experiments, debugging and research in a different sandbox?
Feb 18, 2021 09:54 PM
by
by
Hi,
The activation code is stored in registry.
If you activate the license as a user, the code goes to HKCU/Software/Medixant/
If an admin account is used to activate RadiAnt, the code goes to HKLM/Software/Medixant/
Activation code is tied to a specific hardware ID (based on RAM, CPU, Network, HDD). So if the hardware configuration reported by Wine to RadiAnt is changed, reactivation will be required.
The activation code is stored in registry.
If you activate the license as a user, the code goes to HKCU/Software/Medixant/
If an admin account is used to activate RadiAnt, the code goes to HKLM/Software/Medixant/
Activation code is tied to a specific hardware ID (based on RAM, CPU, Network, HDD). So if the hardware configuration reported by Wine to RadiAnt is changed, reactivation will be required.
Feb 18, 2021 10:58 PM
by boskar
by boskar
So If I don't change any of the hardware the activation code should remain the same even in clean wineprefix?
I mean - is there any randomness in the code, or it should be regenerated and remain the same at the same hardware, therefore more frequent activation could potentially be possible?
I mean - is there any randomness in the code, or it should be regenerated and remain the same at the same hardware, therefore more frequent activation could potentially be possible?
Feb 22, 2021 06:14 PM
by
by
Yes, if hardware is the same, then the activation can be performed on a clean system without any issues again and again.
Jan 17, 2023 01:21 AM
by Lucio
by Lucio
I bought a 2 year license subscription to Radiant and I am using it in Linux via Wine but now I cannot reactivate it because it gives an error saying that all the seats are active Error 404! Ho do I proceed to unlock my license. I have already deactivated the license on the same computer and it worked the first time now it does not work anymore because I have to wait 89 days to deactivae it again...