🚀 go-pugleaf

 +---- mjr@clark.net wrote (27 Mar 1996 11:16:19 -0500):
 | Larry Motylinski <larry@pronet.mpro.net> wrote:
 | >What I used to do is read the CMOS and other eproms (looking for a
 | >serial number or something that made it unique) and then encrypt that
 | >code in a program.  The program (when run) would verify this
 | >information.  It kinda sucks because you will be the one to get a call
 | >if they change their hardware.
 | 
 | 	And if the system is a hospital's database, or something
 | mission critical and life-threatening, and they change their
 | hardware, you'll get a call from their lawyers if it was your
 | stupid copy protect that caused downtime. Think carefully before
 | you do something that will put your customers out of business
 | as a means of protecting your software against them!
 +----

I have a fuzzy memory of cripple tactics like the above being
illegal.  But it might have been specific to consultants and
time bombs (used to ensure a clients timely accounts payable).

-- 
Gary Johnson     "I'd a done sumpin too, but I ain't no Peckerton Ditinctive."
gjohnson@season.com
                            CAMPAIGN '96: Juck 'em if they can't fake a toke.