On Feb 06, 2007, at 9:12 AM, Art Peters wrote:

All,

First, losing the List is really going to hurt me.

My question: Can anyone suggest a way or have a code snippet to obtain a (relatively) unique identification of a Windows machine? I have tried wading through msdn stuff but it is way over my head.

I am looking for some information that will remain relatively consistent and apply to the physical computer. One suggestion was to look at several environment variables and match at least two of them to those of the originally licensed machine.

My problem is that I could not find a list of the env variable names - and have never applied declares - and don't have any idea of the returned data structure. (Although, I believe I can master declares after obtaining Charles' book.)

Does the RB system.environment class access Windows machines? Would this be a good place to start?


Further replies will be directed to [EMAIL PROTECTED] so if you have not subscribed there do so
These lists will be shut down in a few days

You might look into the Windows Functionality Suite that has a lot of Windows functions in it already that may help you
That said, be careful about trying to uniquely identify a machine
Many items can be replaced or spoofed
MAC addresses from Ethernet cards can be spoofed, and HD's can be reformatted so the volume numbers get changed
Combining several items like this may help
I'm not 100% sure what Windows does to decide if IT is running on the same machine but there is a limit to what you can change before even it decides you need a new license as it's a "different" machine

_______________________________________________
Unsubscribe:
<[EMAIL PROTECTED]>

REAL Software has decided to consolidate this mailing list with the online Forums.  
On Monday, February 12, 2007, this mailing list will no longer be active.  We 
encourage you to continue your REALbasic and REAL SQL Server discussions on the 
Forums.  If you are not presently a member of the forum, please sign up today at 
<http://forums.realsoftware.com>.

Reply via email to