UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
How do I stop being frequentkly asked for Licence info?Â
Hi Trevor @woldsweather,
That should not happen after activation of the license on a computer. Which APP version are you using? On which operating system?
Mabula
I have found that changing the amount of RAM in the system automatically causes the license to need re-activating. I found this whilst experimenting some performance issues and was removing and re-adding memory, a better solution would be to record the UUID of the system as this would only change when changing things like the CPU
@mabula-admin Can't get to PC for a few days. Constantly probably not accurate. Maybe once every month or two.
Hi @stastro and @woldsweather,
Okay, yes, the amount of RAM in a computer is used to identify a computer for our license management, so users can use APP on 3 separate computers. Simon, is the UUID a general property of any operating system installation or computer and can any operating system retrieve that property from the computer as far as you know? If so, we can change the computer identification for license management accordingly.
Mabula
Hi @stastro and @woldsweather,
Okay, yes, the amount of RAM in a computer is used to identify a computer for our license management, so users can use APP on 3 separate computers. Simon, is the UUID a general property of any operating system installation or computer and can any operating system retrieve that property from the computer as far as you know? If so, we can change the computer identification for license management accordingly.
Mabula
The UUID would be the operating system (and is generated on a number of factors including date/time), so say for example you have Ubuntu and Windows installed on the same system, each operating system would have its own UUID, and a re-install of the operating system would generate a new UUID. But this would leave you in the following scenarios
1. Windows/Linux Dual boot system wold need a license for Windows and Linux.
2. A re-install would need a re-activation, but this is not an issue as you would not be able to re-use the old one anyway since you re-installed the operating system.
Challenges:
1. If you build a new system, and clone the disk from the old system, the UUID is also cloned, so you could end up running two instances on one license.
2. If you build a new system, and move the boot drive from the old system, no new UUID is generated and would not cause a license issue.
Suggestion:
1. The ability to choose a license slot (1, 2 or 3) when applying the license file, as I have been playing around with CPU and Memory, it ended up clearing the license from my working system, the ability to replace a system in a particular slot would be a good option.
2. The UUID of the operating system could be a good solution, especially if like me, I experiment with different memory configs and CPUs with the same OS installed.
To find the Universal Unique Identifier (UUID) for a Windows installation, you can open an administrator command prompt and type the following command: wmic path win32_computersystemproduct get uuid. I need to find the non WMIC equivalent since WMIC is deprecated in newer versions (24H2), for Ubuntu you would get this from cat /sys/class/dmi/id/product_uuid
3. New UUID - Needs new license
The only problem would be the cloning, but then how many people would actually clone a system and keep both systems running, that's pretty much an outlier right there.
Â
Regards
Simon
Â
