>In an effort to implement some sort of copy protection, I am currently registering the Computer Name
>(using SYS(0) or GETENV() functions).. But that's kind of rudimentary. It can easily be changed.
>
>Is there a better way in VFP to retrieve some sort of Hardware or Windows Serial number?
>I will even settle for Network WorkGroup, or anything else that's unique for a given computer.

Have you actually encountered cases where someone's changed their machine's NetBIOS name to get around your copy protection? Yes, it can be done but it breaks a ton of other stuff someone may have already set up on their computer - basically a PITA. That's why I ask if you've ever seen it happen, or whether you've just heard that it's possible.

I see you've gotten pointers to various hardware identifiers. That's all well and good but if your software gets installed on a VM, someone can distribute the entire VM to get around any such copy protection. Running "legacy" apps in VMs is more and more common, especially as UI evolves on newer versions of Windows and if/when those versions no longer support Win32 well enough for VFP.

If your app is high-value you should consider that any hardware based protection you try to use is already defeated by the use of a VM, and use something else.