Re: Using the serial # in ROM as a copy protection mechanism...?

Article View: comp.sys.next.programmer

Article #1944

Back to comp.sys.next.programmer Previous Next

#1944

From: Gordon Van Huizen
Date: Sun, 20 Dec 1992 17:53

20 lines
1290 bytes

In article <1gte4tINNs3r@ni.umd.edu> louie@sayshell.umd.edu (Louis A.  
Mamakos) writes:
> The approach that I like is to give the user some piece of
> information that needs to be supplied to enable the
> application.  This piece of information uniquely
> identified the *owner* of the software.  That way, if it
> gets "loose", you know who to trace it back to, and thus who
> violated the terms of the software license agreement.  

Does your software respond to a large number of different
keys? If not, how do you deal with the mass-duplication
issue? 

Gordon
 
-- 
----------------------------------------------------------------
Gordon Van Huizen           vox: 619.488.9411  fax: 619.488.3045
Metrosoft                   gvh@metrosoft.com [NeXTmail welcome]
----------------------------------------------------------------

Technical Details

Message-ID: <1992Dec20.175359.4500@metrosoft.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!psinntp!hd0258!gvh

References: <1gte4tINNs3r@ni.umd.edu>

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!psinntp!hd0258!gvh
From: gvh@metrosoft.com (Gordon Van Huizen)
Subject: Re: Using the serial # in ROM as a copy protection mechanism...?
Message-ID: <1992Dec20.175359.4500@metrosoft.com>
Sender: gvh@metrosoft.com
Reply-To: gvh@metrosoft.com (Gordon Van Huizen)
Organization: Metrosoft
References: <1gte4tINNs3r@ni.umd.edu>
Date: Sun, 20 Dec 1992 17:53:59 GMT
Lines: 20

Reply to Parent Message