Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!uvaarpa!virginia!uvacs!edison!mfs
From: mfs@edison.GE.COM (Martin Sant)
Newsgroups: comp.sys.cbm
Subject: Copy protection; How do I do it
Message-ID: <1235@edison.GE.COM>
Date: Fri, 20-Nov-87 10:14:59 EST
Article-I.D.: edison.1235
Posted: Fri Nov 20 10:14:59 1987
Date-Received: Tue, 24-Nov-87 04:50:06 EST
Organization: General Electric Company, Charlottesville, VA
Lines: 30
Keywords: pirates, lost income, money


I am planning to release a music software program for the C-64 soon
and was wondering if there was a reasonable way to guard against
rippoffs.  From conversations with previous customers, some are
rather blatant about the fact that they have every piece of music
software that will run on the C-64.   As I see it, I have a 
couple of choices:

   1)  Release it unprotected and hope most people are honest.

   2)  Release it unprotected and accept that software follows
       the 'spurt' mode, i.e. high initial sales, slacking off
       as the program (bootleg copies) become more available.

   3)  Include some type of disk protection scheme that would
       make it harder for folks to make copies.

   4)  Fashion some type of hardware dongle and include it with the
       program.

   5)  The 'shame' route.  Customize each disk with the name of the
       person who bought it (easy for me since I distribute my own
       stuff).

Yeah, I know, most of youse guys don't like copy protection; I don't
either.  But programmers have to eat too.  Anybody got any suggestions ?
-- 
Mar Tan          
GE Fanuc         
Charlottesville, VA