Printable View
One the application first started you needed to add a expiration date into the registry. Everytime your program runs it checks this date and if the date has passed then create a function to open your .EXE and change the first byte from M to Z and save your program. This change will corrupt your program, so when they call you to fix this just bring your trusty Hex editor change the byte back.
Open the .exe and put some weird chr in it...it will not work anymore :D
*Gasps* You don't know what fusion is?
Basicly, it's a powerful checksum, UPX/Asprotect, and you can make standalone vb5/6 exe's :D
It includes any dll/ocx you want in the binary, and it's extracted into the system directory (You can change that if you want) when the program is run...
http://www.bit-arts.com/downloads.html
Thx for the link :)
But i think it's like Inno package maker
Havent looked at the rest of this thread, but a way to screw the program:
Have a .dat file contain some info necessary to the program, and then a copy of the program (slightly modified:D). When the day that you want the screwing to happen, have the program open the .dat file, and extract the modified program from it. Then set a hard to find setting in the registry. Then shell a dynamically created bat file that deletes the .dat file, and replaces the good program with the extracted one. The extracted one has all the same code, but two extra functions. One would check to see if the .dat file is present, and if not, spur a wierd looking error. If the .dat file is present, it continuously makes random wierd errors.
A scenario for the user:
DingDing Ding!!!!!!!! Time's up!!
[computer whirs for a bit; program shuts down and opens again]
"ERROR 193: Illegal Jumping to Call 'je' on offset 0x027c892"
User says, "Hmmmm I wonder what that could be?" He calls up the programmer (you) and asks what the error means. You tell him to check if hes has the .dat file. He for some mysterious reason doesnt. :rolleyes: So, you charge him a (large) fee to replace it. User thinks all it well and runs the program again:
"ERROR X: [Random error msg here]"
And that happens each time you open it consequently.
Remember I said to have the good program set something in the registry? Make the program also not run if that setting is there. So when they try to reinstall it, that wont work either :D
What's inno package maker?Quote:
Originally posted by DaoK
Thx for the link :)
But i think it's like Inno package maker
Something who put all DLL and OCX and EXE in 1 file.
what's the site for it?
I do not know, I reformated and lost the link and program, I will need to search it again :(
No idea....
Yeah....Secure-It! 2002 SP1 will solve A LOT of problems!:D;)