Code to retrieve.....

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have used code which retrieves the User and Computer names. I am looking to
retrieve something more permanent which cannot be changed by the user, (to
be used in preventing the application from being copied to another computer).

Any suggestions?
 
When a hard disk is formatted a serial number is assigned to it by the
operating system. This site explains how to retrieve it:

http://www.allapi.net/tips/tip030.shtml

I understand your desire to keep someone from installing more copies of your
software than they have a license for, but how do you purpose dealing with
the end user's legitimate right to place the db on another machine? Machines
suffer system failures, and users upgrade all the time.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000

Message posted via AccessMonster.com
 
Tom said:
I have used code which retrieves the User and Computer names. I am looking to
retrieve something more permanent which cannot be changed by the user, (to
be used in preventing the application from being copied to another computer).

Any suggestions?
Click to expand...

Disk serial numbers aren't unique but it may be unlikely to find a match.

The usual sources are the MAC address of an installed network card which is
(supposed to be) unique. Which, of course, requires the PC to have a network
card.

These are the two most commonly used identifiers.

Here's a site that should interest you:

http://www.activelock.com/

The question is how much work is it worth to implement a protection scheme?
 
"Disk serial numbers aren't unique..." The link above states this, but as the
serial number is a 32 bit integer, it not only "may be unlikely to find a
match" but the possibilty is on par with a camel passing thru the eye of a
needle!

"The question is how much work is it worth to implement a protection scheme?"
is a very valid point, John, as well as my question about dealing with the
legitimate transfer of the app to another machine.

BTW, have you actually used ActiveLock?
 
missinglinq said:
"Disk serial numbers aren't unique..." The link above states this, but as the
serial number is a 32 bit integer, it not only "may be unlikely to find a
match" but the possibilty is on par with a camel passing thru the eye of a
needle!

"The question is how much work is it worth to implement a protection scheme?"
is a very valid point, John, as well as my question about dealing with the
legitimate transfer of the app to another machine.
Click to expand...

No. But I did, regretably, develop my own package. Some of the concepts I used are found
in that project but there are also things I did differently.

I say regrettably because I don't think it is a good use of my client's money but they
insist. I try to mitigate the development cost against the potential loss of revenue.

My disk serial number comment is nit-picking considering MAC addresses can be set by
users; I didn't mean it wasn't a valid identifier - I should have explained why the entire
concept is suspect.

A knowledgeable person can bypass most software-protection setups (just look at the gaming
software world) and thus my "at what cost" question.
 
Thank you both. I have found all I need. I am using a combination of the
Serial Number, User Name and Computer Name - this is unlikely to be
duplicated.

With regard to the question of effort vs security, I would agree that any
system can be bypassed. I am relying on an assumption that those buying the
application could develop it themeselves if they had the skills to bypass the
security :).

For info, securiity on the FE includes activation based on machine
identification, MDE and "Project Locked for viewing". It is primarily the
unauthorised copies I am aiming to prevent with this question. Should anyone
succeed, "'tis a time for giving", but the application will always have my
mark on the forms and reports (MDE).

Thanks again.
 
And how are you addressing the end user's legitimate right to transfer the
app to another machine, Tom?
 
Tom Ventouris said:
As a last resort, we might consider selling
the product to the machine, as opposed to
the end user, without the "legitmate right to
transfer", but this will not do, will it? - MLA
to replace EULA?, there's a thought - :)
Click to expand...

It wouldn't do for me, no.

If there were any alternative to a program licensed to a particular machine
with no "right to transfer", I wouldn't use that product. And, there's
(almost) always _some_ alternative.

You can be assured that the more complex and difficult your solution makes
life for your customer, the harder they will search for an alternative, and,
from my POV, licensing to a machine is high on the "complex and difficult"
list.

Larry Linson
Microsoft Access MVP
 
As a last resort, we might consider selling the product to the machine, as
opposed to the end user, without the "legitmate right to transfer", but this
will not do, will it? - MLA to replace EULA?, there's a thought - :)
Click to expand...

We're already there, aren't we? AFAIK Microsoft OEM licences can only
legitimately be used on the computer they were sold with.
 
Back
Top