Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!sri-spam!ames!ucbcad!zen!cory.Berkeley.EDU!herrmann
From: herrmann@cory.Berkeley.EDU (Conrad Herrmann)
Newsgroups: comp.sys.amiga
Subject: Re: Copy protection: A marketing analysis
Message-ID: <3100@zen.berkeley.edu>
Date: Thu, 23-Jul-87 19:42:45 EDT
Article-I.D.: zen.3100
Posted: Thu Jul 23 19:42:45 1987
Date-Received: Sat, 25-Jul-87 09:25:04 EDT
References: <207@cc5.bbn.com.BBN.COM> <892@omepd> <1393@mit-amt.MEDIA.MIT.EDU> <575@hplabsz.HPL.HP.COM> <1756@batcomputer.tn.cornell.edu>
Sender: news@zen.berkeley.edu
Reply-To: herrmann@cory.Berkeley.EDU.UUCP (Conrad Herrmann)
Distribution: na
Organization: University of California, Berkeley
Lines: 16
Keywords: ID code can be good, networks

In article <1756@batcomputer.tn.cornell.edu> kagle@tcgould.tn.cornell.edu (Jonathan C. Kagle) writes:
[problems with ID code systems, such as system replacement]

On the other hand, when I was working for a large Massachussetts
workstation manufacturer that _had_ taken this approach (still does!),
it allowed us to keep all sorts of programs on the corporate network 
on disk servers somewhere, and the program would look up your workstation's
ID in an encrypted user list in order to let you use it.  That way,
we didn't have to worry about installation, upgrades, or anything.  It
was done for us on the server.  Also, if we _did_ have our own copy
of the program (a WYSIWIG word processor), it would look for our
workstation's user permission in the *network's* user list.
So, I think that these ideas are very useful when you're dealing with
a well-integrated networked environment, if not in a home computer.
	Conrad
	herrmann@cory