SF Unlock Key/Machine Code policy?

ChrisG wrote on 11/20/2001, 3:23 PM

Hi there!

I have been very interested in VV since release 2. Now I think time
is there to really start working with it :-) . However, when evaluating
VV3beta I realized that there was an unlock-code generated in
dependancy of a machine code. Well, the problem now is, I upgrade my
hardware relatively often: a new harddrive here, a
mainboard/processor/memory upgrade then. Furthermore, thanks to
M$ there are periodic OS upgrades or patches. Now I really don't want
to buy VV all time it thinks it has a new user (i.e. changed hardware).
How/how often/how fast can I get a new unlock code for your software?
Sorry, but for professionals it isn't acceptable to wait days for
unlock codes just because a fast-to-replace piece of hardware has
just died.

Thank you for your answer in advance!

Regards,
Chris

Comments

dsanders wrote on 11/20/2001, 3:33 PM

Chris, I don't work for Sonic Foundry, but I have personally never found a problem with changing out hardware/software causing VV to stop functioning.

In several cases I have reinstalled windows (and thus VV2) and had to re-regestered VV2 many times (I wanted to try out various hardware configurations not releated to VV). After about 20 times, I finally got the online registration to fail - something about too many attempts being made to activate the software. One simple call to their tech support cleared things right up and I was able to register again.

In addition, I have VV on two different machines. I loaded it on my home machine and a laptop that I carry around with me. The registration process allowed me to activate it on both.

Just as a simple haha, most so called "Professional" programs require several days to turn around a license. Have to ever tried to license a UNIX operating system from Sun, or a graphics program from PV-WAVE?