bright, fresh software
Downloads  |  Buy

Using the TurboActivate wizard

TurboActivate wizardThe TurboActivate wizard is an optional executable that you can include with your application. It's an easy to use interface for customers to enter their product key, activate (online activation or offline activation), and extend their trial. It looks like the activation wizard you see when you install Microsoft Office or Windows and it's exceedingly easy to use for even the most inexperienced end-users.

Translate TurboActivate

You can translate the TurboActivate wizard from English to your language by creating, editing, and downloading translations. Then using the translation is as simple as this:

TurboActivate.exe YourLanguage.xml

Translate TurboActivate wizard

Load an alternative TurboActivate.dat file

TurboActivate loads the details about your app from the TurboActivate.dat file sitting in the same directory as the TurboActivate.exe file. You can specify an alternative location by using the --pdets="<filename>" coommandline switch:

TurboActivate.exe --pdets="C:\Loc\To\TurboActivate.dat"

This is equivalent to the PDetsFromPath() function in the TurboActivate API.


TurboActivate uses the proxy settings configured for the computer (see: Proxies in TurboActivate). You can use an alternative proxy by commandline like this:

TurboActivate.exe --proxy="http://username:password@host:port/"

Trial / Product key at userlevel

The TurboActivate wizard uses the "system-wide" activations by default. You can tell the wizard to use "user-wide" activations and trials by using the --userlevel commandline switch:

TurboActivate.exe --userlevel

Extra data

You can also pass extra data that wil be displayed in the LimeLM interface next to an activation.

TurboActivate.exe --extradata="Bob's-PC"

Return codes

The TurboActivate wizard returns 0 for all cases except one. That one case is when TurboActivate exits to focus another running TurboActivate wizard instance. When that happens the return code is "42".

Starting an app after a successful activation

If you're using the TurboActivate wizard as the way users activate your app we recommend launching the TurboActivate.exe file and then waiting around for it to exit. Then, after the TurboActivate wizard has exited, check IsActivated() and continue executing your app based on that value.

However, an alternative to that method is to launch TurboActivate.exe and specify an app to launch after a successful activation.

TurboActivate.exe --startonsuccess="C:\Location\To\Your App.exe"