On Apr 24, 2012, at 9:11 AM, J. Landman Gay wrote:
> On 4/24/12 10:08 AM, Paul Dupuis wrote:
>
>> However, I'd agree with Richard Gaskin's post that a feature limited
>> demo is generally a better marketing approach than a time limited demo.
>
> I think so too. Or even just make the program slig
Yeah CCC has saved my buttocks a few times, and I use it a lot, so I "donated"
a few times already.
Bob
On Apr 26, 2012, at 1:23 AM, Kay C Lan wrote:
> On Wed, Apr 25, 2012 at 12:11 AM, J. Landman Gay
> wrote:
>
>> Graphic Converter does that and its author has been supporting himself for
>>
My approach to buying shareware is if I try something and it helps me do
something I need to do, I go buy it, even if I do not need to do that thing
again. It's a matter of integrity to me. I think there are a lot of people like
that, but I know there are also a lot of other people who think if
On Wed, Apr 25, 2012 at 12:11 AM, J. Landman Gay
wrote:
> Graphic Converter does that and its author has been supporting himself for
> years with it, it's hugely popular. It isn't limited in any way.
>
> I don't know that Mike Bombich supports himself off the 'donations' to
Carbon Copy Cloner, but
Richmond,
I don't know what your program does but if it allows the user to store data you
could embed the timestamp in the data.
This is what I do with InfoWallet. The program InfoWallet itself isn't really
timestamped but data files it creates are. When the datafile is created it gets
a date
Jacque-
Tuesday, April 24, 2012, 9:11:08 AM, you wrote:
> I think so too. Or even just make the program slightly annoying during
> launch. Graphic Converter does that and its author has been supporting
> himself for years with it, it's hugely popular. It isn't limited in any
> way. He just insert
Hi from Beautiful Brittany,
OK, so we wandered off the subject just a little !
Jecqueline wrote, talking about Graphic Converter :
He just inserts a 10 second wait after every launch before the
program
becomes useable. Like most people, I used the free version for a
couple of
years until th
On Apr 25, 2012, at 4:16 AM, Kay C Lan wrote:
> I agree with the others though, I despise time limited apps because I never
> have 30 days to test them, I only have a day here and a day there and I spend
> half of it recapping what I learnt before.
Maybe the proper solution is a number of uses,
On Wed, Apr 25, 2012 at 12:11 AM, J. Landman Gay
wrote:
> He just inserts a 10 second wait after every launch before the program
> becomes useable. Like most people, I used the free version for a couple of
> years until the ten seconds got so annoying I paid up. I've been paying for
> updates ever
On 04/24/2012 07:11 PM, J. Landman Gay wrote:
On 4/24/12 10:08 AM, Paul Dupuis wrote:
However, I'd agree with Richard Gaskin's post that a feature limited
demo is generally a better marketing approach than a time limited demo.
I think so too. Or even just make the program slightly annoying du
On 4/24/12 10:08 AM, Paul Dupuis wrote:
However, I'd agree with Richard Gaskin's post that a feature limited
demo is generally a better marketing approach than a time limited demo.
I think so too. Or even just make the program slightly annoying during
launch. Graphic Converter does that and i
On 4/24/2012 8:36 AM, Richmond wrote:
> On 24/04/12 04:04, Kay C Lan wrote:
>> On Mon, Apr 23, 2012 at 4:45 PM,
>> Richmondwrote:
>>
>>> Blast! I am trying to find a way so that I don't have a file "floating
>>> about" on somebody's system that they can just flush away to
>>> reset the 30 day limit
Hi Richmond,
I just went through this same thought process. I have a 30 day and
functionality limits in my product but finally accepted that it's
impossible to make them foolproof. In my case, I.m selling a $25 product so
it doesn't make sense to spend huge amounts of time to foil the efforts of
a
Richmond wrote:
Blast! I am trying to find a way so that I don't have a file "floating
about" on somebody's system that they can just flush away to
reset the 30 day limit on my DEMO.
Have you considered a non-expiring feature-limited demo instead?
Time-limited trials not only are they harder t
On 24/04/12 04:04, Kay C Lan wrote:
On Mon, Apr 23, 2012 at 4:45 PM, Richmondwrote:
Blast! I am trying to find a way so that I don't have a file "floating
about" on somebody's system that they can just flush away to
reset the 30 day limit on my DEMO.
I'm assuming then you must have some sort
On Mon, Apr 23, 2012 at 4:45 PM, Richmond wrote:
>
> Blast! I am trying to find a way so that I don't have a file "floating
> about" on somebody's system that they can just flush away to
> reset the 30 day limit on my DEMO.
>
I'm assuming then you must have some sort of licensing system for those
Hi Francis,
Using software that keeps a list of all existing files, it is easy to find
newly created files. This way, it is very easy to find preferences files and
"secret" license files.
On the other hand, I believe that only very few people actually do this. Most
people just delete the softw
Hi from Beautiful Brittany,
Richmond wrote :
Blast! I am trying to find a way so that I don't have a file "floating
about" on somebody's system that they can just flush away to
reset the 30 day limit on my DEMO.
Richmond, forgive me if I am being obtuse, but I don't see the problem.
Create a
In the clouds, baby!
That presupposes that my target demographic are all connected,
permanently, to the internet; and they are not.
Richmond,
The best way to go is to call the DAZE30 function from your standalone and
compare it with a TSTAMP reference stored on the cloud so your customers w
On 04/23/2012 12:30 PM, Mark Schonewille wrote:
Hi,
Yes, it will.
I would use a time limitation using a separate file together with a functional
limitation, e.g. the inability to save documents. Actually, I rarely use time limitations
for my own products, because I believe that every time a u
Hi,
Yes, it will.
I would use a time limitation using a separate file together with a functional
limitation, e.g. the inability to save documents. Actually, I rarely use time
limitations for my own products, because I believe that every time a user
starts up your software is a potential sale.
On 04/23/2012 11:37 AM, Mark Schonewille wrote:
Hi Richmond,
Standalones can't write to themselves and thus your standalone can't save
anything in a substack. You can create a separate stack file in a different
folder, e.g. application data on Windows, Preferences on Mac OS X and the Home
fol
Richmond,
The best way to go is to call the DAZE30 function from your standalone and
compare it with a TSTAMP reference stored on the cloud so your customers won't
find any local file to delete to get a way to bypass your 30 days try-period
key.
HTH,
Le 23 avr. 2012 à 10:31, Richmond a écrit
On 04/23/2012 11:37 AM, Mark Schonewille wrote:
Hi Richmond,
Standalones can't write to themselves and thus your standalone can't save
anything in a substack. You can create a separate stack file in a different
folder, e.g. application data on Windows, Preferences on Mac OS X and the Home
fol
Hi Richmond,
Standalones can't write to themselves and thus your standalone can't save
anything in a substack. You can create a separate stack file in a different
folder, e.g. application data on Windows, Preferences on Mac OS X and the Home
folder on Linux and save time stamp in that stack fil
Um:
--30 Day code--
if the fld "STAMP" of stack "STAMP" is empty then
set the lockScreen to true
put the seconds into into fld "STAMP" of stack "STAMP"
save stack "STAMP"
set the lockScreen to false
end if
put the seconds into DAZE30
put fld "STAMP" of stack "STAMP" into TSTAMP
if D
Um:
--30 Day code--
if the fld "STAMP" of stack "STAMP" is empty then
set the lockScreen to true
put the seconds into into fld "STAMP" of stack "STAMP"
save stack "STAMP"
set the lockScreen to false
end if
put the seconds into DAZE30
put fld "STAMP" of stack "STAMP" into TSTAMP
if D
27 matches
Mail list logo
