OtsAv users... a question?

To many ads? Support ODJT and see no ads!
Thanks, Papa.

I'm far from an expert. All I can offer is what I have heard from folks who've been involved in these matters.

As I understand, when you purchase a copy of software it doesn't matter what machine it's run on as long as it's only on one machine at a time. If you load it on a new or replacement machine, the old HDD copy is supposed to be removed or destroyed. The EULAs that come with software utilities cover this in more detail.

I'm sure Rick can tell you more. He writes the software.
 
Thanks, Papa.

I'm far from an expert. All I can offer is what I have heard from folks who've been involved in these matters.

As I understand, when you purchase a copy of software it doesn't matter what machine it's run on as long as it's only on one machine at a time. If you load it on a new or replacement machine, the old HDD copy is supposed to be removed or destroyed. The EULAs that come with software utilities cover this in more detail.

I'm sure Rick can tell you more. He writes the software.


Rick writes the OtsAV software? BTW, OtsAv is different. They only allow it to be placed on one machine. Not just used by one operator. One machine only, I believe.
 
:sqlaugh:

I'm not sure Chuck, but I think you might need to get a new code, if you switch it to another computer -- I think their code is based on a hardware hash (at least I think that's the way it worked).

PM Bry or Jumpin' Jeff, and they can probably give you the full scoop :)
 
Rick is correct. All you have to do is send Ots Labs an email explaining the situation and they'll make it so that you can get a new Machine License to use with your existing Product License on the new machine. And yeah, I'm pretty sure the Hardware License is some kind of hash based on the HD Serial Number/ID and maybe other stuff like BIOS and motherboard identifiers (if that's even possible).

Their response is very timely, considering that they're Down Under!
 
You can install the code on any number of machines, but each license can only have a single activation. You can't use the code if it isn't activated, and you can't legally activate it on more than a single instance per license, per machine.
 
You can install the code on any number of machines, but each license can only have a single activation. You can't use the code if it isn't activated, and you can't legally activate it on more than a single instance per license, per machine.



MY brain hurts now, Jeff.

It sounds like one activation per license, on a single machine only, correct?
 
Not exactly....

Sorry, it's complicated....

In my case, I have a set of 5 licenses belonging to a single PDI. I can run 5 instances of Ots on the same machine, or 5 licenses on 5 machines. You can also run 5 individeual licenses on the same machine should you want to, but what I was trying to say is that if you have only a single license, that one license can only be active on a single machine at any one moment. If you were to want to move it to another machine that already had the code installed, you could do so, but you may need to contact Ots if you get a code 220 error, meaning you have reached your current license limit. In order to make the transition to another machine, you would need to deactivate the license on the current machine, and then submit for the license on the new machine. If you get the error code 220 message, you will still be able to use the new machine if necessary by activating the temp 7 day license, that activates Ots albeit with a 1 minute delay. This 7 day license can be activatedon the machine just once, so don't waste it, as you would need to completely wipe and re-install everything on the OS drive to reset it to allow it to be used again.

Now your brain really hurts! right?
 
I forgot to mention that Rick is right also.

There are actually 2 licenses that make up your license.
A product license (the PDI), and a machine license.
The Product license allows you to use the software, and
the machine license is activated via the machine Hash that Rick indicates, and marries it to your machine for the duration that it is active.

to extend further, If you have a single license on a machine, you can't run multiple instances of the program on that machine as well.

It's basically a license for each instance you plan to run, no matter if on the same, or multiple machines.