Xref: utzoo comp.sys.mac.programmer:21123 comp.protocols.appletalk:5183 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu From: awessels@ccwf.cc.utexas.edu (Allen Wessels) Newsgroups: comp.sys.mac.programmer,comp.protocols.appletalk Subject: Re: Idea for painless copy protection Message-ID: <43375@ut-emx.uucp> Date: 29 Jan 91 16:59:37 GMT References: <3845@uakari.primate.wisc.edu> Sender: news@ut-emx.uucp Reply-To: awessels@ccwf.cc.utexas.edu (Allen Wessels) Followup-To: comp.sys.mac.programmer Distribution: na Organization: The University of Texas at Austin Lines: 12 In article tosh!starta@asuvax.eas.asu.edu (John Starta) writes: >I don't think your example is suitable for your response. The reason I say >this is that if you maintain a hundred, or even a dozen machines you should >have a profile of each machine. Having to note an additional serial number >is nothing if you maintain reasonable records. And doing so only makes >your job easier in the long run. This really isn't very practical unless you have an automated system for doing the profile building, preferable via a network software package. The more machines you have the more likely people are to dink with the System setup. If you start locking out changes, you are likely to have even more trouble.