Don't bother. All they have to do is install in a VM, or even in Wine. Then if they move the VM, or the Wine folder, the machine ID stays the same. So you don't achieve anything, all you do is annoy your less sophisticated customers, who will find someone who knows how to defeat it. But it gets worse.
The problem is, they will feel they have a legitimate need to be able to move their install from one physical machine to another. They will feel that a restriction to one particular machine, as opposed to one installation, is not fair. However, what you have then encouraged them to do, installing on a VM, gives them the ability to install as many copies as they want, wherever they want. Its counterproductive. Then, you'll start to think, maybe there is a way I can detect and ban VMs. And Wine. Yes, maybe. How will they see that? Will inability to run under Wine or in a VM seem to the customer like a value added feature? -- View this message in context: http://n4.nabble.com/Identifying-a-certain-Windows-machine-tp1742751p1744691.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution