 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Bergov Guest
|
Posted: Thu May 12, 2005 6:24 pm Post subject: OnGuard and other protection schemes |
|
|
I have some questions about using OnGuard and some protection schemes.
1. I would like to protect a product with OnGuard and some things seem unclear.
I want to offer the full version with an expire period. The OnGuard component
which deals with this is OgDaysCode. The way it works is however obscure.
For example it seems that the countdown counter must be hidden in registry and
the only safe enough location is somewhere in HKLM. But HKLM may not be
available if the user doesn't have admin rights. Any ideas? Any docs, besides the
original one?
2. When buy the product the client would receive a key to disable the protection.
Is there a simple way to to prevent using the same key on many computers?
3. What strategies work for upgrades? I mean what should I do/use to keep track
of registered users and offer them discounted prices on upgrades?
Thanks everybody
|
|
| Back to top |
|
 |
Jerry Blumenthal Guest
|
Posted: Thu May 12, 2005 7:40 pm Post subject: Re: OnGuard and other protection schemes |
|
|
Bergov wrote:
| Quote: | I have some questions about using OnGuard and some protection schemes.
1. I would like to protect a product with OnGuard and some things seem unclear.
I want to offer the full version with an expire period. The OnGuard component
which deals with this is OgDaysCode. The way it works is however obscure.
For example it seems that the countdown counter must be hidden in registry and
the only safe enough location is somewhere in HKLM. But HKLM may not be
available if the user doesn't have admin rights. Any ideas? Any docs, besides the
original one?
2. When buy the product the client would receive a key to disable the protection.
Is there a simple way to to prevent using the same key on many computers?
3. What strategies work for upgrades? I mean what should I do/use to keep track
of registered users and offer them discounted prices on upgrades?
Thanks everybody
|
Why use any of them? Compile your program with a critical feature that
will be disabled on a certain date. Then, two months before that date
start reminding the person that they will need to purchase an update.
When they buy it, you email them another program, with a diffrent
expiration date.
Using on multiple computers is more difficult; I"ll let others make
those suggestions.
Jerry
|
|
| Back to top |
|
 |
Steve Troxell Guest
|
Posted: Thu May 12, 2005 8:45 pm Post subject: Re: OnGuard and other protection schemes |
|
|
Jerry Blumenthal wrote:
| Quote: | Why use any of them? Compile your program with a critical feature that
will be disabled on a certain date. Then, two months before that date
start reminding the person that they will need to purchase an update.
When they buy it, you email them another program, with a diffrent
expiration date.
|
Which forces customers to pay more money to buy more upgrades otherwise
the investment they already made self-destructs?
Steve
|
|
| Back to top |
|
 |
Andrew Mortlock Guest
|
Posted: Thu May 12, 2005 11:00 pm Post subject: Re: OnGuard and other protection schemes |
|
|
I used TOgDaysCode and TOgRegistrationCode to provide a 30 day trial and
then restrict the use of the program to one computer. The DaysCode
counts down the days and, before that expires, the user contacts you and
you provide the registration key upon payment. (You can extend the time
by a small program to change the base date) The user then enters the key
which is saved for the RegistrationCode to check.
You can hide the counter anywhere you like. It is retrieved in the
OnGetCode event. I split the counter for TOgDaysCode in two and hide
each half in different fields in the database. That way the user can not
take the database to a different computer. The code for
TOgRegistrationCode is placed in the registry Current User.
OnGuard has an option called "Machine modifier" that makes the key
computer specific.
Andrew
Bergov wrote:
| Quote: | I have some questions about using OnGuard and some protection schemes.
1. I would like to protect a product with OnGuard and some things seem unclear.
I want to offer the full version with an expire period. The OnGuard component
which deals with this is OgDaysCode. The way it works is however obscure.
For example it seems that the countdown counter must be hidden in registry and
the only safe enough location is somewhere in HKLM. But HKLM may not be
available if the user doesn't have admin rights. Any ideas? Any docs, besides the
original one?
2. When buy the product the client would receive a key to disable the protection.
Is there a simple way to to prevent using the same key on many computers?
3. What strategies work for upgrades? I mean what should I do/use to keep track
of registered users and offer them discounted prices on upgrades?
Thanks everybody
|
|
|
| Back to top |
|
 |
Jerry Blumenthal Guest
|
Posted: Sat May 21, 2005 7:16 pm Post subject: Re: OnGuard and other protection schemes |
|
|
Steve Troxell wrote:
| Quote: | Jerry Blumenthal wrote:
Why use any of them? Compile your program with a critical feature
that will be disabled on a certain date. Then, two months before that
date start reminding the person that they will need to purchase an
update. When they buy it, you email them another program, with a
diffrent expiration date.
Which forces customers to pay more money to buy more upgrades otherwise
the investment they already made self-destructs?
Steve
|
I'm just describing HOW to do what he wants. Personally, updates to
all of my software have always been free within version.
Jerry
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|