Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site osu-eddie.UUCP
Path: utzoo!watmath!clyde!cbosgd!osu-eddie!julian
From: julian@osu-eddie.UUCP (Julian Gomez)
Newsgroups: net.micro.mac
Subject: Re: Re: copy protection
Message-ID: <885@osu-eddie.UUCP>
Date: Sun, 24-Nov-85 22:58:27 EST
Article-I.D.: osu-eddi.885
Posted: Sun Nov 24 22:58:27 1985
Date-Received: Tue, 26-Nov-85 07:44:23 EST
References: <1204@jhunix.UUCP> <763@bbnccv.UUCP> <11016@ucbvax.BERKELEY.EDU> <1002@security.UUCP>
Distribution: net
Organization: Ohio State Univ., CIS Dept., Cols, Oh.
Lines: 21

>      An ideal form of copy protection is possible if each machine has a
> serial number that is readable by software (e.g., stored in ROM).  When
> a program is sold, it comes in a form that is uncopyable, but as soon as
> it runs on a machine, two things happen: (1) it "freezes" on that machine,
> that is, it will run only on the machine with that serial number; and (2)
> it becomes copyable.
>      If the customer gets a new machine, he should be able to send the
> original disk back to the vendor (as proof of purchase) and get a new
> unfrozen disk for a nominal charge.

What happens if the customer's Mac goes down and he has to get a loaner
for a while? What about a customer who has more than one Mac and buys a
2nd CPU license, which usually means the customer doesn't get another
distribution kit?  (although i have yet to see more than one Mac in the
same room anywhere besides a dealer)
-- 
"If Chaos himself sat umpire, what better could he do?"

	Julian "a tribble took it" Gomez
	Computer Graphics Research Group, The Ohio State University
	{ucbvax,decvax}!cbosg!osu-eddie!julian