One solution to this that I've thought of (but never implemented) is this:
* Set a preference with your creator id keeping track of the information.
* Set a feature (using FtrSet) with the same information.
When the app is deleted, the preferences will automatically be deleted
(since they share the creator id with the app).
Each time the device is reset, the feature will be cleared.
If you boot up and the feature is present, but the preferences aren't, you
know that the user deleted and then reinstalled. If you boot up and the
preferences are present but the feature isn't, just recreate the feature.
Properties of this solution:
1. If the user tries to reinstall and doesn't reset the device between
deleting and reinstalling, you will detect the attempt.
2. The trash left on the device is very minimal and is cleaned up
automatically when the user next resets.
3. If the user wants to try your program again somewhere down the road
(which I've wanted to do before), they're able to (assuming
they've reset between attempts).
4. This won't stop determined hackers, but can you stop them anyway?
Anyway, I'm not advocating trial periods (personally, I dislike them), but
if you're going to use them, this might be a decent solution.
---
On Mon, 20 Dec 1999, Rubin, Dan wrote:
> Brian,
>
> I don't want to start a war, but let me tell you where I am coming from...
> Basically, I am spending the time to make a useful app that I think would
> benefit others. I have purchased several shareware apps that make my life
> easier. Occasionally, I download something that I think will be useful. Of
> course, I won't purchase it at download time because I want to make sure it
> is worth the asking price and even works at all. I end up deleting most
> shareware apps that I download because they don't work very well or don't do
> what I had hoped. A few shareware apps work very well but to be honest
> unless that app reminds me or inconveniences me I will not register it. I
> have too many things to do to keep track of what I installed 30 days ago
> etc. to adhere to shareware agreements. I don't mind a warning window. Out
> of the 6 palm apps I purchased this year I did it because of a warning or
> built it inconvenience.
>
> So without "polluting the entire world's devices" is there a clean way to do
> this?
>
> Thanks
> - Dan
>
> > -----Original Message-----
> > From: Brian Mathis [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, December 20, 1999 3:30 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Persistant data storage for registration purposes?
> >
> >
> > On Mon, 20 Dec 1999, Rubin, Dan wrote:
> > > Hi All,
> > >
> > > What is the best way to store persistant data in a way that
> > it does not get
> > > removed if the application that creates/uses the data is removed and
> > > re-installed. I would like to store something like an
> > integer etc... that
> > > would be used for registration purposes (to keep track of
> > how many times the
> > > app is started etc...)
> > >
> > > Thanks for any tips...
> > > - Dan
> >
> > This has been hashed out before, but basically, here's my
> > feeling. Your
> > app isn't important enough to me to let you store stuff that I can't
> > remove from my device. I don't care if it's the coolest, newest, most
> > amazing thing in the world. The people who are going to pay
> > will pay, and
> > those who don't want to, won't. The minescule amount of $$
> > you might not
> > receive is not worth polluting the entire world's devices.
> >
> > --
> > Brian Mathis
> > Direct Edge
> > http://www.directedge.com
> >
> >
>
