Hi everyone, I have an .MSI installer imported into the Paquet Builder, I have tested it is working well and installs well on 64- and 32-bit Windows, I wanted to make sure the installation can only be able to install on one PC. Do I have to make an activation keys system, to be able to activate for each machine (PC) or is there a way to work around this? Let me know, thanks in advance.
You can protect the EXE file made with Paquet Builder with a protector such as Obsidium. This ensures to add licensing capabilities:
This is what we use in Paquet Builder and it is very effective.
Hi, I am new to this , so if I made .exe file with Paquet Builder X86 version which suppose to run on both 32-bit and 64-bit machines, which version am I supposed to buy?
Is this onetime fee for a lifetime? Is this the same thing like a license key per 1 PC, like activation keys system? Does this store PC identify alone with activation key in some kind of database online ?
Can it be integrated within Paquet Builder or do I have to use it outside of it?
I might have more questions later. You can reply to this post.
Let me know, thanks in advance,
Get back thanks.
Do not hesitate to contact Obsidium team for your questions about their protection. You’ll need the 32-bit version of Obsidium to protect x86 packages.
Lifetime licenses but with a fee to upgrade.
You have to use it outside Paquet Builder to protect the EXE file made with Paquet Builder.
I have emailed them, they have not responded so far, do they have live chat? Or phone number which is in Denmark?
AFAIK no live chat. A forum and emails.
I think i will download trial version of 32-bit and and then will probably buy, and then i can use a forum, no doubt.
Thaks so much.
1 Like