undoing TA_SYSTEM / TA_USER selection

Is this the intended behaviour?

Yes, because TA_SYSTEM is always the preferred (and best) way to save the activation data. Why? Because the activation data is per-machine already. So another user on the same machine can use the same product key to activate the app and it will still use that single activation.

If you want to do per-user licensing then use TurboFloat. That's what it's designed for.

I would like a way of undoing this mostly for testing purposes, but also because it is usually polite for an uninstaller to undo everything that the installer did, which seems not to be the case here.

Calling Deactivate(1), and making sure it succeeds, will set the files to be 0-bytes. Therefore virtually no hard drive space will be taken up by the files.

>Yes, because TA_SYSTEM is always the preferred (and best) way to save the activation data. Ok, we were thinking of adding an option for the user to choose, but you are saying we should always try TA_SYSTEM and only if that fails go with TA_USER. Then as long as the user has enough permissions when activating it will automatically do all users.

>Calling Deactivate(1), and making sure it succeeds, will set the files to be 0-bytes. Therefore virtually no hard drive space will be taken up by the files.Well it's not really a question of space, but it makes it difficult to test the TA_USER setting if I cannot get back to it once I have run once with TA_SYSTEM.

Regards,Robin

Ok, we were thinking of adding an option for the user to choose, but you are saying we should always try TA_SYSTEM and only if that fails go with TA_USER. Then as long as the user has enough permissions when activating it will automatically do all users.

Yes. Or, just not give the TA_USER option. Instead make sure your installer has admin permissions, call TA_SYSTEM and set it up for good for the user.

Well it's not really a question of space, but it makes it difficult to test the TA_USER setting if I cannot get back to it once I have run once with TA_SYSTEM.

We don't currently have a way to reset it. One way to test it would be to create a VM, make a copy of it that you can revert back to, then do any tests you want.