Twonky Forum

I've been running TMS (4.x, then 5.0beta1) on my ClarkConnect server since Jan 2008 and think I have managed to block my license key during a recent OS upgrade as I ran through the process on a VM image of my server first, and Twonky now reports it as being used on multiple machines.

I think I did something similar about a year ago as well when I upgraded the server hardware and had the new machine running in parallel and had to swap NICs around as well so should've remembered really...

Raised a ticket to get this reset last Saturday but have heard nothing so far apart from the automated ticket details coming back. What's the typical turnaround for support these days, or is there a different route I should have taken?

As a workaround, and opportunity to upgrade, I've installed the 5.0.68 version as a 30 day trial but have since read that I might need a new key for that unless I paid for a lifetime license. I can't remember what type of license I bought, or even whether lifetime ones were still available in Jan 2008 - can I check this somehow, or would it be a matter of firing another request off into the black hole that is support? Don't mind paying a small upgrade fee anyway, but don't want to unnecessarily.

I appreciate this was an issue of my own making, but just want to get it resolved.

Mark.

Have you tried this?

http://www.twonkyforum.com/viewtopic.ph ... 027#p14027

Thanks. I did notice the lost license key link, but haven't tried it as I know what it is - are you suggesting it resets the usage information as well (ie. the multiple machine issue), because if so I'll give it a go...

Mark.

Sorry, I was being vague. It does noe reset the usage count, but it might tell you what type of licence you have.

I was under the understanding that when you stopped using licenses they got freed up..
Unfortunately right now, most of mainland Europe is on holiday, so support might be slow to respond.

Well, I tried the lost license code facility which confirmed my code, but not license type. I guess I'll either wait for support or just go with the 5.x upgrade (if not too much) and hope the new license key has no usage recorded against it (as you would expect)...

Mark.