🚀 go-pugleaf

In article <1992Dec17.230932.16643@jarvis.csri.toronto.edu>  
ematias@dgp.toronto.edu (Edgar Matias) writes:
> 
> A thread is just starting up on comp.sys.mac.programmer on the idea of
> using a computer's serial number embedded in a ROM chip as a means of
> uniquely identifying a given computer.  This could easily be used in
> a copy protection scheme.  I'm told NeXT computers work that way and
> I wonder what all of you think of this kind of copy protection?
> 
> Does is work well?  Is it annoying when machine servicing is required?
> Is the chip soldered to the board?  What do you all think?
> 
> I think it's a pretty good idea and could solve a lot of problems in
> the software industry.  I seem to be one of the few people in
> comp.sys.mac.programmer who thinks so.  What have been your
> experiences?
> 
> Thanks,
> Edgar
> -- 
> Edgar Matias
> Input Research Group
> University of Toronto
> --
> I speak for no one...

As a system administrator as well as a developer the difficulty of maintaining  
licenses at the individual machine level is VERY annoying.  For the system  
administrator all the issues around repairs and swapping out a defective slab  
for a working one, and so on, is complicated by machine specific licenses.  For  
the developer they get all the calls from the administrator needing new  
licenses to match the musical machines being done.  The MUCH preferable  
solution is floating licenses ala OTProvide.  For those worried about stand  
alone machines copying the software: as an administrator I would prefer some  
kind of plug in key off the serial port to being tied to a motherboard serial  
number.

That is my two cents.

-- 
Michael Allen Latta
Kripalu Center
harit@kripalu.com
(413)448-3288