How to - limited day trial executable
BlitzMax Forums/BlitzMax Programming/How to - limited day trial executable
| ||
This is not a tutorial LOL, im hoping you can help me. I want to make a BlitzMax limited time trial |
| ||
!!NOTE!! Methods I talked about is Win32 only, and I don't touch Linux/Mac currently. Many people here using Armadillo with good result. Search Armadillo you should see many way to integrate it. I'm using MoleBox + Obsidium, that's about same budget, plus MoleBox has packing abilities. |
| ||
What the better ? Molebox or Obsidium ? |
| ||
It looks a bit amatureish. How does it compare with Armadillo? |
| ||
I only briefly tested EXEPROTECTOR :-) |
| ||
It will be a week or two before I get round to it knowing me |
| ||
The more you worry about piracy the less time you have for writing your next awesome project. ;) |
| ||
. |
| ||
The average (Non-criminal) user won't mess around with assembly to hack your software, like that link shows. |
| ||
True |
| ||
Any standard solution to protect something, will have a standard solution to un-protect it. The best thing is to do a limited (feature-wise) demo - not a time trial, and then just sell the full version on a separated download. Nothing will stop people from copying and distributing serial keys or your full version, so there isnt much you can do about it :( |
| ||
what about something like this? have the demo not contain all the needed data or even just have a different exe. then instead of sending a key when payment arrives, have the demo patch itself or just send the buyer a new package. you could even set it up to compile a new "personal" (keyed (hidden)) exe for every purchase... the only time it's hacker proof is when it's free. |
| ||
you can de-protect most commerical protections like armillido |
| ||
Perhaps I should use the shareware maker |
| ||
I actually like the feature restricted approach myself. But I can understand and see why you'd want to make it the time based trial ware. One download, and a registration vs two downloads and a registration. I haven't gotten (yet) to the point where I need to concern myself with this type of stuff, so I appreciate the efforts you are making now, and to all those posting for their input. |
| ||
The nature of my particular program is that restricting features could be determental. Thanks. |