Posted 22 November 2009 - 08:20 AM
Hi, I don’t think so about this matter. I’ve read about the “high end services”, since 1990. You know, they are programs applied to other dedicated software. I mean, you have a program with abilities to trade in stock exchange, and it is so good that you decided to sell it to people use it in their trades. Well, nobody wants spent money in such a program whose abilities doesn’t know very well. So, my way is to give permission to this guy to download my program, in order to test it, during a certain amount of time. Ended this time (time that is counted and accumulated – this is the central point), the guy has to pay for continuing to use my service or my embedded auxiliary counter program will block his access to the platform.
I’d search “high end service” at Wikipedia, and read interesting ideas concerning run time, just applied to these attached programs, made to control the time elapsed from the initial download of a demo license until its expiration. I know such programs are downloaded (or created) in the machine data register HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services and then they can be used to measure “accumulative run time”. Logically, they are full of encrypt keys to avoid crackers and so on. Well, here our points of view differ a little bit, first because I’m trying “to open” these embedded programs (that contain the information about to count run time) just to inhibit the counter, and second because you are interested into create one dedicated to “only” count machine “accumulative run time”.
I don’t know write program language, but it seems to me that we are treating the opposite faces of the same coin… or not?! So, I conclude, there is a possibility to develop a program to measure accumulative run time.