Re[2]: Activation Limit Exceeded with Voyager

2006-10-20 Thread Steven P Vallière
Thomas,

Friday, October 20, 2006, 11:20:15 AM, you wrote:

RW Do the reverse when you get home.

TF Or: When using Voyager, BCC to yourself, and leave the
TF messages on the server. When you get back home, just
TF download the messages as usual.

That's often three to four hundred messages PER DAY.
Not sure I want to download two to three THOUSAND
messages a second time -- especially since most are
SPAM.

-- 
Steve Vallière  | mailto:[EMAIL PROTECTED]




 Current ALPHA is 3.86.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/


Re[2]: Activation Limit Exceeded with Voyager

2006-10-16 Thread Vili
Hello Krzysztof,

 That  means  that  the  same  key  was  used  to activate Voyager 5(?)
 Yes.
 times... It can be an _indication_ of software piracy.
 I know It's probably reason to make this limitation.
 Contact Ritlabs and explain the situation asking to extend the
 activation number...
 Hmmm  ...  that's  right,  but  it  takes  time  and  depands  on  manual
 intervention of RITs... very uncomfortable.

What  is  uncomfortable  in  it?  If you should go and mine rock, that
would be uncomfortable, I think :)))

You have used up your 5 chances. It is also uncomfortable for Ritlabs.
But  if  you  know  a better way to handle users who activates Voyager
more  than  5 times, please explain that. I dont...

-- 
Vili
The Bat 3.86.03 ALPHA (beta) on Windows XP 5.1 2600 Szervizcsomag 2



 Current ALPHA is 3.86.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/


Re[2]: Activation Limit Exceeded with Voyager

2006-10-16 Thread Vili
Hello Krzysztof,

 What  is  uncomfortable  in  it?
 Necessity to make a plenty of manual intervetions - first: user must
 send  a message with description, next RITs must evaluate this, next
 RITs  must  reset 'counter' per user to offer next activation. More:
 RITs  must have very detailed database per every sold Voyager. More:
 user  BEFORE  buying  should  be  warned  about  this  very  crucial
 limitation  etc.  More:  let's suppose failure of RITs database with
 counters.  More: let's suppose - some lazy guy in RITs who refuse to
 reset counter for days... etc. Should be enough, don't you think?

If Ritlabs saves with it on software piracy, it is worth doing it. The
Bat!  codes  came  up on the internet, I am glad they start to protect
their intellectual property.

Before  anybody  reminds  me  that  I am a TB dealer: it does not have
anything to do with it. It does not make any change in our income.

It does have more with my (professional) hobby, software writing. Many
people  forgets  that it is a job. E.g. plumber came, I had to pay for
him  fixing  the  sink. Ah, you are a programmer It took me more
time  to  fix  his PC than to fix my sink, and he was surprised when I
gave  him  a bill, and not working free... (Same amount he has charged
to  repair  the  sink..)  Show me another job nowadays that gives that
many free stuff away than programming...

Sorry, if you feel it is OT, I just wanted to protect Ritlabs point of
view.  However,  I have to agree with you and I do it myself: I remind
TB! Prof buyers that Voyager has a limited activation number.

PS.:  If you use up your 5 chances, I think RL can ask you without any
prejudgment, to give them the explanation about the 5 licenses. (Other
software companies draw the line at 3 license normally... or 1.)

-- 
Vili




 Current ALPHA is 3.86.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/


Re[2]: Activation Limit Exceeded with Voyager

2006-10-16 Thread Vili
Hello Thomas,

 What  is  uncomfortable  in  it?
KK Necessity  to make a plenty of manual intervetions - first: user must send
 [...]
 I think I'm with Vili on this one. A limitation makes sense. The
 question is whether 5 is enough. A registered user of TB Pro can use
 Voyager on five USB sticks. I don't know the market out there - Do
 people usually need more?

See from another viewpont: 1 USB stick at a time, and you can ask 5
licenses because:
- deinstalled, reinstalled
- FLASH broke down, reinstall on another one
- dog ate FLASH, reinstall on another one
- FLASH fall into fish tank, reinstall on another one
etc.

The
- Mom use it
- Dad use it
- Sis use it
- Bro use it
- I use it
and now the dog would like to use it... ehhh... this would not be a
good excuse for me to give the user a 6th license :))

If  it  adds  something  to  the  statistics:  no  Hungarian user ever
reported  to  me  that  they  used up the 5 licenses... Not even small
companies with 1-user license purchased...

Believe me, Ritlabs has a very liberal licensing scheme.

-- 
Vili



 Current ALPHA is 3.86.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/


Re[2]: Activation Limit Exceeded with Voyager

2006-10-16 Thread Vili
Hello Thomas,

  A limitation makes sense.
KK No doubt, it makes sens. I don't deny it. I only suggest two ponits:
KK a.  users  of  Voyager  should  be warned about the limitation before they
KK download software;
 I agree, I myself wasn't aware of this limitation until it came up in
 this thread.

I agree with Krzysztof also. Online users should be warned PRIOR the sale.

KK b.  RITs  sould  provide  some  explicit  and  user-friendy  procedure  of
KK extending limitation in question.
 That's a problem. If it is too easy, piracy would be rampant.
KK None of above is satisfied now.
 It's always a compromise.

Agree.

-- 
Vili



 Current ALPHA is 3.86.03 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/