I can think of a couple of ways to do this. For small volume applications you could hard code the expiration date into the application prior to the build. At startup you could then check for a valid reistration code (this could be coded into an ini file) and then, if not registered, perform the appropriate task depending on whether the period has expired. You may also want to check during operation (say, for instance, every hour) to prevent continued use of the program by leaving it running. You could put a button on the front panel which is active an visible only if the program is not registered to allow for writing the registration code.
The second way is to include the start data in the ini file and have the evaluation period hard coded. This method is l
ess secure, although you could invent an encryption style for the date. Otherwise implementation would be similar.
I'm not familiar with the 1way.dll software so I can't give you any guidance on how well that approach would work.
