Hello everyone,

I am just looking for ideas on how I can implement a demo version of my program which will be available in unix environment (solaris and linux).

So what I have in mind is to either implement a limited-time version (trial version expires after 30 days) or a limited-number version (trial version expires after the program has ran for 'x' number of times)

Can anyone please give any idea on how any of this this can be implemented ?

The simplest strategy I can think of is to store a number (for e.g: the date or a count) in a file when the program is run for the first time and then on each subsequent run, read this number and, lets say if its a date, then compare it with the current date.

But then I ran into issues like, where can I store this file? (I want the strategy atleast a little secure, so that it is not very obvious to everyone to go ahead and delete this file whenever the trial version expires) ? Is it possible the program does not have write permission ? Is there any kind of a registry in unix where I can store key, value pairs ?

(Actually, I am not so much concerned about crackers being able to break the demo version, it just should not be too obvious)

Please, just throw in whatever ideas you have.

Thanks !!

The program should not be time limited on a particular system, but should be time limited for a particular user.

And, I guess I can atleast make the file which stores the date a hidden file.

If you are planning to release the code of your program to the rest of the world, then a demo version is redundant. If not, then you can generate a key when the program is installed and store it in some file. You can check for that file's checksum and timestamps when the file is written to and then on subsequent runs, your program should check the file and refuse to run if the checksum/size or the timestamp changes in any way.

For a user, it would be a bit more complicated, but you could go along similar lines.

If you host an ftp server you could publish a version which is recompiled everyday with a datestamp in the source code.

Hmm.. interesting post.

Since you are absolutely fine with the hidden file approach, why not make it as part of the config file, if you have any. That is, put in an encrypted (perhaps XOR encryption) form of the initial date when the app ran for the first time. Everytime you start the app, you will look at that date and then decide on the expiration message. Likewise with the number of trials. In this case, you will update it accordingly.

Or embed the whole source code in your application and then when you are about to exit, recompile the code with the relevant information i.e. number of tries left or the remaining time for the app to run. This is easier said than done