Almost unbeatable evaluation period thingy!!

[I_R_Lee]

If anyone is making software and putting out an evaluation version, here's something I figured out on how to store uses etc.

Put this code in the form load event:

If Var1 < Var2 Then
Var1 = Var2
ElseIf Var2 < Var1 Then
Var2 = Var1
End If
Var1 = Registry.ClassesRoot.GetValue([i]KeyName[/i], 1)
Registry.ClassesRoot.CreateSubKey([i]KeyName[/i])
Registry.ClassesRoot.SetValue([i]KeyName[/i], Var1 + 1)
Var2 = Registry.ClassesRoot.GetValue([i]Key2Name[/i], 1)
Registry.ClassesRoot.CreateSubKey([i]Key2Name[/i])
Registry.ClassesRoot.SetValue([i]Key2Name[/i], Var2 + 1)
If Var1 >= [i]Limit[/i] Or Var2 >= [i]Limit[/i] Then
MsgBox("Your time is up!")
End
End If

But make sure you put this code:

Imports Microsoft.Win32

RIGHT at the top of all of your code.

 

I haven't found a way to beat it yet. Also, make sure you store the keys in some strange place and give them a name that has NOTHING to do with your program name, but so they fit in with the surrounding keys.

 

Hope this helps!

[Volte]

First of all, storing things in the registry is very beatable... just change

the values or delete them.

 

Second of all, "hiding" things in the registry is not good at all. I want

to know exactly where every key in my registry is there and why.

Not to mention programs like RegMon that can monitor this stuff.

 

Easy stuff.

 

There really is no way of completely unbeatable evaluation period

thing. The most effective way of evaluating software is crippling it.

[I_R_Lee]

No, deleting or renaming the keys won't break it, because the values are stored elsewhere, I don't know where, but they are, and the keys are recreated when the program starts up. And you can't (without tools) delete or change the values, because they aren't visible.