Xref: utzoo comp.sys.mac.programmer:21107 comp.protocols.appletalk:5176 Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!uokmax!d.cs.okstate.edu!unx2.ucc.okstate.edu!minich From: minich@unx2.ucc.okstate.edu (Robert Minich) Newsgroups: comp.sys.mac.programmer,comp.protocols.appletalk Subject: Re: Idea for painless copy protection Message-ID: <1991Jan29.034918.6422@unx2.ucc.okstate.edu> Date: 29 Jan 91 03:49:18 GMT References: <1991Jan28.202316@Informatik.TU-Muenchen.DE> Organization: Oklahoma State University Computer Center Lines: 23 by breidenb@Informatik.TU-Muenchen.DE (Oliver Breidenbach): | severeal people mentioned one problem, that is tracking down the offender | when finding that someone already uses my copy. | Actually that is very very easy. Get yourself a traffic watch program | and you can see the peoples names, the nodes number, the serial number of | the programm using that copy protection mode and so on. Then simply look | for the node where your program runs, rememeber the node number and | search for some entry telling you the name or position (whatever name you | give in the chooser). Then all you have to do is to place a lot of flames | on the person who stole your program. Better yet, put in a little routine in the program to answer to copies in a way that is visible to the legal user. I like the idea of a notification manager dohickey that would put a nasty sicn in the apple menu so that you could walk around and look over other's shoulders. Or maybe an audible ping that goes off at a specified offset. Synchronise your watches and look for the confused face! Or.... or... Just knowing a machine name or node number may not tell you much, especially on a medium size net. -- |_ /| | Robert Minich | |\'o.O' | Oklahoma State University| "I'm not discouraging others from using |=(___)= | minich@d.cs.okstate.edu | their power of the pen, but mine will | U | - "Ackphtth" | continue to do the crossword." M. Ho