I'm not sure if I understand. For them to be useable at all they
MUST be different! My registration method is an e-mail request and payment.
After payment is verified, I take this data which my app encrypts via an
in-source set of key const and then sends me in the e-mail, add an
additional set of data that is hidden elsewhere in the source, re-encrypt it
along with the app's CrC, and return as a license file. Now that license
file can only pass validation with that particular user's OS, and only if
the application itself hasn't been tampered with. Of course once registered
with a particular User's copy of the OS, any change to the OS or the use of
a new or different OS, will cause the reg check to fail. But then it only
requires the user to click the Registration button again so that a new
license file is created and sent. Since I keep a record of all clients and
registered apps in my own dB along with their CrC's and key const., I can
easily verify if the app was already registered previously and that I
needn't charge him again.
If the OS Product ID and/or GUID are the same when compared to these
values provided for the same OS but on a different machine and/or for a
different user, then this method wouldn't be any good at all! Now you said
that these values are indeed different for different versions of Windows on
the same machine. But what I really need to know is if they are different
for each one of multiple copies of installed and incensed OS's. That is, if
you and I are both using Vista Ultimate with all the same updates, etc., are
the Product IDs and GUIDs different on yours as they are for mine?
According to what I was told, every copy of a Windows OS that is sold,
installed, and registered, makes a registry entry of these two values, and
NEVER are they the same, even if two copies of the same OS are installed on
the same machine, for example on a separate HD, and/or are owned by the same
user! This is what I need to verify!
from "Robert Meek" dba "Tangentals Design"
Creative Concepts Programming for Windows Vista
E-mail: [email protected]
"...There no longer exists any communities...only special Interests." as
remarked by one Photojournalist and Writer in relation to the infamous
'Mapplethorp trial' of Cinncinate. I'm happy to know why this is true and
the protection it provides everyone from 1st amendment rights
violations...escpecially those in L.A. and Seattle!
As for New York, it's difficult to get worked up over a conglomerate of
special interests such as it represents, when opposition to every one and
every thing not their own has become its most apparent trait and appalling
attribute!
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Irwin Scollar
Sent: Friday, May 22, 2009 3:39 AM
To: [email protected]
Subject: Using license files
Robert Meek suggested using:
> My ProductID = 89580-006-5738705-71882
> My GUID = {0f694440-6a70-11db-8eb3-806e6f6e6963}
I tested this on a multi-OS machine with four versions of
Windows. The values are different for each OS. This appears not to
be a satisfactory solution if this is the case.
Solutions based on hardware serial numbers and/or MAC addresses can
cause problems if external plug-in disks are attached or if the
machine is not connected to a network which causes some versions of
Windows to assign an arbitrary MAC address.
Cameron Cole wrote:
>For the unique machine key we use the Windows Key, Hard Drive
Serial No and BIOS Manu name. Some people like to use >the computer
name and/or the MAC addresses for a machine.
If there is a disk crash or the customer has to re-install the
operating system, this can not be carried over to the repaired
machine without re-licensing, something which costs time and is
irritating for everyone involved.
A method which can be easily implemented if the customer uses a disk
clone and backup program like Acronis TI is needed.
Irwin Scollar
__________________________________________________
Delphi-Talk mailing list -> [email protected]
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi-talk
__________________________________________________
Delphi-Talk mailing list -> [email protected]
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi-talk
