Allow Virtual Machines on License with TurboFloat Server Key by Default?Answered

Acknowledging the warnings, I'd like to have the license for my low-priced app set to “Allow Virtual Machines" due to increasing conflicts and support issues with buyers who have VM enabled in Windows 11 by default.

I changed the license record to “Allow Virtual Machines,” but now users are getting errors which I can only see to fix by individually editing their license andn selecting “TurboFloat Server key" rather than the default setting "TurboActivate key"."

The risk of customers giving access to my app to others via a Virtual Machine is low. With increasing VM default settings in Windows I'm looking for a simple way to set my licenses so customers can do trials and purchases without VM conflicts on their part and without individual license maintenance on my part. I'm using the standard TurboActivate code in my Xojo app and do not have the tech skills or bandwidth to do customizations.

What is my best easy solution? Thanks!

TurboFloat Server should never be run on a virtual machine.

The TurboFloat Library (used inside your app) can be used inside a virtual machine (or a real machine).

TurboActivate *can* be used in a VM, but it's not recommended.

The defaults are correct. And making it deliberately hard to shoot yourself in the foot is the correct design choice. You can, of course, shoot yourself in the foot; you just have to work for it.

Our API lets you set all of these: limelm.pkey.generate • LimeLM API (wyday.com)

Hi Wyatt. I appreciate the quick response, as well as the very good design and the link. My challenge is that I'm not an experienced developer. That fact, plus its native Windows and Mac executables, is why I wrote my app in Xojo. I used your default Xojo code for TurboActivate in my app and do not have the tech chops to modify it with all the options on your link or the time to learn your platform. I'm getting an increasing number of issues, with trials and purchases, of customers not being able to run my app because Windows 11 has VM enabled by default. I really don't want to shoot myself in the foot, but I need to find a solution. What's my best next step in this situation? I like LimeLM and don't want to have to move to another solution. Thanks much!

, edited
Answer

Well, you can either have the customer disable VMs. Or you can allow VM activations (set it at the version level in LimeLM or per-key).


https://wyday.com/limelm/help/faq/#in-vm

Thanks once again, Wyatt. Having the customer disable VM's is a bit of a showstopper. They get error messages upon purchase and installation, which isn't good, and don't know what to do. That requires contacting me for tech support, a response to their email and a delay.

I'm not even sure if my trial versions work with VM. I just made the change to allow VM activations at the version level, but it looks like it then defaults to hardware lock, which causes another problem for the customer, and which I cannot change the default at the version level of the license.

VM is increasingly defaulted to enabled in Windows 11 configurations, so I need to find a solution in which customers can use my trials and buy my software without running into a bunch of tech support issues, for them and for me.

Any solutions that I can implement (without lots of LimeLM dev skills) are greatly appreciated.

Thanks!

Any solutions that I can implement (without lots of LimeLM dev skills) are greatly appreciated.

Yes:

Or you can allow VM activations (set it at the version level in LimeLM or per-key).

I just recently set the apps to allow VM activations at the version level in LimeLM. I thought that then created a problem with Hardware Locking. Is that not the case? Thanks.

Yes, it can. It’s described in detail in our docs.

You have a few choices:

  1. Tell them to not run in VMs.
  2. Let them run in VMs, but force them to use TurboFloat (which requires you to add that to your app)
  3. Let them run in VMs with TurboActivate and deal with the fallout of that.
, edited
Reply
Discard post