Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!snorkelwacker.mit.edu!bloom-beacon!deccrl!news.crl.dec.com!shlump.nac.dec.com!rust.zso.dec.com!pa.dec.com!shodha.enet.dec.com!elvira!ridder
From: ridder@elvira.enet.dec.com (Hans Ridder)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Demo versions
Message-ID: <2438@shodha.enet.dec.com>
Date: 1 Feb 91 15:47:22 GMT
References: <91031.112859GHGAQA4@cc1.kuleuven.ac.be>
Sender: news@shodha.enet.dec.com
Organization: Digital Equipment Corporation, Customer Support Center
Lines: 26

In article <91031.112859GHGAQA4@cc1.kuleuven.ac.be> GHGAQA4@cc1.kuleuven.ac.be (Tyberghein Jorrit) writes:
>It is very easy to make a demo version of an editor, simply remove the
>'save' option and the problem is useles while you still can test the
>power of the editor (look at the TurboText demo). But my debugger simply
>does not have a 'save' command....

How about disabling the 'load' command (if it has one), and have a built
in program with a bug in it (causes a Guru or some such).  Then only
allow that program, and maybe a few other places in memory to be
examined/modified/traced, like the task structure for the "broken" task,
and some system structures....  When the user trys to examine an area
outside of the boundaries, give a nice error message about buying the
non-demo version.

Of course someone could use another debugger to "fix" your debugger,
possibly allowing full or nearly full functionality, but there's some
level of risk you're going to have take to get the benefit of the
publicity of the demo.

>        Jorrit Tyberghein

-hans
------------------------------------------------------------------------
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO