Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!cbatt!ucbvax!dukeac.UUCP!bet From: bet@dukeac.UUCP.UUCP Newsgroups: mod.computers.vax Subject: Submission for mod-computers-vax Message-ID: <8702201110.AA04252@ecsvax> Date: Thu, 19-Feb-87 10:59:48 EST Article-I.D.: ecsvax.8702201110.AA04252 Posted: Thu Feb 19 10:59:48 1987 Date-Received: Sat, 21-Feb-87 05:56:56 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 30 Approved: info-vax@sri-kl.arpa Path: dukeac!bet From: bet@dukeac.UUCP (Bennett Todd) Newsgroups: mod.computers.vax Subject: Re: VAX SOFTWARE PROTECTION SCHEMES Message-ID: <366@dukeac.UUCP> Date: 19 Feb 87 15:59:47 GMT References: <8702180225.AA16886@ucbvax.Berkeley.EDU> Reply-To: bet@dukeac.UUCP (Bennett Todd) Distribution: net Organization: Duke User Services, Durham, NC Lines: 18 In article <8702180225.AA16886@ucbvax.Berkeley.EDU> writes: >If you really want a time limit, have the program print out some sort of com- >plaint every time it is run after the time limit expires. But still have it >work! SAS on IBM mainframes does exactly that, and rather cutely too -- after the time limit runs out, it starts flagging lines of user's programs at random as "fatal syntax errors" or some such, though it also proceeds to run the requested SAS program just fine; when the panic-struck user examines the message text below to find out what the error was, it tells them to contact their local User Services and inform them that the SAS contract has expired. It gets fixed *fast*. -Bennett -- Bennett Todd, Duke User Services, Durham, NC 27706-7756; +1 919 684 3695 UUCP: ...{philabs,akgua,decvax,ihnp4}!mcnc!ecsvax!dukeac!bet BITNET: DBTODD@TUCC